Liaise with OGC re canonical conformance class URIs

[rob-metalinkage]

The OGC ServiceType registry needs to be updated - it represented a snapshot in time and requires a formal governance process in place to update it. Early OGC specifications did not define explicit conformance classes.

Recognising the validity of the process of profiling DCAT to reference OGC services in a standardised way, it is preferable to liaise with the community to identify a set of requirements and implement a common solution by publishing such a profile directly by the OGC, and updating the necessary register of conformance class targets.

Conformance classes will provide a viewpoint via Linked Data and content-negotiation to allow discovery of resources that can be used to implement or validate conformance, using the Profiles vocabulary which is designed for this purpose. Please register the set of conformance classes required at https://github.com/opengeospatial/NamingAuthority/issues and we will publish canonical URIs for these.

The proposal is thus to define conformance targets for OGC services using either a general type from the ServiceTypes registry, or a more specific conformance class defined as a narrower term of these if required, for individual methods. These specific conformances classes could be owl:sameAs or skos:exactMatch, but skos:broadMatch should be used to reference general specifications or versions.

[bertvannuffelen]

@rob-metalinkage thanks for the feedback, we will take it up with the team.