@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix orcid: <https://orcid.org/> .
@prefix this: <http://purl.org/np/RAsSvA6zLo3JlOZpIM7u9ROTdmr7exAXvkV029A5kuqxk> .
@prefix sub: <http://purl.org/np/RAsSvA6zLo3JlOZpIM7u9ROTdmr7exAXvkV029A5kuqxk#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix pav: <http://purl.org/pav/> .
@prefix np: <http://www.nanopub.org/nschema#> .
@prefix doco: <http://purl.org/spar/doco/> .
@prefix c4o: <http://purl.org/spar/c4o/> .

sub:Head {
  this: np:hasAssertion sub:assertion;
    np:hasProvenance sub:provenance;
    np:hasPublicationInfo sub:pubinfo;
    a np:Nanopublication .
}

sub:assertion {
  sub:paragraph c4o:hasContent "We use the Test-Driven quality assessment (TDQA) methodology [21] as our main baseline comparison ap- proach to detect incorrect object values and datatypes and literals. TDQA is inspired from test-driven development and proposes a methodology to define (i) au- tomatic, (ii) semi-automatic and (iii) manual test cases based on SPARQL. Automatic test cases are generated based on schema constraints. The methodology suggests the use of semi-automatic schema enrichment that, in turn, will generate more automatic test cases. Manual test cases are written by domain experts and can be based either on a test case pattern library, or written as manual SPARQL queries.";
    a doco:Paragraph .
}

sub:provenance {
  sub:assertion prov:hadPrimarySource <http://dx.doi.org/10.3233/SW-160239>;
    prov:wasAttributedTo orcid:0000-0003-0530-4305 .
}

sub:pubinfo {
  this: dcterms:created "2019-09-20T18:05:11+01:00"^^xsd:dateTime;
    pav:createdBy orcid:0000-0002-7114-6459 .
}