Re: [Xml-sg-cmt] is "example" an acceptable type within <artwork>
Lynne Bartholomew <lbartholomew@amsl.com> Fri, 04 March 2022 02:45 UTC
Return-Path: <lbartholomew@amsl.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E8A3A0D07 for <xml-sg-cmt@ietfa.amsl.com>; Thu, 3 Mar 2022 18:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 2ZO32pZyEtvR for <xml-sg-cmt@ietfa.amsl.com>; Thu, 3 Mar 2022 18:45:39 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14CC63A0CF9 for <xml-sg-cmt@ietf.org>; Thu, 3 Mar 2022 18:45:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id EA980425C194; Thu, 3 Mar 2022 18:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EKekCisuLwhb; Thu, 3 Mar 2022 18:45:38 -0800 (PST)
Received: from [10.0.0.63] (c-67-164-82-70.hsd1.ca.comcast.net [67.164.82.70]) by c8a.amsl.com (Postfix) with ESMTPSA id D357E425A344; Thu, 3 Mar 2022 18:45:38 -0800 (PST)
From: Lynne Bartholomew <lbartholomew@amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 03 Mar 2022 18:45:38 -0800
References: <b749b97d-9a78-bf28-50be-baaec9e86e93@greenbytes.de> <C243E539-F02B-48B5-9AFB-DFEBB9914DE6@amsl.com>
To: "xml-sg-cmt@ietf.org" <xml-sg-cmt@ietf.org>, RFC System <rfc-editor@rfc-editor.org>
In-Reply-To: <C243E539-F02B-48B5-9AFB-DFEBB9914DE6@amsl.com>
Message-Id: <B79AF33A-DE79-4E04-898E-F4632C4D672C@amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/CsfJfV5dLpZrs6q2i-DkacndPjs>
X-Mailman-Approved-At: Fri, 04 Mar 2022 06:45:54 -0800
Subject: Re: [Xml-sg-cmt] is "example" an acceptable type within <artwork>
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2022 02:45:46 -0000
Hi, KC and everyone. Thank you for sending this to <xml-sg-cmt@ietf.org>, KC! A similar question came up for me as well -- this time for <sourcecode>. draft-ietf-httpbis-priority-12 has four <sourcecode> entries with type="example" and two with type="drawing", so I asked the authors if they would like to request that type="example" and type="drawing" be added to the list of usable sourcecode types on <https://www.rfc-editor.org/materials/sourcecode-types.txt> (because I was under the impression that if a type isn't explicitly listed as acceptable, it shouldn't be used unless someone decides to add it to the list in question, i.e., <artwork> or <sourcecode>). In the case of both <artwork> and <sourcecode>, is it OK for authors to use whatever type they deem appropriate for their document, even if the type isn't used or listed anywhere else? Thanks again. Lynne > On Mar 3, 2022, at 5:17 PM, Karen Moore <kmoore@amsl.com> wrote: > > Hi team, > > In RFC-to-be 9112 (which is currently in AUTH48), Julian would like to set the type to “example” within the <artwork> elements (since they are not ascii-art). Is this acceptable, or do you see any issues with this? There are three instances in the text. > > One example > > Old: > <artwork type=“ascii-art"><![CDATA[ > https://www.example.org/pub/WWW/TheProject.html > ]]></artwork> > > New: > <artwork type=“example"><![CDATA[ > https://www.example.org/pub/WWW/TheProject.html > ]]></artwork> > > > The files are here: > https://www.rfc-editor.org/authors/rfc9112.txt > https://www.rfc-editor.org/authors/rfc9112.pdf > https://www.rfc-editor.org/authors/rfc9112.html > https://www.rfc-editor.org/authors/rfc9112.xml > > Thanks, > Karen > >> Begin forwarded message: >> >> From: Julian Reschke <julian.reschke@greenbytes.de> >> Subject: Re: AUTH48 [KC]: RFC 9112 <draft-ietf-httpbis-messaging-19.txt> NOW AVAILABLE >> Date: March 1, 2022 at 11:47:25 AM PST >> To: Karen Moore <kmoore@amsl.com>, "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net> >> Cc: httpbis-chairs@ietf.org, httpbis-ads@ietf.org, Tommy Pauly <tpauly@apple.com>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org> >> >> Am 11.02.2022 um 20:21 schrieb Karen Moore: >>> ... >> >> Hi Karen, >> >> I found three cases where we have examples in <artwork> elements, and none of these cases are "ascii-art". Please revert (or apply attached XML). >> >> Best regards, Julian > <rfc9112-to-be.xml> > >
- [Xml-sg-cmt] is "example" an acceptable type with… Karen Moore
- Re: [Xml-sg-cmt] is "example" an acceptable type … Lynne Bartholomew
- Re: [Xml-sg-cmt] is "example" an acceptable type … Sandy Ginoza
- Re: [Xml-sg-cmt] is "example" an acceptable type … John R Levine
- Re: [Xml-sg-cmt] is "example" an acceptable type … Julian Reschke