Skip to content
This repository

Seki is middleware/a front-end for connecting to an independent SPARQL server using node.js

tree: 4769932326

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 .settings
Octocat-spinner-32 Fuseki-0.2.0
Octocat-spinner-32 data
Octocat-spinner-32 docs
Octocat-spinner-32 misc
Octocat-spinner-32 notes
Octocat-spinner-32 src
Octocat-spinner-32 www
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .gitmodules
Octocat-spinner-32 .project

Seki is a front-end to an independent SPARQL server using node.js

It operates as a Web server, building queries from HTTP requests and passing them to the SPARQL server and formatting the results to HTML which is passed back to the client (typically a browser).

Block Diagram

For updates see Seki on G+

Also TODO List

There are two branches in the git repository: master and dev. Master is essentially frozen (tweaks & bugfixes only). dev is in active development.

_to switch to the dev branch you need (I think) to: git branch dev git checkout dev git pull origin dev _

If (were it live) you pointed a browser at it would take "" to build a query to find out about that resource - in the data store it will have a title, content etc. - which then get turned into HTML to show in the browser.

There is a form to allow POSTing, inserting title, content etc. for a given resource into the RDF store (there's no authentication as yet). Files can also be served from the filesystem.

It has been built against a Fuseki server, which uses protocols/query syntax according to the latest SPARQL 1.1 drafts, and so it should be reusable with any SPARQL server.

(Note that the current version includes a little SAX-based XML SPARQL results to JSON converter, this was for demo purposes (don't ask!) - future versions may use JSON SPARQL results directly).

At present it considers all resources to be information resources - the ones that get displayed are instances of sioc:Post. Descriptions of those resources are contained in little named graphs (named by the resources in question). The Fuseki config includes #dataset tdb:unionDefaultGraph true so SPARQL queries can be applied over a (virtual) merge of all the named graphs.

After the tutorial version is stable the plan is to use it as an experimental Read/Write Data Web testbed, e.g. adding support for the linked data API, RDF affordances play.

See contents.txt in individual folders for description.

Installation/running is easy :

  • install node.js (or copy node.exe into the src dir)
  • run Fuseki using Fuseki-0.2.0/run.bat (make executable first on *nix)
  • node seki.js
  • point a browser at http://localhost:8888/seki/

post data should have URIs of the form the Fuseki server (SPARQL endpoint) will be accessible at http://localhost:3030/

top-level danja project notes

Danny 2011

Something went wrong with that request. Please try again.