Collecting rough notes on our practices in different standards to help thinking about future development of this tool.

“references-model” and “references-models-seperator” - so we can reference one model from another - eg reference an organisation from a project

“references-data-key”, “references-data-list” and “references-datas-seperator” - so one part of a JSON data item can reference another part - eg reference a source in a project. Could also be used for BODS; where one statement references another.

A pre-commit hook compiles schema when checking in to repo

Meta schema, defines schema of schema - so clearly defining what extra things they do! EG

• for merging; omitwhenmerged https://standard.open-contracting.org/latest/en/schema/merging/#merging-specification
• deprecated
• open & closed codelist

PropertyOrder

https://ocdskit.readthedocs.io/en/latest/cli/schema.html#set-closed-codelist-enums does codelists