> much of the reason XML is complex is that it’s trying to solve complex problems of data interchange by providing a meta language to describe the data. As JSON gains wider adoption, it will face some of the same issues XML tackled over the last decade.
shrug I don't actually think these problems are all that complex. XML made them complex.
The bottom line is that you need to treat any data format as a protocol. The only thing you need to know about the data is what protocol it is. A simple file extension pretty much takes care of that. Then each data format can pick whatever (in)formalism they want to describe the protocol.
JSON is popular precisely because it doesn't try to solve any non-problems.
"If a solution is much smarter than the problem and really stupid people notice it, they believe they have got their hands on something /great/, and so they destroy it . . ."
shrug I don't actually think these problems are all that complex. XML made them complex.
The bottom line is that you need to treat any data format as a protocol. The only thing you need to know about the data is what protocol it is. A simple file extension pretty much takes care of that. Then each data format can pick whatever (in)formalism they want to describe the protocol.
JSON is popular precisely because it doesn't try to solve any non-problems.