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

Chris Lilley <chris@w3.org> Tue, 07 December 2010 14:51 UTC

Return-Path: <chris@w3.org>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5C303A69A1 for <ietf-types@core3.amsl.com>; Tue, 7 Dec 2010 06:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.294
X-Spam-Level:
X-Spam-Status: No, score=-8.294 tagged_above=-999 required=5 tests=[AWL=2.005, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbnFhNX+bgRq for <ietf-types@core3.amsl.com>; Tue, 7 Dec 2010 06:51:22 -0800 (PST)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by core3.amsl.com (Postfix) with ESMTP id 4E62A3A69A2 for <ietf-types@ietf.org>; Tue, 7 Dec 2010 06:51:21 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id oB7EqP2i001480 for <ietf-types@iana.org>; Tue, 7 Dec 2010 06:52:46 -0800
Received: from localhost ([127.0.0.1]) by jay.w3.org with esmtpa (Exim 4.69) (envelope-from <chris@w3.org>) id 1PPytw-0005Pg-Ae; Tue, 07 Dec 2010 09:52:20 -0500
Date: Tue, 07 Dec 2010 15:52:19 +0100
From: Chris Lilley <chris@w3.org>
X-Mailer: The Bat! (v3.95.6) Home
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <335994208.20101207155219@w3.org>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
In-Reply-To: <4CEE0291.2040305@it.aoyama.ac.jp>
References: <1364503167.20100617162624@w3.org> <1715145489.20101118190255@w3.org> <1912120148.20101118235236@w3.org> <1034064166.20101124233635@w3.org> <4CEDF469.7060101@it.aoyama.ac.jp> <4CEE0291.2040305@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [208.77.188.39]); Tue, 07 Dec 2010 06:52:46 -0800 (PST)
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-types@iana.org, ietf-xml-mime@imc.org
Subject: Re: [ietf-types] Registration of media typeimage/svg+xml
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Chris Lilley <chris@w3.org>
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 07 Dec 2010 14:51:25 -0000

On Thursday, November 25, 2010, 7:30:41 AM, Martin wrote:

MJD> What about:

MJD> Fragment Identifiers

MJD> For documents labeled as application/svg+xml, the fragment
MJD> identifier notation follows the XML Pointer Language (XPointer) 
MJD> Framework (see http://www.w3.org/TR/xptr-framework/). Fragment 
MJD> identifiers are either Shorthand Pointers (formerly called barenames) or
MJD> SVG view specifications. For details, please see Section 17.3.2 of the
MJD> SVG specification 
MJD> (http://www.w3.org/TR/SVG11/linking.html#SVGFragmentIdentifiers).


MJD> or some such. 

I looked into this. At first, I was going to normatively reference XPointer Framework as you suggested.

However, the SVG WG had made a decision not to reference XPointer (superceeded) and not to reference XPointer Framework either, partly because of concerns over the scope of the conformance criteria
http://www.w3.org/TR/xptr-framework/#conformance
and also because this is not in any case needed just to define barenames.

So I have added adapted wording:


    Fragment Identifiers

        For documents labeled as application/svg+xml, the 
        fragment identifier notation is either Shorthand Pointers
        (formerly called barenames) or the SVG-specific SVG Views
        syntax; 
        http://www.w3.org/TR/SVG/linking.html#LinksIntoSVG
        both described in the fragment identifiers section of the 
        SVG specification.
        http://www.w3.org/TR/SVG/linking.html#SVGFragmentIdentifiers


 >>> Published specification:

 >>> This media type registration is extracted from Appendix P of the
 >>> SVG 1.1 specification.
 >>> http://www.w3.org/TR/SVG/mimereg.html

MJD> First, we made some tweaks, and second, the published specification is
MJD> all of SVG 1.1, not just the mimereg part, as far as I understand.

Also fixed; both Appendix P and the spec as a whole are separately referenced.

Published specification:

    This media type registration is extracted from Appendix P 
    http://www.w3.org/TR/SVG/mimereg.html
    of the SVG 1.1 specification.
    http://www.w3.org/TR/SVG/

-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups