> "Unstructured text is ignored; there is no such thing as a parsing error"

That is a naively wrong-headed recipe for problems later down the road. What if structure is mistyped such that it looks like unstructured text?

The format has structure, and consequently, examples of that format can be erroneous. Just because you don't diagnose errors doesn't mean they aren't there.

The live demos aren't appearing for me in Firefox, which makes the page nearly useless in understanding what ArchieML actually looks like.

The relevant error appears to be:

    TypeError: aml.innerText is undefined archieml.org:364:6

Reminds me a little of INI files. They are a good demonstration of how sometimes simplicity is best.

Interesting that there's mention of JSON and YAML, but no mention of TOML. I'm more interested in hearing why TOML wasn't an adequate solution.

So, I guess ArchieML is to JSON what Markdown is to HTML?

Akin to :skip, wouldn't a :preserve or :quote block to suspend syntax temporarily be useful?

That is, for tracts of text that need to be quoted verbatim, including colons or [brackets] or similar?

Given how the parser is designed it seems like this would be particularly easy to implement...

I love that it has comments, which is something I greatly miss in JSON.

Off topic: I clicked because I thought it's sth. related to the ML programming language.