WIP: Use consistent schema for standards' pages

[jamietanna]

As a step towards being able to produce metadata for the standards pages, we should use a consistent model across our standards.

To do this, we add a JSON schema for the standards, which attempts to make as much required and formatted appropriately.

This requires we:

• wrap string fields, where appropriate, in string quotes
• remove the redundant name field, as it duplicates title
• remove the redundant category field, as it duplicates classification
• where fields are likely to be not free-form, we can mark them as enums

This uses the json-schema library, as it's got nice error reporting, but unfortunately is stuck on draft-04 of JSON Schema.

TODO:

• [ ] what is the data model we actually want?
• [ ] ADR for what we're deciding

[jamietanna]

Removing classification makes https://alphagov.github.io/data-standards-authority/standards-catalogue/standards/ 's view odd - do we know what we'd want to put in there instead? Or re-add Classification as an enum?

[arnau]

Removing classification makes https://alphagov.github.io/data-standards-authority/standards-catalogue/standards/'s view odd - do we know what we'd want to put in there instead? Or re-add Classification as an enum?

What attribute are we settling in for classifications? topic, subject, keywords? Whichever, I would put it in the table.

The enum is another issue. The list of valid values should probably be open-ended or validated against the actual source (e.g. table Topic in the Erd diagram)

[jamietanna]

Closing as we've used separate PRs to perform this work