This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 2.3.3, 3rd paragraph, last sentence. Question on constraint "A specific Role Type MUST NOT be specified in more than one participantType element." What is the reason for this restriction? It would be reasonable to expect an organization to be more than one Participant Type, where these Participant Types have a common Role Type.
requires technical discussion and/or justification
From meeting on 25-jan-05: http://lists.w3.org/Archives/Member/member-ws-chor/2005Jan/att-0010/2005-01- 25_WS-Chor_Notes.txt requires technical discussion and/or justification
Discussed at feb-mar 05: http://lists.w3.org/Archives/Member/member-ws-chor/2005Mar/att- 0001/Ws_Chor_f2f__Feb-Mar_2005_-0.txt Issue 1023: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1023 not related to yesterday's issue nick: channel has a roletype, if roletype belongs to two participant, we don't know which participant is targeted ... looks like a primer thing Martin: is the restriction removed, you can get from participant to role but not role to participant Nick: in the interact we are using From and TO: role but not participant <SRT> Gary says, wrt the current situation regarding 1023 "different participants could simply use the same interface, but use different role type names" Nick: 2.3.1. change "element declared within a Choreography Package" to "within a participant" Agreed
Yin-Leng 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/0012.html
changed to resolved fixed
Yin-Leng has confirmed the resolution is acceptable: http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Aug/0019.html