Converted some @types into rdf:type entries.
#66
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
While rdfpipe appears to handle '@type's containing OWL restrictions without any problem, it appears to throw off the JSON-LD library we're using in JPhyloRef. I'll make this quick fix here for now and then decide what the correct solution should be.
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.
RDFpipe can handle '@type's containing entire OWL restrictions without any problem (e.g.
"@type": [{ "@type": "owl:Restriction", ... }]). Doing this causes an error in the JSON-LD library we're using in JPhyloRef, which expects@typeto be a string or an array of strings (1).The quick solution to this is to set
rdf:typein the JSON-LD instead of@type, which seems to work with both RDFpipe (and subsequently Protege) as well as JPhyloRef.