Change yes/no to true/false

[remcohaszing]

This specification defines a YAML file which should use yes/no is accepted in several places. However, the meaning of yes/no is ambiguous in YAML. In YAML 1.1 and older these values represent booleans, but in YAML 1.2 they don’t, meaning they represent strings.

I suggest to remove this ambiguity by changing them to unambigous booleans (true/false) in the specification.

[ruphy]

thank you @remcohaszing, I think it's a good idea

[libremente]

This issue was related #8

[libremente]

See also italia/publiccode-editor#48

[remcohaszing]

yaml-language-server 1.0 and VSCode Yaml 1.0 have just been released, where they switched from using YAML 1.1 to YAML 1.2. This means they will now mark the values yes/no as invalid, which comes from JSON schema validation based the publiccode JSON schema in the schema store.

[bfabio]

I think explicitly base the format on YAML 1.2 is the number one issue we need to address. Moving to Discussions.