Canonical JSON

[gregoriopellegrino]

Hi,
in this PR you will find the first public version of the script for generating canonical JSON from the guidelines and techniques documents.

Also find the updated canonical JSON.

See you later!

[gautierchomel]

Probably, instead of Null, we should reproduce the Compact.

[mattgarrish]

You can iterate over the json and automatically populate the null values with the compact ones at run time.

Or code the output so that you never attempt to use the descriptive statement in those cases that are null.

Or write some bloated checking to test if you need the descriptive statement and take the compact when it's null.

I can live with null values, in other words, although my preference would be to not have them. If it means we have to duplicate every string in the guidelines so they can be harvested, that might sway me the other way. But could the script that builds the json automatically insert the compact statement instead of null?

[gregoriopellegrino]

@mattgarrish there is no need to have all the strings in the guidelines, I can fix the script that generates the JSON to use the same value for compact and descriptive, in case there is no descriptive

[mattgarrish]

I would double up the strings, then, rather than use null.

We're already repeating the strings in the json for the no information available outputs.

[mattgarrish]

The whitespace needed to join these strings together is missing in the new output.