This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Unnecessary specification of the role name restricts the places where the function can be used. For example, a condition expression that would otherwise be applicable at all roles related to a choreography, may be unnecessarily constrained to a particular role because it relies on one of these expressions. Whereas, if the role is not specified, the expression could be used at a wide range of roles. Regards Gary and Steve
From meeting on 11-jan-05 http://lists.w3.org/Archives/Member/member-ws-chor/2005Jan/att-0002/2005-01- 11_WS-Chor_Notes.txt: Discussion deferred as deemed to be a technical issue.
at meeting on 15 march http://www.w3.org/2002/ws/chor/5/03/15-minutes.html the group agreed: 1000 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1000 Summary: CDL 'ROLE' FUNCTIONS URL: http://lists.w3.org/Archives/Public/public-ws-chor- comments/2005Jan/0004.html Bug 1000 discussion: Gary: in some cases thr role attribute causes confusion. Gary: is the role attr. required? Gary: time functions have similar problem Nick: in some cases the context is not enough Nick: in getVariable() the a role is optional Nick: role is inferred from the context Take same text from getVariable() and apply to other functions. From the spec: The fourth parameter is OPTIONAL. When the fourth parameter is used, the Variable information MUST be available at the Role specified by roleName. If this parameter is not used then the Role is inferred from the context that this function is used. Applied to RoleName to all functions and making RoleName optional rather than mandatory Changing "fourth" to the appropriate number for the function. PROPOSAL ABOVE ACCEPTED. MARK BUG EDITORIAL
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