[rfc-i] "vanity" reference anchors

Paul Hoffman paul.hoffman at vpnc.org
Thu Apr 17 07:32:14 PDT 2014


On Apr 17, 2014, at 5:45 AM, Julian Reschke <julian.reschke at gmx.de> wrote:

>  <display-reference from="OLD" to="NEW" />

This seems fine.

> Allow these elements in two places:
> 
> 1) as child node of <rfc>
> 
> 2) as child node of <references>
> 
> Case 1) is useful for people who want to include a list of mappings maintained in a separate file. Case 2) is useful so that the mapping can be maintained close to the <reference> it affects.

I prefer Case 2 because it makes errors easier to find. 

> Syntax of @to: probably should be constrained, for instance, it whitespace. A pragmatic approach might be to allow all XML name characters (<http://www.w3.org/TR/REC-xml/#NT-NameChar>), lifting the constraint on the first character...
> 
> PS: xml2rfc IDs currently already allow non-ASCII characters (per XML's ID rules); we probably should add a USASCII-constraint, right?

Yes, and unfortunately yes.

--Paul Hoffman


More information about the rfc-interest mailing list