This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 923
Who | When | What | Removed | Added |
---|---|---|---|---|
gritzinger | 2004-11-02 19:22:52 UTC | Component | Spec | Spec: Editorial |
martin.chapman | 2004-12-01 16:29:23 UTC | Status | NEW | RESOLVED |
Resolution | --- | FIXED | ||
Summary | No explanation of "action" and "new" in channel type defns 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". No explanation of "action" and "new" in channel type defns | 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 |
Back to bug 923