- graap-wg - lists.ogf.org

Fw: Call today?
by Heiko Ludwig 21 Jul '05

21 Jul '05

Let's use this number for today, as Jim cannot make it. Toll-free dial-in: 1-877-421-0025 Toll dial-in: 1-770-615-1242 Participant passcode: 598600 Heiko ----- Heiko Ludwig, Dr. rer. pol. IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 hludwig(a)us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 http://www.research.ibm.com/people/h/hludwig/ ----- Forwarded by Heiko Ludwig/Watson/IBM on 07/20/2005 11:17 AM ----- Heiko Ludwig/Watson/IBM wrote on 07/20/2005 11:05:25 AM: > The call is not activated. Is there a call right now? > > Heiko > > ----- > Heiko Ludwig, Dr. rer. pol. > IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 > hludwig(a)us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 > http://www.research.ibm.com/people/h/hludwig/ >

2 1

Re: Fw: Complex Constraints, our call today
by Heiko Ludwig 21 Jul '05

21 Jul '05

Dear GRAAP members, one of the last open issues for the next release of our spec was the semantics of compositors and the use of templates. There were some concerns about using compositors on a template as well as offer/agreement level, potentially introducing semantic ambiguity as to who must or can exercise options. After some discussion since the last call, Toshi, karl and I propose the following, to be discussed in today's call: 1. Compositors have agreement offer-level semantics only. They are not to be interpreted as choices of the initiator. 2. To express more flexibility, we propose to extend the CreationConstraints as follows: Add an attribute "mode" to Location that can be "insert" or "replace". If the value is set to replace, have another attribute "before" with values of positive integers and "end". With those instruments in addition to complex types in creation contraints we can express, for example, the following: ... <wsag:ServiceDescriptionTerm> <ns1:docroot> <ns1:fieldA>myfixedvalue</ns1:fieldB> <ns1:fieldB>default value</ns1:fieldB> </ns1:docroot> </wsag:ServiceDescriptionTerm> ... <CreationConstraints> <Item name="i1"> <Location mode="replace">//ns1:fieldB<Location> <xsd:restriction base="xsd:string"> <xsd:enumeration value="foo"/> <xsd:enumeration value="bar"/> </xsd:restriction> </Item> <Item name="i2"> <Location mode="insert" before="end">//ns1:docroot<Location> <xsd:sequence maxOccurs="128"> <xsd:element ref="ns1:fieldC"/> // You could inline a more complex element here. <xsd:choice minOccurs="0"> // To any fieldB element, we can add more arbitrary input, e.g., file names etc. <xs:element ref=wsgram:FileStageIn minOccurs=0 maxOccurs=unbounded/> </xsd:choice> </xsd:sequence> </Item> </CreationConstraints> Using the added expressivness of the Location element, we can deal with zero or more cardinalities. I propose to use schema for associating the occurrance of one element (fieldC) with another (fieldC). You cannot express this in either the Infoset notation nor the compositors. This way, we achieve a pretty powerful composition semantics, do not replicate expressivness covered by schema and don't need template-level compositors. Talk to you at 11 EST, Heiko ----- Heiko Ludwig, Dr. rer. pol. IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 hludwig(a)us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 http://www.research.ibm.com/people/h/hludwig/

2 3

Call today?
by Heiko Ludwig 20 Jul '05

20 Jul '05

The call is not activated. Is there a call right now? Heiko ----- Heiko Ludwig, Dr. rer. pol. IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 hludwig(a)us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 http://www.research.ibm.com/people/h/hludwig/

3 2

FYI, WS-Agreement Ontology at U of Georgia
by Heiko Ludwig 19 Jul '05

19 Jul '05

Dear GRAAP members, FYI, I just learned about this WS-Agreement ontology: http://lsdis.cs.uga.edu/projects/meteor-s/modulePages/index.php?page=2 It's interesting to browse. It is part of the Meteor-S project going on at the LSDIS Lab at U. of Georgia, under Amit Sheth: http://lsdis.cs.uga.edu/projects/meteor-s/ Heiko ----- Heiko Ludwig, Dr. rer. pol. IBM TJ Watson Research Center, PO Box 704, Yorktown, NY, 10598 hludwig(a)us.ibm.com, tel. +1 914 784 7160, mob. +1 646 675 8469 http://www.research.ibm.com/people/h/hludwig/

1 0

teleconference on 7/13
by Jim Pruyne 19 Jul '05

19 Jul '05

All, We'll resume our teleconference schedule this week. The times and numbers will be the same as usual: 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. My hope is to re-visit some of the issues raised during our "status" session at GGF, and define a plan for completing the spec. I'd also be interested to hear what people's opinions of GGF14 were. Thanks. --- Jim

3 5

no telecon on 7/6
by Jim Pruyne 06 Jul '05

06 Jul '05

Folks, I'm assuming that most of you are like me, and are still catching up after the week at GGF and the 4th holiday here in the US. So, I'm cancelling our call on the 6th, and we'll resume at the usual time on the 13th. --- Jim

1 0

4PM Session in "Ontario"
by Jim Pruyne 29 Jun '05

29 Jun '05

For anyone at GGF today, and planning to attend our 4:00 session, please note that it has been moved to the Ontario room. --- Jim

1 0

[Fwd: [ogsa-wg] GGF14 slide template]
by Jim Pruyne 27 Jun '05

27 Jun '05

Folks, This appears to be a nice slide template. For those presenting at sessions, you may want to use this. I plan to. --- Jim -------- Original Message -------- Subject: [ogsa-wg] GGF14 slide template Date: Mon, 27 Jun 2005 21:44:04 +0900 From: Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com> Organization: Fujitsu To: Ogsa-Wg <ogsa-wg(a)gridforum.org> Hi GGF14 presenters, As usual, I've upload slide template to GridForge. If you need ppt template, please use this. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_slide_template/… The file also includes template of session report for OGSA-WG #12 report session; Outcomes and achievements, Open Issues, and action items & next step. Session owners: Please fill in after your session and bring them to the session #12 (Thue 11am-12:30pm) or send them to me in advance. Thanks, -- Hiro Kishimoto

1 0

telecon minutes for 6/22
by Jim Pruyne 26 Jun '05

26 Jun '05

They are attached. We'll see folks at GGF next week. Have good travels. --- Jim Minutes from June 16 '05 Telecon Attendees --------- Jim Pruyne Toshiyuki Nakata Heiko Ludwig Wolfgang Ziegler Philip Wieder Agenda ------ - GGF Sessions: Three are scheduled. Status session on the 29th at 4:00. Experience session on the 29th at 6:00. Next steps session on the 30th at 11:00. For those presenting at the experience session, it would be helpful to cover these points to the extent that you can based on your experience. - What's the use case and background. - What portions of the spec. are you using, and what not? - What experience do you have that would suggest changes? - Implementation environment, and what makes implementation difficult? - What negotiation aspects are you using, or what requirements do you see yourself needing? - Status of needed updates: Item 3: Heiko--Now complete 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 20: Jim; make it like WSDM with a terminology section at the beginning--To be done Item 21: Schema updated as we suggested on last call. Item 22: To be discussed at GGF **Action: Jim to add to discussion for GGF. Item 24: Jim to contact Tiziana again about this. Item 29: Now complete Items 31-36: Now complete Others: Item 3: Toshi--complete 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. GGF Status Issues: - Compliance of offer with template - Expiration and Termination Time discussions - Uniqueness and identity of agreement (are EPRs the identity?) - Documentation annotations to be reviewed by Jim For the forward looking session - Primer - Negotiation - Key Performance Indicators (Asit?) - Resource Reservation (OGSA-RSS, Philip) - How to claim an agreement by referencing an agreement (e.g. in a SOAP header). Heiko to provide some material here - Charter discussion - Pushing the spec. out into other groups. What actions should we take? For example in to OGSA-EMS.

2 4

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