Feature: use the resolved namespace instead of the default vocabulary in the @context #141
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
35 tasks
syphax-bouazzouni
changed the title
|
Close as merged in #199 |
|
Need to be restricted to only the real properties in vocabularies. |
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.
We see that in the @context it is always the default vocabulary (http://data.bioontology.org/metadata/) that is used instead of the resolvable one. For example, the prefLabel context is "http://data.bioontology.org/metadata/skosprefLabel" where we should have "http://www.w3.org/2004/02/skos/core#prefLabel"
The @conrext before
The @context after