Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artwork> src and content confusion
Paul Hoffman <paul.hoffman@icann.org> Wed, 03 October 2018 23:33 UTC
Return-Path: <paul.hoffman@icann.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBFE130DC3 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 16:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 3giZDag1mX-k for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 16:33:13 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 502F9130DBE for <xml2rfc-dev@ietf.org>; Wed, 3 Oct 2018 16:33:13 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 3 Oct 2018 16:33:11 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Wed, 3 Oct 2018 16:33:10 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: XML Developer List <xml2rfc-dev@ietf.org>
Thread-Topic: [Ext] [xml2rfc-dev] RFC 7991 issue #34: <artwork> src and content confusion
Thread-Index: AQHUW3FxrOFfTu1Ep0uTl65AVFRyJQ==
Date: Wed, 03 Oct 2018 23:33:10 +0000
Message-ID: <A54EFD42-1CB5-4306-94EC-4F2A9A09CB98@icann.org>
References: <DA5858DE-A402-440F-83C4-4CE6C44E2E63@icann.org>
In-Reply-To: <DA5858DE-A402-440F-83C4-4CE6C44E2E63@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_A0BBF203-7ADA-4D1D-808A-0BB224FA0EA5"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Sf2rs2xpJrSYoZe90X18pQK-m4w>
Subject: Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artwork> src and content confusion
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 23:33:15 -0000
> Section 2.5 > > Alternatively, the "src" attribute allows referencing an external > graphics file, such as a vector drawing in SVG or a bitmap graphic > file, using a URI. In this case, the textual content acts as a > fallback for output representations that do not support graphics; > thus, it ought to contain either (1) a "line art" variant of the > graphics or (2) prose that describes the included image in sufficient > detail. > > And later: > > It is an error to have both a "src" attribute and content in the > <artwork> element. Yeeps. That later sentence seems wrong, particularly when you look at the "alt" attribute: 2.5.2. "alt" Attribute Alternative text description of the artwork (which is more than just a summary or caption). When the art comes from the "src" attribute and the format of that artwork supports alternate text, the alternative text comes from the text of the artwork itself, not from this attribute. The contents of this attribute are important to readers who are visually impaired, as well as those reading on devices that cannot show the artwork well, or at all. --Paul Hoffman
- [xml2rfc-dev] RFC 7991 issue #34: <artwork> src a… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artw… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artw… Robert Sparks
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artw… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #34: <artw… Jim Schaad