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.
(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.
In short: So having attributes on your elements allows you to be more explicit. Often these XML's represent structures and relations more than the data it self.
The GET method sends the encoded user information appended to the page request.
In this scheme, name/value pairs are joined with equal signs and different pairs are separated by the ampersand.
Spaces are removed and replaced with the character and any other nonalphanumeric characters are replaced with a hexadecimal values.
The PHP $_REQUEST variable can be used to get the result from form data sent with both the GET and POST methods.
Try out following example by putting the source code in script.
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.