[issue10730] add .svgz to mimetypes.suffix_map and .svg to types_map

[R. David Murray]

R. David Murray <rdmur...@bitdance.com> added the comment:

Yes, adding the x- version would probably be pointless as most likely nobody 
uses it.

Has anyone found any definitive info on where exactly in the approval process 
image/svg+xml is?

I think we should probably just go ahead and put it in, but it would be nice to 
link to some mailing list discussion somewhere that indicates that it is 
solidly standards track.

I found a mailing list posting from 2000 about browser support.

I found this: http://www.w3.org/TR/SVG/intro.html from June 2010 saying the 
registration was in progress at the w3c.  How w3c registration relates to IANA 
registration is not entirely clear, but most likely IANA wouldn't register it 
without w3c approving it first.

RFC 3023 mentions it and says it hasn't been approved yet so it shouldn't be 
used.  That was in 2001.

Why the incredibly long delay?

As best as I can guess, the mime-type registration is conditioned on the 
acceptance of the underlying SVG standard it references, and that standard (SVG 
1.1) has not yet been ratified by the W3C, which is, if I'm underanding the 
RFCs correctly, required for IANA approval of the media type request.  SVG 1.1 
has, according to wikipedia, been put out for Last Call.

All of which seems pretty irrelevant to the value and likely stability of the 
image/svg+xml name itself.  Since all the major browsers are supporting it, as 
far as I can tell, I think Python should too.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10730>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com