You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, codelist and openCodelist are at the OCDS "field" level, e.g. properties/tag.
However, tag is an array of codes. In JSON Schema, it would make more sense to add these fields at properties/tag/items (where enum is already, in OCDS 1.1).
By not having the validation properties at the correct level, lib-cove-ocds (and any other JSON Schema validator) needs to implement workarounds.
That said, the effort to update tools might be too great. One option would be to start having tools pre-process schema and move these properties to the correct location. Once all tools have done this, it will be easier to change the schema.
The text was updated successfully, but these errors were encountered:
jpmckinney
added
the
Schema
Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.)
label
Jul 17, 2023
Presently,
codelist
andopenCodelist
are at the OCDS "field" level, e.g.properties/tag
.However,
tag
is an array of codes. In JSON Schema, it would make more sense to add these fields atproperties/tag/items
(whereenum
is already, in OCDS 1.1).By not having the validation properties at the correct level, lib-cove-ocds (and any other JSON Schema validator) needs to implement workarounds.
That said, the effort to update tools might be too great. One option would be to start having tools pre-process schema and move these properties to the correct location. Once all tools have done this, it will be easier to change the schema.
The text was updated successfully, but these errors were encountered: