- From: Graham Klyne <gk@ninebynine.org>
- Date: Thu, 02 Oct 2003 11:08:37 +0100
- To: Brian McBride <bwm@hplb.hpl.hp.com>, Jeremy Carroll <jjc@hplb.hpl.hp.com>
- Cc: w3c-i18n-ig@w3.org, w3c-rdfcore-wg@w3.org
I would support this approach. I believe it is entirely consistent with the RFC2119 intent for SHOULD, which is, roughly, "you may choose to break this rule, but don't do so unless you have a really good reason and know what you're doing". #g -- At 11:00 02/10/03 +0100, Brian McBride wrote: >I also wonder whether this issue might be addressed by toning down the >language from MUST to SHOULD e.g. > >[...] > >>which includes the additional following para: >>[[ >>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. >>]] > >becomes something like > >[[ >The string in both plain and typed literals SHOULD be in Unicode Normal >Form C [NFC]. This is motivated by anticipation that [Charmod], >particularly section 4 Early Uniform Normalization will become >standardized practice. Implementations SHOULD accept strings which are >not in Normal Form C and MAY issue a warning in such circumstances. >]] ------------ Graham Klyne GK@NineByNine.org
Received on Thursday, 2 October 2003 06:18:05 UTC