[rfc-i] [IAB] draft-iab-xml2rfc-03, "2.19 <displayreference> "

julian.reschke at gmx.de (Julian Reschke) Wed, 02 March 2016 16:45 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Wed, 2 Mar 2016 17:45:17 +0100
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03, "2.19 <displayreference> "
In-Reply-To: <3963CC28-58A0-4B88-8C51-CDD850A2A962@cisco.com>
References: <56D607FC.4070903@gmx.de> <40F98072-B8FE-48D7-A506-946558ACB9D6@cisco.com> <56D688F7.5060508@gmx.de> <7F5B319D-106C-4928-8B48-88F9D3A3CF99@cisco.com> <EED7D730-19DD-4A4B-BAAA-B43C9706CB0B@vpnc.org> <56D71133.2070104@gmx.de> <3963CC28-58A0-4B88-8C51-CDD850A2A962@cisco.com>
Message-ID: <56D7189D.7080402@gmx.de>

On 2016-03-02 17:30, Joe Hildebrand (jhildebr) wrote:
> OK, here's an approach that would simplify things a little bit for the output formatters:
>
> - add a reference/@targetdisplay attribute
> - after the preptool has included all references
> - have the preptool fill in reference/@display with either displayreference/@to or reference/@target
> - preptool removes <displayreference>
> - preptool sorts references by reference/@display if rfc/@sortRefs is true
>
> I understand that this doesn't change much in terms of the amount of code to be written.  However, I think it makes it more likely that future output formatters will not ignore <displayreference>.

 From the preptool's point of view that makes sense.

However I continue to be worried by all the attributes sprinkled into V3 
because of the preptool, because:

a) it creates cases where we have two (or more) ways to achieve the same 
result, thus we'd need to state what takes priority, and

b) the size of the V3 vocab.

The latter point could be mitigated if we moved all preptool decorations 
into a separate namespace.

Best regards, Julian