sparql-router
Advanced tools
The NodeJS/Express application that powers queery.link to serve canned SPARQL queries to the world.
| master (demo) | develop (demo) |
|---|---|
  |   |
SPARQL is the query language to retrieve data from RDF triple stores. I often had the issue that fellow developers or data fanatics asked for data that was in a triple store, but they don't know SPARQL.
This server application solves the issue:
biggest-asian-cities)http:/yourhost/api/tables/biggest-asian-cities.csv for manipulations as a spreadsheethttp:/yourhost/api/tables/biggest-asian-cities.json as input for a Web apphttp:/yourhost/api/tables/biggest-asian-cities.xml if they are into XML
/public/api/tables, /public/api/graphs or /public/api/ask depending on the query type (SELECT, CONSTRUCT, DESCRIBE, SPARQL Update)/api/tables/{query-name}, /api/graphs/{query-name} or /api/ask/{query-name}Accept HTTP header)/api/sparql and get the results, without saving itA screenshot of the tests as overview of the features.
Configuration and detailed usage documentation
nodejs and npm.git clone https://github.com/ColinMaudry/sparql-router.git --depth=1
cd sparql-router
npm install --production
SPARQL router is also available as an NPM package.
Once it's configured, you must initialize the system queries and test queries:
npm run initialize
I haven't found a proper way to mock a triple store for testing purposes. I consequently use a remote triple store. That means the tests only work if the machine has Internet access.
The configuration used for the tests is stored in config/test.json.
First, make sure, you have all the dev dependencies installed:
npm install
Tests rely on mocha and supertest for the API, and on nightwatch for the frontend.
To run the API tests:
npm test
To run the frontend tests:
# Make sure the dev dependencies are installed
npm install
# Start the server in development mode with the test configuration
NODE_ENV=test npm run dev
# Run the frontend tests
npm run test-ui
Using config/default.json configuration file:
npm start
Using config/myconfig.json configuration file:
NODE_ENV=myconfig npm start
Start in debug mode:
DEBUG=functions,routes npm start
If you want the app to restart automatically after fatal errors, I suggest you use forever.
When forever is installed globally, run the following command in the sparql-router folder:
forever bin/www
See this wiki page for detailed instructions: Using SPARQL router
The API documentation can be found here (development version). If you're running the app, at /api.
The actions that are not read-only on the canned queries or the data require basic authentication.
If SPARQL router doesn't match your requirements, you can have a look at these solutions:
/api/asknpm start command for commodity/sparqlMIT license
If you use it, I'd really appreciate a public statements such as a tweet!
FAQs
The NodeJS/Express application that powers queery.link to serve canned SPARQL queries to the world.
We found that sparql-router demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Threat Research
/Security News
Compromised maintainer accounts pushed malicious @ethersphere/bee-js 13.3.0 and Swarm Desktop 0.56.2, reusing SleepyDuck’s Ethereum-addressed C2 infrastructure.
Security News
Socket has released a free Certified Patch for a critical Rails Active Storage vulnerability, giving developers time to upgrade to a secure Rails version.
Security News
/Threat Research
A malicious Ruby gem runs a credential-stealing worm during installation, poisons AI coding tools, and can wipe files when a stolen GitHub token is revoked.