Integrate Local Blazegraph SPARQL Endpoint #167
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
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.
Summary
This pull request introduces functionality that allows all nanopublications being published using this library to update a local Blazegraph SPARQL endpoint. This feature is primarily designed for development and testing environments, enabling users to keep their data private by running both the nanopub-server and blazegraph locally.
Key Features
Optional Blazegraph Updates: Users can choose whether to update the Blazegraph endpoint when publishing a nanopublication. The default setting is false.
Customizable Endpoint: By default, the endpoint is set to http://localhost:9999/blazegraph/namespace/kb/sparql. Users can easily change
localhost:9999to match their Blazegraph server's address while keeping the namespace and path intact.Benefits
This enhancement facilitates local development and testing while ensuring that all data remains private and doesn't clutter the original servers. It simplifies the workflow for developers who want to integrate nanopublications with Blazegraph without exposing their data to external servers too.