Re: [xml2rfc] Experience with --v2v3

[Henrik Levkowetz <[e-mail]>]

On 2019-12-15 20:37, Brian E Carpenter wrote:
> On 16-Dec-19 08:20, Paul Kyzivat wrote:
>> On 12/15/19 6:38 AM, Robert Moskowitz wrote:
>>>
>>>
>>> On 12/15/19 5:03 AM, Julian Reschke wrote:
>>>> On 15.12.2019 03:19, Robert Moskowitz wrote:
>>>>> ...
>>>>> I really did not like it expanding <?rfc> references like:
>>>>>
>>>>>      <?rfc include="reference.RFC.2119.xml"?>
>>>>>
>>>>> The reason for the references rather than the content is that they can
>>>>> change (like author changes to drafts).  Thus I feel they are wrong to
>>>>> expand and should be left as is.  I manually put them back.
>>>>> ...
>>>>
>>>> There's the "--add-xinclude" command line switch which is supposed to
>>>> change this:
>>>>
>>>>>   V2-V3 Converter Options:
>>>>>     --add-xinclude                      replace reference elements 
>>>>> with RFC
>>>>>                                         and Internet-Draft seriesInfo 
>>>>> with the
>>>>>                                         appropriate XInclude element
>>>>
>>>> Best regards, Julian
>>>
>>> I will give this a try shortly, but I feel that the switch is 
>>> backwards.  The default should be NOT to expand xincludes.
>>>
>>> rfc xincludes are used for a vary valid reason.  What is the reason to 
>>> remove them for v3?  And making putting them back needing special action?
>> 
>> Do I understand correctly that the translation takes a wildcard 
>> reference (to the latest version of the draft) and binds it to a 
>> particular version at the time of the translation?
>> 
>> If so, that seems like the wrong thing to do.
> 
> Utterly wrong.

Agreed.

> How does one refer to the latest version in v3 format?
> Something like
> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-andrews-tcp-and-ipv6-use-minmtu.xml"/>
> doesn't work.

Given an existing URL, the handling of non-version-specific references in
v2 and v3 should be equivalent.  Any reference URL that works in v2 should
work in v3.  In v3, as in v2, the version-specific URLs include 'draft-'
in the name, while the non-version-specific URLs omits 'draft-'.  This is a
legacy from Marshall Rose's time, and the inconsistency has been the same
for years.

The correct <xi:include> entry for the non-version-specific reference should
be:

  <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.andrews-tcp-and-ipv6-use-minmtu.xml"/>

I've handled this differently in the reference entries generated on-the-fly
by the datatracker; there all of the following forms:

   bibxml3/reference.I-D.andrews-tcp-and-ipv6-use-minmtu.xml
   bibxml3/reference.I-D.draft-andrews-tcp-and-ipv6-use-minmtu.xml
   bibxml3/reference.I-D.andrews-tcp-and-ipv6-use-minmtu-04.xml
   bibxml3/reference.I-D.draft-andrews-tcp-and-ipv6-use-minmtu-04.xml

work.  Expanding the second to the full path gives:

https://datatracker.ietf.org/doc/bibxml3/reference.I-D.draft-andrews-tcp-and-ipv6-use-minmtu.xml


Best regards,

	Henrik