An easy way to extend CoverageJSON is to add new fields to it. In order to avoid name clashes (both with other extensions and future versions of the format) it is recommended to use names of the form "prefix:suffix". If CoverageJSON documents using that prefix shall be published more widely, then the prefix should be registered together with the corresponding namespace URI. A registration avoids name clashes and eases common understanding of extensions without establishing the full machinery of JSON-LD for example. More details can be found in the "Extensions" section of the specification.

How to register a prefix

Very simple! The only thing you have to do is edit the prefixes.yaml file on GitHub and submit a pull request. Once the request is accepted, the prefix entry immediately appears in the table below, as well as in the covjson.org/prefixes.jsonld file which is included in the default JSON-LD context, making it available for linked data applications. If you register a prefix for a common namespace, try to use an established prefix. The website prefix.cc may provide some help for that.
Prefix URI
covjsonhttps://covjson.org/def/core#
covjsondthttps://covjson.org/def/domainTypes#
xsdhttp://www.w3.org/2001/XMLSchema#
ssnhttp://www.w3.org/2005/Incubator/ssn/ssnx/ssn#
skoshttp://www.w3.org/2004/02/skos/core#
dcthttp://purl.org/dc/terms/
hydrahttp://www.w3.org/ns/hydra/core#
qudthttp://qudt.org/schema/qudt#
ignfhttp://data.ign.fr/def/ignf#
inspireglosshttp://inspire.ec.europa.eu/glossary/
relhttp://www.iana.org/assignments/relation/