October 2006 - graap-wg - lists.ogf.org

Re: [GRAAP-WG] telecon on 10/25
by t-nakata＠cw.jp.nec.com 25 Oct '06

25 Oct '06

HI I AM RETURNING FROM A BIZ TRIP. WILL BE LATE BY 10-20MIN. REGARDS TOSHI >We're due for our next telecon on 10/25 at the usual time and phone number: > >9:00AM Central Daylight Time US (UTC-5) >which should be: >10:00AM Eastern Daylight Time US >1500 UK >1600 Germany >2300 Japan >2100 Thailand > >Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the >US. >Conference code #8578310. > > >--- Jim >-- > graap-wg mailing list > graap-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/graap-wg >

4 5

Re: [GRAAP-WG] telecon on 10/25
by t-nakata＠cw.jp.nec.com 25 Oct '06

25 Oct '06

HI I AM RETURNING FROM A BIZ TRIP. WILL BE LATE BY 10-20MIN. REGARDS TOSHI >We're due for our next telecon on 10/25 at the usual time and phone number: > >9:00AM Central Daylight Time US (UTC-5) >which should be: >10:00AM Eastern Daylight Time US >1500 UK >1600 Germany >2300 Japan >2100 Thailand > >Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the >US. >Conference code #8578310. > > >--- Jim >-- > graap-wg mailing list > graap-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/graap-wg >

1 0

telecon on 10/25
by Jim Pruyne 25 Oct '06

25 Oct '06

We're due for our next telecon on 10/25 at the usual time and phone number: 9:00AM Central Daylight Time US (UTC-5) which should be: 10:00AM Eastern Daylight Time US 1500 UK 1600 Germany 2300 Japan 2100 Thailand Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the US. Conference code #8578310. --- Jim

1 0

Suggested WSDL and XSD modification
by Tianchao Li 25 Oct '06

25 Oct '06

Hi, as you know, I'm implementing the WSAG on top of GT4. I've found some issues with the current WSDL and schema definition and suggest the corresponding modification is made. There are three kinds of issues that are concerened: (1) in AgreementState.wsdl <xs:complexType name="AgreementStatePropertiesType"> <xs:sequence> <xs:element ref="wsag:AgreementState" /> <xs:element ref="wsag:GuaranteeTermStateList" /> <xs:element ref="wsag:ServiceTermStateList" /> </xs:sequence> </xs:complexType> should be <xs:complexType name="AgreementStatePropertiesType"> <xs:sequence> <xs:element ref="wsag:AgreementState" /> <xs:element ref="wsag:GuaranteeTermState" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="wsag:ServiceTermState" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> It avoids the definition of additional type wsag:GuaranteeTermStateList and wsag:ServiceTermStateList. It is more consistent with the WSRF specification by giving individual access to each of the GuaranteeTermState and ServiceTermState items. Correspondingly, the current definition of wsag:GuaranteeTermStateList and wsag:ServiceTermStateList in agreement_state_types.xsd : <xsd:element name="GuaranteeTermStateList" type="wsag:GuaranteeTermStateListType" /> <xsd:element name="ServiceTermStateList" type="wsag:ServiceTermStateListType" /> should correspondingly be modified into <xsd:element name="GuaranteeTermState" type="wsag:GuaranteeTermStateType" /> <xsd:element name="ServiceTermState" type="wsag:ServiceTermStateType" /> (2) Related with issue (1), I stongly suggest wsag:AgreementStateType and wsag:GuaranteeTermStateType and wsag:ServiceTermStateType defined in the way as the attached agreement_state_types.xsd . Take ServiceTermState for example. Briefly speaking, it defines the ServiceTermState as a global element to support issue(1). AND, the ServiceTermStateType extends the TermStateType and the corresponding type of state is defined as an attribute extension. ---original--- <xsd:complexType name="GuaranteeTermStateListType"> <xsd:choice maxOccurs="unbounded"> <xsd:element name="NotDetermined" type="wsag:TermStateType" /> <xsd:element name="Fulfilled" type="wsag:TermStateType" /> <xsd:element name="Violated" type="wsag:TermStateType" /> </xsd:choice> </xsd:complexType> ---suggestion--- <xsd:element name="ServiceTermState" type="wsag:ServiceTermStateType" /> <xsd:complexType name="ServiceTermStateType"> <xsd:complexContent> <xsd:extension base="wsag:TermStateType"> <xsd:attribute name="state"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="NotReady" /> <xsd:enumeration value="Ready" /> <xsd:enumeration value="Completed" /> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> This has several practical advantages. First, if the state element has sub elements, the change of state will result into complicated XML process or Java object operations in the old definition and with the suggested definition you only need to change the state parameter. Second, both Globus and Axis 1.x has problem in stub generation for xsd:choice maxOccurs="unbounded". Third, this definition is more consistent with the style of definition in agreement_types.xsd (look at the different term type definitions there). After all, this change does not result into the loss of constraint power and do not require modification of the current specification except for the XSD file itself. Please see the attached agreement_state_types.xsd file for modifications to other types. (3) in one of my previous posts, I asked about the exact meaning of wsag:AgreementServiceReferenceList as a sub element of wsag:AgreementProperties and got no answer yet. It seems to be a duplication of the information in ServiceReference element of ServiceDescriptionTerm, which is another sub element of wsag:AgreementProperties. If I'm correct, then it should be removed. Correct me if I'm wrong. And if you agree, please vote. Best regards, Tianchao Li ============================== Institut fuer Informatik, TU Muenchen Germany http://www.lrr.in.tum.de/~lit

1 1

Failure in agreement_types.xsd
by Oliver Wäldrich 13 Oct '06

13 Oct '06

Hallo, I found a failure in the agreement_types.xsd. The type AgreementServiceReferenceListType is currently delared as follows: <xs:complexType name="AgreementServiceReferenceListType"> <xs:sequence> <xs:element name="ServiceReference" type="wsag:AgreementServiceReferenceType" /> </xs:sequence> <xs:attribute name="ServiceName" type="xs:NCName" /> </xs:complexType> However, since this is a list type the element ServiceReference should be declared as unbounded: <xs:complexType name="AgreementServiceReferenceListType"> <xs:sequence> <xs:element name="ServiceReference" type="wsag:AgreementServiceReferenceType" maxOccurs="unbounded" /> </xs:sequence> <xs:attribute name="ServiceName" type="xs:NCName" /> </xs:complexType> Regards, Oliver ----------------------------------------------------------------------- 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

2 1

minutes from Sep 27 telecon
by Jim Pruyne 11 Oct '06

11 Oct '06

Are attached. The next call will be in two weeks, on Oct. 11. --- Jim Minutes from the September 27, 2006 GRAAP Telecon Attendees --------- Jim Pruyne Asit Dan Toshi Nakata Tianchao Li(?) Discussion ---------- - GFSG is recommending a new 30-day public comment period on WS-Agreement due to the large number of comments we received previously. - Part of the suggestion is to solicit comments from outside of GGF (e.g. from OASIS). - Toshi can work on a change summary by extracting from the slides he did at previous GGFs. - Jim will apply the new header stuff to the document and will communicate with Greg Newby. - At GGF17: - Workshop for implementers at GGF was on intro. day and we heard from various approaches, including as a basis for higher-level operations such as negotiation. They were looking for the spec. to get stabilized. - Approach to getting a primer done is to annotate the slides from the tutorial given by Toshi and Heiko and make those more widely distributed. - Telecons will be every other week with a focus on the implementations. - Next GGF will be done more workshop style during the regular GGF session days to help the attendance and support. - The approach to interoperability is to try to use a subset of JSDL as the domain shared across implementations. We'll see what interoperability processes have been used in other WGs. - Negotiation was also discussed in a session. There's quite a bit of interest, but getting a spec. done in this area may be difficult. - Asit recommends that we get alignment with outside groups as a focus for the WG going forward as it is needed to see adoption of the spec.

4 5

telecon on 10/11
by Jim Pruyne 11 Oct '06

11 Oct '06

Folks, Tomorrow is our scheduled day for our next bi-weekly telecon. Details are below. 9:00AM Central Daylight Time US (UTC-5) which should be: 10:00AM Eastern Daylight Time US 1500 UK 1600 Germany 2300 Japan 2100 Thailand Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the US. Conference code #8578310. We'll update the status of the WS-Agreement doc. and how we're responding to GFSG's request for an additional 30-day public comment period. --- Jim

1 0