- From: Richard Ishida <ishida@w3.org>
- Date: Fri, 6 Feb 2004 15:00:27 -0000
- To: <fallside@us.ibm.com>
- Cc: <w3c-xml-protocol-wg@w3.org>, <www-i18n-comments@w3.org>
Dear David, Many thanks for your comments on the 2nd Last Call version of the Character Model for the World Wide Web v1.0 [1]. We appreciate the interest you have taken in this specification. You can see the comments you submitted on behalf of the XMLP WG, grouped together, at http://www.w3.org/International/Group/2002/charmod-lc/SortByGroup.html#C060 (You can jump to a specific comment in the table by adding its ID to the end of the URI.) PLEASE REVIEW the decisions for the following additional comments and reply to us within the next two weeks at mailto:www-i18n-comments@w3.org (copying w3c-i18n-ig@w3.org) to say whether you are satisfied with the decision taken. C060, C061 Information relating to these comments is included below. You will receive notification of decisions on remaining comments at a later date. The Character Model has recently been split into two parts. These comments relate to the editor's version at http://www.w3.org/International/Group/charmod-edit/charmod1.html Best regards, Richard Ishida, for the I18N WG DECISIONS REQUIRING A RESPONSE ============================== C060 Na Na C David Fallside XMLP WG P MD 2 XML Protocol LC#2 review question on implementation testing * Comment (received 2002-05-30) -- XML Protocol LC#2 review question on implementation testing http://lists.w3.org/Archives/Public/www-i18n-comments/2002May/0029.html In reviewing the Charmod LC#2, the XML Protocol WG has a request in relation to implementation conformance. - Section 2 Conformance, 3rd paragraph, last sentence - '[S] [I] [C] In order to conform to this document, specifications MUST NOT violate any requirements preceded by [S], software MUST NOT violate any requirements preceded by [I], and content MUST NOT violate any requirements preceded by [C].' - The XML Protocol WG has produced a protocol specification, which makes various testable assertions, as well as a Collection of Tests [http://www.w3.org/2000/xp/Group/2/03/11/soap-1.2-conformance.html] each showing whether an assertion is implemented in the protocol processor. As such, the tests do not check for conformance to other specifications (e.g. XML 1.0). The XML Protocol WG asks the I18n WG to comment on whether the [I] implementation requirements of Charmod apply to the XMLP Test Collection. * Decision: Not applicable * Rationale: We have classified this comment as 'not applicable', because it is a question, not a comment leading to a potential change of the Character Model. The test suite should test for CharMod-related requirements in the specification(s) being tested. The tests should conform to [C] requirements (except where they are wrong on purpose). If the test collection includes code, then that should also conform to [I] requirements. C061 E Na N David Fallside XMLP WG P MD 1.1 'All W3C specifications must conform to this document' * Comment (received 2002-05-30) -- XMLP WG response to Charmod LC#2 http://lists.w3.org/Archives/Public/www-i18n-comments/2002May/0030.html Goals and Scope, second last paragraph 'All W3C specifications must conform to this document (see section 2 Conformance).' This statement seems too comprehensive and probably needs qualification. What about existing W3C specifications or a W3C specification whose status is very close to LC (e.g. XMLP's)? Suggest: 'All W3C specifications published after [a certain date or event such as this Charmod becoming a recommendation] must conform to this document (... etc).' * Decision: Rejected * Rationale 'Rejected': This para states the general principle and refers to section 2 for details. The various requirements will come into force once the CharMod spec becomes a REC. * New decision: Not applicable Rationale: We have classified this comment as 'not applicable' because we have been told that it is inappropriate for a W3C spec to directly enforce requirements on other specifications, and have removed the relevant language from section 2. We still define conformance to CharMod. We have been instructed to request a finding from the TAG corresponding to the text that we removed. So CharMod will be enforced by the fact of being a REC, coupled with an eventual TAG finding and ongoing reviews of relevant specs by the I18N WG. USEFUL LINKS ============== [1] The version of CharMod you commented on: http://www.w3.org/TR/2002/WD-charmod-20020430/ [2] Latest editor's version (still being edited): http://www.w3.org/International/Group/charmod-edit/charmod1.html http://www.w3.org/International/Group/charmod-edit/charmod2.html [3] Last Call comments table, sorted by ID: http://www.w3.org/International/Group/2002/charmod-lc/
Received on Friday, 6 February 2004 10:00:44 UTC