[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: json v. xml
derek denny-brown said: > Aside from the cross-domain issue, I think XML also missed the boat by > not providing a canonical 'object serialization', akin to JSON. Part > of the explosion of JSON is due to it's low barrier to entry. "Missed the boat" suggests that canonical object serialization should have been a goal of XML in the first place, which it wasn't. (But perhaps Denny is right: if we'd gonge with the instance-based type annotation ideas that IIRC Charles Goldfarb suggested, this would be a different discussion.) The world is big enough for more than one syntax for things. JSON is to XML what IDL is to DTDs. Ultimately, the XML methodology is markup: annotation. (And arbitrary, unlimited annotation with arbitrary constraint checking.) Not everything should be markup. We are better off with two (or ten) small, distinct languages that developers can master rather than multiplying the complexity of XML in futile attempts to make it useful for everything. The opposite of complexity is not simplicity but modesty. As I understand JSON, it is merely client-side programmers saying "Hey, we already have a syntax for representing data structures in JavaScript, why not just use that so we don't need any special API for naming and navigating?" That is an utterly reasonable position, it seems to me. Cheers Rick Jelliffe
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|