On JSON, XML and S-Expressions
Reading Don Box’s piece “Some Trees Are Better Than Others”, which implies you gotta read Megginson’s piece “All Markup ends up looking like XML” and Doug Crockfords comment on that last one “For the trees”, gets me thinking.
JSON and S-expressions (LISP) is code or can be evaluated as code and embedded in the environment; XML is not (at least not until somebody develops an XML programming language. an idea that sometimes doesn’t seem so farfetched considering what people are doing with (N)Ant).
It reminds me of something I’ve heard Kim Harding Christensen from EOS say a lot when it comes to architecting with Web Services, namely that instead of creating opague API’s give people a “command object”, effectively the ability to return code that should be executed in the runtime/environment enabling the caller (under restrictions of course) to get whatever he wants/need.
Reading these posts clarifies some of that thinking for me.
Leave a Reply
You must be logged in to post a comment.
I work for 

