Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Mime type for compound document.

From: Dave Pawson <davep@-------.--.-->
To: XML Developers List <xml-dev@-----.---.--->
Date: 12/7/2007 5:08:00 PM
Mark Baker wrote:

>> Is it the case then that every time someone creates a new namespace
>> they have to create a new MIME type to go with it?!
> 
> Not necessarily a new namespace, but every new language should have a
> new media type, yes.
> 
Which definition of language Mark?

> I gave a presentation to the W3C CDF WG a while back that might help
> shed some light on the subject;
> 
> http://www.markbaker.ca/Talks/2004-media-types-and-compdocs/slide1-0.html

 From which
Many assume that applications will dispatch on the root namespace
But implementations don't, in general, do this ... ok, newer ones do, 
mostly. Older ones don't though.

and
Such a document might be handled....
and
Obviously there's some wriggle room for interpretation....

I like the arguments put forward, but you seem to accept it's all
ifs and buts and maybes as of today?
Content-Type: application/compound+xml (??)
<html:body cdf:type="image/svg+xml">
   <svg:svg ... />

Seems quite workable and extensible (given your security caveats).


Is it a TAG issue? They don't seem to have done much other than say 
register?
http://www.w3.org/2001/tag/2002/0129-mime

Nothing about applications or dispatching.
Suggests it's one of those that nicely falls in the cracks?



regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent