Hi; I will look into the question of what sorts of Windows-specific things might be appropriate for a WindowsApplicationType. I suspect that if we have a common ApplicationType that includes the things we've talked about then the WindowsApplicationType may be fairly small -- at least that's what I'm hoping for. :-) Marvin. -----Original Message----- From: Donal K. Fellows [mailto:donal.k.fellows@manchester.ac.uk] Sent: Thursday, June 08, 2006 5:49 AM To: Marvin Theimer Cc: A S McGough; ogsa-bes-wg@ggf.org; Ed Lassettre; JSDL Working Group Subject: Re: [ogsa-bes-wg] Questions and potential changes to BES, as seen from HPC Profile point-of-view Marvin Theimer wrote:
Currently the posix extension to jsdl includes various things that I would argue are more generic than posix. I think it would be interesting to define a common subset (that includes things execution pathname, command-line args, and working directory) as well as defining a WindowsApplicationType that describes those things that are Windows-specific.
I believe[*] it is possible to define a new element type that describes an abstract ExecutableApplication element with these generic bits in and which is grandfathered into being a supertype of the POSIXApplication element (as well as being the parent of the WindowsApplication you're positing). This would require a small change to the existing schema, though we'd want to make sure that the documents accepted by the schema remained the same, and would enable this suggestion (which I approve of, by the way) to be slotted into the larger scheme of things without fuss. By the way, what would these extra Windows-specific bits be? I can imagine a number of the POSIX things being dropped (e.g. the limits) but I'm not nearly well-versed enough on Win (despite using it a lot) to be able to think what these extra additions might be. Just out of curiosity! :-) Donal. [* This is believe as in "I've done this sort of thing in other schemas" so I know that XML Schema can support it. ]