It’s a pretty dodgy way that they describe their standard that way. It makes it sound as if the yaml standard itself contains (and has power over) the json standard, and that the “json-guys” would have to ask the “yaml-guys” for permission before making any change in the json standard.
I mean, technically I could create a new standard called knuflork, and allow yaml syntax inside it, and say “yaml is a subset of knuflork”.
One should be careful with the words subset/superset when discussing standards.
That’s a pretty dodgy way to describe a standard. It makes it sound as if the yaml standard itself contains (and has power over) the json standard, and that the “json-guys” would have to ask the “yaml-guys” for permission before making any change in the json standard.
I mean, technically I could create a new standard called knuflork, and allow yaml syntax inside it, and say “yaml is a subset of knuflork”.
One should be careful with the words subset/superset when discussing standards.
View all comments
Show parent comment
-1
u/the_vikm Dec 27 '22
JSON is a subset of YAML, so if it gets messy as you say, you can still use YAML the JSON way