search

opengeospatial / OGC-Web-API-Guidelines

Apache License 2.0
28 stars 7 forks source link

Principle 17b - Use OGC services reserved URIs #24

Closed joanma747 closed 5 years ago

joanma747 commented 6 years ago

Should we reserve some paths for some "Common" cases and special meanings?. Can this be and added principle?

For example: /api /conformance /collections /metadata

cmheazel commented 6 years ago

This is similar to issue #19 (Master branch Principle 17). There should be "standard" paths and path templates which are used by all services. This will give OGC services a common look and feel. Note that the Secure Dimensions branch interprets Principle 17 to mean something very different.

joanma747 commented 6 years ago

Ok, I have added this list of possible OGC well knwon URIs to principle 17 to start the discussion about them.

securedimensions commented 5 years ago

this does belong to discussions on "building blocks" and "common elements" but not in the guidelines