Re: [xml2rfc-dev] docName?

[Julian Reschke <[e-mail]>]

On 10.05.2019 15:09, Henrik Levkowetz wrote:
> On 2019-05-10 15:03, Henrik Levkowetz wrote:
>> Hi Miek,
>>
>> On 2019-05-10 14:02, Miek Gieben wrote:
>>> [ Quoting <[e-mail]> in "Re: [xml2rfc-dev] docName?..." ]
>>>> No, the docName should not change to a number; the docName is used to add
>>>> metadata about the draft from which an RFC is derived when writing a v3
>>>> RFC in html format, and to insert the draft name when writing draft output.
>>>>
>>>>>> Also because there is a number attribute
>>>>>> (https://tools.ietf.org/html/rfc7991#section-2.45.7), which I added eons
>>>>>> ago because xml2rfc complained; maybe that can be removed now (because
>>>>>> its deprecated) ?
>>>>
>>>> No, as Julian indicates, follow 7749 with respect to metadata.  The number
>>>> still indicates which RFC number is to be generated.
>>>>
>>>> 	Henrik
>>>
>>> Ok, thanks for the info; I'll make those changes.
>>>
>>> One more question if you have docName will xml2rfc; will this work as well:
>>>
>>> Warning: Expected a <link> with rel='prev' providing the datatracker url for the origin draft.
>>
>> The v2v3 converter inserts a <link> with rel='prev' if docName is given;
>> for v3 xml you should set that.  I think, however, that this warning should
>> more correctly be a note or comment.
>
> No, I'm wrong.  It should be at least a warning, possibly an error.  This is
> covered in https://tools.ietf.org/html/rfc7998#section-5.6.3 .  This is
> emitted only in RFC production mode.


...but see
<https://github.com/rfc-format/draft-iab-rfcv3-preptool-bis/issues/3>.