Skip to content
Dimitris Kontokostas edited this page Jun 26, 2014 · 20 revisions

RDFUnit Command Line Interface

Download & build RDFUnit

$ git clone https://github.com/AKSW/RDFUnit.git
$ cd RDFUnit/
$ mvn clean install

Basic usage

# 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> 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.

-s < schema1,schema2,schema3,...> 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.

Available options

# argument help
$ bin/rdfunit -h

Clone this wiki locally