He argues that XSD mapping to native is code (and back) is a source of
many problems, so if WADL encourages you to use XSD for a type system,
then you've made a wrong turn already.
I think I have to concur about the XSD side of things, it is something
to strongly discourage. Given the number of existing WADL documents to
be compatible with is zero, it may be time to push for it to be
relax-ng *only*. That is, if you expect WADL and the corresponding
types to be handwritten. If instead they get generated from some
service interface, then you are back in the same mess that we got from
reverse-engineered WSDL files.
Has anyone tried to write a WADL description for any modern service,
like Amazon EC2 REST API?
Interesting bit of pushback on WADL from Dare Obsanjano: http://www.25hoursaday.com/weblog/CommentView.aspx?guid=f88dc5a6-0aff-44ca-ba42-38c651612092 He argues...
I can't disagree that XSD code generation causes problems, but WADL is trying to fix and stabilize more than just the data formats. WADL (and any IDL in the...
... I'm thinking if you've decided on mapping your data to XML in the first place, you've made a wrong turn. XML is a poor serialization format, because it...
... Someone just asked me, w/r/t to the referenced post: Ok, I'll bite. How does JSON make life better? JSON is a self-descriptive data representation. It...
... sub-elements? ... list? ... Actually I meant to send the question to the list (darn web interface), so thanks for forwarding the response. I'm sorry, but...
... I tend to think that there's no obvious mapping between JSON and XML; or more appropriately, the same type of mapping between JSON and XML as you would get...
... There is no difference b/w the two: both documents and data structures are designed to fit a problem space. You might prefer one approach over another,...
This is a very interesting and important discussion by the way. The problem with xml is that it is pure syntax. So there is no clear way to interpret the data....
... For me, the logical representation to use is RDF for the self-descriptive capability. Whether you choose to use RDF/XML or N3 is more a matter of personal...
... As was said, you're putting your preferences in front of fact. A schema aware XML could provide the data types, far more so than json. As for self...
... Sure, if you add in a bunch of other stuff (XSD, RNG, Turing-complete languages, &c.) either could be way more descriptive than the other. But in the...
... I would argue that the type is defined by the observer, not the emitter. For instance, if I had the following XML: <book> <author>John Doe</author> ...
... For me, an important point to remember is that knowing the primitive type is often not enough. For example: is a weight value that is represented by a...
Excellent example. The "data as protocol" reality shows up in the XPath check for the Shopping protocol. REST already has contracts: data exchange with ...
... Easy problem to solve: stop using imperial units! What self- respecting engineer doesn't use metric units? :P (j/k) Semantizing data is an endless road....
Of course convention rules. People, groups and standards bodies can mint new URLs to describe different parts of the conceptual space. As in Java or other OO...
... The example.org vocabularies are there as placeholders right now as I am still writing the use case. I don't know of any currency or measurement...
... I assume that this exchange is tongue-in-cheek ;-) ... but on a serious note, there is a real (indeed regulatory) need to represent both in certain...
That looks like a really cool example, but I'm afraid that I don't understand enough of rdf to grasp everything that's going on there. Any chance of expanding...
... The example is currently only in version 1 draft. I will take your comments on board and add in more explanatory text over time. Regards, Alan Dean ...
... Add the information of (Sorry for not using RELAX NG..): <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" ...
... It's the difference between structured versus nominal types. I don't think you can say one form is better than the other without saying what the problem...
And what's nice about that is, if you need to firm things up later (this is a phone number, that's a IEEE754 float), you (or a recipient) can annotate the RDF...
Alan Dean ... And I am casting my vote in opposition to RDF. I don't have it on the wiki yet, but I just detailed my thoughts in an email to the simple web...
... XML is good for data you will map to documents though (if you are a whiz at whatever language is doing the work and lousy at XSLT you will obviously have...