W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2000

RE: text/xml for SOAP (and XP) considered harmful

From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
Date: Tue, 12 Dec 2000 10:44:21 -0800
Message-ID: <00d801c0646b$8b241590$308f3b9d@redmond.corp.microsoft.com>
To: "Larry Cable" <larry.cable@sun.com>, "Larry Masinter" <LMM@acm.org>
Cc: <mmurata@trl.ibm.co.jp>, <xml-dist-app@w3.org>
But there already *is* an identifier for SOAP - it is

 http://schemas.xmlsoap.org/soap/envelope/

Why not say something like

 Content-Type: text/xml; ns="http://schemas.xmlsoap.org/soap/envelope/"

where the ns parameter specifies the ns identifier of outermost element.

I don't understand why a new naming convention has to be introduced here.

Henrik

> > Well, MIME media types are not just 'names', they're specifically
> > used to invoke different kinds of processing
> >
> > From
> >
> > http://search.ietf.org/internet-drafts/draft-murata-xml-09.txt
> >
> > section 7:
> >
> >    XML generic processing is not always appropriate for 
> XML-based media
> >    types. For example, authors of some such media types may 
> wish that
> >    the types remain entirely opaque except to applications that are
> >    specifically designed to deal with that media type. By 
> NOT following
> >    the naming convention '+xml', such media types can avoid 
> XML-generic
> >    processing. Since generic processing will be useful in 
> many cases,
> >    however -- including in some situations that are difficult to
> >    predict ahead of time -- those registering media types SHOULD use
> >    the '+xml' convention unless they have a particularly compelling
> >    reason not to.
Received on Tuesday, 12 December 2000 13:44:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:58 GMT