- From: Steve Ross-Talbot <steve@pi4tech.com>
- Date: Tue, 9 Aug 2005 19:04:38 +0100
- To: 'WS-Choreography List' <public-ws-chor@w3.org>
Based on http://www.w3.org/2002/ws/chor/5/07/snapshotCR.html Abstract "coordination protocol and adressing are implementation details." SHOULD READ "coordination protocol and addressing are implementation details." 1.1 Notational Conventions "in the specification and please notify W3C." SHOULD READ "in the specification. Should such an error come to light please notify W3C." 2. Model Overview "A ParticipantType is grouping together those parts of the observable behavior that must be implemented by the same logical entity or organization. A logical entity or organization may represent more than one party within a Choreography." SHOULD READ "A ParticipantType is a grouping together of those parts of the observable behavior that must be implemented by the same logical entity or organization. A logical entity or organization may represent more than one party within a Choreography." 3.5 Semantics "contents of thedescription sub-element." SHOULD READ "contents of the description sub-element." "The semantics of any element or attribute from the WS-CDL namespace SHOULD remain unchanged and MUST not be contradicted." SHOULD READ "The semantics of any element or attribute from the WS-CDL namespace SHOULD remain unchanged and MUST NOT be contradicted." 4.2 Relationship Types " RelationshipType identifies the roleTypes and Behaviors" SHOULD READ " RelationshipType identifies the roleTypes and behaviors" 4.4 Channel Types "A ChannelType MUST describe the roleType and the type of a party reference" SHOULD ADD AT END OF PARA "Where a party is defined as ......" - subject of discussion 5.1 Information Types "Information Types describe the type of information used within a Choreography. By introducing this abstraction, a Choreography definition avoids referencing directly the data types, as defined within a WSDL document or an XML Schema document" SHOULD READ "Information Types describe the type of information used within a Choreography. By introducing this abstraction, a Choreography definition avoids directly referencing the data types, as defined within a WSDL document or an XML Schema document" 5.2 Variables "Channel Capturing Variables. For example, a Channel Variable could contain information such as; the URL to which the message could be sent, the policies that are to be applied (e.g. security), whether or not reliable messaging is to be used, etc." QUESTION: How and where exactly is this extra information (policies, security and reliable messaging) expressed. The reader is left wondering. 5.3 Expressions "The language used in WS-CDL for specifying expressions and query or conditional predicates is XPath 1.0." SHOULD READ "The language used in WS-CDL for specifying expressions and queries or conditional predicates is XPath 1.0." 5.3.1 WS-CDL Supplied functions "The roleTypeName . parameter is OPTIONAL." SHOULD READ "The roleTypeName parameter is OPTIONAL." NOTE: This occurs in getCurrentTime, getCurrentDate, hasDurationPassed, isVariableAvailable "The values of the status can be 'enabled', 'completed-successfully', 'completed-unsuccessfully', 'closed' or 'instance-unknown'. The 'instance-unknown' status is encountered when this function is invoked when the choreography has not been enabled. The other valid transitions of the choreography status are outlined in Section 5.7, Choreography Life-line." SHOULD READ "The values of the status can be 'enabled', 'completed-successfully', 'completed-unsuccessfully', 'closed' or 'instance-unknown'. The 'instance-unknown' status is encountered when this function is invoked and when the choreography has not been enabled. The other valid transitions of the choreography status are outlined in Section 5.7, Choreography Life-line." 5.6 Work Units "In the following Work Unit, the guard condition waits for an alignment Interaction to happen between the "Customer" Role and the "Retailer" Role:" SHOULD READ "In the following Work Unit, the guard condition waits for an alignment Interaction to happen between the "Customer" Role and the "Retailer" Role. In this example the work unit waits until the purchase order at the buyer and seller roles have been aligned based on a previous interaction. Alignment means that both roles have agreement on the values of their respective purchase order variables." 5.7 Choreography Lifeline "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 "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." 5.8 Choreography Exception Handling " Interaction Failures, for example the sending of a message did not succeed Protocol Based Exchange failures, for example no acknowledgement was received as part of a reliable messaging protocol Security failures, for example a Message was rejected by a recipient because the digital signature was not valid Timeout errors, for example an Interaction did not complete within the required time Validation Errors, for example an XML "Order" document was not well formed or did not conform to its XML-Schema definition" QUESTION: How do I reference these exceptions in a CDL description? THATS IT FOLKS CHEERS STEVE T
Received on Tuesday, 9 August 2005 18:05:06 UTC