- From: Monica J. Martin <Monica.Martin@Sun.COM>
- Date: Tue, 12 Oct 2004 09:50:23 -0700
- To: "WS Choreography (E-mail)" <public-ws-chor@w3.org>
- Cc: "'steve@enigmatec.net'" <steve@enigmatec.net>
Last week, I was asked about Issue 684 and explicit roles. It actually could relate to Issue 691 for which Steve has provided a solution. My recommendation would be to have explicit roles defined. I believe Steve's resolution recognizes this. I would request we consider if this variable definition change should apply to other constructs in the specification: Fragments from Steve's proposal: Syntax fragment: <variableDefinitions> <variable name="ncname" informationType="qname"|channelType="qname" mutable="true|false"? free="true|false"? silentAction="true|false"? roleType="qname"* />+ </variableDefinitions> Text fragment: .....Thus all variables MUST have a name and that name MUST be distinct with respect to the Role Type(s) in which the variable resides. In those cases where the visibility of a variable is wholly within a single role then that role needs to be named in the definition of the variable as the Role Type. In those cases where the variable is shared amongst a subset of roles within a choreography those roles need to be named within the definition of the variable as the Role Types..... My point to Steve last week in coordinating issues, was that noAction and silentAction are specific to a role and not visible to another party. I also pointed out to Steve, the same may apply to locally defined variables (Issue 691). We indirectly touched on this issue when discussing distributed choice and visibility in the contract in the F2F. If the roles are not explicit, would not these actions be visible to both roles in a relationship? Should not the spirit of this proposed change (Issue 691) be considered to apply to other constructs in the specification such as noAction and silentAction? On noAction and silentAction, we do have an open action from last F2F to provide more semantics around these, so this may be an input to that. Thanks to Steve for his work on this action. Thank you.
Received on Tuesday, 12 October 2004 16:50:26 UTC