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

Mandating NFC for All Web Content

From: Cliff Schmidt <cschmidt@microsoft.com>
Date: Fri, 7 Jun 2002 01:29 +0900
To: www-i18n-comments@w3.org
Cc: cschmidt@microsoft.com (Cliff Schmidt)
Message-Id: <20020606162936.D6C091403@toro.w3.mag.keio.ac.jp>

This is a last call comment from Cliff Schmidt (cschmidt@microsoft.com) 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: Cliff Schmidt (cschmidt@microsoft.com)
Submitted on behalf of (maybe empty): Microsoft
Comment type: substantive
Chapter/section the comment applies to: 4.4 Responsibility for Normalization
The comment will be visible to: public
Comment title: Mandating NFC for All Web Content
Comment:
--------------------------------------------------------------------------
"[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. 
 [S] Specifications of text-based formats and protocols MUST, as part of their syntax definition, require that the text be in normalized form."
--------------------------------------------------------------------------
CONCERN:
This restriction is currently applied to "all text content on the Web" when only content intended for interoperability in open systems will necessarily benefit from it.  Although the first requirement for content producers ([C]) could be interpreted to have no impact on intranet scenarios, the second requirement for specifications ([S]) will impact the tools that intranet scenarios have been depending on.  

RECOMMENDATION: 
Replace above text with text similar to:
"[C] In order to conform to this specification, all text content on the Web intended for consumption by foreign systems MUST be in include-normalized form and SHOULD be in fully-normalized form. 
 [S] Specifications of text-based formats and protocols MUST, as part of their syntax definition, reference the above requirement."



Structured version of  the comment:

<lc-comment
  visibility="public" status="pending"
  decision="pending" impact="substantive">
  <originator email="cschmidt@microsoft.com" represents="Microsoft"
      >Cliff Schmidt</originator>
  <charmod-section href='http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-NormalizationApplication'
    >4.4</charmod-section>
  <title>Mandating NFC for All Web Content</title>
  <description>
    <comment>
      <dated-link date="2002-06-06"
        >Mandating NFC for All Web Content</dated-link>
      <para>--------------------------------------------------------------------------
"[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. 
 [S] Specifications of text-based formats and protocols MUST, as part of their syntax definition, require that the text be in normalized form."
--------------------------------------------------------------------------
CONCERN:
This restriction is currently applied to "all text content on the Web" when only content intended for interoperability in open systems will necessarily benefit from it.  Although the first requirement for content producers ([C]) could be interpreted to have no impact on intranet scenarios, the second requirement for specifications ([S]) will impact the tools that intranet scenarios have been depending on.  

RECOMMENDATION: 
Replace above text with text similar to:
"[C] In order to conform to this specification, all text content on the Web intended for consumption by foreign systems MUST be in include-normalized form and SHOULD be in fully-normalized form. 
 [S] Specifications of text-based formats and protocols MUST, as part of their syntax definition, reference the above requirement."
</para>
    </comment>
  </description>
</lc-comment>
Received on Thursday, 6 June 2002 12:29:39 GMT

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