They are attached. --- Jim Minutes from Apr. 27 '05 Telecon Attendees --------- Jim Pruyne Philipp Wieder Asit Dan Karl Czajkowski Heiko Ludwig Agenda ------ - Item 26: This seems to be a hold over from negotiation. It should be removed. Note that xsd/wsdl is probably not kept consistent with the doc. in general at this point. - Item 28: Consistent/standard use of compositors. What is WS-Policy state at this point? **Action: we cannot reference WS-Policy as we do other specs. given its state. We could re-sync. with WS-Policy to get back to being more consistent with it, but it will not satisfy the comment that's looking for a stand-alone spec. that we can reference. Asit will look at this. - Item 25: Change things over to making the assesment interval contain a penalty and/or a reward. **Action: Heiko to make this change. - Item 33: Explain service reference better. **Action: Heiko will basically paste in the examples he's alredy done in the comment. - Item 30: Having these terms defined is really useful, but defining terms related to agreements on WS is outside the current scope. We'd love to see a companion spec., but it needs to stay outside the scope of the current spec.
are attached.. Best Regards Toshi -- Toshiyuki Nakata t-nakata@cw.jp.nec.com +81-44-431-7653 (NEC Internal 8-22-60210)
Hello: Sorry I could not make it yesterday. (Had intended to but seem to have lost conciousness.(ie, fell asleep)) Best Regards Toshi Toshiyuki Nakata wrote:
are attached..
Best Regards Toshi
-- Toshiyuki Nakata t-nakata@cw.jp.nec.com +81-44-431-7653 (NEC Internal 8-22-60210)
Hi, during the implementation of the current spec an inconsistency between the description of the Term Compositor Structure (page 16 in the latest sourceforge version of the spec) and the schema description on page 46. We suggest to replace this description: <xs:element name="All" type="wsag:TermCompositorType"/> <xs:complexType name="TermCompositorType"> <xs:sequence> <xs:choice maxOccurs="unbounded"> <xs:element name="ExactlyOne" type="wsag:TermCompositorType"/> <xs:element name="OneOrMore" type="wsag:TermCompositorType"/> <xs:element ref="wsag:All"/> <xs:element name="ServiceDescriptionTerm" type="wsag:ServiceDescriptionTermType"/> <xs:element name="ServiceReference" type="wsag:ServiceReferenceType"/> <xs:element name="ServiceProperties" type="wsag:ServicePropertiesType"/> <xs:element name="GuaranteeTerm" type="wsag:GuaranteeTermType"/> </xs:choice> </xs:sequence> </xs:complexType> with the following: <xs:element name="All" type="wsag:TermCompositorType"/> <xs:complexType name="TermCompositorType"> <xs:sequence> <xs:choice maxOccurs="unbounded"> <xs:element name="ExactlyOne" type="wsag:TermCompositorType"/> <xs:element name="OneOrMore" type="wsag:TermCompositorType"/> <xs:element ref="wsag:All"/> <xs:element name="Service" type="wsag:ServiceType"/> </xs:choice> </xs:sequence> </xs:complexType> <xs:complexType name="ServiceType"> <xs:sequence> <xs:element name="ServiceDescriptionTerm" type="wsag:ServiceDescriptionTermType" maxOccurs="unbounded"/> <xs:element name="ServiceReference" type="wsag:ServiceReferenceType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="ServiceProperties" type="wsag:ServicePropertiesType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="GuaranteeTerm" type="wsag:GuaranteeTermType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> In addition to allow the implementation of what is described in page 16 the structure is more easy to understand after separating the definition of the ServiceType object from the TermCompositorType Best regards Wolfgang -- 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"
participants (3)
-
Jim Pruyne -
Toshiyuki Nakata -
Wolfgang Ziegler