Ignore explicit declarations of reserved prefixes #632
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
- added a new method to `Vocab` to get the base URI of a vocabulary - In the prefix parsing utility of `VocabUtil`, check the URI associated with re-declared reserved prefix: an error is reported only if this URI is **not** the URI of the known vocabulary associated to the reserved prefix. In other words, explicit declaration of reserved prefixes is now allowed; trying to override a reserved prefix still raises an error. Fixes #585
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.
Vocabto get the base URI of a vocabularyVocabUtil, check the URI associatedwith re-declared reserved prefix: an error is reported only if this
URI is not the URI of the known vocabulary associated to the
reserved prefix. In other words, explicit declaration of reserved
prefixes is now allowed; trying to override a reserved prefix still
raises an error.
Fixes #585