Skip to content

Commit 0dc39da

Browse files
Update docs/schema/conformance_and_extensions.md
Co-authored-by: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
1 parent 59ee5c8 commit 0dc39da

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/schema/conformance_and_extensions.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,16 @@ Extensions to the standard may add new objects and fields to accommodate specifi
2525

2626
The schema for the standard by default allows for new fields, and does not fail validation of a file which contains unknown fields.
2727

28-
### Extension conformance guidelines
28+
### Extension conformance
29+
30+
This section documents the normative rules that OCDS extensions must conform to. It uses the following terms from JSON Schema to describe the rules for extension schemas:
31+
32+
* [property](https://json-schema.org/understanding-json-schema/reference/object#properties): A key-value pair belonging to an object, defined using the `properties` keyword in the schema or subschema for the object, e.g. `ocid` is a property of an OCDS release and it is defined under the top-level `properties` keyword in the OCDS release schema.
33+
* [definition](https://json-schema.org/understanding-json-schema/structuring#defs): A subschema defined using the top-level `definitions` keyword, e.g. the `Award` definition contains the subschema for an OCDS award and it is defined under the `definitions` keyword in the OCDS release schema.
34+
* [keyword](https://json-schema.org/understanding-json-schema/keywords): A key within a JSON Schema used to define the structure of JSON data , e.g. the `type` keyword specifies the data type for a property.
35+
36+
37+
2938

3039
#### Changes to existing fields
3140

0 commit comments

Comments
 (0)