Status | Author | Line(s) / Section | Original text | Replacement text | Comment | Resolution |
Greg Ritzinger | 153 | · The syntax appears as an XML instance, but the values indicate the data types instead of values. | Maybe this should be re-worded. I don’t understand it as is. | |||
Greg Ritzinger | 172 | Business or other activities that involve multiple different organizations or independent processes that collaborate using the Web Services technology can be successful if they are properly integrated. | Business or other activities that involve multiple different organizations or independent processes that collaborate using the Web Services technology can only be successful if they are properly integrated. | |||
Greg Ritzinger | 189 | jointly. Each entity may then implement its portion of the Choreography as determined by t heir common view. | jointly. Each entity may then implement its portion of the Choreography as determined by t he common view. | I think we are talking about the global view, correct? | ||
Greg Ritzinger | 198 | The respective Business analysts at both companies agree upon the | The respective business analysts at both companies agree upon the | |||
Greg Ritzinger | 205 | In this example, Choreography specifies the interoperability and interactions between | In this example, a Choreography specifies the interoperability and interactions between | |||
Greg Ritzinger | 213 | complementary observable behavior, where message exchanges occur, when the | complementary observable behavior, where message exchanges occur, and when the | |||
Greg Ritzinger | 216 | Some additional goals of this definition language are to permit: | Some additional goals of this definition language are: | The items in this bulleted list need to be aligned (grammatically) with this statement. | ||
Greg Ritzinger | 229 | · Modular. Choreographies can be defined using an "import" facility that allows a choreography to be created from components contained in several different Choreographies | Is “components” the best term to use? Alt: segments, sections? | |||
Greg Ritzinger | 232 | Information Driven. Choreographies describe how participants that take part in Choreographies maintain where they are in the Choreography by recording their exchanged information, and the observable state changes caused by these exchanges of | Information Driven. Describe how participants that take part in Choreographies can maintain where they are in the Choreography by recording their exchanged information, the observable state changes caused by these exchanges of | |||
Greg Ritzinger | 239 | · Exception Handling. Choreographies can define how exceptional or unusual conditions that occur whilst the choreography is performed are handled | · Exception Handling. Choreographies can define how exceptional or unusual conditions that occur while the choreography is performed are handled | |||
Greg Ritzinger | 257 | A Choreography Language is not
an "executable business process description language" [16' 17' 18'
19' 20] or an implementation language [23]. The role of specifying the
execution logic of an application will be covered by these specifications; by
enabling the definition of the control flows (such as conditional'
sequential' parallel and exceptional execution) and the rules for
consistently managing their non-observable business data. |
A Choreography Language is not an "executable business process description language" [16, 17, 18, 19, 20] or an implementation language [23]. The role of specifying the execution logic of an application will be covered by these specifications. | |||
Greg Ritzinger | 284 | Participants, Roles and Relationships - In a Choreography information is always exchanged between Participants, within the same or across trust boundaries | Participants, Roles and Relationships - In a Choreography information is always exchanged between Participants within the same or across trust boundaries | Need to include something about roles and relationships too. Perhaps each of the items enumerated in the first two bullets should have its own bullet in order to "stand out". | ||
Greg Ritzinger | 291 | Choreographies - A Choreography allows defining collaborations between peer-to-peer interacting business processes: | Choreographies - A Choreography allows defining collaborations between interacting peer-to-peer business processes: | |||
Greg Ritzinger | 295 | Choreography Life-line expresses the progression of a collaboration. Initially, the collaboration is started at a specific business process, then work is performed within it and finally it completes, either normally or abnormally | What is 'it', the business process or the choreography? | |||
Greg Ritzinger | 303 | Choreography Finalizer Block - describes how to specify what additional interactions should occur to reverse the effect of an earlier successfully completed choreography | Coming from a programming perspective, a finalize block is a part of a try block that is executed in either the normal or abnormal execution cases. I think we should stick to convention and use the term "compensate" or something close to it. | |||
Greg Ritzinger | 322 | A WS-CDL document is simply a set of definitions. The WS-CDL definitions are named constructs that can be referenced. There is a package element at the root' and individual Choreography definitions inside. | A WS-CDL document is simply a set of definitions. Each definition is a named construct that can be referenced. There is a package element at the root and the individual Choreography definitions are inside. | Insert a schema or document example here. | ||
Greg Ritzinger | 327 | A WS-CDL package contains a set of one or more Choreographies and a set of one or more collaboration type definitions, allowing the various types whose use may be wider than a single Choreography to be defined once. | Types of what? At this point I have no idea what a "collaboration type definition" is or how it affects this paragraph. Either define it or link to its definition. | |||
Greg Ritzinger | 381 | WS-CDL documents MUST be assigned a name attribute of type NCNAME that serves as a lightweight form of documentation. The targetNamespace attribute of type URI MUST be specified. The URI MUST NOT be a relative URI. A reference to a definition is made using a QName. Each definition type has its own name scope. Names within a name scope MUST be unique within a WS-CDL document. The resolution of QNames in WS-CDL is similar to the resolution of QNames described by the XML Schemas specification [11]. | • WS-CDL documents MUST be assigned a name
attribute of type NCNAME that serves as a lightweight form of
documentation. • The targetNamespace
attribute of type URI MUST be specified and the URI MUST be absolute. A reference to a definition is made using a
QName. • Each definition type has its own name scope. • Names within a name scope MUST be unique
within a WS-CDL document. • The
resolution of QNames in WS-CDL is similar to the resolution of QNames
described by the XML Schemas specification [11]. |
|||
Greg Ritzinger | 392 | If desired to extend the WS-CDL language' this specification allows inside a WS-CDL document the use of extensibility elements and/or attributes defined in other XML namespaces. Extensibility elements and/or attributes MUST use an XML namespace different from that of WS-CDL. All extension namespaces used in a WS-CDL document MUST be declared.Extensions MUST NOT change the semantics of any element or attribute from the WS-CDL namespace. | To support extending the WS-CDL language, this specification allows the use of extensibility elements and/or attributes defined in other XML namespaces inside a WS-CDL document. Extensibility elements and/or attributes MUST use an XML namespace different from that of WS-CDL. All extension namespaces used in a WS-CDL document MUST be declared. Extensions MUST NOT change the semantics of any element or attribute from the WS-CDL namespace. | |||
SRT | 217-219 | does this mean no WSDL is required? Does it mean same WSDL is required? Does it mean different WSDLs are possible? | We need to figure out what this may mean. The text is abstract enough to incorporate any direction that we choose to take. The current situation would suggest that WSDL2.0 is required. (see line 250) | |||
SRT | 269-270 | Does this mean WSDL2.0 or earlier or both? | See section 1.4 | |||
SRT | 295, 299, 503,… | Do we need the term "business processes"? Can we just have "processes" since WS-CDL may be used in areas in which the term business process has less relevance. | Yes okay. | |||
SRT | 321-322 | Semantics allow the creation of descriptions that can record the semantic definitions of almost every single component in the model If it is "almost" then what is excluded? | We need to verify what almost means. We need to check why it is not included in some constructs. Need to file an issue and follow it through | |||
SRT | 441, 459 | Dumb question from me. What is the relationship between 'role name="ncname"' and 'role type="qname"'. Maybe I don't understand what ncname is. I presume qname is qualified name relative to some schema. | ncname is not a qname - so not qualified. Begs the question why one over the other - that needs clarification. namespace names are qnames and thing in the CDL that are ncnames define names in the CDL namespace which is why target name space is in a CDL | |||
SRT | Section 2.3.3 (Relationships): | Would I be correct in thinking about a relationship as a static connection between processes? | If a process is an abstraction of some named behavior then this correct at least for one case. Kind of makes sense. | |||
SRT | 321-322 | Back to Semantics above: What would semantics be and how would the look? | Semantics are descriptive text which may be structured in RDF to enable other tools to make some assertions about a CDL. | |||
SRT | 449, 547-551 | Does this mean that a channel is a web service and so they are coupled? | This is an abstraction layer. Today it is bound to WSDL2.0. But should this need to be changed it can be without any adverse impact. | |||
SRT | 534-535 | Is there any reason not to have numbers other than 1 and unlimited? | This is really question for our invited experts. | |||
SRT | 573 | Is the <token type="tns:purchaseOrderID"/> the effective correlation id in this example? Is this how correlation will be performed relative to channels? | Yes | |||
SRT | 579-580 | that can influence the observable behavior In what way can a WS-CDL document influence behavior since it is a description? Does this only apply to generation in which case I can see such a relationship? | Yes the latter question is right. | |||
SRT | 602-607 | Do these variables describe the relationship between messages? i.e. A is composed of specific parts of B Is this correlation? | No it is not intended to be correlation. It's sort of alpha renaming on the one hand. It could be used to guide skeleton generations for variabled on invoke and receive in BPEL. | |||
SRT | 624 | a Channel Variable could contain information such as URL to which a message should be sent Is this a "could"? | Depends on channel type and so is a could. | |||
SRT | 674 | What is a silent-action used for? Alas no example to illustrate. | The silent-action represents something that is not observable. Perhaps our invited experts might help us with a use case. | |||
SRT | 739-745 | Given the definition previously why is "part" valid? Is this an XQuery thing? | This is a mistake. "Part" should be removed. | |||
SRT | 748 | Is "prescribes" the right word here? | Describes is better | |||
SRT | 872-878 | How do I guard with more than one variable? Is there any notion of existential qualifier associated with this so that I can have a guard that simply says: If there exists an x, y and a z then .... | You can use as many variables as you wish. Extension functions on XPath in the WS-CDL document include getVariable. | |||
SRT | Section 2.4.8.1 Exception Block. | How is the guard in an Exception Block work unit related to the non-exceptional work units in the enclosing choreography? Are they always the same? Are they always non-overlapping? Are they unrelated? Is it user defined? What is the consequence of un-restriction? | It probably doesn't make sense for the same guard to be used. Raises some model checking issues because there may be a need to validate guards against one another. | |||
SRT | 1094-1099 | What if there are no matches for an guarded work unit in an exception block? | See above? The exception block might well be caught higher up. No explicit final catch all is defined in CDL. | |||
SRT | 1177 | Activity-Notation "+". This allows 1 or more not two or more. | Yes it should be two or more. You can express this in the schema however. | |||
SRT | 1211-1212 | Is it possible to model a one way receive? | An interaction is a pair. | |||
SRT | 1271-1283 | Does this mean that some higher order messaging protocols allow states in the CDL to be inferred rather than captured explicitly? (i.e. if I know that when I send a message from A to B that B gets the message then I can infer something about the state of B relative to the receiving of that message.) | No you cannot infer. It does not guarantee that B read the message as opposed to just received the message. What is needed is guarantee of understanding of the message that was about. | |||
SRT | 1312-1313 | If align and initiateChoreography are not present what is the default behavior (true or false)? | Align is defaulted to false. | |||
SRT | 1355-1359 | Default behavior again? | See above. | |||
SRT | 1583-1596 | Not sure why you use the terms "this" and "free" and what they might mean? Is it to indicate that the fromRole is the "this" and the toRole is "free based on being the initiator (i.e. Directionality?) | this is a variable is the aliased name of the free variable. | |||
SRT | 208 | interoperability and interactions between services within one b | interoperability and interactions required to ensure conformance between services within one business entity. | |||
SRT | 227-228 | Can you provide an "e.g." to elaborate what Composability might mean? | ||||
SRT | 232-235 | Can you provide a defintion of "observable state"? | ||||
SRT | 238 | exchanged information as well. | exchanged information. | |||
SRT | 239-240 | Can you provide an example (an e.g.) to elaborate what might constitute an exception? | ||||
SRT | 264 | trully | truly | |||
SRT | 310 | where and how to exchange information | where and how information is exchanged | |||
SRT | 314 | results in exchange of messages | results in an exchange of messages | |||
SRT | 424 | these type of environment | these types of environments | |||
SRT | 492-493 | This allows modeling how the destination of messages is dete | This allows the modeling of both
static and dynamic message destinations ," |
|||
SRT | 562 | The passing element allows ConsumerChannel to be sent | The passing element allows an instance of a ConsumerChannel to be sent | |||
SRT | 683 | defined in Cheography | defined in Choreography | |||
SRT | 813-814 | Difficult to understand and would benefit from an example. | ||||
SRT | 918 | defines In the below example, | defined in the example below, | |||
SRT | 959-961 | A Request for Quote (RFQ) Choreography that involved a Buy | A Request for Quote (RFQ) Choreography that involves a Buyer Role a request for a quotation for goods and services to a Supplier to which the Supplier resonds with either a "Quotation" or a "Decline to Quote" message, and | |||
SRT | 962-963 | An Order Placement Choreography where the Buyer placed a | An Order Placement Choreography where the Buyer places an order for goods or services and the Supplier either accepts the order or rejects it | |||
SRT | 1059-1060 | did not complete within a required timescale | did not complete within the required time | |||
SRT | 1121 | used to perform the actual work | used to description the actual work | |||
SRT | 1125 | A Ordering Structure | An Ordering Structure | |||
SRT | 1243 | have agreement of the outcome | have agreement on the outcome | |||