Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Conformance declaration: requirements class or conformance class URIs? #244

Closed
cportele opened this issue Jul 5, 2019 · 1 comment · Fixed by #245
Closed

Conformance declaration: requirements class or conformance class URIs? #244

cportele opened this issue Jul 5, 2019 · 1 comment · Fixed by #245
Assignees
@cportele
Labels
Editorial Editorial changes and document updates outside of requirements classes Part 1: Core Issue related to Part 1 - Core
Milestone
Part 1, Second Dr...

Comments

@cportele
Copy link
Member

cportele commented Jul 5, 2019

Since there is a one-to-one relationship between requirements and conformance classes in the OGC modular specification policy it is in a way arbitrary and editorial, but which URIs should be included in the /conformance response?

Currently it is the requirements class URI, but we call it the "conformance declaration". Is there potential for confusion and we should change this to require use of the conformance class URI?
@cportele cportele added Part 1: Core Issue related to Part 1 - Core Editorial Editorial changes and document updates outside of requirements classes labels Jul 5, 2019
@cportele cportele added this to the Part 1, Second Draft Release milestone Jul 5, 2019
@cportele cportele self-assigned this Jul 8, 2019
@cportele
Copy link
Member Author

cportele commented Jul 8, 2019

Decision: Use the conformance class URIs. Clemens will update the text.

@cportele cportele mentioned this issue Jul 8, 2019
Merged
@cportele cportele mentioned this issue Mar 20, 2020
Closed
@philvarner philvarner mentioned this issue Jun 30, 2021
Closed
@teezip teezip mentioned this issue Apr 18, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cportele cportele

Labels
Editorial Editorial changes and document updates outside of requirements classes Part 1: Core Issue related to Part 1 - Core
Projects
Features Part 1: Core
Status: Done
Milestone
Part 1, Second Draft Release
Development

Successfully merging a pull request may close this issue.

req class URIs -> conf class URIs opengeospatial/ogcapi-features
1 participant
@cportele