2011-05-09 Monday - Why You Might Need JSON

"Even the most humble carpenter has hammers of different sizes"

Hypothetical Problem:  
An average payload of 50-100 bytes of data needs to be made available via an online service - but an enterprise canonical XSD structure might flood the network with about 200K of just empty tag elements alone.

Proposed Solution:

For certain types of data servcies, a light-weight RESTful service using JSON (over heavier-weight enterprise-level XSD-based canonical models for SOAP-based SOA services) might be more appropriate.

http://en.wikipedia.org/wiki/JSON

JSON Schema

http://json-schema.org/

RFC 4627 - The application/json Media Type for JavaScript Object Notation (JSON)

http://tools.ietf.org/html/rfc4627

JSON support in JAXB

http://wikis.sun.com/display/Jersey/JSON+support+in+JAXB

http://blogs.oracle.com/arungupta/entry/totd_8_generating_json_using

http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/RESTEasy_Reference_Guide/JAXB_and_JSON_provider.html

XMLSpy supports XML-to-JSON conversion

http://www.altova.com/xmlspy/json-editor.html