Re: [ietf-types] Registration of media typeimage/svg+xml

Keith Moore <moore@network-heretics.com> Thu, 25 November 2010 06:21 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAP6LDj1006234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2010 23:21:13 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id oAP6LDDo006233; Wed, 24 Nov 2010 23:21:13 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from new1.smtp.messagingengine.com (new1.smtp.messagingengine.com [66.111.4.221]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAP6LBYQ006227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-xml-mime@imc.org>; Wed, 24 Nov 2010 23:21:12 -0700 (MST) (envelope-from moore@network-heretics.com)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id AC5C720079; Thu, 25 Nov 2010 01:21:10 -0500 (EST)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 25 Nov 2010 01:21:10 -0500
X-Sasl-enc: Q5D2DL4GJBS6y8iY2a7CKEYxLZv/wGYTozgrTuzVAEdh 1290666069
Received: from 99-205-106-50.pools.spcsdns.net (99-205-106-50.pools.spcsdns.net [99.205.106.50]) by mail.messagingengine.com (Postfix) with ESMTPA id D6753400B34; Thu, 25 Nov 2010 01:21:07 -0500 (EST)
Subject: Re: [ietf-types] Registration of media typeimage/svg+xml
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4CEDF82A.7000502@it.aoyama.ac.jp>
Date: Thu, 25 Nov 2010 01:21:05 -0500
Cc: Chris Lilley <chris@w3.org>, Alexey Melnikov <alexey.melnikov@isode.com>, "ietf-types@iana.org" <ietf-types@iana.org>, "ietf-xml-mime@imc.org" <ietf-xml-mime@imc.org>, Henri Sivonen <hsivonen@iki.fi>, Larry Masinter <masinter@adobe.com>
Message-Id: <82567D04-0B63-4508-A3BB-2A966A447809@network-heretics.com>
References: <1364503167.20100617162624@w3.org> <1715145489.20101118190255@w3.org> <1912120148.20101118235236@w3.org> <4CE60C77.6000601@it.aoyama.ac.jp> <C68CB012D9182D408CED7B884F441D4D04FADF4AF3@nambxv01a.corp.adobe.com> <701217612.20101124231612@w3.org> <4CEDF82A.7000502@it.aoyama.ac.jp>
To: =?iso-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.1082)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id oAP6LCYP006228
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

+1.  

Let's try to make things clear for people who are reading just the type registration.  Someone who looks at the registration separately from the RFC or other specification shouldn't have to guess as to what "this specification" is.

Keith

On Nov 25, 2010, at 12:46 AM, Martin J. Dürst wrote:

> Hello Chris, Larry,
> 
> On 2010/11/25 7:16, Chris Lilley wrote:
>> 
>> On Wednesday, November 24, 2010, 9:14:12 PM, Larry wrote:
>> 
>> LM>  Martin, in a couple of places you complained that the SVG registration
>> LM>  template, contained in a W3C document, referred to "this specification",
>> LM>  and said:
>> 
>> LM>  # "this specification" doesn't work when the registration template is
>> LM>  # taken out of the SVG spec. Either say "the SVG specification" or
>> LM>  # explicitly reference a specific version of the specification.
>> 
>> LM>  However, I think it is common practice both in W3C and IETF, that
>> LM>  a registration template embedded within another document can
>> LM>  reasonably say "this specification" to mean the document in which
>> LM>  it is embedded,
> 
> In that context, this looks reasonable, but out of context, it does no longer make sense. Registration are often taken out of context, and should be able to stand alone, without readers having to guess what "the specification" might be.
> 
>> LM>  with the registry itself pointing to an
>> LM>  explicit version of the spec as well as the template within.
> 
> IANA often, if not always, lists the relevant RFC. But I haven't seen them listing other specifications. I may have missed it. Anyway, that's usually outside the registration, so the registration is still not standalone.
> 
>> Larry, your interjection is timely, as I was just about to edit the registration to address Martin's comment.
>> 
>> Given that we already have
>> 
>> Published specification:
>> 
>>     This media type registration is extracted from Appendix P of the
>>     SVG 1.1 specification. http://www.w3.org/TR/SVG/
>> 
>> I'm tempted to just s/this specification/the published specification/
> 
> Great! That makes the registration standalone, while at the same time doesn't look weird inside the specification.
> 
>> LM>  There are plenty of examples... perhaps those comments don't apply?
> 
> The fact that there are plenty of examples doesn't mean that we can't fix it when we have a chance. I don't think it's worth doing back and fixing one by one, but if we are working on a registration anyway, we can make it better form the start.
> 
>> LM>  (This comment applies to all registries, not just of media types.)
> 
> Agreed.
> 
> 
> Regards,   Martin.
> 
> -- 
> #-# Martin J. Dürst, Professor, Aoyama Gakuin University
> #-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types
>