W3C home > Mailing lists > Public > www-i18n-comments@w3.org > February 2001

Comments for WD-charmod-20010126

From: Susan Lesch <lesch@w3.org>
Date: Thu, 1 Feb 2001 23:17:55 -0800
Message-Id: <p05010408b6a00a65618d@[204.210.33.45]>
To: www-i18n-comments@w3.org
These are comments for your Character Model [1] Last Call Working
Draft.

Would it help to have a conformance checklist, either a table or
lists, showing what is expected, linking back to prose sections?
Items could be grouped by key word (e.g. MUST, MUST NOT, SHOULD).
It is easy to grasp the idea that you are asking for conformance
from every W3C specification developer, but it is not a simple
task to grasp what is required.

When section 3.5 was rewritten, the link to [RFC 2070] disappeared.
This is quite a broad claim, with nothing to back it up anymore:
"...Since its early days, the Web has seen the development of a
     Reference Processing Model. This model was first adopted for HTML
     and later embraced by XML and CSS."
HTML4, CSS1, and XML don't mention the "Reference Processing Model."
CSS2 has "2.3 The CSS2 processing model" but it is concerned with
formatting (http://www.w3.org/TR/REC-CSS2/intro.html#processing-model).
I found section 4.3.3.2 "The Reference Processing Model" in
XML-Signature, but it concerns XPath node-sets and not Unicode
(http://www.w3.org/TR/xmldsig-core/#sec-ReferenceProcessingModel).
Are you talking about another facet of the same model? I suggest
that, either way, section 3.5 could link to [RFC 2070] again:
"...Since its early days, the Web has seen the development of a
     Reference Processing Model, first described for HTML in
     [RFC 2070]. This model was later embraced by XML and CSS."

The second to last paragraph in section 9 could refer to the
Unicode Consortium's instructions on how to refer to Unicode.
You could add a reference item for "Citations and References"
in http://www.unicode.org/unicode/standard/versions/

Hiragana and Katakana are capitalized in 3.1.2 and
lowercase in 5. Can they match?

 From here down, a section number is followed by a quote and
then a suggestion. (It may be premature to report typos.)

1.1 par. 1
the W3C goal of Universal Access
the W3C goal of <em>universal access</em>

1.1 par. 2
The main target audience of this document are
The main target audience of this document is

1.1 par. 6 and 9. par. 4
The Unicode Standard
the Unicode Standard

2. par. 2
All new or revised W3C specification
All new or revised W3C specifications

3.1.7 par. 1
Text is then defined as sequences of characters.
<em>Text</em> is then defined as sequences of characters.

3.6.1 par. 3
developers and software that tags
developers and software that tag

8 request for feedback
conversion a legal URI
conversion to a legal URI

9 par. 5
in synchronism
in synchrony

Other References
- W3C specs could all have publication dates
- in XML 1.0, "Eve Maler Eds." -> "Eve Maler, Eds."
- W3C specs need commas between maturity level and date

[1] http://www.w3.org/TR/2001/WD-charmod-20010126/

Best wishes for your project,

-- 
Susan Lesch - mailto:lesch@w3.org  tel:+1.858.483.4819
World Wide Web Consortium (W3C) - http://www.w3.org/
Received on Friday, 2 February 2001 02:18:03 GMT

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