Added @RunWith(JUnit4.class)
Deleted wrong RIOT writer
test to ensure the sparql template are well formed and once instantiated they are correctly processed by virtuoso
No need dedicated resource file in test to test the template loading
Extract the rdf block from the record submitted for registration
Can't use jena Query because does not support inference rule, can't use jena HttpEngine because it does not support long queryif we do not use Query: hence let's query with handmade post request to the sparql endpoint.
testing template loading
Testing the registry library
ByPass QueryBuilder, otherwise the virtuoso pragma are not parsable
Playing with inference rules on the remote sparql endpoint
testing
Updated test
Testing RDF XML serialization
API that read from Virtuoso
Testing Virtuoso DESCRIBE remote queries.
Fixed virtuoso drop and added test
API for storing on virtuoso
keep playing with virtuoso
JobNodes to work with Virtuoso
VirtuosoClient and some tests assuming there is a local virtuoso server (hence ignored)
First tests with Virtuoso.