On Sat, Mar 15, 2008 at 5:44 PM, Rob Heittman <[EMAIL PROTECTED]> wrote: > > Great recommendation. I hadn't played with XOM before -- it looks very nice > and I will try it out in an upcoming project! I'd still argue that it is > good to understand the W3C DOM API, whether or not one actually uses it, > because it is ubiquitous and largely similar in many languages and > environments.
maybe, but DOM sucks in JavaScript and .NET too. If there is one thing worse, its XML Schema. > > Empirically, I think the spartan nature of REST designs often encourages > adopters to use very simple markup for representations. Simple XML and JSON > documents are quite easy to create even with bad or no tools, and the real > advantages of more powerful and language-adapted APIs may not show up as > critically for users who have never heard of, say, an XML namespace. yes. And most importantly of all: doesnt mandate XML everywhere. Whereas SOAP requires you to work with namespaces and XML Schema, and then tries lots of tricks to make non-XML content fit inside a SOAP payload, tricks that have yet to be consistently implemented around all the SOAP stacks. -steve
