JSON: At least it's not YAML
YAML: At least it's not JSON
XML: Maybe if I don't move at all it can't see me
@abstractcode the DTD in enforcing mode ensures XML doesn’t move
@abstractcode This makes me wonder if JSON and YAML folk distinguish “well-formed” and “valid” as concepts.

@futzle @abstractcode json schema does exist. I don’t know if anything like that exists for yaml but technically, json schema could be used to validate yaml too.

and openAPI is SOAP redux, json style

@bri_seven @futzle We put JSON schema in our current project briefly and then shifted away from it as not adding sufficient value for what we were doing. As it couldn't do all our checks we'd need a second thing anyway and might as well just have one thing that does everything.

Our use case is not someone else's use case though.

@abstractcode @futzle json-schema is in perpetual beta mode and continually adds more capabilities (and breaking changes)- chances are they’ve added what you would have needed by now
@bri_seven @futzle It was being used for validation of business rules and it was never going to be able to specify all of them. Nor would I really want it to.
@abstractcode ASN-1: That is not dead which can eternal lie ...
@abstractcode @futzle of the three I prefer XML hands down. But this is funny 😜
@abstractcode You are in a maze of twisty little XML elements, all alike. You are likely to be eaten by a grue.
@abstractcode I don't* mean to be That Being but JSON *is* valid YAML
@abstractcode Meanwhile TOML :
**screeeeeeeeeeech**
@abstractcode
TOML: I see you're writing your software in Rust

@abstractcode But isn't YAML a super set of JSON? So the first line isn’t actually true.

XML for sure isn’t YAML though…

@abstractcode from.my humble experience its YAML for properties, JSON for object serialization and either XML or DSLs for the rest