schema/network-schema.json: Disallow additional properties in Geometry

[duncandewhurst]

Related issues

• Coordinates modelling (add support for WKT to Flatten Tool) #10

Description

This PR relates to an issue that surfaced whilst updating tooling for version 0.3:

Following #262, WKT is used to represent Geometry objects in the CSV publication format. WKT does not support additional properties so in order to prevent undefined behaviour and to support roundtripping without data loss, we need to disallow additional properties in the Geometry object. Certain property names (properties and features) were already prohibited, per the GeoJSON specification. Given that there are not yet any implementations and given that we've heard no demand for additional properties within Geometry objects, I think this change is fine to make.

Merge checklist

• Update the changelog (style guide)
• Run ./manage.py pre-commit to update derivative schema files, reference documentation and examples

If you used a validation keyword, type or format that is not already used in the schema:

• Update the list of validation keywords, types or formats in JSON Schema usage.
• Add a field that fails validation against the new keyword, type or format to network-package-invalid.json. (existing file is sufficient)
• Check that OFDS CoVE reports an appropriate validation error.

[duncandewhurst]

• Check that OFDS CoVE reports an appropriate validation error.

@odscjames, contrary to what I said about no more schema changes, this PR does make a change to the schema that will need to be reflected in CoVE. Are you able to spin up a dev instance with the updated schema so that we can check how it handles the additionalProperties keyword?

[duncandewhurst]

@Bjwebb you can ignore the link check failure. It will be resolved once the 0.3 release is tagged.

[ghost]

This has been released in libcoveofds 0.8.1