This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 923 - 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...
Summary: No explanation of "action" and "new" in channel type defns2.3.4 Channel Types...
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Editorial (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: WS Choreography mailing-list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-25 14:41 UTC by Steve Ross-Talbot
Modified: 2004-12-01 16:29 UTC (History)
0 users

See Also:

Attachments

Description Steve Ross-Talbot 2004-10-25 14:41:22 UTC 
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".
Comment 1 Steve Ross-Talbot 2008-06-05 13:24:54 UTC 
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