Skip to content

Consider a "strict" schema to introduce JSON Schema validation keywords prior to 2.0 #1046

@jpmckinney

Description

@jpmckinney

Several issues deal with incorrect or missing JSON Schema validation keywords. See milestone: https://github.com/open-contracting/standard/milestone/25

Typically, we would need to wait for a major version (2.0) to make changes that invalidate data from earlier versions (i.e. backwards-incompatible changes).

However, we can offer a voluntary, "strict" schema that adds in these keywords, removes deprecated fields and codes, removes deprecated types, etc.

Users of the Data Review Tool could voluntarily select the strict schema. Similarly, OCDS Helpdesk analysts could inform publishers of opportunities to improve their data by passing the stricter criteria.

Metadata

Metadata

Labels

Schema: ValidationRelating to constraints in the JSON Schema

Type

No type

Projects

Status

Review in progress

Relationships

None yet

Development

No branches or pull requests

Issue actions