Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission

[Julian Reschke <[e-mail]>]

Am 28.07.2021 um 12:00 schrieb Carsten Bormann:
> On 2021-07-27, at 09:40, Julian Reschke <[e-mail]> wrote:
>>
>> Just stop generating v2 :-)
>
> There was a smiley here, but some people might take this at face value.
>
> As long as
>
>       <?rfc include="reference.RFC.2119”?>
>
> no longer works in v3, I’ll recommend people who can’t (*) convert to markdown to stay with v2 (preferably processed in hybrid mode).
> ...

Note I said "stop generating", as opposed to "stop authoring".

> This one specimen is, of course, just an example of how v2 was designed a little bit more for authors, while v3 is prioritizing a form of standards compliance that actually is not giving us anything on the author side.
>
> How is the below better than the above:
>
>      <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
>
> The v3 version encodes a URI that is brittle (you would probably already tell me that the authority component is wrong now, and the path name also is brittle).  It requires xi:include processing in any additional author-side tools.  And it is impossible to type from memory.

The fact that the URI is brittle is entirely the fault of the IETF. This
should have been fixed years ago. Cool URIs do not change.

My experience is that people copy & paste from existing documents or
references, so I really don't buy the "type from memory" argument.

The issue with the v2 PI is that is was never specified, and has
heuristics for document types wired in. Plus local caching. There's a
reason why a huge number of XML processed in AUTH48 before the switch
now does not compile anymore.

Yes, one could argue that for the common cases, a simpler syntax would
be nice. -> Feature request.

> I’m a German, so I do have the genes for excessive bureaucracy.
> But this…  No.
>
> Grüße, Carsten
>
> (*) You co-author might retire soon and this is “their last RFC”, so they don’t want to learn something new while they have ingrained RFCXMLv2 skill.  Or some such.

Then run through the converter, and edit from there?

Best regards, Julian