Initiate 3.2 schema and handle $ref for contact and license

[LasneF]

Initiate the 3.2 schema as a copy of 3.1

switch label from 3.1 to 3.2

introduce a first changes with supporting $ref for licence and for contact for handling the issues here

#3569

#3552

changed are done step by step

tell me if i should update the yaml or the json ? was not sure
should we put it also inside the 3.1 ? , was not sure following semantic versionning it depends

[handrews]

@LasneF I'm not sure what the process is for setting up the 3.2 schema (usually we've done that at the very end of the process for a given release). But changes to the spec cannot be made in the schema. They must start in the spec, preferably after enough discussion in issues so that all we discuss in the PR is whether it implements what we agreed to in the issue correctly. That last is not a hard-and-fast rule, and sometimes a PR is easier. But we're already struggling with getting the PR backlog down to something manageable, so doing as much work in issues as possible will help us get back to a PR list that is only active items.

[handrews]

@LasneF since this includes changes that can't be initiated on schemas, I'm going to close this PR. I'd suggest asking on Slack (on the #spec channel) what the process is for setting up the schema for a new minor release, because I can't remember what it is other than that it was not what I would expect. But we should resolve the process issue on slack or in issues before opening PRs. Otherwise the PRs hang around with no one knowing what to do about them.

[karenetheridge]

3.2 should be a descendant of 3.1.1, not 3.1.0.

[handrews]

@karenetheridge there isn't a separate 3.1.1 schema, all patch releases on a minor release use the same schema (since you can't change anything in a patch release that would change the schema anyway).