Tripper>=0.3.5 resolves EMMO namespace correctly. #332
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
This means that using EMMO.prefLabel actually leads to the full and correct IRI.
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.
Description:
From tripper 0.3.5 importing EMMO as namespace resolves correctly.
I.e. EMMO.Force resolves to
https://w3id.org/emmo#EMMO_1f087811_06cb_42d5_90fb_25d0e7e068ef
It makes not longer sense to use "emmo:Force" in the mapping as the prefix will be resolved, but not the full IRI.
Type of change:
Checklist for the reviewer:
This checklist should be used as a help for the reviewer.