[rfc-i] draft-iab-xml2rfc-02 and draft-flanagan-nonascii feedback: Internationalization Considerations and 7760

bclaise at cisco.com (Benoit Claise) Thu, 24 March 2016 16:24 UTC

From: bclaise at cisco.com (Benoit Claise)
Date: Thu, 24 Mar 2016 17:24:12 +0100
Subject: [rfc-i] draft-iab-xml2rfc-02 and draft-flanagan-nonascii feedback: Internationalization Considerations and 7760
In-Reply-To: <37C06524-A6E5-4DFD-9A59-DABE43BAC336@vpnc.org>
References: <56A9F27D.1080301@cisco.com> <37C06524-A6E5-4DFD-9A59-DABE43BAC336@vpnc.org>
Message-ID: <56F414AC.6000703@cisco.com>

Hi Paul,

Yes, it does the job ... until we have collisions from real names to a 
single ASCII name
Low probability I guess but my point was more: shouldn't RFC 7760 work 
with the author's full name?

Regards, Benoit

> On 28 Jan 2016, at 2:50, Benoit Claise wrote:
>
>> I believe we miss a requirement in RFC 7760 "Statement of Work for 
>> Extensions to the IETF Datatracker for Author Statistics"
>> Indeed, people might start authoring draft/RFC with their real live 
>> names.
>> If we want the stats to be correct, the tool should have a feature to 
>> combine the ASCII with the non-ASCII author name stats.
>
> Benoit:
>
> In Section 2.7, the <author> element has three new attributes:
>
> 2.7.1.  "asciiFullname" Attribute
>
>    The ASCII equivalent of the author's full name.
>
> 2.7.2.  "asciiInitials" Attribute
>
>    The ASCII equivalent of the author's initials, to be used in
>    conjunction with the separately specified asciiSurname.
>
> 2.7.3.  "asciiSurname" Attribute
>
>    The ASCII equivalent of the author's surname, to be used in
>    conjunction with the separately specified asciiInitials.
>
> Do these not meet your concern? Or is your concern that the RFC Editor 
> might not enforce the use of those attributes?
>
> --Paul Hoffman
> .
>