Add support for compund CRS in the form of CURIEs #192
Conversation
This file contains 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
balazsdukai
force-pushed
the
feature/compound-crs
branch
from
29dfdc4 to
8876897
Compare
|
We should do this, but for v2.1 only. v2.0 should stay backwards compatible. |
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.
Allow compound CRS in
metadata.referenceSystemthe form of CURIEs, in addition to the current URI syntax.For example:
The schema allows any UPPER/lowercase letter or digit as identifier, and any UPPER/lowercase letter as authority.
However, this change breaks backwards compatibility, so it would require a new major version.
If we decide to merge this PR, the specs need to be updated too.
Fixes #181