ID | Location | Comment | Mail thread | Accepted |
---|---|---|---|---|
1 | General |
Editorial: The RFC 2119 Keywords (must etc.) would be better to read if they would be in bold face. In sec. 10.5.7.1, there is a MUST in capital letters. |
- | - |
2 | Sec. 3.5.3.8 | Editorial: "This is can be viewed " should be "This can be viewed". | - | - |
3 | Sec. 6.1 | You write "The media type application/ccxml+xml will be registered for CCXML documents.". When will this be the case? | - | - |
4 | Sec. 6.2.2.1 | Editorial: You define the <meta> property name in terms of rdfs:seeAlso. You should update the reference to the RDF Schema recommendation. | - | - |
5 | Sec. 6.2.2.1 | rdfs:seeAlso: Its mechanism for URI escaping relies on the RDF Concepts and Abstract Syntax specification. To be able to use the <meta> property name in internationalized contexts, please refer to section 3.1 of the IRI specification instead. | - | - |
6 | Sec. 6.2.7 | You state that except from http and https, other URI based protocolls might be supported for <fetch>. Please refer to the IRI specification instead. As for the table in section 6.2.7.2, a reference to IRI instead of URI should be made for the attribute next. | - | - |
7 | Sec. 6.2.9.2 | The comment on Sec. 6.2.7 also applies to the attribute next on the <createccxml> element, and on many more (see comment 9). | - | - |
8 | Sec. 6.3 and others | The comment on Sec. 6.2.7 also applies to the attribute URI from the fetch.done event. (sec. 6.3.2), the error.fetch event (sec. 6.3.3), the scr attribute at the <dialogprepare> element (sec. 7.2.1.2), the URI reference in the src attribute at the <dialogstart> element (sec. 7.2.2.1), the URI attribute from the 7.3.5: dialog.transfer event (sec. 7.3.5), the scr attribute at the <script> element (sec. 8.2.2.2), the session variables session.uri and session.ioprocessors (sec. 8.3), the target attribute at the <send> element (sec. 9.2.3.2), the conncetion properties local and remote (sec. 10.2.2), the dest attribute at the <redirect> element (sec. 10.5.2.2) and a the <createcall> element (sec. 10.5.4.2), the conferenceid at the <createconference> element (sec. 10.5.5.2) or at e.g. the <destroyconference> element (sec. 10.5.6.2), and various parts of the appendix. | - | - |
9 | Appendix I. 1 | You refer to security conditions for URL (RFC 1738). Please refer to RFC 3986, section 7 instead. RFC 3986 updates 1738 and obsoletes 2732, 2396, 1808. It would be even better if you could refer to RFC 3987, section 8. | - | - |
Version: $Id: ccxml1-0-review.html,v 1.5 2005/07/27 05:32:10 fsasaki Exp $