The principal difference between XML and JSON is that JSON is . To answer the original question, there's no data that can be represented in either system that the other can't also do.It's optimized for expressing serialized data, not for document markup, and so it does a much better job of expressing serialized data. It's just a lot smaller and cleaner in JSON, almost every time, because JSON was specifically designed for data storage and XML wasn't.So for some operations it causes more of a bloat since you want to save 5 lines of data while having 20 or more lines of xml because you need to satisfy the schema.Wikipedia has quite a good summary of it: https://en.wikipedia.org/wiki/XML JSON on the other hand is only meant to represent data and nothing more. You can nest them in any manner you want but thats your limitation. More here: Sure you can move attributes to their own array within the dictionary or so and you could achieve most of the same, and thats why there is this comparison often is mentioned.The terms parent, child, and sibling are used to describe the relationships between elements. All elements can have text content (Harry Potter) and attributes (category="cooking"). Siblings are children on the same level (brothers and sisters).
The information is encoded as described in case of GET method and put into a header called QUERY_STRING.
After the information is encoded it is sent to the server.
The GET method sends the encoded user information appended to the page request.
(It would be harder to follow if you didn't pretty-print it, but who wants to try to read non-pretty-printed XML anyway?
) This makes XML files larger and bulkier than they need to be. Just for starters, you have two distinct ways to represent sub-data on a node: nodes between the opening tag and its closing tag, and Attributes inside the opening tag.
XML is great when you have complex structures, relations between objects, maybe even overrides of one file by another (handled by another answer mentioned XPath). That's important to understand: It's designed to be essentially like HTML--a document markup language--but a bit more formalized.