- From: Martin Chapman <martin.chapman@oracle.com>
- Date: Tue, 16 Aug 2005 19:17:21 +0100
- To: "'Charlton Barreto'" <charlton_b@mac.com>, "'WS-Choreography List'" <public-ws-chor@w3.org>
BTW I don’t think SOAP is an acronym these days! >-----Original Message----- >From: public-ws-chor-request@w3.org >[mailto:public-ws-chor-request@w3.org] On Behalf Of Charlton Barreto >Sent: Tuesday, August 09, 2005 8:42 PM >To: 'WS-Choreography List' >Subject: Changes to CR draft for WS-CDL > > > >Based on http://www.w3.org/2002/ws/chor/5/07/snapshotCR.html > >1. Introduction >"WSDL 2.0 also supports types defined in other systems such as >DTD, RelaxNG, and RDF" This seems out of place, since this >sentence is already included in the list of Web Service >components. I would suggest striking this redundant reference. > >"* SOAP: defines the basic formatting...." >SHOULD READ >"* Simple Object Access Protocol (SOAP): defines the basic >formatting...." > >"* WSDL: describes the static interface of a Web Service...." >SHOULD READ >"* Web Services Description Language (WSDL): describes the >static interface of a Web Service...." > >1.1 Notational Conventions >"This specification uses an informal syntax to describe the >XML grammar of a WS-CDL document:" SHOULD READ "This >specification uses an informal syntax to describe the XML >grammar of a WS-Choreography Definition Language (WS-CDL) document:" > >"* <-- extensibility element --> is a placeholder...." >SHOULD READ >"* "<-- extensibility element -->" is a placeholder...." > >"* Examples starting with <?xml contain enough >information...." SHOULD READ >"* Examples starting with "<?xml" contain enough information...." > >1.2 Purpose of the Choreography Description Language >"The advantage of a contract based on a global viewpoint as >opposed to anyone...." SHOULD READ >"The advantage of a contract based on a global viewpoint as >opposed to any one...." > >"It is the intent of CDL that the conformance of each >implementation to the common view expressed in CDL is easy to >determine." SHOULD READ "It is the intent of WS-CDL that the >conformance of each implementation to the common view >expressed therein is easy to determine." > >3.3 WS-CDL document Naming and Linking >"A reference to a definition is made using a QName." >SHOULD READ >"A reference to a definition MUST be made using a QName." > >3.5 Semantics >"Where machine processable, WS-CDL parsers are not required to >parse the contents of thedescription sub-element." SHOULD READ >"Where machine processable, WS-CDL parsers are not required to >parse the contents of the description sub-element." > >4.2 Relationship Types >"For example if the purchase...." >SHOULD READ >"For example, if the purchase...." > >5.5 Choreographies >"A Choreography defines re-usable common rules, that >govern...." SHOULD READ "A Choreography defines re-usable >common rules that govern...." > >"This Boolean conditional expression MUST use short circuit >evaluation according to the XPath left to right rules." SHOULD >READ "This Boolean conditional expression MUST use short >circuit evaluation according to the XPath lexical rules." > >5.6 WorkUnits >In two places: >"This Boolean conditional expression MUST use short circuit >evaluation according to the XPath left to right rules." SHOULD >READ "This Boolean conditional expression MUST use short >circuit evaluation according to the XPath lexical rules." > >5.7 Choreography Life-line >"Distinct instances of a top-level or enclosed choreography, >if they ever run in a temporarily overlapped fashion, must not >interfere with each other in their involved communication >actions." SHOULD READ "Distinct instances of a top-level or >enclosed choreography, if they ever run in a temporarily >overlapped fashion, MUST NOT interfere with each other in >their involved communication actions." > >"In other words, given a choreography description, >interactions belonging to one of its instances must be >logically, hence executionally, distinguishable from those in >another." SHOULD READ "In other words, given a choreography >description, interactions belonging to one of its instances >must be logically, and hence executionally, distinguishable >from those in another." > >6.2.3 Interaction Syntax >"Within the record element, the when attribute specifies if a >recording happens before or after a send or "before" or >"after" a receive of a message at a Role in a Request or a >Response exchange or when a timeout has expired." SHOULD READ >"Within the record element, the when attribute specifies if a >recording happens before or after a send, or before or after a >receive of a message at a Role in a Request or a Response >exchange, or when a timeout has expired." > >6.3 Composing Choreographies >"For example if two separate Choreographies were defined as >follows:" SHOULD READ "For example, if two separate >Choreographies were defined as follows:" > >8.1 Conforming WS-CDL documents >"A CDL document...." >SHOULD READ >"A WS-CDL document...." > >8.2 Endpoint conformance >"A conformant CDL endpoint is an entity that correctly >implements the observable behaviour of a role defined in a CDL >choreography." SHOULD READ "A conformant WS-CDL endpoint is an >entity that correctly implements the observable behaviour of a >role defined in a choreography." > >Cheers, > >-Charlton. > >
Received on Tuesday, 16 August 2005 18:16:31 UTC