W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > October 2003

Re: Fwd "a comment on NFC"

From: Martin Duerst <duerst@w3.org>
Date: Fri, 03 Oct 2003 14:52:10 -0400
Message-Id: <4.2.0.58.J.20031003145147.053cab90@localhost>
To: Jeremy Carroll <jjc@hplb.hpl.hp.com>, Jeremy Carroll <jjc@hplb.hpl.hp.com>
Cc: Francois Yergeau <FYergeau@alis.com>, "'Brian McBride'" <bwm@hplb.hpl.hp.com>, w3c-i18n-ig@w3.org, w3c-rdfcore-wg@w3.org

Hello Jeremy,

I think this is sufficient to move forward to last call.

Regards,    Martin.

At 16:33 03/10/03 +0100, Jeremy Carroll wrote:


>Particulary Fran輟is and Martin
>
>RDF Core considered and agreed this text below, contingent on I18N comment 
>..., we also agreed to move to second last call.
>
>
>Is this satisfactory? Or are there possible further edits that should be 
>made (without losing consensus)?
>
>Jeremy
>
>
>
>Jeremy Carroll wrote:
>
>>
>>We seem to have consensus on weakening MUST to SHOULD.
>>Maybe we can remain silent about the areas we still disagree on. In 
>>general, the RDF specs do not specify behaviour on ill-formed input.
>>I note that the only explanatory text offered anywhere is a pointer to 
>>charmod, so that implementors chosing to permit non-NFC, can only honour 
>>the RFC 2119 requrement to understand the full implications of not 
>>implementing SHOULDs by first reading CHARMOD.
>>
>>Possible edits:
>>Syntax:
>>(latest editors draft
>>http://www.w3.org/2001/sw/RDFCore/TR/WD-rdf-syntax-grammar-20030117/
>>)
>>(IN order searching for "NFC" through the document - all these changes 
>>might benefit from further polish).
>>change
>>[[
>>MUST be a Unicode[UNICODE] string in Normal Form C[NFC]
>>]]
>>to
>>[[
>>MUST be a Unicode[UNICODE] string and SHOULD be in Normal Form C[NFC]
>>]]
>>change
>>[[
>>MUST be in Normal Form C[NFC].
>>]]
>>to
>>[[
>>SHOULD be in Normal Form C[NFC].
>>]]
>>change
>>[[
>>This string x MUST be in Unicode[UNICODE] NFC Normal Form C[NFC]
>>]]
>>to
>>[[
>>This Unicode[UNICODE] string x SHOULD be in NFC Normal Form C[NFC]
>>]]
>>change
>>[[
>>a.string-value MUST be a Unicode[UNICODE] string in Normal Form C[NFC],
>>]]
>>to
>>[[
>>a.string-value MUST be a Unicode[UNICODE] string and SHOULD be in Normal 
>>Form C[NFC],
>>]]
>>
>>In concepts
>>(editors' draft)
>>http://www.w3.org/2001/sw/RDFCore/TR/WD-rdf-concepts-20030117/
>>change
>>[[
>>The string in both plain and typed literals is required to be in Unicode 
>>Normal Form C [NFC]. This requirement is motivated by [CHARMOD] 
>>particularly section 4 Early Uniform Normalization.
>>]]
>>to
>>[[
>>The string in both plain and typed literals is recommended to be in 
>>Unicode Normal Form C [NFC]. This is motivated by [CHARMOD] particularly 
>>section 4 Early Uniform Normalization.
>>]]
>>Section 5 datatypes
>>change
>>[[
>>The lexical space of a datatype is a set of Unicode [UNICODE] strings in 
>>Normal Form C [NFC].
>>]]
>>to
>>[[
>>The lexical space of a datatype is a set of Unicode [UNICODE] strings.
>>]]
>>Section 5.1 XML Content within an RDF Graph
>>change
>>[[
>>The lexical space
>>is the set of all strings:
>>- in Normal Form C [NFC];
>>- which are well-balanced, self-contained XML content [XML];
>>]]
>>to
>>[[
>>The lexical space
>>is the set of all strings:
>>- which are well-balanced, self-contained XML content [XML];
>>]]
>>
>>6.5 RDF Literals
>>change:
>>[[
>>All literals have a lexical form being a Unicode [UNICODE] string in 
>>Normal Form C [NFC].
>>]]
>>to
>>[[
>>All literals have a lexical form being a Unicode [UNICODE] string, which 
>>SHOULD be in Normal Form C [NFC].
>>]]
>>
>>
>
Received on Friday, 3 October 2003 15:03:43 EDT

This archive was generated by hypermail pre-2.1.9 : Friday, 3 October 2003 15:03:47 EDT