File staging faults
Hi! Hopefully, this is the last thing that bothers me: 1. As far as I can see, there no such thing as an XML Schema for HPC File Staging Profile. Is that right? 2. Assuming that #1 is true, I'm preparing a schema for me to ease handling of the specified elements. The faults seem a bit unclear to me, though. What are their types? Are they all xsd:string? What about UnsupportedProtocolFault and DeleteOnTerminationFault from which description you can read that they could have a <File> subelement? Do they solely have this subelement or are they mixed-type so that they can contain both string and <File> subelement, e.g.: <DeleteOnTerminationFault> something bad happend <File>ftp://foo.com/bar.txt</File> </DeleteOnTerminationFault> Thanks for any clarifications! -- Piotr Domagalski
Hi Piotr, Sorry for the delay. It took us a little to look into this. (and vacations for various people made it difficult to connect at times) At the time, we did not publish any XSD for the file staging profile, essentially because all of the faults defined in it are optional and we believed that a single canonical XSD was not "necessary". But you raise some good points. In the hopes of lessening the general pain involved in interop, I am attaching XSD to this email for the file staging profile. Does this help? Will this particular XSD make it easier for you to build clients/services? Again, we're very sorry for the lateness. Please let us know if this helps! -- Marty -----Original Message----- From: ogsa-hpcp-wg-bounces@ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Piotr Domagalski Sent: Thursday, July 10, 2008 6:30 PM To: ogsa-hpcp-wg@ogf.org Subject: [ogsa-hpcp-wg] File staging faults Hi! Hopefully, this is the last thing that bothers me: 1. As far as I can see, there no such thing as an XML Schema for HPC File Staging Profile. Is that right? 2. Assuming that #1 is true, I'm preparing a schema for me to ease handling of the specified elements. The faults seem a bit unclear to me, though. What are their types? Are they all xsd:string? What about UnsupportedProtocolFault and DeleteOnTerminationFault from which description you can read that they could have a <File> subelement? Do they solely have this subelement or are they mixed-type so that they can contain both string and <File> subelement, e.g.: <DeleteOnTerminationFault> something bad happend <File>ftp://foo.com/bar.txt</File> </DeleteOnTerminationFault> Thanks for any clarifications! -- Piotr Domagalski -- ogsa-hpcp-wg mailing list ogsa-hpcp-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg
I am attaching XSD to this email for the file staging profile.
Also missing from this schema - but covered in the specification is a 'Credential' element type. This wraps up any authentication token provided by the user and is added into the JSDL data staging element using the extensibility mechanisms. Steven
2008/8/13 Marty Humphrey <humphrey@cs.virginia.edu>:
At the time, we did not publish any XSD for the file staging profile, essentially because all of the faults defined in it are optional and we believed that a single canonical XSD was not "necessary". But you raise some good points. In the hopes of lessening the general pain involved in interop, I am attaching XSD to this email for the file staging profile. Does this help? Will this particular XSD make it easier for you to build clients/services?
Yes, that helps and clarifies the faults. It would help to have this officialy published/attached to the spec. I'm still just wondering why not all faults have <File> element to indicate which particular file caused the problem... P.S. I also don't like mixed content in XML, but that's just my personal opinion ;-) -- Piotr Domagalski
participants (4)
-
Marty Humphrey -
Piotr Domagalski -
Piotr Domagalski -
Steven Newhouse