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

Carsten Bormann <cabo@tzi.org> Fri, 24 November 2023 14:07 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE63C151080 for <rfc-interest@ietfa.amsl.com>; Fri, 24 Nov 2023 06:07:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kDEYYcUQaluB for <rfc-interest@ietfa.amsl.com>; Fri, 24 Nov 2023 06:07:05 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A157C14F738 for <rfc-interest@rfc-editor.org>; Fri, 24 Nov 2023 06:07:03 -0800 (PST)
Received: from eduroam-0647.wlan.uni-bremen.de (eduroam-0647.wlan.uni-bremen.de [134.102.18.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4ScGxv5k6lzDCcd; Fri, 24 Nov 2023 15:06:59 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <153bde12-5773-42ce-bfdf-392e4492c06b@gmx.de>
Date: Fri, 24 Nov 2023 15:06:59 +0100
Cc: rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 722527619.296361-0c26889c9966f7fbca23ad802acc85e1
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D66A3A2-5516-4924-8B1E-420871D862C5@tzi.org>
References: <310371.1700735021@dyas> <7C81D316-7D04-4941-BEE5-6AE8C96F0DE1@tzi.org> <D1F8F86E-80D7-4FC7-B7B5-32648ACB5D65@tzi.org> <MN2PR11MB3757AF8CCDF388BA5CECFE1AB9B8A@MN2PR11MB3757.namprd11.prod.outlook.com> <153bde12-5773-42ce-bfdf-392e4492c06b@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/M87mMuSb29yt957tY3FUFifaEaE>
Subject: Re: [rfc-i] getting SVG of RFC diagrams
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Nov 2023 14:07:09 -0000

On 2023-11-24, at 14:56, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> include a text file automatically.

All authoring environments have support for that.
(If not, it is trivial to add a Makefile.)

The more interesting aspect is painlessly retrieving the components (attachments, sourcecode, diagrams) out of the drafts and RFCs, and a URL naming convention would help with that.

I offer the naming convention provided by kramdown-rfc-extract-sourcecode.
(Which has been extended for the next version by making use of slugified names instead of counting unnamed components.)

This could lead to:
https://www.rfc-editor.org/rfc/rfc9334/svg/layered-attester.svg
https://www.rfc-editor.org/rfc/rfc9334/ascii-art/layered-attester.ascii-art
https://datatracker.ietf.org/doc/draft-ietf-cbor-edn-literal/abnf/cbor-edn.abnf

Grüße, Carsten