fix for faux data property ranges #357
Merged
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
brianjlowe
approved these changes
Jan 24, 2023
ghost
pushed a commit
that referenced
this pull request
Feb 23, 2023
Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
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.
Fix for recent PR
What does this pull request do?
Fixes faux data property range options
What's new?
Create custom rdfs:literal range option as data property dao returns null for rdfs:literal uri.
Fixed untyped option label
How should this be tested?
A description of what steps someone could take to:
Interested parties
@brianjlowe @chenejac @bkampe @VIVO-project/vivo-committers