I think this is missing a little justification. They go from this, which I agree with: > A good markup language describes an abstract hierarchical structure o

I think this is missing a little justification. They go from this, which I agree with: > A good markup language describes an abstract hierarchical structure of the document, and lets a separate program to adapt that structure to the desired output. > Great markup format unambiguously interprets an input string as an abstract tree model of a document. To this: > [In Markdown] there's no way to express generic tree structure, conversion to HTML with specific browser tags is hard-coded. I understand why you'd want the markup to be turned into a tree, but that's different from saying you should be able to build any tree with the markup. Isn't the point to encode text documents? The fact that you can't build the entire layout of your HTML result in the markup language doesn't seem like a sensible requirement. Why do you want or need infinitely-nested structure in documents?