Re: [ietf-types] Updating registrations

Julian Reschke <julian.reschke@gmx.de> Thu, 07 June 2012 20:02 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F3D11E8148 for <ietf-types@ietfa.amsl.com>; Thu, 7 Jun 2012 13:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.235
X-Spam-Level:
X-Spam-Status: No, score=-104.235 tagged_above=-999 required=5 tests=[AWL=-1.636, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAvkbObAdYte for <ietf-types@ietfa.amsl.com>; Thu, 7 Jun 2012 13:02:11 -0700 (PDT)
Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id A4D3E11E8147 for <ietf-types@ietf.org>; Thu, 7 Jun 2012 13:02:10 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora8.dc.icann.org (8.13.8/8.13.8) with SMTP id q57K1n1n003931 for <ietf-types@iana.org>; Thu, 7 Jun 2012 20:02:09 GMT
Received: (qmail invoked by alias); 07 Jun 2012 19:35:05 -0000
Received: from p5DD972CB.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.114.203] by mail.gmx.net (mp071) with SMTP; 07 Jun 2012 21:35:05 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/U7AEPHPjUQPIJ60/QaeNVte3HryOfB/W1uBVPud JE/gvJaHkn/sNB
Message-ID: <4FD1023F.2090001@gmx.de>
Date: Thu, 07 Jun 2012 21:34:23 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <D6788E6173C4A64B9B42DE1F2EB94EB9BBE1DC84@exm02-wvp.cisra.canon.com.au> <jqptr7hk02ojuqnil4fuil5vfgtjpur2kv@hive.bjoern.hoehrmann.de>
In-Reply-To: <jqptr7hk02ojuqnil4fuil5vfgtjpur2kv@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Greylist: Delayed for 00:26:42 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Thu, 07 Jun 2012 20:02:09 +0000 (UTC)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Updating registrations
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 20:02:11 -0000

On 2012-05-25 04:10, Bjoern Hoehrmann wrote:
> * Nikos Andronikos wrote:
>> Removal of the Media Type Registration chapter from SVG 2
>>
>>    CM: I thought that because we have the media type registered
>>    now that we don't need the chapter
>>    ... I asked Chris
>>    ... He thinks we don't
>>    ... unless there are objections, I'll remove it
>>    ... it existed in the spec so the registry could point to
>>    something
>>    ... the media type won't mean anything difference between SVG 1
>>    and SVG 2. not neccessary to resubmit
>
> W3C's http://lists.w3.org/Archives/Public/www-svg/2012May/0084.html SVG
> Working Group registered image/svg+xml some time ago and is revising the
> underlying format, and as above there is proposal that the specification
> defining the new version does not include the registration template, and
> I assume not "resubmitting" means it is also being proposed that there
> will be no attempts to update the registration information on file. FYI.

There are two aspects to this:

1) The IANA registry currently links to 
<http://www.w3.org/TR/SVG/mimereg.html>; will that become a dangling 
reference?

2) If the actual format changes, the assumption is that the media type 
registration is *updated*.

Best regards, Julian