- jsdl-wg - lists.ogf.org

RE: [jsdl-wg] Any JSDL parser around
by Vivian Li 15 Apr '05

15 Apr '05

Hi, Try if this works? <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions name="xxx" targetNamespace="http://xxx" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" <wsdl:types> <xsd:schema targetNamespace="http://xxx"> <xsd:include schemaLocation="xxx/jsdl.xsd"/> </xsd:schema> </wsdl:types> </wsdl:definitions> name the above codes into xxx.wsdl, then pass to Axis. you need to replace xxx with proper ones. You could also give it a package name where you want the classes to be generated when you tool it. Regards, Vivian > -----Original Message----- > From: owner-jsdl-wg(a)ggf.org [mailto:owner-jsdl-wg@ggf.org] On Behalf Of > Aleksandr Konstantinov > Sent: 15 April 2005 12:46 > To: jsdl-wg(a)ggf.org > Subject: Re: [jsdl-wg] Any JSDL parser around > > It seems Axis can't digest jsdl.xsd. Any suggestions on how to convert it > to wsdl (if possible at all)? > > > A.K. > > > > On Fri, 15 Apr 2005 13:11:05 +0200 > Roger Menday <r.menday(a)fz-juelich.de> wrote: > > > > > On Fri, 2005-04-15 at 11:11 +0100, William Lee wrote: > > > When you say a parser, do you mean a XML-to-Object binding for JSDL > > > schema? JSDL is specified in XML, therefore any XML tools (e.g. DOM4j, > > > JDOM, JAXB in Java) will do the job. > > > > In java, I'm currently using xmlbeans, http://xmlbeans.apache.org/ for > > this kind of thing. IMHO the XML schema support is unparallelled. It > > eats the JSDL.xsd with no problems ! I guess everyone has their > > favourite in such matters though. > > > > Roger > > > > > If you are looking for a JSDL > > > consumer, Imperial College has a project called GridSAM > > > (http://www.lesc.ic.ac.uk/gridsam) which translates JSDL into > > > DRM-specific (e.g. Condor, SGE) actions. UCL has a project for > > > translating JSDL into Condor ClassAds. > > > > > > William > > > > > > Aleksandr Konstantinov wrote: > > > > > > > Hello JSDL gurus, > > > > > > > > Does anybody know any common purpose JSDL parser implementation? Or > project which is going to release such? > > > >Preferably with C/C++ API. > > > > > > > >Thanks, > > > > > > > > > > > >A.K. > > > > > > > > > > > > > > > > > > > >

2 1

Any JSDL parser around
by Aleksandr Konstantinov 15 Apr '05

15 Apr '05

Hello JSDL gurus, Does anybody know any common purpose JSDL parser implementation? Or project which is going to release such? Preferably with C/C++ API. Thanks, A.K.

4 7

Re: [jsdl-wg] Any JSDL parser around
by Chee-Kian Koh 15 Apr '05

15 Apr '05

Hi William, GridSAM looks cool! What DRMs support now? Will we see one for Grid Engine soon? > On Fri, 15 Apr 2005 11:11:44 +0100 > William Lee <wwhl(a)doc.ic.ac.uk> wrote: > > > > > When you say a parser, do you mean a XML-to-Object binding for > JSDL > > schema? JSDL is specified in XML, therefore any XML tools (e.g. > DOM4j, > > JDOM, JAXB in Java) will do the job. If you are looking for a > JSDL > > consumer, Imperial College has a project called GridSAM > > (http://www.lesc.ic.ac.uk/gridsam) which translates JSDL into > > DRM-specific (e.g. Condor, SGE) actions. UCL has a project for > > translating JSDL into Condor ClassAds. > > > > William ----------------------------------------- Melvin Koh Chee Kian Grid Research Engineer Asia Pacific Science & Technology Center Sun Microsystems Inc. Website: http://apstc.sun.com.sg/ -----------------------------------------

1 0

Naming elements
by Michel Drescher 14 Apr '05

14 Apr '05

Folks, from the last phone conference, I had the action assigned to follow the suggestion of naming elements. Based on some thinking and toying around, I propose the following layout: JSDL allows to define a) applications that are supposed to be executed, b) sets of resources that are to be consumed, c) files to be staged in and out and, finally, d) establishes associations between applications, resources and data sets. An exhaustive 3-tuple of associations is called "JobDescription". A JobDescription can also contain a set of identifiable elements serving various kind of purposes, such as accounting, billing, etc. These elements are aggregated in an element called "JobIdentification". All this is aggregated in a root element called "JobDefinition" (a name I would like to question, but more on this at a later point). This short description from a bird's eye view may not be totally new, but it gives some valuable hints on what is worth being referencable and what not: a) resources, b) applications and c) data sets. A JobDescription does not necessarily has to be referencable, since it is usually a unique association between other elements that, in this configuration, serve a unique purpose. It is adequatically specified through the document's namespace. Similar jobs (who have a different namespace) may want to use exactly the same set of resources or the same application etc. Most likely, however, the resource sets or applications etc. that have been defined for another job will not fit exactly the new job's needs, so a mechanism to tweak existing definitions could be handy. So, more technically and closer to the spec/schema, the following elements should be made referencable: - /JobDefinition/JobDescription/Application - /JobDefinition/JobDescription/Resource - /JobDefinition/JobDescription/DataStaging - Additionally, a similar mechanism exists for /JobDefinition/JobDescription/Resource/FileSystem and /JobDefinition/JobDescription/DataStaging/FileSystemID. I also propose to change FileSystemID to the type xsd:QName. - Following the convention used with the construct "xsd:group", I propose to use an attribute "name" of type "xsd:NCName" to make an element referencable. An attribute named "ref" of type "xsd:QName" is proposed to be used as a reference to a referencable element. - Sibling to JobDescription, applications, resource sets and data staging elements are allowed to be specified. They all get an attribute "name" of type "xsd:NCName" to be made referencable. - JobDescription defines local elements(!) with the same name (for applications, resource sets and data staging) and each gets an optional attribute named "ref" of type "xsd:QName" to refer to already defined elements (either in the same document, or externally). - These locally defined elements allow exactly the same appropriate groups of elements as the elements sibling to JobDescription. - Elements specified in JobDescription's local elements override elements with the same name in referred elements. - Finally, I propose to change the name of "JobDefinition" to something else, e.g. "JSDL" or something that does *not* have "Job" in its name since it does not define jobs alone anymore. (I just have no clue on a reasonable replacement.) The following proposals are of more concern to schema hackers and are related to technical issues of design and "taste". They can easily be skipped by others although they may touch higher level concerns: - I further propose to follow one of the two scenarios: a) define exactly one global element ("JobDefinition") so that any valid JSDL document always has "JobDefinition" as root element b) define a limited number of global elements, i.e. JobDefinition, JobDescription, Resource (rename to "ResourceSet"?) Application and DataStaging so that any valid JSDL document may have any of these globally defined elements as root element - Any other elements and types should be locally defined. Or do we want to allow i.e. "jsdl:NetworkBandwidth" to be root element? - Use xsd:group to group elements together and refer to these groups instead of repeating element definitions Cheers, Michel

4 12

JSDL 0.9.5-02 uploaded
by Andreas Savva 14 Apr '05

14 Apr '05

I have uploaded JSDL spec. 0.9.5-02 and corresponding schema files to gridforge. This release contains a number of changes, mainly by Michel, especially around limits as well as the rangevalue definition and explanation. Also the POSIXApplication is now split off into a separate schema. ** This is a snapshot release so it is known to have inconsistencies ** and inaccuracies. Use at your own risk. The plan is to go back to releasing a snapshot every week (or bi-weekly if there are insufficient changes) ideally before each call. People with text assignments please send me, or the list, your updates to this version in time for me to put things together. Ali when releasing the previous version said: > I propose that any outstanding issues from GGF13 be added to the spec, > incrementing the double digits at the end of the version number at each > iteration for this purpose. i.e. 0.9.5-00 to 0.9.5-01 etc. I've kept the numbering scheme for this release (note that -01 was never formally released) but I would like to propose instead to start calling the spec "JSDL version 1.0, draft XX" where the XX corresponds to the version number of the document on gridforge. E.g., this release would be "JSDL version 1.0, draft 17." URLs: https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/e… https://forge.gridforum.org/projects/jsdl-wg/document/jsdl.xsd/en/8 https://forge.gridforum.org/projects/jsdl-wg/document/jsdl-posix.xsd/en/1 Equivalent shorter urls: http://tinyurl.com/3taa2/draft-ggf-jsdl-spec/en/17 http://tinyurl.com/3taa2/jsdl.xsd/en/8 http://tinyurl.com/3taa2/jsdl-posix.xsd/en/1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

RE: JSDL Meeting
by Bill Harris 13 Apr '05

13 Apr '05

I apologize for fat fingering the meeting time to 7:00 AM instead of eight, no excuses just in a hurry. Meeting are scheduled for 8:00 AM mountain time every Tuesday in the future. Darren has asked that we reschedule for Wed this week so meeting time is 8 AM Mountain Wed April 13, 2005. Darren has sent out the issues list for discussion. my apologies again billh meeting tomorrow ........... information below telecomm only... Darren will be sending out web information William Harris Program Architect Oryx follow me - 800 281 6462 Inside cadence 88 202 6462 Cell Phone 801 301 2744 The contact details are: Dial In Numbers: Belgium - 0800-7053 Bezeq - 1-800-940-1786 France - 0800-903109 Germany - 0800-1815765 Hong Kong - 800-968932 Italy - 800874509 Japan - 00531123656 Korea-Tele - 00798-14-800-0512 Netherlands - 0800-0225447 Singapore - 800-1200766 Sweden - 020-7905043 Taiwan - 00801-13-8546 UK - 0800961294 US - 800-933-3594 --> ext 3000 pin: 6444 The telecom time is: wed April 13 this week 07:00 PST 08:00 MST 09:00 CST 10:00 EST 15:00 BST 16:00 CET 23:00 JST William Harris Program Architect Oryx follow me - 800 281 6462 Inside cadence 88 202 6462 Cell Phone 801 301 2744

3 2

POSIX UID/GID
by Donal K. Fellows 13 Apr '05

13 Apr '05

The telecon has decided to move the UID/GID bits from User to the POSIX version of Application (whatever that's called; I'm behind tracking the exact name of things right now). But a question has come up about the meaning of the content of these elements. It is obvious that they have to be able to accept usernames in their xsd:string content (and I'm aware of systems with spaces in usernames, even if this is not something I'd ever do myself) since they're how POSIX user identities are exposed to users normal. However, with names like they have, should they also accept numeric UIDs? I don't have a use case for this (it's a detail I'd want to always hide) and I'm not aware of anyone ever having a wholly numeric username. As I see it, we have three options: * Current name, user-name semantics * Current name, user-name-and-uid semantics * Change name (to UserName?), user-name semantics Which do people prefer? (GID handling should mirror UID handling) Donal.

3 3

JSDL: Telecon...
by Ali Anjomshoaa 13 Apr '05

13 Apr '05

...on the hour in 15 mins... Agenda: http://www-unix.gridforum.org/mail_archive/jsdl-wg/2005/04/msg00054.html Web: Subject: JSDL Meeting URL: https://www.livemeeting.com/cc/xangoit/join Meeting ID: JSDL Attendee Key: Wxx*}$Hk4 Role: Attendee Phone: --> ext 3000 pin: 6444 Belgium - 0800-7053 Bezeq - 1-800-940-1786 France - 0800-903109 Germany - 0800-1815765 Hong Kong - 800-968932 Italy - 800874509 Japan - 00531123656 Korea-Tele - 00798-14-800-0512 Netherlands - 0800-0225447 Singapore - 800-1200766 Sweden - 020-7905043 Taiwan - 00801-13-8546 UK - 0800961294 US - 800-933-3594 --> ext 3000 pin: 6444 Cheers, Ali -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa EPCC, University of Edinburgh James Clerk Maxwell Building Mayfield Road E-mail: ali(a)epcc.ed.ac.uk Edinburgh EH9 3JZ Phone: + 44 (0) 131 651 3388 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

telecon error "the meeting has ended"?
by Karl Czajkowski 12 Apr '05

12 Apr '05

I cannot seem to dial in using the call info sent earlier to the list... anyone know what is up? karl -- Karl Czajkowski karlcz(a)univa.com

1 0

Requirements and preferences on resources
by Massimo Sgaravatto - INFN Padova 12 Apr '05

12 Apr '05

Dear all I have just recently joined this mailing list, and so maybe the question that I am going to raise have already been discussed: my apologies if this is the case. My question concerns the Resource element ... It is not clear to me if/how it is possible to specify not only requirements, but also preferences on resources, for example to allow a smart brokering service to choose among multiple resources matching the resource requirements. If you are familiar with Condor, I am referring to something similar to Requirements and Rank of Condor classads Thanks Cheers, Massimo \\\|/// \\ ~ ~ // (/ @ @ /) -------oOOo-(_)-oOOo---------------------------------- Massimo Sgaravatto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: ++39 0498277047 Fax: ++39 0498277102 oooO E-mail: massimo.sgaravatto(a)pd.infn.it ( ) Oooo Home page: http://www.pd.infn.it/~sgaravat --------\ (----( )---------------------------------- \_) ) / (_/

2 1