- jsdl-wg - lists.ogf.org

Re: Copy/Paste bug in JSDL spec
by Michel Drescher 27 Mar '06

27 Mar '06

Folks, thanks to Ralf, there is another typo known in the spec. Though it is not a serious mistake (it is just in an example, after all), I wonder if it is feasible to burden the GGF Editor with all these small nits and bits to update the specs. To the GGF process experts: Does GGF provide something like a maintained errata list for published specs, similar to the IETF (e.g. an errata list for HTTP/1.1)? Or do the WG have to do that themselves? What if WG have dissolved, and errata are discovered afterwards? Is there a general need to define a process for that? Cheers, Michel On 24 Mar 2006, at 11:01, Ratering, Ralf wrote: > Hi Michel&Donal, > > I just noticed a minor copy/paste bug in the > JSDL specs. > > In the examples for the Posix extensions -51) > there is: > > page 50: > <jsdl-posix:Input filesystemName="HOME"> > output.txt > </jsdl-posix:Input> > > page 51: > <jsdl-posix:Input filesystemName="HOME"> > error.txt > </jsdl-posix:Input> > > it should obviously be: > <jsdl-posix:Output filesystemName="HOME"> > output.txt > </jsdl-posix:Output> > > and > > <jsdl-posix:Error filesystemName="HOME"> > error.txt > </jsdl-posix:Error> > > Besides that, I like it :-) > Ralf > > Ralf Ratering > Intel GmbH > Software & Solutions Group > Hermuelheimer Strasse 8a > 50321 Bruehl > Germany > Tel: +49 2232 209049 > Fax: +49 2232 209029 >

3 2

Re: Fwd: [jsdl-wg] Re: Copy/Paste bug in JSDL spec
by Gregory Newby 27 Mar '06

27 Mar '06

On Mon, Mar 27, 2006 at 08:41:04AM +0100, Michel Drescher wrote: > Argh! > > Greg, sorry, forgot to get you into this mail in the first place. > > Cheers, > Michel Hi, Michel. We'd like to start an Errata list, and the GFSG agreed in principle to this...perhaps with something like a 90-day grace period for updating/replacing documents as needed. Sort of a blend of IETF policy and a more relaxed approach that GGF has had so far. We could probably just keep a plain text or HTML errata page for individual documents, making them available from the main document link at ggf.org. Or something a little different -- this is something that we just started planning, but any ideas are welcome. -- Greg > > Begin forwarded message: > > >From: Michel Drescher <Michel.Drescher(a)uk.fujitsu.com> > >Date: 27 March 2006 8:36:15 BDT > >To: JSDL WG <jsdl-wg(a)gridforum.org> > >Cc: Ralf Ratering <ralf.ratering(a)intel.com>, Joel Replogle > ><replogle(a)ggf.org> > >Subject: [jsdl-wg] Re: Copy/Paste bug in JSDL spec > > > >Folks, > > > >thanks to Ralf, there is another typo known in the spec. > > > >Though it is not a serious mistake (it is just in an example, after > >all), I wonder if it is feasible to burden the GGF Editor with all > >these small nits and bits to update the specs. > > > >To the GGF process experts: Does GGF provide something like a > >maintained errata list for published specs, similar to the IETF > >(e.g. an errata list for HTTP/1.1)? Or do the WG have to do that > >themselves? What if WG have dissolved, and errata are discovered > >afterwards? Is there a general need to define a process for that? > > > >Cheers, > >Michel > > > > > >On 24 Mar 2006, at 11:01, Ratering, Ralf wrote: > > > >>Hi Michel&Donal, > >> > >>I just noticed a minor copy/paste bug in the > >>JSDL specs. > >> > >>In the examples for the Posix extensions -51) > >>there is: > >> > >>page 50: > >><jsdl-posix:Input filesystemName="HOME"> > >>output.txt > >></jsdl-posix:Input> > >> > >>page 51: > >><jsdl-posix:Input filesystemName="HOME"> > >>error.txt > >></jsdl-posix:Input> > >> > >>it should obviously be: > >><jsdl-posix:Output filesystemName="HOME"> > >>output.txt > >></jsdl-posix:Output> > >> > >>and > >> > >><jsdl-posix:Error filesystemName="HOME"> > >>error.txt > >></jsdl-posix:Error> > >> > >>Besides that, I like it :-) > >>Ralf > >> > >>Ralf Ratering > >>Intel GmbH > >>Software & Solutions Group > >>Hermuelheimer Strasse 8a > >>50321 Bruehl > >>Germany > >>Tel: +49 2232 209049 > >>Fax: +49 2232 209029 > >> > > >

1 0

JSDL: Telecon Minutes 15 Mar 2006
by Ali Anjomshoaa 15 Mar '06

15 Mar '06

Hi all, today's telecon minutes are at: https://forge.gridforum.org/projects/jsdl-wg/document/Minutes_-_2006-03-15/… Cheers and take care, 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 650 5818 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

GGF-17 plans/schedule?
by Stuart Martin 15 Mar '06

15 Mar '06

Hi all, Are there plans for when the JSDL group will meet at GGF-17? I'd like to attend if possible and am trying to set my travel schedule. Thanks, Stu --------------------------------------- Stuart Martin GRAM Technology Coordinator Argonne National Laboratory Bldg 221, Office B-143 9700 South Cass Ave Argonne, IL 60439-4844 Office Phone: +1-630-252-0904

2 1

[Fwd: [ogsa-wg] Revised CDL for BLAST slides (Re: Proposed agenda for March 15th call)]
by Andreas Savva 15 Mar '06

15 Mar '06

This is part of the activity within OGSA-WG that I mentioned on the JSDL call earlier. (See attached slides.) -- Andreas Savva

1 0

JSDL: telecon tomorrow
by Ali Anjomshoaa 14 Mar '06

14 Mar '06

Hi all, There will be a 1 hour telecon tomorrow to discuss the way forward following GGF16's discussions on future work - minutes are at: https://forge.gridforum.org/docman2/ViewCategory.php?group_id=122&category_… Call Details: Date: 15th March Time: 14:00 GMT Dial-in numbers: US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 207 3655269 (London) Japan: +81 3 3570 8225 (Tokyo) Participant PIN: 4371991 Take care, 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 650 5818 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

FW: comments on ideas that might be accomplished by extending JSDL
by Brisard, Fred D 27 Feb '06

27 Feb '06

I forwarded this to the JSDL-WG membership so everyone can be aware of our discussions. Fred Brisard fred.brisard(a)ca.com -----Original Message----- From: David A. Alexander [mailto:alexanda@txcorp.com] Sent: Monday, February 27, 2006 4:05 PM To: Ly, An V Cc: Brisard, Fred D; 'Johnson, Tony S.'; 'Jerome LAURET' Subject: RE: comments on ideas that might be accomplished by extending JSDL Hi An Ly, We have one reference implementation so far and that is our own Java Application client (and a command line program) to access the STAR Unified Meta Scheduler (see http://www.star.bnl.gov/STAR/comp/Grid/scheduler/) I have attached the RDL specification document that we have so far that also describes some use cases and our thoughts on the applicable situations and the possible limitations. I would be good if we could collaborate in some. For example, maybe we could propose to make our effort a special investigation for or under the guidance of the JSDL working group or something to that effect? I noticed in your last projection of what you would like to do with JSDL there was talk of work flows. We would be very interested to see how we could be of service in this area. Thanks, dave > -----Original Message----- > From: Ly, An V [mailto:An.Ly@ca.com] > Sent: Monday, February 27, 2006 1:45 PM > To: alexanda(a)txcorp.com > Cc: Brisard, Fred D > Subject: RE: comments on ideas that might be accomplished by extending > JSDL > > Hi David, > > I'm a member of JSDL and I reviewed the paper regarding RDL/TDL that you > sent to the JSDL group. The concept of a user-oriented/high-level way to > describe the (grid) job or its status is interesting. Would it be > possible to get examples/use cases of your applications that are > currently described/managed in the RDL/TDL-like manner? > > Thanks, > An Ly > > -----Original Message----- > From: Brisard, Fred D > Sent: Monday, February 27, 2006 2:44 PM > To: Ly, An V > Subject: RE: comments on ideas that might be accomplished by extending > JSDL > > > > Fred Brisard > fred.brisard(a)ca.com > > -----Original Message----- > From: David A. Alexander [mailto:alexanda@txcorp.com] > Sent: Monday, February 27, 2006 1:35 PM > To: ali(a)epcc.ed.ac.uk; andreas.savva(a)jp.fujitsu.com; Brisard, Fred D; > darren(a)pulsipher.org; scrumb(a)ggf.org; asm100(a)doc.ic.ac.uk > Subject: RE: comments on ideas that might be accomplished by extending > JSDL > > Gentlemen, > > I didn't hear back from anyone about my question. I realize that you > may be > busy and it may take more time and effort to respond to an email than it > would to talk in person. Therefore, would you mind if I called you to > talk > about the JSDL and how we our projects might be mutually beneficial? > > Thanks, > David Alexander > Cell 720.581.6737 > > _________________________________________________ > David Alexander desk: 303-448-7751 > Tech-X Corporation fax: 303-448-7756 > Boulder, CO email: alexanda(a)txcorp.com > (303)448-7751 http: www.techxhome.com > > > -----Original Message----- > > From: David A. Alexander [mailto:alexanda@txcorp.com] > > Sent: Thursday, February 23, 2006 10:30 AM > > To: 'ali(a)epcc.ed.ac.uk'; 'andreas.savva(a)jp.fujitsu.com'; > > 'fred.brisard(a)ca.com'; 'darren(a)pulsipher.org'; 'scrumb(a)ggf.org'; > > 'asm100(a)doc.ic.ac.uk' > > Cc: 'Jerome LAURET'; 'Johnson, Tony S.' > > Subject: comments on ideas that might be accomplished by extending > JSDL > > > > > > Dear JSDL Working Group Administrators & Chairs, > > > > We are formulating ideas on how to develop a "request language" (or > what > > in your community might be best termed a high-level request language > that > > a consuming submission system would turn into a workflow). I have > looked > > at the 1.0 specification of JSDL and we have a lot of overlapping > concerns > > except that it says that workflow issues are out of the scope of JSDL. > > Attached is a short white paper on our idea as it stands. We would > > appreciate any comments on how you think we can collaborate or where > our > > ideas fit into your views of JSDL or other specifications that already > > exist. We are not trying to re-invent the wheel. However, we do wish > to > > provide a way for Open Science Grid users to specify what they need at > a > > high-level beyond the individual job. > > > > Thanks, > > > > David Alexander, Tech-X Corporation > > > > On behalf of our team that includes: > > Jerome Lauret, Brookhaven National Lab > > Tony Johnson, Stanford Linear Accelerator Center > > > > > > _________________________________________________ > > David Alexander desk: 303-448-7751 > > Tech-X Corporation fax: 303-448-7756 > > Boulder, CO email: alexanda(a)txcorp.com > > (303)448-7751 http: www.techxhome.com

1 0

RE: [jsdl-wg] Future plans for JSDL
by Lee, William 23 Feb '06

23 Feb '06

+1 on the multiple <xsd:any/>, I don't really know what the precise semantic is. Do they collapse into one? How do you deal with multiplicity? ... Anyway, the toolings I've worked with seems to be able to cope with that (SOAPScape and Sun J2EE server). Another way we can do this is to define the new Application element and manually add all the posix:XYZ elements that we need in a sequence without using any of the XSD extension mechanism. William --- William Lee - Software Coordinator --- --- London e-Science Centre, Imperial College London --- A: Room 380, Department of Computing, Imperial College London, Huxley Building, South Kensington campus, London SW7 2AZ, UK E: wwhl at doc.ic.ac.uk | william at imageunion.com W: www.lesc.ic.ac.uk | www.imageunion.com P: +44(0)20 7594 8310 F: +44(0)20 7581 8024 -----Original Message----- From: Donal K. Fellows [mailto:donal.k.fellows@manchester.ac.uk] Sent: 23 February 2006 13:12 To: Lee, William Cc: JSDL WG Subject: Re: [jsdl-wg] Future plans for JSDL Lee, William wrote: > Roughly.... > <xsd:complexType name="MPIApplicationType"> > <xsd:complexContent> > <xsd:extension base="jsdl-posix:POSIXApplication_Type"> > <xsd:sequence> > <xsd:element ref="ProcessorCount"/> > </xsd:sequence> > </xsd:extension> > </xsd:complexContent> > </xsd:complexType> How does that work with <xsd:any>? When I've tried that sort of thing, the results have tended to be less than satisfactory when tooled up (multiple anys in the element, etc.) Donal.

2 1

RE: [jsdl-wg] Future plans for JSDL
by Lee, William 23 Feb '06

23 Feb '06

In the parallel extension we have created in GridSAM. We have a new element called <mpi:MPIApplication/> that extends the jsdl:posix:POSIXApplication_Type. Therefore the MPIApplication inherits the arguments, executable, etc. with the additional elements to specify parallelism. Roughly.... <xsd:complexType name="MPIApplicationType"> <xsd:complexContent> <xsd:extension base="jsdl-posix:POSIXApplication_Type"> <xsd:sequence> <xsd:element ref="ProcessorCount"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="ProcessorCount" type="xsd:positiveInteger"/> <xsd:element name="MPIApplication" type="MPIApplicationType"/> William --- William Lee - Software Coordinator --- --- London e-Science Centre, Imperial College London --- A: Room 380, Department of Computing, Imperial College London, Huxley Building, South Kensington campus, London SW7 2AZ, UK E: wwhl at doc.ic.ac.uk | william at imageunion.com W: www.lesc.ic.ac.uk | www.imageunion.com P: +44(0)20 7594 8310 F: +44(0)20 7581 8024 -----Original Message----- From: owner-jsdl-wg(a)ggf.org [mailto:owner-jsdl-wg@ggf.org] On Behalf Of Donal K. Fellows Sent: 23 February 2006 09:11 To: JSDL WG Subject: Re: [jsdl-wg] Future plans for JSDL A S McGough wrote: > 3) Prioritise the items. From the session parallel jobs seemed to be > the thing most people wanted next. Just a quick note to say that the main reason for doing the parallel jobs stuff next (probably starting from the base proposed by the people from Barcelona; they've identified the stuff that's needed after all) is that otherwise there'll be several different groups doing it themselves in an incompatible way. To me, that says it is an *excellent* idea to foster a standard extension for this and to expedite this. OK, I think other extensions/improvements are more important in the grand scheme of things, but the fact that people are doing it now forces our hand. Looking at the parallel proposal, I have to ask how it is supposed to be combined with the POSIX extension, since without that it's not going to work (still need command-line args, env-vars, etc.) Once we've nailed that down, I think it will be just A Simple Matter Of Writing. :-) Donal.

2 1

Future plans for JSDL
by A S McGough 23 Feb '06

23 Feb '06

All, We had a session here at GGF16 where we brain stormed some ideas for where JSDL should go next. This also included some material which had come up from the last OGSA f2f meeting. Attached are the edited slides from this session which lists some of the areas where people think that JSDL should look into. The things that need doing now include: 1) Request from the list for items that were missed out from the session. 2) Classify these items as: a) Out of Scope (TM) b) Extensions for JSDL 1.0 c) New functionality for JSDL 2.0 d) Separate to JSDL versions (eg items for a primer document) 3) Prioritise the items. From the session parallel jobs seemed to be the thing most people wanted next. steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------

3 2