W3C home > Mailing lists > Public > www-i18n-comments@w3.org > May 2002

Objection to prohibition against receiver from normalizing text

From: Jim Melton <jim.melton@acm.org>
Date: Thu, 30 May 2002 04:48 +0900
To: www-i18n-comments@w3.org
Cc: jim.melton@acm.org (Jim Melton)
Message-Id: <20020529194843.6D822DFE@toro.w3.mag.keio.ac.jp>

This is a last call comment from Jim Melton (jim.melton@acm.org) on
the Character Model for the World Wide Web 1.0
(http://www.w3.org/TR/2002/WD-charmod-20020430/).

Semi-structured version of the comment:

Submitted by: Jim Melton (jim.melton@acm.org)
Submitted on behalf of (maybe empty): W3C XML Query Working Group
Comment type: substantive
Chapter/section the comment applies to: 4.4 Responsibility for Normalization
The comment will be visible to: public
Comment title: Objection to prohibition against receiver from normalizing text
Comment:
Section 4.4, "Responsibility for Normalization", specifies one requirement (on web content) that states "[C] In order to conform to this specification, all text content on the Web MUST be in include-normalized  form and SHOULD be in fully-normalized form."  While this statement expresses a clearly desirable situation, it is 100% guaranteed that the web will *never* contain only include-normalized text.  The character model MUST (irony noted) recognize that fact and give guidance for dealing with such data.  A preferred alternative, currently prohibited by the Character Model document, is to allow a *consuming* application to do the normalization.  [1] currently prohibits such action, as addressed in the next comment.

This prohibition is unreasonable and we believe that its inclusion will dramatically inhibit adoption of the Character Model by products and implementors. 


Structured version of  the comment:

<lc-comment
  visibility="public" status="pending"
  decision="pending" impact="substantive">
  <originator email="jim.melton@acm.org" represents="W3C XML Query Working Group"
      >Jim Melton</originator>
  <charmod-section
      href="http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-NormalizationApplication"
    >4.4</charmod-section>
  <title>Objection to prohibition against receiver from normalizing text</title>
  <description>
    <comment>
      <dated-link date="2002-04-29"
        >Objection to prohibition against receiver from normalizing text</dated-link>
      <para>Section 4.4, "Responsibility for Normalization", specifies one requirement (on web content) that states "[C] In order to conform to this specification, all text content on the Web MUST be in include-normalized  form and SHOULD be in fully-normalized form."  While this statement expresses a clearly desirable situation, it is 100% guaranteed that the web will *never* contain only include-normalized text.  The character model MUST (irony noted) recognize that fact and give guidance for dealing with such data.  A preferred alternative, currently prohibited by the Character Model document, is to allow a *consuming* application to do the normalization.  [1] currently prohibits such action, as addressed in the next comment.

This prohibition is unreasonable and we believe that its inclusion will dramatically inhibit adoption of the Character Model by products and implementors. </para>
    </comment>
  </description>
</lc-comment>
Received on Wednesday, 29 May 2002 15:49:21 GMT

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