Use Ontology Access Kit in OxoEndpoint methods #6
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
|
yes, quite possible something changed in the upstream services |
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.
These changes delegate the real work within the
OxoEndpointmethods to anOlsImplementationobject from Ontology Access Kit.I noticed as I was testing that the PNGs generated by the
mapcrawlexamples in theREADMEusing this branch look different than they look in the saved output images presented in theREADME. But they do look the same as when running the examples in themainbranch. So perhaps something with the upstream services has changed since those output images were saved.There are also some somewhat unrelated changes in here that convert the test files into
unttest.TestCaseclasses.