I read somewhere XML is document oriented and JSON is object oriented. What does that mean?
相关问题
- Jackson Deserialization not calling deserialize on
- Illegal to have multiple roots (start tag in epilo
- How to maintain order of key-value in DataFrame sa
- StackExchange API - Deserialize Date in JSON Respo
- Design RESTful service with multiple ids
相关文章
- json_encode 没有把数组转为json
- Livy Server: return a dataframe as JSON?
- Creating XML Elements without namespace declaratio
- Get Attribute Value From Simple XML Using JQuery /
- Unexpected end of JSON input from an ajax call
- How do I do a nested list (array) of schema refere
- iconv() Vs. utf8_encode()
- Convert C# Object to Json Object
XML was designed, as SGML before it, to represent documents. Later, it became adopted in web-based remote procedure calls and configuration files as a data rather than document oriented format.
JSON was designed to represent JavaScript data. It has flourished in the data-oriented areas into which XML had previously expanded and is a better fit there.
XML has retained its original advantage as a document format. It has numerous schema definition languages (XSD, Relax NG, Schematron, and DTD) developed across many sectors, powerful selection (XPath) and transformation (XSLT) tools, and it supports mixed markup needed in document representation.
JSON has ridden the JavaScript wave and is now used for data exchange and persistence across many other languages and platforms. It is lighter weight and closer in syntactic form to programming data structures.
They both have their place in modern systems and application development.