Seems to me the ideal solution would follow the pattern defined by the OGC specification model ([OGC 07-056r1](https://portal.ogc.org/files/?artifact_id=21976)), in which a set of conformance classes are defined in the spec, each with a set of conformance tests and a URI. Then dct:conformsTo could point to the URI for a conformance class and its pretty clear what it means. Example from the recent OGC features API: [Conformance Class GeoJSON](http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson) with URI http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson. The missing piece is that the URI currently resolves to html, not something like a prof rdf doc that might be machine actionable. This is for the most part just an idea, since there are relatively few spec that follow the OGC specification model. I think the source of confusion is with the specification practice-- spec writers need to specify how to identify things that conform to their spec. -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1338#issuecomment-849731200 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Thursday, 27 May 2021 15:31:36 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:37 UTC