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

[Marc Blanchet <[e-mail]>]

On 5 Mar 2020, at 15:47, John C Klensin wrote:

>
> I want to thank Marc for copying the i18ndir list on this review.

I have not. see below.

>
> Given our low, and perhaps waning, levels of activity and the
> "no one is expert on all i18n issues" principle described in
> draft-klensin-unicode-review, I think it would be helpful if all
> requests for reviews of i18n-related documents and review
> assignments were posted to the i18ndir list.  That would reduce
> the chances of duplicated effort and increase the odds of enough
> cross-checking (however slightly) to be sure that directorate
> opinions were at least consistent with each other.    Without
> that sort of communication, we are not a directorate; we would
> be, at best, a loosely-structured review team.

I was assigned by Pete by way of a specific i18n review request in the 
datatracker. When the reviewer submits the review, the text is 
automatically broadcasted to the wg mailing list, drafts authors and 
i18ndir mailing lists.

Marc.

>
> With the understanding that it might not accomplish much of
> anything if we continue to be as inactive as we have been in
> recent months, is there any reason to not expose review requests
> and assignments to this list?
>
> thanks,
>    john
>
>
>
> --On Thursday, March 5, 2020 11:06 -0800 Marc Blanchet via
> Datatracker <[e-mail]> wrote:
>
>> Reviewer: Marc Blanchet
>> Review result: Ready with Issues
>>
>> I was assigned by the Internationalization Directorate to do a
>> review of this document with a specific eye on
>> internationalization and also a specific request from AD to
>> look at section 10.
>>
>> I would like to point out that in some cases, the spec seem to
>> provide a choice for the implementor/deposit provider to use
>> something else than UTF-8 for the non-ascii encoding. For
>> example, section 4.6.2.1. provides a choice of encoding for
>> csv files: "encoding  Defines the encoding of the CSV file
>> with the default encoding of "UTF-8". Moreover, section 10
>> talks about UTF-8 and UTF-16 and recommends UTF-8 instead of
>> making it mandatory. At the same time, there are multiple
>> fields in this spec that are defined as UTF-8. Therefore, it
>> would be appropriate and much less prone to interoperability
>> problems to make UTF-8 the only encoding possible, specially
>> given that most protocols, data payloads and software
>> librairies are using UTF-8 encoding. If the authors agree, then
>> section 10 and 4.6.2.1 could be revised, and probably adding a
>> paragraph in section 1 or 4 that states the only possible
>> encoding is UTF-8 for both CSV and XML files.
>>
>> Section 9.14 schema has a comment on ACE name field. Wonder if
>> A-label would be more appropriate.
>>
>> Section 5.6.2.1.1. While in other parts of the spec, the
>> encoding was clearly identified as UTF-8, the definition of
>> "<rdeCsv:fUName>  Name of the NNDN in Unicode character set
>> for the <csvNNDN:fAName> field element." does not state any.
>> Might want to say it clearly as UTF-8 like others.