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

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 23 November 2023 15:16 UTC

Return-Path: <paul.hoffman@vpnc.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 CA9E3C14CF15 for <rfc-interest@ietfa.amsl.com>; Thu, 23 Nov 2023 07:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ZNxkYknWNRXI for <rfc-interest@ietfa.amsl.com>; Thu, 23 Nov 2023 07:16:46 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70BEEC14F6EC for <rfc-interest@rfc-editor.org>; Thu, 23 Nov 2023 07:16:46 -0800 (PST)
Received: from [10.32.60.128] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 3ANFGiQR055214 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 23 Nov 2023 08:16:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.32.60.128]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: rfc-interest@rfc-editor.org
Date: Thu, 23 Nov 2023 07:16:43 -0800
X-Mailer: MailMate (1.14r5937)
Message-ID: <6062AA58-6798-4B82-9FE3-6FA1AF05F7CD@vpnc.org>
In-Reply-To: <310371.1700735021@dyas>
References: <310371.1700735021@dyas>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/Ua-zuL5v4rzzufcB55XkD7nL1sU>
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: Thu, 23 Nov 2023 15:16:50 -0000

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. The first figure in that RFC has the code:
         <div class="alignCenter art-svg artwork" id="section-3-2.1.1">
<svg xmlns="http://www.w3.org/2000/svg" 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. 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.

--Paul Hoffan