Correct conformance class URLs#2360
Merged
Merged
Conversation
tomkralidis
requested changes
Jun 11, 2026
tomkralidis
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Per the conformance class in OGC API - Feaures: 5, use OGC API - Common conformance URL sets.
.../ogcapi-features-5/1.0/conf/schemas->.../ogcapi-common-3/1.0/conf/schemas.../ogcapi-features-5/1.0/conf/core-roles-features->.../ogcapi-common-3/1.0/conf/advanced-property-rolesAs introduced in #1967, pygeoapi uses the conformance class in the specification: http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30. However, the url that resolves is http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas3.I was able to find multiple references to the.../oas3version of the the oas conformance class in the NamingAuthority repository: search:opengeospatial/NamingAuthority). I did not find any references in the naming authority toogcapi-features-1/1.0/conf/oas30orogcapi-features-1/1.0/conf/oas30Not sure if this is a fix that is first needed in the OAF spec.Remaining specification URLs that do not resolve are in draft as described in #1637.
Related Issue / discussion
#1967
#1637
opengeospatial/ogcapi-features#1045
Additional information
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)