- graap-wg - lists.ogf.org

telecon on 1/3
by Jim Pruyne 03 Jan '07

03 Jan '07

Happy New Year! Our last telecon was successful in managing many of the comments we have received. If people are available, I would like to continue making progress on these at our usual time and the new-ish usual number. Also, OGF meeting is only a few weeks away, so perhaps it would be worth it to discuss activities there. I know this may not work for some people, so if we don't have good attendance, we'll try again next week. 9:00AM Central Standard Time US (GMT-0600) which should be: 10:00AM Eastern Standard Time US 1500 UK(?) 1600 Germany(?) 0000 Japan (sorry Toshi) Phone Number: 866-480-9967 in the US. 832-445-2343 for those outside the US. Conference code #8578310. --- Jim

1 0

minutes from 12/20 telecon
by Jim Pruyne 30 Dec '06

30 Dec '06

Are attached. --- Jim Minutes from the December 20, 2006 GRAAP Telecon Attendees --------- Jim Pruyne Toshi Nakata Wolfgang Ziegler Discussion ---------- >From the most recent comments as shown in Toshi's spreadsheet in email dated 12/8: 1) Jim will edit the text accordingly. 2) Has been completed 3) Many affiliations are incorrect. We will remove them since it may be impossible to track them constantly. 4) Agreed, but outside scope. 5) It need not apply to a web service, so we need not specify more clearly. Section 3 does talk about this issue in itemized list part 2. 6) Agreed. Perhaps the ValueUnit and ValueExpr should be wrapped in a tag which can be replicated within the Penalty tag. Let's forward for discussion to Asit & Heiko and the mailing list. 7) Agreed, but we cannot fix it. 8) We think we've done this. 9) Done. 10) Done. 11) Jim will check to see if we should be more "spec. friendly" with a SHOULD or MAY statement somewhere. 12) Consensus is that Tiancho's suggestions make sense. 13 - 16) We'd like to consult the WSDL authors (Heiko) 17) Done. 18) This is as we intended, but we need some clarification text. Jim to do this. 19) Done. * We'll have our next telecon early in Jan., particularly when we have discussion on the open issues that leads us to believe we can resolve on the telecon. Most likely date is Jan. 10. * We still hope to make interop. discussion a primary topic at the next OGF meeting in North Carolina.

4 3

telecon on 12/20
by Jim Pruyne 20 Dec '06

20 Dec '06

Folks, Our last couple telecon attempts have fallen by the way-side. I suggest we try one more time before the end of the year at our usual time. NOTE: the dial-in details have changed. Please check below. We'd like to get organized to address the last round of public comments and complete the WS-Agreement spec. 9:00AM Central Standard Time US (GMT-0600) which should be: 10:00AM Eastern Standard Time US 1500 UK(?) 1600 Germany(?) 0000 Japan (sorry Toshi) Phone Number: 866-480-9967 in the US. 832-445-2343 for those outside the US. Conference code #8578310. --- Jim

1 0

exception handling in the current wsag spec
by Oliver Wäldrich 14 Dec '06

14 Dec '06

Reviewing the latest spec we have recognized that the fault handling that occures if an greement could not be created (currently 1 fault) is not sufficient for the protocol. There are several issues related to this: 1. currently only the fault ResourceUnknownFault is defined. That fault indicates that the in the EPR referenced AgreementFactory (instance) is not known to the server. 2. taking that in mind the createAgreement method should also define a ResourceUnavailableFault indicating that the AgreementFactory instance is known but it experiences problems at the time. 3. There should be a general CreateAgreementError that indicates that the creation of an agreement failed. There was a ContinuingFaultError defined for this, however it looks to me that the naming of the error produced some problems in the past and it was therefore removed. Perhaps it is feasible to reintroduce this general error but rename it. (e.g. AgreementCreationError) 4. It would be convenient to have some general error codes defined for things that can go wrong when creating agreements. I would suggest the following: <xs:complexType name="AgreementCreationErrorCodes"> <xs:sequence> <xs:element name="GeneralError" type="xs:int" fixed="0"/> <xs:element name="TemplateUnknownError" type="xs:int" fixed="1"/> <xs:element name="InvalidAgreementOfferError" type="xs:int" fixed="2"/> <xs:element name="CreationConstraintsViolationError" type="xs:int" fixed="3"/> </xs:sequence> </xs:complexType> Even if the public comment periode is over I would suggest having at least one separate exception in the schema that can be thrown if an agreement can't be created. Regards, Oliver Waeldrich ----------------------------------------------------------------------- Oliver Wäldrich Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2830; Fax: +49 2241 14 42830 CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms

1 0

Re: [GRAAP-WG] Updated Comments sheet
by Toshiyuki Nakata 08 Dec '06

08 Dec '06

Updated in order to reflect two minor points. No.17) 1) In section 7.1 (Agreement States), the text "Terminated - The terminated state means that an Agreement offer has been terminated by the Agreement Initiator and that the obligation no longer exists. This state MAY follow Pending, PendingAndTerminating, Observed or ObservedAndTerminating when the termination decision is made." implies that a transition from Pending directly to Terminating is possible, yet no such transition is depicted in the diagram of the agreement state model. => I am afraid this had been a cut & paste error on my part :-( :-( The pre-thanksgiving version already does have the necessary arrow. No.19) Section 8.2 Forms of Acceptance. The second last sentence: "The initiator MAY still determine the result of by other means such as querying the status of the resulting Agreement." appears to be missing some words between "of" and "by". => … Will be fixed.:-( Candidate is.. "The initiator MAY still determine the responder’s response to wsag:CreatePendingAgreement offer by other means such as querying the status of the resulting Agreement." #responder's response is a bit redundant.. ----- Toshiyuki Nakata 中田　登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509) >

1 0

Re: [GRAAP-WG] Updated Comments sheet
by Toshiyuki Nakata 06 Dec '06

06 Dec '06

Hi: Official Comment Period is over. The comments page cannot be accessed from the Top page. However, it still does exist as https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor/ discussion.rec_ws_agreement_spec_0 (or just click Cell C4 in the attached excel file..) Best Regards Toshi ----- Toshiyuki Nakata 中田　登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509) >

4 5

Re: [GRAAP-WG] New Public Comments List
by Toshiyuki Nakata 29 Nov '06

29 Nov '06

Hi： Apologies for being a nuisance but Andreas Savva-san (of Fujitsu Laboratories) has kindly taken care of the TOC (Thank you very much Andreas!) so posting again in case someone else also tries... Best Regards Toshi ----- Toshiyuki Nakata 中田　登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509) >

4 12

Re: [GRAAP-WG] New Public Comments List
by Tianchao Li 24 Nov '06

24 Nov '06

Hi, I've got the following responses after posting my proposal, which makes me feeling lost. What is the correct response to this question? Best regards, Tianchao

3 4

telecon on 11/22
by Jim Pruyne 23 Nov '06

23 Nov '06

We'll hold a telecon on November 22. On the last call, we decided to keep the same time in the US even after the daylight savings time change, and I'm doing my best to convert to other times below. If my conversions are incorrect, I apologize, and let me know so I can correct on future messages. 9:00AM Central Standard Time US (GMT-0600) which should be: 10:00AM Eastern Standard Time US 1500 UK(?) 1600 Germany(?) 0000 Japan (sorry Toshi) Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the US. Conference code #8578310. --- Jim

3 2

WS-Agreement link.
by Michael Parkin 21 Nov '06

21 Nov '06

Hi, A quick one: when I go to... http://www.ggf.org/gf/docs/?public_comment ...and click on the WS-Agreement Specification link I get a 404 message for the link http://www.ggf.org/Public_Comment_Docs/Documents/Oct-2006/WS- AgreementSpecificationDraftFinal_sp_tn_jpver_v2.pdf Is the document available yet? (Mind you, all the links in that column in that page appear broken). Thanks, Michael.

2 2