For example, the codelist page can briefly explain what purpose codes and codelists serve (similar to
text prepared for OC4IDS), what they are, and how they're implemented in OCDS. For closed codelists, can describe that they provide titles and descriptions to the enum of array fields, with an example.
On the schema page, a brief paragraph can clarify the use of terms like 'fields', and refer to JSON Schema (similar to text prepared for OC4IDS).
The extensions list page has very little text. We can repeat a brief explainer of what extensions are and why they matter.
Check what the OCDS documentation has for these concepts (if missing, there might be an opportunity to improve in OCDS 1.1.5).
For example, the codelist page can briefly explain what purpose codes and codelists serve (similar to text prepared for OC4IDS), what they are, and how they're implemented in OCDS. For closed codelists, can describe that they provide titles and descriptions to the
enumof array fields, with an example.On the schema page, a brief paragraph can clarify the use of terms like 'fields', and refer to JSON Schema (similar to text prepared for OC4IDS).
The extensions list page has very little text. We can repeat a brief explainer of what extensions are and why they matter.
Check what the OCDS documentation has for these concepts (if missing, there might be an opportunity to improve in OCDS 1.1.5).