Comment by bryanrasmussen
3 months ago
probably nobody would choose it for anything new because the sweet spots for XML usage have all already been taken, that said if someone was to say hey we need to redo some of these standards they can of course find ways to make JSON work for some standards that are XML nowadays, but for a lot of them JSON would be the absolute worst and if you were redoing them you would use XML to redo.
example formats that should not ever be JSON
TEI https://tei-c.org/ EAD https://www.loc.gov/ead/ docbook https://docbook.org/
are three obvious ones.
basically anything that needs to combine structured and unstructured data and switch between the two at different parts of your tree are probably better represented as XML.
EAD does indeed look like a good example of why we shouldn't use XML.
hah hah yeah, these scoped content examples would be a joy to do in JSON
https://www.loc.gov/ead/tglib1998/tlin125.html
Yes. A sane schema that actually encapsulates the data would be a lot easier to read.
Earlier I had only seen the mix of values in body and values in tags. With one even being a tag called "value".
Thanks for showing more examples of XML being used to write unreadable messes.
3 replies →