- From: <noah_mendelsohn@us.ibm.com>
- Date: Thu, 20 Apr 2006 23:12:26 -0400
- To: Chris Lilley <chris@w3.org>
- Cc: Julian Reschke <julian.reschke@gmx.de>, public-tag-announce@w3.org, Vincent Quint <Vincent.Quint@inrialpes.fr>, w3c-ac-members@w3.org, www-tag@w3.org
> Chris Lilley wrote: > > On Tuesday, April 18, 2006, 6:37:43 PM, Julian wrote: > > JR> Chris Lilley wrote: > >> ... > >> Still to do : > >> > >> SOAP and WebDAV use of text/xml > >> ------------------------------- > >> > >> Not clear what to say here; text/xml is > >> deprecated and we don't want to annoy them? Do > >> SOAP and WebDAV have other Media Types that > >> they are transitioning towards? ... > > JR> RFC2518bis (WebDAV) will deprecate text/xml in > JR> favor of application/xml, see > JR> <http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=42>). > > Great, thanks for the update. SOAP 1.2 has from the start had a preferred media type of application/soap+xml [1], support for which is mandatory in the widely used SOAP HTTP binding [2]. Bindings for other transports are free to choose any representation for the XML Infoset of the SOAP envelope, but application/soap+xml would be the obvious choice if an XML 1.0-compatible serialzation were desired (alternatives would include compressed, optimized, or encrypted representations, and bindings to other transports would be free to use such forms.) SOAP 1.1, which is widely deployed but is older not a Recommendation, does typically use text/xml. Anyway, I don't think there's a risk of "annoying" the SOAP community by pushing for members of the application/xxx+xml family, as it's a done deal in SOAP 1.2. Noah [1] http://www.w3.org/TR/soap12-part2/#ietf-draft [2] http://www.w3.org/TR/soap12-part2/#soapinhttp -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------
Received on Friday, 21 April 2006 03:13:40 UTC