W3C home > Mailing lists > Public > www-tag@w3.org > January 2002

RE: Media types

From: David Orchard <david.orchard@bea.com>
Date: Wed, 9 Jan 2002 14:07:19 -0800
To: "'Mark Baker'" <distobj@acm.org>, <www-tag@w3.org>
Cc: <ietf-xml-mime@imc.org>
Message-ID: <00d201c1995a$024f1c90$180ba8c0@beasys.com>
Mark,

The same concerns I raised in xmlp apply here.  The slippery slope of
manifests appears.  What about other namespaces and vocabularies?  For
example, SOAP with my foo vocabulary using xml schema data types would be:
 application/xml; xmlns="soapns" xmlns="foons" xmlns="datatypesns"

or perhaps
 application/xml; xmlns="soapns foons datatypens"

This would have to duplicata all the xmlns decls in the document.

Does this make sense?

The way I see it, media types are broken for multiple namespace'd xml
documents, especially documents that are targetted to be frameworks like
soap.  The "+" syntax for media-types simply doesn't scale to these kinds of
documents.  I don't know how, but we have to find someway of either
expressing a manifest, or the name of a profile that is a reference to a
manifest.  At least with the use of xmlns we have some notion of versions as
well, given the namespace name would be used.

Cheers,
Dave

> -----Original Message-----
> From: www-tag-request@w3.org
> [mailto:www-tag-request@w3.org]On Behalf Of
> Mark Baker
> Sent: Wednesday, January 09, 2002 1:55 PM
> To: www-tag@w3.org
> Cc: ietf-xml-mime@imc.org
> Subject: Re: Media types
>
>
> [I should have CCd ietf-xml-mime on the initial post, but it didn't
> occur to me.  Anyhow, that post can be found here;
> http://lists.w3.org/Archives/Public/www-tag/2002Jan/0063.html ]
>
> Speaking for myself now,
>
> > Q. 3; What is, or what should be, the relationship between
> a media type
> > and an XML namespace?
>
> One of the thoughts that I had quite a while ago (that I believe came
> from something I saw from Dan Connolly), was of being able to migrate
> from media types to namespaces by exposing the namespace through an
> optional namespace parameter on a generic XML media type, for example
> XHTML could be described with;
>
>   application/xml; xmlns="http://www.w3.org/1999/xhtml"
>
> instead of with the custom type, application/xhtml+xml.
>
> I raised this with the authors of RFC 3023 long ago, but they rejected
> it.  But I believe it remains worth considering.  It seems to me to be
> a nice bridge, similar to the one the XMLP WG has taken with
> "relocating" SOAPAction to a parameter on the proposed SOAP media
> type[1].
>
>  [1]
> http://lists.w3.org/Archives/Public/xml-dist-app/2002Jan/0029.html
>
> MB
> --
> Mark Baker, Chief Science Officer, Planetfred, Inc.
> Ottawa, Ontario, CANADA.      mbaker@planetfred.com
> http://www.markbaker.ca   http://www.planetfred.com
>
>
Received on Wednesday, 9 January 2002 17:10:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:03 GMT