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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 25 November 2010 05:46 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAP5kYT5004501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2010 22:46:34 -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 oAP5kY8b004500; Wed, 24 Nov 2010 22:46:34 -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 scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id oAP5kWZb004495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-xml-mime@imc.org>; Wed, 24 Nov 2010 22:46:33 -0700 (MST) (envelope-from duerst@it.aoyama.ac.jp)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oAP5kVgZ024074 for <ietf-xml-mime@imc.org>; Thu, 25 Nov 2010 14:46:31 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 0b84_3025_5ac4d2be_f857_11df_a477_001d096c5782; Thu, 25 Nov 2010 14:46:31 +0900
Received: from [IPv6:::1] ([133.2.210.1]:40011) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S148FB56> for <ietf-xml-mime@imc.org> from <duerst@it.aoyama.ac.jp>; Thu, 25 Nov 2010 14:46:29 +0900
Message-ID: <4CEDF82A.7000502@it.aoyama.ac.jp>
Date: Thu, 25 Nov 2010 14:46:18 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Chris Lilley <chris@w3.org>
CC: Larry Masinter <masinter@adobe.com>, 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>
Subject: Re: [ietf-types] Registration of media typeimage/svg+xml
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>
In-Reply-To: <701217612.20101124231612@w3.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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>

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