Hi, As clarification: - JSON does not require JavaScript or a Browser. It is a text-based representation of data that is language independent, yet well-matched to all major languages. - Simple-to-use libraries exist for all major languages/platforms. No complex transformation tools needed.
JSON is not good at representing documents; XML is great for that. We're interested in representing "data", not "documents". -vince On Wed, Sep 19, 2012 at 3:06 PM, Stine, John A. <[email protected]> wrote: > I do not know if I agree with this or not. This appears to be an area > where many of us, including myself, are not the experts. > > I asked someone who is what the pros and cons are with using JSON versus > XML. These are his thoughts > > "If all you are going to do is have a browser that runs JavaScript then > JSON is fine. > > But if you want to exchange data between web services, transform the data, > or query the data, then XML is the way to go. XML is 14 years old (if you > consider that XML has its ancestry in SGML, then you could argue that XML > is 37 years old). JSON is at best 10 years old. There are no validation > tools for JSON, no transformation tools (unless you want to write > JavaScript code), no query tools. > > Regarding embedded systems: I am told that many of the cellphone vendors > are using XML. To address the verboseness of XML, they use the standard > binary XML format called Efficient XML Interchange (EXI)." > > It would appear to me that with JSON you are forcing the use of JavaScript > and to do a whole lot more coding but with XML you would be much more > flexible and have many more tools to support you. > > John > >
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
