Comment by ongy 3 months ago EAD does indeed look like a good example of why we shouldn't use XML. 5 comments ongy Reply bryanrasmussen 3 months ago hah hah yeah, these scoped content examples would be a joy to do in JSONhttps://www.loc.gov/ead/tglib1998/tlin125.html ongy 3 months ago 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. bryanrasmussen 3 months ago you must find reading HTML a slog. 2 replies →
bryanrasmussen 3 months ago hah hah yeah, these scoped content examples would be a joy to do in JSONhttps://www.loc.gov/ead/tglib1998/tlin125.html ongy 3 months ago 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. bryanrasmussen 3 months ago you must find reading HTML a slog. 2 replies →
ongy 3 months ago 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. bryanrasmussen 3 months ago you must find reading HTML a slog. 2 replies →
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.
you must find reading HTML a slog.
2 replies →