This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Here is another comment, on variables: In 2.4.6 b (this is workunit section) and elsewhere, there are several sentences which can be read as if "cdL:getVariable" can be performed to obtain a variable from any other role, resulting in fetching the value of a variable at a remote site. In 2.4.6b we find: ...the guard condition checks if the Variable "StockQuantity" at the "Retailer" Role is available and is greater than .... If in the given workunit, an action by Seller is done and it is Retailer's datum used for guards, then this results in a remote read. Claritication of this point during the final inspection period will be useful.
agreed on con call 15-feb-05: Editorial possible duplicate
Clarification requested in http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0029.html but no response yet. On telecom 26 April 05 it was clarified that the optional roleType parameter is used to specify the role[Type] when this is not otherwise clear from the context, but the getVariable function can not be used to do a remote value fetch. In section 2.4.6 changed · The WS-CDL function getVariable is used in the guard or repetition condition to obtain the information of a Variable To · The WS-CDL function getVariable is used in the guard or repetition condition to obtain the value of a Variable at the specific role (i.e. it can not be used to perform a remote value fetch)
group notification of status change: http://lists.w3.org/Archives/Member/member- ws-chor/2005Jul/0004.html
no comments from group so closed confirmed: http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/0004.html