[rfc-i] draft-iab-xml2rfc-04, "2.19 <displayreference>"
julian.reschke at gmx.de (Julian Reschke) Wed, 27 July 2016 04:19 UTC
From: julian.reschke at gmx.de (Julian Reschke)
Date: Wed, 27 Jul 2016 06:19:28 +0200
Subject: [rfc-i] draft-iab-xml2rfc-04, "2.19 <displayreference>"
Message-ID: <86897458-2ade-cc57-c958-efb357231b58@gmx.de>
<https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-04.html#rfc.section.2.19>: "This element gives a mapping between the anchor of a reference and a name that will be displayed instead. This allows authors to display more mnemonic anchor names for automatically-included references. The mapping in this element only applies to <xref> elements whose format is "default"." So what about <relref>? Is that unaffected? "It is expected that this element will only be valid in input documents. It will be likely be removed by prep tools when preparing a final version after those tools have replaced all of the associated anchors, targets, and derivedContent attributes." I think that step was removed. "2.19.2 "to" Attribute (Mandatory) This attribute is a name that will be displayed as the anchor instead of the anchor that is given in the <reference> element. The string given must start with one of the following characters: 0-9, a-z, A-Z. The other characters in the string must be 0-9, a-z, A-Z, "-", ".", and "_"." Is there a requirement that there are no name collisions? Wouldn't it be a problem if a document has referenced named "A" and "B", and "B" gets remapped to "A" for display purposes? Best regards, Julian
- [rfc-i] draft-iab-xml2rfc-04, "2.19 <displayrefer… Julian Reschke