Re: [rfc-i] What do do about SVG
"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 16 December 2020 01:08 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 C2CF53A0A4D; Tue, 15 Dec 2020 17:08:52 -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 (body has been altered)" header.d=joelhalpern.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 qlgwrLCoOP60; Tue, 15 Dec 2020 17:08:51 -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 064FC3A0A3E; Tue, 15 Dec 2020 17:08:50 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C8C40F40709; Tue, 15 Dec 2020 17:08:44 -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 DB241F40709 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 17:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 R6zCjV-OR20C for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 17:08:40 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by rfc-editor.org (Postfix) with ESMTPS id 18CC0F40708 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 17:08:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4CwcT93nlFz1nsKD; Tue, 15 Dec 2020 17:08:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1608080925; bh=Y0/N9hqIPI8FJ5CSxj+3H9C1+OajyGfud8+8gb76Iqc=; h=Subject:To:References:From:Date:In-Reply-To:From; b=XRAI0hThQ9Yz7Baq+Tm6bpStggx7LT+UckXFT//XeVuwqk6huRXbA6riEBjReGnX+ CJ+SDkHbg3KkQUxFXmQJhYKNMR4iCZRtrgklpibtPM9V8v9yws9ZDjD9WG0+IUZ3OU T/+yzqy/BlzD3xVWYkM6lXvEE9pPs5b2C50rHSSY=
X-Quarantine-ID: <Mt0wvzn4Mnm2>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4CwcT81wJfz1ns3Z; Tue, 15 Dec 2020 17:08:44 -0800 (PST)
To: 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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <0d979304-d3d6-3b8b-acab-7cbc37276250@joelhalpern.com>
Date: Tue, 15 Dec 2020 20:08:41 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <7b8ef1d3-f33b-fc1b-88d3-c399c7cb6279@alum.mit.edu>
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>
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. 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-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