[rfc-i] [rfc-design] draft-iab-xml2rfc-03, "1.3.4 Additional Changes from v2"

[julian.reschke at gmx.de (Julian Reschke)]

On 2016-06-22 01:56, Paul Hoffman wrote:
> On 17 Jun 2016, at 7:25, Julian Reschke wrote:
>
>> <https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#rfc.section.1.3.4>:
>>
>>
>> "Made <seriesInfo> a child of <front>, and deprecated it as a child of
>> <reference>. This also deprecates some of the attributes from <rfc>
>> and moves them into <seriesInfo>."
>>
>> I recently worked on my implementation of that change, and found it to
>> cause lots of friction because code that supports v2 and v3 now needs
>> to support it in two places.
>>
>> It'll also cause problems with the reference libraries; do we expect
>> them to switch to v3 format (breaking older existing documents)?
>
> That's an open question. Maybe they'll support both versions.

They can only do that if we specify what it means to have <seriesInfo> 
in both places. Otherwise formatters will generate duplicate entries in 
the output.

>> AFAIU, this cause was motivated by the desire to use <seriesInfo> also
>> outside <reference>, thus for the current document. If that's the
>> goal, ouldn't it be much simpler to keep <seriesInfo> as child element
>> of reference>, and just allow it as child element of <rfc>?
>
> We discussed this earlier, and we didn't agree that it would be "much
> simpler".

Pointer?

I'm now arguing from implementation experience; I hope that counts. :-)

Best regards, Julian