Mixed content models...
<p>Doing <b>this</b> in <i>JSON</i> sucks.</p>
For a more practical example, view source on this page and imagine marking it up in JSON. Or consider how you would model say DocBook in JSON.
XML is intended to cover all the bases, not just the informal data representations we use day-to-day for which JSON is often a good fit.
That's before we get onto subjects like namespaces and schema.
Old school open source projects. Some new school ones too.
It's like DocBook which is supposed to be the open source XML implementation for creating technical books. Here's a link to the actual book online : http://www.docbook.org/tdg5/en/html/ch00.html
Thanks. I'll for sure read up.
>http://www.docbook.org/[DocBook.org]
Yes, http would be the name of the macro in the example case. The target would be "//www.docbook.org/", and the attribute would be "DocBook.org". The built-in http macro would convert that to the link: DocBook.org