- graap-wg - lists.ogf.org

Comments WS-AG Spec
by Dominic Battre 23 Jun '05

23 Jun '05

Hi. I haven't followed the mailing list very closely recently, so I read the current specification again after a long absence. I don't know, whether you are still looking for comments, but these are some points, that came into my mind. Some typos and inconsistencies and some requests for possible clarification. Have a good travel to Chicago. Section 1.3 Namespace The prefix should be xsi instead of Xsi (lower case x) Section 4.1 Agreement Context most objects are optional, so I think the gray box should have several ? instead of + to indicate that. it should be /wsag:Context/{any} and /wsag:Context/@{anyAttribute} instead of /wsp:Context/... Section 4.2.1 Term Types: <wsag:Term Name="xsd:NCName?"/> -> <wsag:Term Name="xsd:NCName"?/> (moved ?) Section 4.2.5.1 Variable Set wsag:Metric="xsd:QName"? in gray box (new ?) as "This element is optional and..." Section 4.2.6.3.3 Preference I am a little bit confused about the /wsag:Preference/wsag:ServiceTermReference: what does it reference? /wsag:ServiceDescriptionTerm@wsag:Name? in that case, the type should be xs:NCName How come, you don't use wsag:Location? "/wsag:Preference/wsag:Utility This element can appear multiple times, one corresponding to each ServiceTermReference." Where is the connection of Utility to the ServiceTermReference? First S.T.R. <> first utility, second S.T.R. <> second utility, ...? I have read the schema files and from that I think it is better to put <wsag:Preference> { <wsag:ServiceTermReference>xsd:string</wsag:ServiceTermReference> <wsag:Utility>xsd:float</wsag:Utility> } + </wsag:Preference> into the gray box. Section 6 Compliance of Offers with Templates "In order for an agreement offer to be accepted, it MUST comply with at least one template advertised by the agreement provider to which the offer is submitted." In section 4.1 Agreement Context, you have requested that the /wsag:Context/wsag:TemplateName points to exactly one agreement template. I think it would help to add statements whether it is allowed to - add Terms that are not specified in the AgreementTemplate's Terms section, - delete Terms from the Agreement, that are part of the AgreementTemplate's Terms section but are not referenced in its creation constraints. As the added or deleted terms are not expressed in the wsag:CreationConstraints section in these cases, I assume that both operations are valid. Section 7.2 Guarantee States The guarantee states describe the current situation, but what is the semantic of the current situation? Example "I request a response time of <1 sec.", this response time has been exceeded for 1 hour yesterday, but we are within the limits again. Is the guarantee to *always* offer response times <1 sec fulfilled or not? Appendix Template <wsag:Item wsag:name="argumentsTerm"> <wsag:Location>//wsag:ServiceDescriptionTerm/job:arguments</wsag:Location>  </wsag:Item> is "allowed" the right wording? From how I interpret the WSAG specification, it is required. Best, Dominic

1 0

minutes from 6/7 teleconference
by Jim Pruyne 22 Jun '05

22 Jun '05

They are attached. Next meeting will be on 6/16 at the usual time of day and phone numbers. --- Jim Minutes from June 7 '05 Telecon Attendees --------- Jim Pruyne Asit Dan Toshiyuki Nakata Heiko Ludwig Philip Wieder Agenda ------ - GGF Sessions: Three are requested. Spec. work, Implementations, and future looking. Implementations will have about 15mins. each, and we'll end with about 30-mins of discussion leading to ideas about how interop. will proceed. **Action: Jim to send out requested set of points to be covered in the implementations presentations. - OGSA Roadmap document: Will include section on ws-agreement as a "crucial" spec. to ogsa. Jim sent feedback on this to encourage vision beyond just job management. Toshi discussed with Hiro, chair of OGSA-WG, and idea is that ws-agreement fits more into the "EMS" section of ogsa rather than the "BES" as BES is more simplistic and simply a "container." **Action: Jim to circulate the roadmap document to the graap mailing list. Philip involved with some of the EMS related work such as "RSS." There will be an RSS BoF at GGF. Philip can act as liason to some of the work in OGSA in this area. - Status of needed updates: **Action: Heiko will act as integration point over the next week, and send status of updates to Toshi to update his spreadsheet. Item 1: Toshi Item 3: Related Agreement removal: Heiko Item 4: Heiko Item 5: Toshi Item 8: Heiko Item 9: Same as 3 Item 10: Toshi Item 11: Heiko Item 16, 17: Heiko Item 18: Handled as part as number 5 Item 19: Heiko Item 20: Jim; make it like WSDM with a terminology section at the beginning Item 21: Asit Item 22: Need to discuss on June 16 Item 24: Jim to contact Tiziana again about this. Item 26: Toshi will lok into this with Karl Item 27: Heiko Item 29: Extensibility of term types; Heiko Items 31-36: All fall into guarantee term updates; Heiko Others: Item 3: Toshi Item 4: Related to 26 Item 5: Asit to provide some text to Toshi Example updates: Asit WSDL updates and passing through XML validators: Heiko and Jim to address when other changes are complete

4 5

minutes from Jun16 telecon
by Jim Pruyne 22 Jun '05

22 Jun '05

They are attached... --- Jim Minutes from June 16 '05 Telecon Attendees --------- Jim Pruyne Toshiyuki Nakata Heiko Ludwig Wolfgang Ziegler Karl Czajkowski Agenda ------ - GGF Sessions: Three are scheduled. Experience session on the 28th at 2:30. Status session on the 29th at 4:00. Next steps session on the 30th at 11:00. Joint session with CDDLM on the 30th at 9:00. - Status of needed updates: Item 1: Toshi-- complete Item 3: Related Agreement removal: Heiko--Small things left Item 4: Heiko--Complete Item 5: Toshi--Complete Item 8: Heiko--Guarantee term has obliged party added, but we did not have anything being explicit about who is providing the service. Service provider id has been added to the context. This sounds good since if it were in terms it could not be filled in by the provider when an offer agreement is accepted since the terms cannot be updated upon acceptance. Item 9: Same as 3--complete Item 10: Toshi--complete, used "evolving instutitional" as in OGSA roadmap. Item 11: Heiko-- complete Item 16, 17: Heiko--Complete accept for section refs. Item 18: Handled as part as number 5--Expiration and termination time added to the glossary **Action: Jim to do this and update discussion in 4.1. More thoughts on adding things to glossary possibly coming from Wolfgang. Item 19: Heiko-- complete Item 20: Jim; make it like WSDM with a terminology section at the beginning--To be done Item 21: Asit--complete, but need review of schema work in 9.5.1 and 9.5.2.-- perhaps change to xsd:any##other Item 22: Need to discuss on June 16-- Defer to next call or GGF discussion Item 24: Jim to contact Tiziana again about this. Item 26: Toshi will look into this with Karl--Should be post-1.0 of WS-Agreement since faults in WSDL and language mappings are not good. This item itself is complete. Item 27: Heiko--complete Item 29: Extensibility of term types; Heiko--complete but check with Heiko Items 31-36: All fall into guarantee term updates; Heiko Others: Item 3: Toshi Item 4: Related to 26 Item 5: Asit to provide some text to Toshi--nothing from Asit yet. **Action: Asit to send. **Action: Jim to clean-up WG members/acknowledgement/author list. Steve T. to get Univa on his author line. Check with Ming Xu on his affiliation if we can find him. **Action: Jim to do his actions and editting pass on most recent version and provide back version to the group prior to 6/22 call.

2 1

OGSA Roadmap document
by Jim Pruyne 08 Jun '05

08 Jun '05

Here's the roadmap document for OGSA. There are references to WS-Agreement in here, so people may be interested in seeing what OGSA is saying about WS-Agreement. The link is below: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-roadma… --- Jim

3 3

telecon reminder for 6/7
by Jim Pruyne 07 Jun '05

07 Jun '05

All, Just a reminder that we're having our telecon on Tues. June 7 this week, but at the normal times and numbers: Start Time: 10:00 AM Central US 11:00 AM Eastern US 8:00 AM Pacific US 1700 Germany 1600 UK Midnight Japan Dial in numbers: 866-673-8466 or 702-477-6031 code 8578310. --- Jim

1 0

Re: [graap-wg] WS-Agreement spec
by Toshiyuki Nakata 06 Jun '05

06 Jun '05

Hi: Rather than fighting with MS-Word, I decided that adding entries in the Excel sheet to mark what is reflected and what is not reflected in the spec would be quicker and gives the whole scope better.. So I added two columns in Public Comments. I hope they make the situation more clearer.. Best Regards PS in Page 15 there are two '/wsp:context' should these be '/wsag:context'?? Toshiyuki Nakata wrote: > Hello: > I tried to see if the various resolutions for the comments had been > reflected. > (I've only got to Comment 11, but there are many that had not been > reflected in the spec yet.) > > I've put the resolution part from the comments table as comments + ID. > I've attached the DOC (in zip file) in this file. > > #Funny thing is when I save the info, the comment Author's name > changed from Toshi to Author.. > #I've never experienced this before, and this is a nuisance. If any > one knows how to stop this.. > #For the time being, I've added TOSHI in front of the comments to show > that they are the ones. I put in > > It is going to take some time for me to check all these, so I am going > to post incrementally. > Best Regards > Toshi > > Jim Pruyne wrote: > >> As always, the most recent draft can be found at: >> >> https://forge.gridforum.org/projects/graap-wg/document/WS-AgreementSpecific… >> >> >> --- Jim >> >> Toshiyuki Nakata wrote: >> >>> Hi: >>> Could some one please tell me the URL of the newest >>> draft of the spec so that I can check? >>> >>> Best Regards >>> Toshi >>> >> >> > -- Toshiyuki Nakata ????? Internet System Laboratories NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60210) Fax +81-44-431-7681 (NEC Internal 22-60219)

1 2

Request for WS-Agreement Implementation experience and plans
by Jim Pruyne 02 Jun '05

02 Jun '05

All, At GGF14, we'd like to host a session on people's experience implementing and plans for using WS-Agreement. To do this, we need participation from those who have this experience. So, I'm requesting that anyone who's implemented all or parts of WS-Agreement take part in this session. Also, anyone who is evaluating WS-Agreement for a specific purpose is welcome to present. The goal is to expose this experience to all, and ideally capture shared understanding of what's worked, what hasn't, and what issues we see when considering interoperable WS-Agreement implementations. We'd also like to find out what common scenarios or use cases we can derive which will help with further discussion in the future. Anyone who can contribute, please let me, and preferablly the entire mailing list know by replying to this, and I'd like to talk with you further about participating in this session at GGF. Thanks! --- Jim

3 4

change in telecon schedule
by Jim Pruyne 01 Jun '05

01 Jun '05

All, Due to conflicts with my schedule, we are slightly changing the teleconference schedule for the next two weeks. Next week, the teleconference will be on Tues. June 7 rather than Wed. June 8. The following week, the teleconference will be on Thurs. June 16 rather than Wed. June 15. The time of day will remain the same (10AM Central time US as the basis for conversions) Reminders will hopefully follow, but may not, particularly for the one on the 16th. --- Jim

1 0

minutes from 5/18 telecon
by Jim Pruyne 25 May '05

25 May '05

[These are last week's minutes since, apparently, my messages to GRAAP were not going out for the last week or two] Minutes are attached. We'll meet again next week at the usual time. --- Jim Minutes from May 18 '05 Telecon Attendees --------- Jim Pruyne Wolfgang Zeigler Heiko Ludwig Asit Dan Agenda ------ - GGF Plans: We probably need a session on what's next for GRAAP assuming WS-Agreement spec. work is mostly complete. * One session could be planning a primer. Would people show up for such a session and commit to following-up? * Presentations on implementations in one session: Toshi? Wolfgang? Asit on Alphaworks? Globus/WS-GRAM? This could get us started toward interop. work as well as summarizing domains of use. We'll send out a call for participants in this session on the list. ** We should have a pointer on our group page to on-going implementation work. * Planning work on definition on guarantee term description as a possible additional session. - Asit on term compositor and WS-Policy: When we look at an agreement (not a template) there does not seem to be compelling use cases for specifying alternatives using term compositor with the guarantee and service description terms. There are cases for alternatives in the guarantee terms (e.g. times when guarantee terms are applicable), but those cases are already covered in the guarantee term structure, i.e., by using qualifying condition. Similarly, alternative service term selection as expression of service level objective is already covered with the current guarantee term structure.So, perhaps it is best to remove the compositor from the agreement structure. Additionally, if people really want alternatives in their service description, they can use compositors in their domain-specific portion of the service description. This leads to the issue of what about the template where we do need some alternatives. We'd need to introduce back a notion along the lines of a "service selection" clause to talk about groups of service description terms and associated guarantee terms. * Discussion said that this actually makes sense. Not having alternatives in a final agreement seems to be correct. * However, this seems to be a late time to be changing the structure of the agreement so basically. * Perhaps such a change would really come about in a post-1.0 version of WS-Agreement, particularly when we have some more implementation experience. * General consensus is that it is too late to change now, so unless further discussion pushes us, that's the (non-)action we'll take on this for the current spec.

1 0

test, please ignore
by Wolfgang Ziegler 25 May '05

25 May '05

-- Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258 Fax: +49 2241 14 42258 http://www.scai.fraunhofer.de "Heut ist nicht so kalt wie gestern, trotzdem dass heut kaelter ist"

1 0