null
Web Service Sublimation For the record, messages should be typed, described in XSD, and as loosely coupled as possible -- as specified in their XSD definitions. Excelent article. Consisely captures the history and tradeoffs.
One sentence in particular captures the debate that Don Box and I started over beers last week. If they [are] described with another technology, like Java, the promise of interoperability based on XML technologies will be lost. Exactly. My feeling is that a one-to-one and onto mapping of XML schema to any pre-existing language is neither possible nor desirable. So while the approach of having metadata associated with a class definition define the serialization is effective for most situations, I still believe that .NET remoting and/or ASP.NET need to have a mechanism for allowing an individual service to augment or override this. Simon agrees. As we left it, Don remained unconvinced.
As Tim Ewald (one of the co-authors of this XML.com article)
said at last week's DevCon,
everyone starts from their own language/platform and works
towards the middle and hopes we'll all get to the same place.
No successful API was
ever defined that way.