W3C home > Mailing lists > Public > www-i18n-comments@w3.org > January 2004

Your comments on the Character Model [C162, C163]

From: Richard Ishida <ishida@w3.org>
Date: Fri, 23 Jan 2004 19:48:25 -0000
To: <karl@w3.org>, <www-qa-wg@w3.org>
Cc: <www-i18n-comments@w3.org>
Message-ID: <005901c3e1e9$ddaedd00$6401a8c0@w3cishida>

Dear Karl and QA WG,

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, grouped together, at 
http://www.w3.org/International/Group/2002/charmod-lc/SortByGroup.html#C112
(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. 
        C162, C163

Information relating to these comments is also included below.

You can find the latest version of the Character Model at
http://www.w3.org/International/Group/charmod-edit/ . 

Best regards,
Richard Ishida, for the I18N WG




DECISIONS REQUIRING A RESPONSE
==============================

C162
-----------------
	Na	Na	C	Karl Dubost
	QA WG
	P	MD	2	Conformance

    *
      Comment (received 2002-06-18) -- QA Review for Charmod
[http://lists.w3.org/Archives/Public/www-i18n-comments/2002Jun/0022.html]

      [...] I would like to know how you plan to enforce the use of charmod
in other specifications by process, pubrules, charters? We are faced to the
same question in QA WG.
    *
      Decision: Not applicable.
    *
      Rationale: We have classified this comment as 'not applicable' because
it does not make any suggestions re. changes of the specification. 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. As we understand, many of the requirements on other specs that the
QA WG is looking at are much more procedural in nature, whereas the
requirements in CharMod are more technical. Therefore, different
considerations may apply to your work.



C163
------------------
	Na	Na	C	Karl Dubost
	QA WG
	P	MD	2	Testable Assertions/Requirements

    *
      Comment (received 2002-06-18) -- QA Review for Charmod
[http://lists.w3.org/Archives/Public/www-i18n-comments/2002Jun/0022.html]

      I found interesting the way you have declared the rules of Conformance
for your specifications. I would like to know if there's a plan for a Test
Suite or at least Examples and Techniques to demonstrate your technologies.

      For example in the first statement (Testable assertion?), I had
difficulty to define a binary test case, is it possible to have testable
examples for each rule in a separate document. It will help people
understand the statement you have defined.
    *
      Our response (sent 2002-06-20) -- Re: QA Review for Charmod
[http://lists.w3.org/Archives/Public/www-i18n-comments/2002Jun/0024.html]

      Binary tests are very difficult in many case, or have to be worked out
individually for each spec (e.g. XML, CSS,...).
    *
      Decision: Not applicable.
    *
      Rationale: We have classified this as 'Not applicable', because you
are just as kind about our plans, not suggesting changes to the document.
The Character Model is an architectural specification, and it is therefore
difficult if not impossible to create binary tests. If we had an automatic
test to see whether another specification conforms to the character model,
that would indeed be great, but it is obvious that this is impossible.

      In some cases, tests can be worked out for individual specifications
that conform to the character model (e.g. XML, CSS,...), but those would be
part of the test suite for that spec. For some aspects of the character
model, or some material we reference, there are already tests, e.g. for NFC.
Regarding examples and techniques, the text already contains many examples
where we found they are necessary to clarify the specification, and we have
added more examples as a result of last call comments. We also expect that
for passing CR, we will have to provide a list of other specifications that
follow the various provisions in Charmod, and such a list will provide a
wealth of examples.





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/
[3] Last Call comments table, sorted by ID: 
http://www.w3.org/International/Group/2002/charmod-lc/
Received on Friday, 23 January 2004 14:48:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:32:34 GMT