[rfc-i] I-D Action: draft-iab-rfc-nonascii-01.txt
Heather Flanagan (RFC Series Editor)
rse at rfc-editor.org
Tue Mar 1 10:12:56 PST 2016
On 2/29/16 1:09 PM, Julian Reschke wrote:
> On 2016-02-29 21:17, Joe Hildebrand (jhildebr) wrote:
>> The one place we *do* perform sorting is in references, with sortRefs
>> ='true'. In the prototype prep tool, I'm preferring the reference's
>> displayreference/@to, then falling back to the reference's @anchor.
>> that actually compares non-ascii strings.
>> One way to fix this would be to disallow non-ascii strings in
>> reference anchors and displayreference/@to. If that's the approach,
>> the non-ascii draft needs a note and the prep tool draft needs a step
>> to check for those.
> "The value needs to be a valid XML "Name" (Section 2.3 of [XML]),
> additionally constrained to US-ASCII characters [USASCII]. Thus, the
> character repertoire consists of "A-Z", "a-z", "0-9", "_", "-", ".", and
> ":", where "0-9", ".", and "-" are disallowed as start characters."
> "Keywords and citation tags must be ASCII only."
> I believe "citation tags" is about the anchor attribute on <reference>.
Yes, that's correct.
> So it seems all that needs to be done is aligning V3 with V2, and adding
> a similar constraint to <displayreference>.
> Best regards, Julian
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
More information about the rfc-interest