URIs of requirements classes, requirements, conformance classes, and abstract tests

[ghobona]

The OGC policy document OGC-NA Name type specification – specification elements (10-103r1) requires that:

The end of the URI of a requirements class be of the form /req/<req-class-name>

The end of the URI of requirement be of the form /req/<req-class-name>/<req-name>

The end of the URI of a conformance class be of the form /conf/<conf-class-name>

The end of the URI of requirement be of the form /conf/<conf-class-name>/<conf-name>

Using modifiers

Note that you can use hyphens as a modifier, for example /req/earth-science/bedrock-geology

[alexrobin]

Thanks @ghobona. I think that's what we are doing for requirements. Is there a specific place where the requirement URI is not conformant?

[ghobona]

The following sets of requirements in Part 1 appear to have four segments instead of three.

Requirements 43 to 74

Requirements 81 to 84

[alexrobin]

Ah ok I modeled these on OGC API - Features. I will change them to keep only 3 segments. Thanks

[alexrobin]

This should be fixed in latest draft of part 1

[ghobona]

@alexrobin I can confirm that the problem of the number of segments in the URIs has been resolved.

Issue 28B

However, I also noticed that some permissions and recommendations begin with a /req/ segment.

URI segments of recommendations should begin /rec/.

URI segments of permissions should begin /per/.

Issue 28C

I also noticed that the requirements classes were not linked to the requirements. So I created a pull request showing how to create the link for one requirements class.

https://github.com/opengeospatial/ogcapi-connected-systems/pull/29/files

[alexrobin]

Thanks for the PR. I fixed the URLs of recommendations and permissions