- ogsa-wg - lists.ogf.org

8 May 2008 - ISV HTC Primer call minutes
by Michel Drescher 09 May '08

09 May '08

Guys, please find attached the minutes for today's conference call on the ISV HTP primer. Cheers, Michel

1 1

response to your public comment view of 'info/data model arch doc'
by Ellen Stokes 08 May '08

08 May '08

Donal, Response embedded below prefaced by (EJS). I will post in the tracker resolution and update the doc accordingly for May 8 OGSA call. Ellen Nitpicking Though a good paper overall, the process of converting it to PDF seems to have badly affected several of the figures, and a few others need tweaking: (EJS) I generated a pdf using a free facility called pdf995....and my responses are based on that. Fig 1: The top bubble is wholly black! (EJS) Using pdf995, I cannot reproduce this problem. Fig 2: Should have something in the space in the middle or it looks like a mistake (a cloud? a question mark?) rather than a preparation for Fig 3. (EJS) I disagree...it is prep for figure 3...having the ability for slide overlay has proven in the past to be a good thing. Fig 4: Something is wrong with the transparency of the figures in the VOs. (EJS) This I agree is a problem in the pdf and will fix. However, the fix may be to include just one figure in each VO instead of multiples (how to fix the pdf transparency problem is not readily obvious). Fig 5: Would it be possible to increase the font sizes so that the text is easier to read when printed? And move the & #034;matching" text so that it is not covering/covered by the line it labels. (EJS) I will do what I can to increase the font size. As for text covering the lines, I do not see that in the pdf. Fig 7: Consider highlighting/making bold the terms that will be picked up by the queries in Figures 8-11. (EJS) I think the highlighting you suggest will be too confusing to the reader (even if we state that in text) and make the XML less readable. The reader can alway use query functions to find terms. Fig 11: Make the font a little smaller so that none of the lines wrap where not desired (yes, I find this a pain in the documents I write too...) (EJS) Right now the font is at 9 pitch. Even if I make it at 8 pitch (which is the smallest) some lines will still wrap. And given your comment in Figure 5 that the font was too small (8 pitch), I really hesitate to make the font in this figure smaller. Also, the contributors list probably ought to have the addresses of the organizations for which the authors work, and the contributor acknowledgments probably shouldn't use shortened first names. (EJS) The authors chose to not include the explicit org addresses (very long)..email addresses are most useful. In the acknowledgements section, I'm not aware that shortened first names have been used so I don't know what to fix (and these are names that have been used in other docs as-is). (Finally, don't forget to fix the GFD references, of course.) (EJS) thanks for the reminder.

2 1

[Invitation] ISV HPC usege primer @ Thu May 8 9am – 10am ()
by Hiro Kishimoto 07 May '08

07 May '08

ogsa-wg(a)ogf.org, you are invited to Title: ISV HPC usege primer Time: Thu May 8 9am – 10am (Timezone: Central Time) Calendar: Description: When:10-11am EDT, 9-10am CDT, 7-8am PDT, 11pm-midnight JST, 3-4pm UK Dial-in numbers: US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Germany: +49 (0)69 50070802 (Frankfurt) Switzerland: +41 (0)1 8009574 (Zurich) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Note taker assignment - https://forge.gridforum.org/sf/go/wiki1848 Roll call Agenda bashing 2) Minutes approval and AI review Minutes for approval April 7th call: https://forge.ogf.org/sf/go/doc15174 April 10th call: https://forge.ogf.org/sf/go/doc15180 Action Item review http://forge.ogf.org/short/ogsa-wg/ailist 3) ISV HPC usage primer (Steven Newhouse) 4) AoB You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=cmxrNHA3bWprYzNyMTM5cD… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

[Invitation] modeling arch PC review @ Thu May 8 8am – 9am ()
by Hiro Kishimoto 07 May '08

07 May '08

ogsa-wg(a)ogf.org, you are invited to Title: modeling arch PC review Time: Thu May 8 8am – 9am (Timezone: Central Time) Calendar: Description: When: 9-10am EDT, 8-9am CDT, 6-7am PDT, 10-11pm JST, 2-3pm UK The dial-in number; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) Germany: +49 (0)69 50070802 (Frankfurt) Switzerland: +41 (0)1 8009574 (Zurich) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Note taker assignment - https://forge.gridforum.org/sf/go/wiki1848 Roll call Agenda bashing 2) Minutes approval and AI review (see the bottom of this agenda) Minutes approval Feb. 21 call: https://forge.gridforum.org/sf/go/doc15122 Action Item review http://forge.ogf.org/short/ogsa-wg/ailist 3) modeling arch doc PC review (Ellen Stokes) Ellen has revised the ogsa info model arch doc based on the comment received in public comment period. https://forge.gridforum.org/sf/go/doc13726?nav=1 Comment resolution has been sent out in 2 previous emails. Unless there is major disagreement with the resolutions this week, I expect to be able to send this document by early next week to the OGF editor for publication. 4) AoB You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=NmZzNG1nZ250cXNqNjY2dj… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

revised ogsa info model arch doc (post public comment period)
by Ellen Stokes 07 May '08

07 May '08

I've revised the ogsa info model arch doc based on the comment received in public comment period. https://forge.gridforum.org/sf/go/doc13726?nav=1 Comment resolution has been sent out in 2 previous emails. We'll be reviewing at the Thursday May 8 OGSA call, 8am-9am central (you should be receiving note from Hiro on this shortly). Unless there is major disagreement with the resolutions this week, I expect to be able to send this document by early next week to the OGF editor for publication. Ellen

1 0

Re: [ogsa-wg] information data model - reviewed latest
by guru prasad 07 May '08

07 May '08

Sorry!!! please find the latest version. Ignore my previous email. ----- Original Message ---- From: guru prasad <guru_bn(a)yahoo.com> To: stokese(a)us.ibm.com Cc: ogsa-wg(a)ogf.org Sent: Friday, March 28, 2008 4:53:04 PM Subject: [ogsa-wg] information data model - reviewed Hello, I am enclosing my comments on Information & Data Modeling in OGSA® Grids Architecture Paper. I look forward to hearing from you guys on this. Best, Guru No Cost - Get a month of Blockbuster Total Access now. Sweet deal for Yahoo! users and friends. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

[Invitation] WSRF BP interop @ Tue May 6 8am – 9am ()
by Hiro Kishimoto 06 May '08

06 May '08

ogsa-wg(a)ogf.org, you are invited to Title: WSRF BP interop Time: Tue May 6 8am – 9am (Timezone: Central Time) Calendar: Description: When: 9-10am EDT, 8-9am CDT, 6-7am PDT, 10-11pm JST, 2-3pm UK The dial-in number; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) Germany: +49 (0)69 50070802 (Frankfurt) Switzerland: +41 (0)1 8009574 (Zurich) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Note taker assignment - https://forge.gridforum.org/sf/go/wiki1848 Roll call Agenda bashing 2) Minutes approval and AI review (see the bottom of this agenda) Minutes approval April 3rd call: April 24th call: Action Item review http://forge.ogf.org/short/ogsa-wg/ailist 3) OGSA WSRF profile inteop (David Snelling) Interop page - https://forge.gridforum.org/sf/go/wiki1744 4) Proposal for fixing the specification Dave has checked with Ian Foster and Tom Maguire, co-authors on the OGSA BP, and we all three agree to the following: 1) We should create a profile specific topic for change notification to circumvent the problem with WS-Notification/WS-Topics. 2) We should change the representation of the plural QName lists from a [1..1] property contain a list to a [1..n] property with one QName each. 5) AoB You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=MmIzOThmOTBsMnE0dTM2Z2… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

2 1

Word from OGSA BP Profiles
by David Snelling 05 May '08

05 May '08

Folks, I have checked with Ian Foster and Tom Maguire, co-authors on the OGSA BP, and we all three agree to the following: 1) We should create a profile specific topic for change notification to circumvent the problem with WS-Notification/WS-Topics. 2) We should change the representation of the plural QName lists from a [1..1] property contain a list to a [1..n] property with one QName each. Thanks: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Fujitsu Laboratories of Europe Limited Hayes Park Central Hayes End Road Hayes, Middlesex UB4 8FE Reg. No. 4153469 +44-208-606-4649 (Office) +44-7768-807526 (Mobile)

1 0

my review comments on model guidelines doc v13
by Ellen Stokes 03 May '08

03 May '08

Fred, Here are my comments on the model guidelines doc v13...nothing major in my opinion. - inconsistent use of the words attributes and properties; modify to use one word or the other throughout the document - section 2.3: this is correct at this point in time; however, please be aware that DMTF (in conjunction with its alliance partners) is modifying processes to provide the capability of extension through federation and/or delegation, and this work is expected to complete this year - recall that the DMTF structure just changed from WGs and TC to WGs, SCs, and TC....this needs to be reflected in sections 4.1 and 4.3 - section 4.3: DMTF is in the process of making a change to its portal so that attachements can be provided during feedback to the DMTF; so alternatively (when the portal change is complete) a CR with an attachment could be submitted using the portal (which is an easy way to get it to the right group and state that DMTF owns the rights of the change (alliance partner contributions are also acknowledged within the MOF/XML and on the CIM release web page) - the dates in the copyright in the Copyright Notice at the beginning of the document and in section 10 should say '2006-2008' - all URLs in the doc should be hyperlinks (found in various sections) - appendix A: last bullet should say 'CIM v2.16 experimental' - any figure/table references in the doc text need to have links to those referenced figures/tables Ellen

4 9

Fwd: WSRF BP Interop and WS-Notification QName issue (was: Re: Globus team will join next week or so)
by Michel Drescher 01 May '08

01 May '08

Guys, as per last OGSA call on WSRF BP interop I was appointed to forward my proposal, which I originally sent only to the interop participants, to the whole OGSA Mailing list. The mail is very technical, and deals with found shortcomings in WS- Notification and hence OGSA WSRF BP 1.0, too. I would like to put up my proposal to the WG as a whole - so please read, (try to understand), and make comments. If you feel it is appropriate please feel to forward to relevant discussion groups, too (e.g. project specific mailing lists such as for UNICORE, Globus, etc.) Cheers, Michel Begin forwarded message: > From: Michel Drescher <Michel.Drescher(a)uk.fujitsu.com> > Date: 8 April 2008 15:57:56 BST > To: Mark Morgan <mmm2a(a)virginia.edu>, Rachana Ananthakrishnan <ranantha(a)mcs.anl.gov > >, Shiraz Memon <a.memon(a)fz-juelich.de>, Vivian Li <Vivian.Li(a)uk.fujitsu.com > > > Cc: David Snelling <david.snelling(a)uk.fujitsu.com>, Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com > >, "A.S.McGough" <asm(a)doc.ic.ac.uk>, Andrew Grimshaw <grimshaw(a)cs.virginia.edu > >, Andreas Savva <andreas.savva(a)jp.fujitsu.com> > Subject: WSRF BP Interop and WS-Notification QName issue (was: Re: > Globus team will join next week or so) > > Folks, > > WRT last week's call on WSRF BP interop. > > [I put the coders in the "To:" list, as they are the primary > suspects of having to implement changes ...] > > I have been digging (can't help it ...) and finally found what I > think is the answer to our "QName problem". The documents I am > referring to are: > > 1) "Namespaces in XML" > World Wide Web Consortium, 14 January 1999 > http://www.w3.org/TR/1999/REC-xml-names-19990114/ > > 2) "Namespaces in XML 1.0 (Second Edition)" > W3C Recommendation from 16 August 2006 > http://www.w3.org/TR/REC-xml-names/ > > In short: > > WS-Notification is plain wrong, as it requires namespace > declarations to be in scope for character data, opposing both > documents. > > In detail: > > Document 2 is an update of document 1; I refer to both documents to > demonstrate that namespaces - particularly namespace declarations > and namespace scope(!) - are defined as such since 1999, predating > WS-Notification. > Chapter 6 of document 2 is more or less a verbatim copy of chapter 5 > in document 1. Hence I will refer to document 2 only from now on. > > The whole document 2 deals with namespaces; only chapter 6 deals > with namespace scoping. Particularly section 6.1 defines the scope > of namespaces. The most important sentence in that section is the > 2nd paragraph: > > "Such a namespace declaration applies to all element and attribute > names > within its scope whose prefix matches that specified in the > declaration." > > In other words, namespaces are IN SCOPE for all child elements and > attributes, but NOT IN SCOPE for all possibly appearing character > data. > > Therefore, WS-Notification requires a parsing methodology which > violates this W3C Recommendation. > > Proposed solution: > > We cannot force implementations that use tooling conforming to the > referenced W3C Recommendation to change the tooling (or overriding > it) to be non-conformant to XML Namespaces. > > Therefore, I propose the following to the OGSA-WG: > > a) Define a OGSA-WG dialect for Notification topics which is > congruent to the "SIMPLE" dialect. > b) Define a XML Element of type xs:QName to carry the QName of the > topic a client wants to subscribe to. > c) Mandate that, when a client uses the OGSA-specific dialect, that > the OGSA-specific element MUST be present in the > wsn:NotificationTopic element in the subscription request > > If, for example, the dialect name would be defined as "http://www.ogf.org/ogsa/2008/04/wsrf-bp/notification/simple > " and the OGSA-specific element would be defined as "<element > name="TopicName" type="xs:QName" /> then an example subscription > message for the interop testing could look lime this: > > ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP > ---------- > ... > <wsn:TopicExpression dialect="http://www.ogf.org/ogsa/2008/04/wsrf-bp/notification/simple > "> > <ogsa-bp:TopicName>bp-interop:Ticker</ogsa-bp:TopicName> > <wsn:TopicExpression> > ... > ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP > ---------- > > This way, all implementations MUST respect the namespace scope, and > any deserialiser for the ogsa-bp:TopicName element MUST de-reference > the prefix correctly. > > Side note to Query Resource Properties support: > The same holds to for the support for the QueryResourceProperties > operation - as the namespaces are not in scope for the XPath > expression (which is encoded as a String), there is no way for an > implementor (unless violating XML Namespaces) to reliably de- > reference prefixes used in a XPath expression unless the message > carries explicit namespace-to-prefix information (other than the > streamlined xmlns:prefix attributes). Which is, unfortunately not > true for neither QueryResourceProperties nor WS-Notification's XPath > dialect... > > Process question (mostly to Hiro): > Given we agree on my proposal (or something similar) - is it > possible to change the WSRF BP before it advances to the > Recommendation status (after having the Experience doc written)? > > Cheers, > Michel

2 1