Re: [Tools-discuss] <contact/>: asciiFullname should be latinFullname

[Julian Reschke <[e-mail]>]

Am 07.10.2020 um 16:32 schrieb Carsten Bormann:
> On 2020-10-07, at 16:20, Julian Reschke <[e-mail]> wrote:
>>
>>> The original specification was strict ASCII.  (...)
>>
>> Pointer?
>
> RFC 7991 Section 2.7.1-.3 (and a ton of “ascii” attributes patched into other places) says “ASCII”.  Not “strict ASCII”, but I don’t know the difference between the two.  RFC 7997 says ASCII or ASCII-only when it really is talking about “accessible to a reader familiar with the Latin writing system” (except maybe for Section 3.4); that is exactly the bug that I’m trying to address.
>
> Of course, the Relax-NG in RFC 7991 doesn’t enforce that textual mandate, so no schema change is needed to fix this bug.

RFC 7991 Section 2.7 is about <author>.

What we are discussing here is using names in prose, that is not
described in 7991.

RFC 7997 ("The Use of Non-ASCII Characters in RFCs") says in Section 3.2
(<https://greenbytes.de/tech/webdav/rfc7997.html#rfc.section.3.2>):

"Person names may appear in several places within an RFC (e.g., the
header, Acknowledgements, and References). When a script outside the
Unicode Latin blocks [UNICODE-CHART] is used for an individual name, an
author-provided, ASCII-only identifier will appear immediately after the
non-Latin characters, surrounded by parentheses. This will improve
general readability of the text."

So the v3 RFCs indeed says that an ASCII-only identifier should be
present (I forgot about that). What RFC 7997 does *not* say is how the
XML for that is supposed to look. That's right because that's 7991's
job, and my recollection of the history of 7991 is that we did not feel
any special markup was needed for that.

Best regards, Julian