March 2008 - jsdl-wg - lists.ogf.org

Call next week?
by Andreas Savva 25 Mar '08

25 Mar '08

Our call schedule is roughly bi-weekly, so the next call would be in two weeks time (Mar.26). But it looks like the chairs won't be available that week. We are therefore thinking of a call next week, conditional on having sufficient material for discussion. We discussed parameter sweep yesterday and we probably won't have enough material for next week on this topic. That leaves the Activity schema, for which the main action from OGF22 was to provide use cases (Chris, Shabaz, Philipp). So could you please let me know if the use cases are likely to be ready by next week? I'll send out a call announcement if there is sufficient material, otherwise the next call will probably be in early April. -- Andreas Savva

5 4

No call this week
by Andreas Savva 18 Mar '08

18 Mar '08

From the responses received so far it doesn't look like we are going to be ready for a call this week. Next week the chairs are not available so the next call will likely be on April 2 or April 9. There will be an announcement sent to the list in advance. If you working on a use case for the activity schema please upload it to gridforge (and/or send to the list) when you are ready. You don't have to wait for the next call. -- Andreas Savva Fujitsu Laboratories Ltd.

1 0

(Param Sweep) artf6147 : Explanation for matching on part of element content
by geoff 13 Mar '08

13 Mar '08

Hi all, Would like to propose a modification of the [2.3 [parameter]] content in the draft along the following lines. 1) Addition at the point of introduction of XPath use of the following links for referencing XPath nomenclature: XPath 1.0 : http://www.w3.org/TR/xpath XPath 2.0 : http://www.w3.org/TR/xpath20/ 2) Insertion of a second example (e.g. a new [2.3.3]) to illustrate use of substring function: The following example illustrates the ability to match on part of an element content through the use of the XPath 1.0 substring function: <jsdl:JobDefinition> <jsdl:JobDescription> <jsdl:Application> <jsdl-posix:POSIXApplication> <jsdl-posix:Executable>/bin/some_exe</jsdl-posix:Executable> <jsdl-posix:Argument>-infile</jsdl-posix:Argument> <jsdl-posix:Argument>in.NNN.dat</jsdl-posix:Argument> </jsdl-posix:POSIXApplication> </jsdl:Application> </jsdl:JobDescription> <sweep:Sweep> <sweep:Assignment> <sweep:Parameter> substring(/*//jsdl-posix:Argument[2], 4, 3) </sweep:Parameter> <sweepfunc:Values> <sweepfunc:Value>001</sweepfunc:Value> <sweepfunc:Value>002</sweepfunc:Value> <sweepfunc:Value>003</sweepfunc:Value> <sweepfunc:Value>004</sweepfunc:Value> <sweepfunc:Value>005</sweepfunc:Value> </sweepfunc:Values> </sweep:Assignment> </sweep:Sweep> </jsdl:JobDefinition> The above yields the following 5 jobs: "-infile in.001.dat" "-infile in.002.dat" "-infile in.003.dat" "-infile in.004.dat" "-infile in.005.dat" Note: I've referred to the substring function as "XPath 1.0" (unlike the draft which implies in the footer that it's an XPath 2.0 function) as it's XPath 1.0 that defines its use. Not sure if this is important. 3) For the benefit of the less attentive reader, perhaps the use of emphasis e.g. bold (or titled as "Invalid Example 1") to stress that the existing [2.3.3 Example 2] represents an invalid form. gef

1 0

Parameter Sweep discussions
by geoff 11 Mar '08

11 Mar '08

Dear Michel, Andreas, and others group members, A group of us currently meeting in KISTI, S.Korea have been sharing ideas and considerations for the implementation of a parameter sweeping mechanism to support the research community. Input has principally come from David Meredith (NGS), Soonwook Hwang and Byungsang (KISTI) and myself. David is the creator of the UK National Grid Service JSDL Application Repository portal (https://portal.ngs.ac.uk) and has been tasked with creating a parameter sweeping mechanism for the NGS portal (I am currently working with David on implementing this functionality). Naturally we would like to adopt JSDL sweep related standards. Soonwook and Byungsang are in charge of development of KISTI's AURORA Application Repository (http://aurora.kisti.re.kr) which has been in use for some time and uses its own schema definition for parameter sweeping. AURORA's mechanism is loosely aligned with JSDL, but focuses on the sweeping of parameters within input files, rather than sweeping over elements defined within the JSDL document itself. We consider this to be an important additional functionality. Indeed, David has already reported on a number of (bespoke) parametric job definition schemes used to sweep over parameters within input files which have been developed as a matter of requirement by a number of different NGS user communities. The JSDL parameter sweeping specification in its current draft form appears to provide the flexibility to sweep over any element within a JSDL document, and as such provides powerful flexibility to the user. >From our experience however, many applications (for example KISTI and NGS supported NSCCS applications, e.g. CFD Solver, AutoDock) require the ability to sweep over values within input files. Consequently, where possible, we would like to propose further extensions to the existing draft sweep schema specification for including; a) the definition of parametric variables that can exist within input files, and b) referral to the associated data\input files. We were therefore wondering whether the same conclusion had been reached by those contributors to the original draft specification or indeed, whether you all feel that such an approach falls outside the remit of the OGF standard specification. Maybe we could organize a joint phone chat to discuss some of these issues and offer ideas and suggestions. We will working together until late Friday so if it's possible to have some feedback to these queries during this period it would be very much appreciated. Best wishes, Geoff, Byungsang, David, Soonwook. Note, **KISTI – Korea Institute for Science Technology Information **NSCCS – National Service for Computational Chemistry

3 3

JSDL Teleconference - 12 March 2008 @2pm UTC
by Andreas Savva 11 Mar '08

11 Mar '08

Confirming a call for Wednesday, March at **2pm GMT**. Proposed agenda: - Agenda bashing/Updates - Confirm teleconf slot for future calls - Parameter Sweep - Use cases for Activity instance document schema (if any) ===== Full call-in details ==== Date: 12 March 2008 Time: UTC/GMT 2:00 PM / EDT 10:00 AM / PDT 7:00 AM / JST 11:00 PM Duration: 1 hour Dial-in numbers (toll): US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 207 3655269 (London) Japan: +81 3 3570 8225 (Tokyo) Other countries: http://tinyurl.com/eg48j User guide: http://tinyurl.com/qknrf Teleconference participant PIN: 4371991 Screen share: http://jsdl.glance.net/?key=0312 Note: When you dial in after the initial message in English for the PIN there is another message in Japanese only (sorry) to state your name and press '#' in order to join the call.

1 0

Call timeslot
by Andreas Savva 10 Mar '08

10 Mar '08

Our next call is scheduled for this Wednesday. The US has changed to summer time and we may have people joining from the US Pacific coast, so would the [2pm UTC] time slot be acceptable: UK 2pm / Germany 3pm / PDT 7am / EDT 10am / JST 11pm Opinions welcome. I think there is no other slot that keeps start times <=11pm and >=7am for the above timezones. -- Andreas Savva

1 0