Re: [rfc-i] What do do about SVG
Adam Roach <adam@nostrum.com> Wed, 16 December 2020 04:54 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71B53A0EDA; Tue, 15 Dec 2020 20:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level:
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KFPOLx_2nLp; Tue, 15 Dec 2020 20:54:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1084A3A0EC3; Tue, 15 Dec 2020 20:54:07 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8DD3CF40749; Tue, 15 Dec 2020 20:54:00 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 8D60DF40749 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 20:53:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqejP742lgHY for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 20:53:55 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by rfc-editor.org (Postfix) with ESMTPS id BCB9AF40745 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 20:53:55 -0800 (PST)
Received: from Zephyrus.local (76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0BG4riIi058473 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 15 Dec 2020 22:53:46 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1608094429; bh=e9ns3i798wqyL/U9LN4jZ2jmrYv6JNAdBeCd8nabKCk=; h=Subject:To:References:From:Date:In-Reply-To; b=sglS/bXtOLaN+szt921C0ei1R0SAx+u1NhzaenCCuBkH4qKPsLvbYu1lJEHq+cy4i YTvqJSy4oiZzrp+RpJvU3fLooqagq25DrzHSCrco4F7TRXtfY7dSB5bqM1pZJMKMVN Sz2QRE68/LO26K98ChyqoE6dVKuWP93uo7Jgy/eg=
X-Authentication-Warning: raven.nostrum.com: Host 76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253] claimed to be Zephyrus.local
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
References: <f564019-d8b1-76c2-2768-c135d834dc32@iecc.com> <763b8195-6139-fb20-aa4e-2b4d89b5681c@gmail.com> <7b8ef1d3-f33b-fc1b-88d3-c399c7cb6279@alum.mit.edu> <0d979304-d3d6-3b8b-acab-7cbc37276250@joelhalpern.com> <916267c9-bf4c-7c0c-eb99-a24e73fc22df@gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <dca14b37-525a-ac60-20c2-8c8cbfb2830d@nostrum.com>
Date: Tue, 15 Dec 2020 22:53:37 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <916267c9-bf4c-7c0c-eb99-a24e73fc22df@gmail.com>
Content-Language: en-US
Subject: Re: [rfc-i] What do do about SVG
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
It is increasingly sounding like we got ourselves in this pickle by coming up with some reasonable policy decisions (no greyscale, no animations, no scripts, no external references), and then decided to use a technical enforcement mechanism by way of an SVG profile. Perhaps rather than using syntax to enforce policy, we could shift to using editorial control to enforce policy. That is, we specify that non-ASCII diagrams in RFCs are in full-fledged SVG, which has really, *really* good support in a lot of tools. And then put have in place instructions to the authors and to the RPC that describe the policy restrictions (such as those I list above), along with a tool -- in the style of id-nits -- that helps identify (in an advisory way) when those policies might not have been followed. /a On 12/15/20 19:27, Brian E Carpenter wrote: > On 16-Dec-20 14:08, Joel M. Halpern wrote: >> There are a whole host of issues that were raised. The agreement was to >> get simple graphics first, and then work on the othe rissues. >> >> For example, if one allows color, how does one ensure readability by >> those who are color blind. >> Similarly, if one allows gray scale, how does one make sure the result >> is understandable to those who do not perceived detailed contrast >> differences as easily. > Both of which are made worse by an assumed requirement to be able to > use a monochrome printer, where colours may not be distinguishable > and pale hues may be invisible. (Speaking purely for myself, I > really resent the price gouging for coloured inks.) > > Brian > >> And scripting is a nightmare all its own. >> >> Some issues are easier. For example, external URLs simply fail the test >> for archival representation. >> >> Yours, >> Joel >> >> On 12/15/2020 7:54 PM, Paul Kyzivat wrote: >>> On 12/15/20 5:51 PM, Brian E Carpenter wrote: >>> >>>> Restrictions we do need, IMHO, include >>>> - no colour >>>> - no greyscale >>>> - no scripting >>>> - no external URLs >>>> - use viewbox and *no* height/width, to allow proper scaling >>> ISTM that the "no colour" and "no greyscale" are only there in lieu of >>> the unstated requirement: >>> >>> Only allow drawings that can be also be drawn using text >>> graphics while retaining the key information content. >>> >>> Otherwise I don't see now they are justified. Am I missing something? >>> >>> Thanks, >>> Paul >>> _______________________________________________ >>> rfc-interest mailing list >>> rfc-interest@rfc-editor.org >>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest >> _______________________________________________ >> rfc-interest mailing list >> rfc-interest@rfc-editor.org >> https://www.rfc-editor.org/mailman/listinfo/rfc-interest >> > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://www.rfc-editor.org/mailman/listinfo/rfc-interest _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] What do do about SVG John R. Levine
- Re: [rfc-i] What do do about SVG Adam Roach
- Re: [rfc-i] What do do about SVG Brian E Carpenter
- Re: [rfc-i] What do do about SVG Paul Kyzivat
- Re: [rfc-i] What do do about SVG Joel M. Halpern
- Re: [rfc-i] What do do about SVG Brian E Carpenter
- Re: [rfc-i] What do do about SVG Adam Roach
- Re: [rfc-i] What do do about SVG Martin Thomson
- Re: [rfc-i] What do do about SVG Julian Reschke
- Re: [rfc-i] What do do about SVG Michael Richardson
- Re: [rfc-i] What do do about SVG Michael StJohns
- Re: [rfc-i] What do do about SVG Michael Richardson
- Re: [rfc-i] What do do about SVG Carsten Bormann
- Re: [rfc-i] What do do about SVG Brian E Carpenter
- Re: [rfc-i] What do do about SVG Martin Thomson
- Re: [rfc-i] What do do about SVG Carsten Bormann
- Re: [rfc-i] What do do about SVG Leonard Rosenthol
- Re: [rfc-i] What do do about SVG Martin J. Dürst
- Re: [rfc-i] What do do about SVG Nevil Brownlee
- Re: [rfc-i] [Tools-discuss] What do do about SVG Brian E Carpenter
- Re: [rfc-i] [Tools-discuss] What do do about SVG HANSEN, TONY L
- Re: [rfc-i] [Tools-discuss] What do do about SVG Leonard Rosenthol
- Re: [rfc-i] [Tools-discuss] What do do about SVG Brian E Carpenter
- Re: [rfc-i] [Tools-discuss] What do do about SVG Martin J. Dürst
- Re: [rfc-i] [Tools-discuss] What do do about SVG Leonard Rosenthol
- Re: [rfc-i] [Tools-discuss] What do do about SVG Robert Sparks