W3C home > Mailing lists > Public > www-tag@w3.org > December 2005

Re: Registration of media type image/svg+xml

From: Chris Lilley <chris@w3.org>
Date: Fri, 16 Dec 2005 11:53:12 +0100
Message-ID: <126347793.20051216115312@w3.org>
To: MURATA Makoto <murata@hokkaido.email.ne.jp>
Cc: ietf-types@iana.org, www-tag@w3.org

On Friday, December 16, 2005, 2:26:53 AM, MURATA wrote:

Chris>>    Optional parameters:
Chris>>           None
Chris>> 
Chris>>           The encoding of an SVG document shall be determined by the
Chris>>           XML encoding declaration. This has identical semantics to the
Chris>>           application/xml media type in the case where the charset
Chris>>           parameter is omitted, as specified in RFC3023 sections
Chris>>           8.9, 8.10 and 8.11.


MM> The W3C TAG finding "Internet Media Type registration, consistency of use"
MM> says:
MM>         We recommend that section 7.1 of [RFC3023] be amended to
MM>         something like the following:

MM>         The use of the charset parameter, when the charset is reliably
MM>         known and agrees with the encoding declaration, is RECOMMENDED,
MM>         since this information can be used by non-XML processors to
MM>         determine authoritatively the charset of the XML MIME entity.

MM> Chris is behind this TAG finding, and I agree.

To clarify - I am not the sole or even primary author of that TAG
finding, but I stand behind it as an ex member of the TAG.

However, i am delighted to hear you say that you support the wording in
the TAG finding and support it's incorporation into RFC 3066 bis.

MM> Chris and I are co-editors for RFC 3023 bis.

Yes.

Once we can have the language you quote above in RFC 3023bis, I
would be much happier with a charset parameter on image/svg+xml.

With RFC 3023 as it stands, however, it has all the problems that the
TAG finding notes regarding inconsistency of dual metadata; in
consequence it was felt safer to omit the parameter. As RFC 3066
carefully describes a consistent handling of +xml media types where a
charset is omitted, this was not felt to be a problem.

MM> So, why does thie media type omit the charset param? I think that it
MM> makes a lot of sense to do exactly what the W3C TAG finding says.

I think so too. If you could send me the XML  source of RFC 3066 bis,
then as co-editor I can add the text that you quoted above.


-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG
Received on Friday, 16 December 2005 10:54:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:10 UTC