I was very pleased to learn about your JSON Schema initiative. I'm
sure I must have seemed pig-headed to many people on this forum when I
insisted on the XML purity of SOFEA and resisted JSON as a Data
Interchange mechanism. I hope you understand where I was coming from.
If our Front-End Architecture (FEA) is to be truly Service-Oriented
(SO), it must respect one of the basic features of Service-
Orientation, i.e., tight contracts. We must be able to rigorously
define interface data structures and verify the integrity of data that
is actually interchanged. So far, XML Schema has been the only way to
enforce that. Sure, it's clumsy and difficult to work with compared to
JSON, but at least that capability exists.
Now with JSON Schema, the game has changed, and I'll be the first to
admit it. I really welcome this development and wish it all success,
because we can now have ease of use without compromising data
integrity. A JSON-based SOFEA client can now maintain a *verifiable*
contract with a service interface.
I've blogged about this <a href="http://wisdomofganesh.blogspot.com/
How soon before we can see this implemented and demo-able? :-)