The RDF Datastore Administration Service is another basic service and allows for the selection of data stores for use by the EPCIS Repository. Currently there are two options that have been fully tested and those are Neo4j and Allegrograph. SPARQL Query engine configuration settings for the Allegrograph server are also included in this service.

At present only the Allegrograph data store is providing adequate support for reasoning with the OWL2 ontologies in an acceptable fashion and so if this functionality is required this is your best bet. The Allegrograph is also the default configuration.

Neo4j has just released V1.0 and we will work to get this functionlity tested and integrated in an acceptable fashion. V1.0 looks to be working better with Sail and the integrated SPARQL query engine is also looking up. With luck this functionality should be incorporated by April/May 2010.

The configuration allows for both local and remote data stores and may, at some point in the future, be configured to include the data migration services currently available as Online Services.

For the time being you are able to choose between the two available datastores, but only for the repository, as all other data, CRM, Group Info, Preferences et al are stored in a Neo4j instance.

You may also select an external reasoner for an Allegrograph repository to either augment or replace the default Fact++ reasoner.

We are hoping to be able to include additional functionality in the near future, but for now this should be sufficient for most users.

In the mean time we have an RDF based demo up here. It demonstrates the general features of RDF as well as showning a few examples of output types.

To use the demo just click on any of the exposed links. When executing the stored queries ex1 and ex2 look for the links above the returned data to display as map or graph output.

There is also a demo SPARQL Endpoint here. This store is populated with data from the NK-CRM demo datastore.