1079 2005-02-07 15:13:02 +0000 Interaction Syntax - successul-sending and properly-received are not clearly defined 2005-12-12 11:36:27 +0000 1 1 1 Unclassified WS Choreography Last Call Comment: Confirmed Closed unspecified PC Linux CLOSED WONTFIX http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Jan/0037.html P2 normal -- 1455 1 gritzinger martin.chapman martin.chapman oldest_to_newest 4238 0 gritzinger 2005-02-07 15:13:02 +0000 Section 2.5.2.3 Interaction Syntax " <record name="ncname" when="before"|"after"|"timeout" causeException="true"|"false"? > <source variable="XPath-expression"? | expression="Xpath-expression"? /> <target variable="XPath-expression" /> </record>* " Suggestion: The definitions of successul-sending and properly-received is vital to any legally relevant communication specification mechansimssuch as CDL (see above refs). By defining *events* for when a data message ha been sent and receive, an important level of precision is achieved. The exact definition of successful reception is not only a technical problem but more importantly also a legal issue. A simple mechanism is to explicitly define the 4 Events and relate Interaction completions and variable binding to the events. Organisations such UN/CEFACT and national bodies can then apply their specific definitions of succesful-reception etc. The suggestion seem easilly implementable without changing the CDL semantics and CDL usefulness and appropriatness for eCommerce will increase. Adding (4 or more) Events-specifications to Recording and relate them to *when* be be an additions. There is a vital/key difference between *before* and *successful-sending* where usually the legal meaning is attached to *successful-sending*. " <record name="ncname" act="send"|"receive" when="before"|"after"|"timeout" causeException="true"|"false"? > <source variable="XPath-expression"? | expression="Xpath-expression"? /> <target variable="XPath-expression" /> <event name="ncname" act="send"|"receive" when="before"|"after"|"timeout"(|"exception")/> ... precise definitions added elsewhere ... </event> </record>* " It is important to, in the rest of the CDL document, be clear that the occurence of these events are the real trigges for variable assignements etc. 4039 1 martin.chapman 2005-02-14 21:40:47 +0000 From 8-feb-05 concall: http://lists.w3.org/Archives/Member/member-ws-chor/2005Feb/att-0003/Minutes- 02082005-0.txt REQUIRES TECHNICAL DISCUSSION 3736 2 gritzinger 2005-04-12 20:34:40 +0000 RESOLVED WONTFIX, MINUTES 2005-04-12 3297 3 martin.chapman 2005-05-12 11:57:34 +0000 decision minutes: http://www.w3.org/2002/ws/chor/5/04/12-minutes.html Anders has been informed of the group's decision [1] and we are awaiting confirmation. Category changed to LCC: Closed. [1] http://lists.w3.org/Archives/Public/public-ws-chor- comments/2005May/0023.html 3260 4 steve 2005-05-16 15:15:12 +0000 Add clarity to message exchanges on sending and receiving in primer specially around triggering of when things happen etc with a good example early on in sections dealing with interactions. ADDED - SRT Changed to primer from last call closed and QS contact changed to steve from martin 3089 5 martin.chapman 2005-05-26 19:21:20 +0000 Anders is ok with this resolution: http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005May/0033.html