923 2004-10-25 14:41:21 +0000 No explanation of "action" and "new" in channel type defns2.3.4 Channel Types<channelType name="ncname" usage="once"|"unlimited"? action="request-respond"|"request"|"respond"? > <passing channel="qname" action="request-respond"|"request... 2004-12-01 16:29:23 +0000 1 1 1 Unclassified WS Choreography Spec: Editorial unspecified Other other RESOLVED FIXED P2 normal -- 1 steve martin.chapman public-ws-chor-comments oldest_to_newest 2554 0 steve 2004-10-25 14:41:22 +0000 2.3.4 Channel Types <channelType name="ncname" usage="once"|"unlimited"? action="request-respond"|"request"|"respond"? > <passing channel="qname" action="request-respond"|"request"|"respond"? new="xsd:boolean"? />* <role type="qname" behavior="ncname"? /> <reference> <token type="qname"/> </reference> <identity> <token type="qname"/>+ </identity>? </channelType> There is no explanation of "action" after "usage". There is no explanation of "new" after "action". 20379 1 steve 2008-06-05 13:24:54 +0000 The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was: No explanation of "action" and "new" in channel type defns2.3.4 Channel Types<channelType name="ncname" usage="once"|"unlimited"? action="request-respond"|"request"|"respond"? > <passing channel="qname" action="request-respond"|"request"|"respond"? new="xsd:boolean"? />* <role type="qname" behavior="ncname"? /> <reference> <token type="qname"/> </reference> <identity> <token type="qname"/>+ </identity>?</channelType>There is no explanation of "action" after "usage".There is no explanation of "new" after "action".No explanation of "action" and "new" in channel type defns