Re: [I18ndir] I18ndir last call review of draft-ietf-regext-dnrd-objects-mapping-06

[Asmus Freytag <[e-mail]>]

As I read the W#C document, "NormalizedString" is not an actual format, 
other than that it disallows all line endings and tab.

There are parameters for how to normalize remaining whitespace, but 
without specifying which parameters are set. It's like calling a string 
"Unicode normalized" and not knowing from that term whether it's in NFC, 
NFD, NFKC or NFKD.

In the W3C these are enumerated as part of the "constraining facets" 
listed in 3.3.1.1

For an archival format, then, either each field has attributes that give 
these facets, as applicable, or the format itself needs to require 
particular settings.

None of that, by the way, speaks in any way about casefolding or Unicode 
normalization, the kinds of operations that are critical in identifier 
contexts.

A./


On 3/6/2020 7:55 AM, Hollenbeck, Scott wrote:
> Note below on the draft's reference to the XML Schema normalizedString data type:
>
>> -----Original Message-----
>> From: I18ndir <[e-mail]> On Behalf Of John C Klensin
>> Sent: Friday, March 6, 2020 10:46 AM
>> To: Asmus Freytag (c) <[e-mail]>; [e-mail]
>> Subject: [EXTERNAL] Re: [I18ndir] I18ndir last call review of draft-ietf-regext-
>> dnrd-objects-mapping-06
>>
> [snip]
>
>> [1]  I am not familiar enough with the Regext set of documents to know if
>> "normalizedString" is defined somewhere.  Certainly,
>> draft-ietf-regext-dnrd-objects-mapping-06 uses it without defining it locally
>> or providing a specific normative reference to such definitions.  At minimum,
>> this suggests another problem with the I-D that may need fixing.  But, if
>> there is not a clear definition -- if the instruction for what should go into
>> those fields is essentially "just normalize", than that is obviously bad news.  It
>> is bad news even for IDN U-labels because a string in, e.g., NFC would not
>> conform to the requirements for U-labels.  Normal IETF and RFC practice
>> requires a statement, probably in the Terminology section and probably with
>> a normative reference, to where definitions of that and other attributes can
>> be found.
> Reference here:
>
> https://www.w3.org/TR/xmlschema-2/#normalizedString
>
> The draft should include a normative reference to the W3C XML Schema specification:
>
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028
>
> Scott
>