I’m attending the XML 2007 Conference in Boston – sitting in on a plenary session entitled “Does the XML have a future on the web?” What I hope to share with you is a debate between two interesting and intriguing trains of thought for consideration of publishing not only your church’s website, but also sermons, Bible Studies, weekly calendars and other information your charitable organization needs to distribute.
One one side, sporting the bearded guru’s view, is Doug Crockford of Yahoo whose response to the insecurities of HTML, Jason and DOM – and whose apparent frustration with XML’s built-in hostility towards traditional programming and database management – has given us the specification known as JSON or JavasScript Object Notation.
In the mustache only camp is C. M. Sperberg-McQueen, a member of W3C technical staff who asserts that since the Web is for everyone, and because loose coupling and multiple format distribution from a single source are more desired than “fashion” and “delivery speed” that XML will only die when … and I quote “… rip it out of [his] cold dead hands.”
After both individuals gave their opposite opinions – with some in-the middle interjection by Michael Day of YesLogic – what ensued was some impassioned questions from those attending the conference. The responses by both Mr. Crawford and Sperberg-McQueen were equally animated.
Mostly what I heard from the floor was frustration over the complexity of XML. Crockford took that opportunity to point out how JSON more closely reflect the programmer’s perview. I agree. Sperberg-McQueen pointing out how now modern day browsers now support XHTML + XSLT. I’ll add to this that one only need visit a FeedBurner RSS feed to see this in action.
When I posed my question how all this fits in to the Software as a Service paradigm, Mr. Crockford enumerated all of the insecurities of AJAX that have become a concern for many developing online applications in an enterprise architecture. Sperberg-McQueen jabbed back with JSON’s eval equates to an equally insecure solution (to XML). Neither answered my question “what do I tell my clients who tell ask me ‘why don’t I go out and get Web 2.0’ … as if it is a product I can purchase off-the-shelf?”
Neither really answered the question – because the real problem with both JSON and XML as I see it are FREE TOOLS that make it mindlessly easy for the average church secretary to publish a sermon. The same frustration I heard/felt with many of the developers in the audience.
More later, but feel free to pitch in with your opinions.