include taxonlabels for ease of human readability related to https://… #1
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
|
OK, right, we can do that. The nt:hasLabelFromApi triple is in the pubinfo graph though. I made the corresponding commit here: b0e6fce The used endpoint is found in the endpoint.txt file, btw: https://github.com/knowledgepixels/bdj-nanopub-api/blob/main/endpoint.txt |
jhpoelen
pushed a commit
to globalbioticinteractions/knowledgepixels
that referenced
this pull request
Jan 5, 2024
|
@tkuhn thanks for your prompt action and for pointing out the endpoint.txt . btw - have you ever experimented with oxigraph as a triple store? |
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.
…github.com/globalbioticinteractions/globalbioticinteractions/issues/923
hi @tkuhn - please review / accept this pull request to include taxon labels to help make the generated tables a little easier to read and interpret.
Note that I wasn't able to test the query, because I don't know whether you are running a public sparql against the nanopub corpus somewhere.