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

Carsten Bormann <> Thu, 23 November 2023 15:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7F9E7C14CF15 for <>; Thu, 23 Nov 2023 07:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Status: No, score=-1.909 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] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4Tul7cz7SwyE for <>; Thu, 23 Nov 2023 07:27:39 -0800 (PST)
Received: from ( [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 (Postfix) with ESMTPS id CF6C1C14EB19 for <>; Thu, 23 Nov 2023 07:27:38 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4SbhnM6yNYzDCdD; Thu, 23 Nov 2023 16:27:35 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Thu, 23 Nov 2023 16:27:35 +0100
Cc: Michael Richardson <>,
X-Mao-Original-Outgoing-Id: 722446055.437966-48ce3826b136e07dcf74bbaaae9998df
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <310371.1700735021@dyas> <>
To: Paul Hoffman <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [rfc-i] getting SVG of RFC diagrams
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Nov 2023 15:27:44 -0000

On 2023-11-23, at 16:16, Paul Hoffman <> wrote:
> On 23 Nov 2023, at 2:23, Michael Richardson wrote:
>> The question is: how to make these SVG files more easily available from the
>> HTML version of the RFC?
> Pedantically, it is not an SVG file but instead is an SVG element of the HTML.

(And of the XML — that’s why my original code didn’t work.)

> The first figure in that RFC has the code:
>         <div class="alignCenter art-svg artwork" id="section-3-2.1.1">
> <svg xmlns="" version="1.1" height="416" width="560" viewBox="0 0 560 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px">
> A possible (and backwards-compatible!) solution would be to add an id to each SVG element, which would then be a hoverable link.

A fragment identifier doesn’t really help with extracting (while it would help with naming extracted SVG elements, but that is easy by using the id on the div above).

(I think the underlying problem here is that browsers don’t provide for image extraction for SVG — does anybody know why?)

> I don't know if this in fact works; HTML experts here would. If it could work, please propose it for XMLRFCv3.1 over on the RSWG.

I don’t think the RSWG designs the HTML.

I don’t understand why we would want the HTML file to autonomously provide extraction of attachments; I’m more interested in having a separate URI for each attachment similar to the way Paul Kyzivat showed.

Grüße, Carsten