OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] What does SOAP really add?

[ Lists Home | Date Index | Thread Index ]

> -----Original Message-----
> From: Simon St.Laurent [mailto:simonstl@simonstl.com]
> Sent: Sunday, April 21, 2002 1:19 PM
> To: Joshua Allen
> Cc: xml-dev@lists.xml.org
> Subject: RE: [xml-dev] What does SOAP really add?
> On Sun, 2002-04-21 at 15:06, Joshua Allen wrote:
> > Are you asking what benefit SOAP brings vs. everyone just rolling
> > own XML serialization/envelope formats?
> Yes.

At this point in time, the primary benefit of SOAP is a common framing
format (e.g., Envelope/Header/Body) with a well-understood extensibility
model. Not rocket science, but pretty widely accepted as the way web
services will work.

The serialization aspects of SOAP became less important as XML Schema
solidified (remember that when we started in 1998, there wasn't even a
schema WG in the W3C). 

At this point, I believe most SOAP plumbers have conceded that XML
Schema will be the dominant type system and metadata format for interop.
How one converts from their local type system to the world of XML Schema
is a local problem that is (and should be) outside the scope of SOAP. 

In MSFT-land, we do the conversion by importing XML Schema into our
runtime and making the "foreign" types look local. That technology is
broadly useful outside the scope of SOAP and/or web services, so we make
it accessible everywhere, although I'm sure there are lots of customers
who have no idea this is even in the platform.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS