IIRC, we implicitly version schemas by bumping the package version. If this is correct, it does not provide schema versioning on a granular level. Perhaps we ought to adopt a versioning scheme similar to that of the JSON schema spec itself, namely an id field and suffixing the version number to the schema's filename (e.g. draft-04.json).
tlvince
commented
9 years ago
IIRC, we implicitly version schemas by bumping the package version. If this is correct, it does not provide schema versioning on a granular level. Perhaps we ought to adopt a versioning scheme similar to that of the JSON schema spec itself, namely an id field and suffixing the version number to the schema's filename (e.g.
draft-04.json).