Dear all, Here is the Email thread concerning introducing XQuery expressions in JSDL. The respective document is:http://www.ggf.org/documents/GFD.137.pdf A presentation (by me I think) is: http://www.ogf.org/gf/event_schedule/?id=903 Cheers, Michel ---------- Forwarded message ---------- From: Sergio Andreozzi <sergio.andreozzi@egi.eu> Date: 16 November 2011 10:42 Subject: Fwd: [glue-wg] GLUE 2.0 attributes for usage inside JSDL To: Michel Drescher <michel.drescher@egi.eu> Hi Michel, The OGF doc is referenced below. Plus you can consider this presentation about extending JSDL with XQuery made by a guy you should know: http://www.ogf.org/gf/event_schedule/?id=903 :) Cheers, Sergio ---------- Forwarded message ---------- From: Sergio Andreozzi <sergio.andreozzi@egi.eu> Date: 21 September 2011 12:38 Subject: Re: [glue-wg] GLUE 2.0 attributes for usage inside JSDL To: Etienne URBAH <urbah@lal.in2p3.fr> Cc: "John-Paul F. NAVARRO" <navarro@mcs.anl.gov>, glue-wg@ogf.org, jsdl-wg@ogf.org Dear Etienne et Al., The issue of JSDL/GLUE integration was touched few times in the past. If the use case is to express requirements on GLUE-based information, I consider the approach taken in JSDL 1.0 not suitable for a more complex set of information such as coming from GLUE. When selecting a computing service for instance, you may want to express requirements on the characteristics of the endpoint, of the execution environment, of the application environment and on the share. For each computing service, you may have many instances of the subcomponents, but not all are associated. E.g. a certain computing share is defined on top of 2 of the 5 execution environments, so you need to match requirements on the execEnv, on the share and the fact that the two are "in relationships". In the past, we have discussed to have the option to express requirements using an XQuery expression embedded in the JSDL. While this is a generic approach and would make JSDL not depended on GLUE terms (which is a good option as giving more flexibility), it has the drawback of having the need to write queries that may be complex. To mitigate this, you could think about letting the users express requirements with a simple descriptive format from which a query can be generated automatically. See section 5.3 of this document as an example of XQuery expression based on an XML document describing computing resources based on a preliminary draft of GLUE 2 back in 2008: http://www.ggf.org/documents/GFD.137.pdf My recommendation is, before to make any final choice, test the solution on production use cases to verify the suitability. Kind regards, Sergio On 21 September 2011 11:27, Etienne URBAH <urbah@lal.in2p3.fr> wrote:

On Tue, 20/09/2011 17:09, Etienne URBAH wrote:

...

Michael,

Concerning the GLUE 2.0 attributes for usage inside JSDL, I suggest to look at following pages :

http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqJD3

...

http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.pgi-wg/doc...

...

Best regards.

----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr -----------------------------------------------------

_______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg

-- Sergio Andreozzi - Policy Development Manager - EGI.eu http://www.egi.eu - skype:sergio.andreozzi.egi -- Sergio Andreozzi - Policy Development Manager - EGI.eu http://www.egi.eu - skype:sergio.andreozzi.egi -- Stichting European Grid Initiative (EGI.eu) P.O. Box 41882, 1009 DB Amsterdam 140 Science Park, 1098 XG Amsterdam The Netherlands F: +31 (0)20 893 2007 M:+31 (0)6 303 726 55 Skype: michel.drescher.egi