> Here are some very frequently occurring examples of bad schema design:
(4 lines, 75 characters)
> Here's the right way:
(10 lines, 133 characters)
I have a suspicion as to what went wrong.
(4 lines, 75 characters)
> Here's the right way:
(10 lines, 133 characters)
I have a suspicion as to what went wrong.
The author's point is that XML should not be a data format.
The point being, I think the author is arguing you should use the right tool for the job, and XML not being designed for arbitrary data structures makes it not the right tool. Just recently people have shown you can build a raytracing engine in SQL, but if someome was arguing we shall call it SQLCycles and ship it in Blender, I'd definitely have a few objections!
For humans, this is documents with certain meanings attached. For computers, it’s documents with certain meanings attached.
It’s all data. XML is a data markup language. It’s just that humans call it “semantics” in a “document.”
It easy to query with xpath
It parses the same regardless of the order. With the right way, is <item><key>Name</key><value>John</value></item> the same as <item><value>John</value><key>Name</key></item> ?