-
Notifications
You must be signed in to change notification settings - Fork 41
$ git clone https://github.com/AKSW/RDFUnit.git
$ cd RDFUnit/
$ mvn clean install# Simple call (Dereferencing or local file)
$ bin/rdfunit -d <dataset-uri> -s <schema1,schema2,schema3,...>
# Simple call (Dereferencing when you want to keep the manual tests for a dataset)
$ bin/rdfunit -d <dataset-uri> -u <source-URI> -s <schema1,schema2,schema3,...>
# Simple call (SPARQL)
$ bin/rdfunit -d <dataset-uri> -e <endpoint> -g <graph1,graph2,...> -s <schema1,schema2,schema3,...>
# with use of enriched ontnology
$ bin/rdfunit -d <dataset-uri> -e <endpoint> -g <graph1,graph2,...> -s <schema1,schema2,schema3,...> -p <enriched-schema-prefix>-d <dataset-uri> e.g. http://dbpedia.org, http://example.com/data.ttl, /home/datasets/data.ttl
is required in all cases and states a URI that relates to the tested dataset. It could be http://dbpedia.org for the DBpedia SPARQL endpoint or again the same for the DBpedia dumps. RDFUnit uses the dataset URI to associate manual test cases specific for a dataset.
If no endpoint or -u option is given, RDFUnit assumes that the dataset uri is to be tested and tries to test it directly. Note that this can also be a local file e.f. /home/rdf/data.ttl
-s < schema1,schema2,schema3,...> e.g. foaf,skos,prov,http://my.ontology.com/ns/core
schemas are also required for running an evaluation. You can use known prefixes, e.g. foaf or skos and RDFUnit automatically resolves the namespaces through the LOV endpoint or the schemaDecl.csv file. Note that any entries on the file will override
the entries retrieved from LOV.
-u <source-URI> e.g. http://example.com/data.ttl, /home/datasets/data.ttl
when we want to test a dataset directly we can use the bin/rdfunit -d <dataset-uri> -s <schemas> option. However, when we have associated manual test cases for a dataset uri and the actual url is different or the dump is downloaded locally, -u overrides defines the actual location and -d is used for loading any associated manual test cases.
-e <endpoint> -g <graph1,graph2,...> e.g. -e http://dbpedia.org/sparql -g http://dbpedia.org
You can run RDFUnit directly on a SPARQL endpoint by defining the -e and (optionally) the -g parameters.
Note by default RDFUnit does the following:
- We have a local H2 cache that stores the results and is located in
rdfunit-validate/cache/sparql/*. The cache has a default TTL 1 week - We do automatic pagination for retrieving big results. The default value is 800.
- We have a 5 seconds delay between queries to keep public endpoint load low.
- We have a limit of 800 results per query.
**All these values can be overridden from the command line options. (run bin/rdfunit -h for the available options
# argument help
$ bin/rdfunit -h