Removed dep to gcube registry and ignore integration tests
Fixes https://support.d4science.org/issues/11240#note-27: namespace dnet should not be used. The full namespace URL must be used when adding triples, otherwise it will be just a string, not a real name under the namespace as expected.
Fixes #11240#note-21: changed names of provenance graph and properties to be URLs instead of plain strings.
Double check tests after latest updates
Fixed web param name and ignoring webmvc test
timeout is a string
Ignore integration test
Added new timeout parameter for anytime query
Removed test for deprecated method
Removed/deprecated unused methods
According to george's feedback, base types to be considered for the JRR are {Project, Service, Actors, Datasets, Software, Physical Collections, Standards} i.e. {PE35_Project, PE1_Service, E39_Actor, PE18_Dataset, D14_Software, E78_Collection, E29_Design_or_Procedure)....
Test collection sparql template
New methods to get subjects with pagination given a datasource API
No sparql template for E55_Type
Test with metashare service
ignore integration test
Looks like using UNION is much more performant than using OPTIONAL. See http://www.snee.com/bobdc.blog/2014/10/dropping-optional-blocks-from.html
Test adapted to previous commit
Ignore tests that require a running virtuoso on localhost
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.