Re: [rfc-i] getting SVG of RFC diagrams

[Carsten Bormann <[e-mail]>]

On Nov 27, 2023, at 00:07, Paul Hoffman <[e-mail]> wrote:
> 
> On 26 Nov 2023, at 14:53, Paul Kyzivat wrote:
> 
>> OK, it seems Carsten and I are in violent agreement.
>> Can we hear from some others here on rfc-interest on whether this is popular enough to pursue further? At some point it probably needs to be discussed on the tools list.
> 
> This discussion started with "I want to be able to extract $x" and veered into "the RPC should be making $x available to everyone for every RFC”.

Not sure that the RPC needs to do this.
The PoC shows that this can be a simple community-driven effort.
Also, if we want to give this a little more status, such a tool would fit into author tools or possibly in datatracker.

> A different path would be "it would be nice if I could extract $x from one or more RFCs locally".

Done: kramdown-rfc-extract-sourcecode.

> Given that no one has asked the original question before now, it seems likely to only be needed by a small number (maybe less than a few dozen) people.

As I said, people are using their homegrown tools, existing (but single-purpose) tools like aex, or even the extracted files published by IANA (YANG).  So the functionality is needed by quite a few people, but many people think this needs a lot of fudging as they don’t know that this extraction has become mostly straightforward since we keep the XML files around (and then a little more complex again with RFC 8792).

> Thus, a discoverable tool that does it might be better than making the RPC add the tool and the process for everyone.

Which points to author tools/datatracker, or, if the tools team doesn’t want to pick this one up, to a community effort.

Grüße, Carsten