@prefix dc: <http://purl.org/dc/terms/> .
@prefix this: <http://purl.org/np/RAUVvjCDAV_U2PKJ1zMm1mkBWOtOLHpM4G2whII2XQqmU> .
@prefix sub: <http://purl.org/np/RAUVvjCDAV_U2PKJ1zMm1mkBWOtOLHpM4G2whII2XQqmU#> .
@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 linkflows: <https://github.com/LaraHack/linkflows_model/blob/master/Linkflows.ttl#> .
sub:Head {
  this: np:hasAssertion sub:assertion ;
    np:hasProvenance sub:provenance ;
    np:hasPublicationInfo sub:pubinfo ;
    a np:Nanopublication .
}
sub:assertion {
  sub:comment-3 a linkflows:ActionNeededComment , linkflows:ContentComment , linkflows:NeutralComment , linkflows:ReviewComment ;
    linkflows:hasCommentText "The problem addressed is a rather interesting one, giving first insights in how to adapt crowdsourcing to LDQ issues. From my point of view, I would have liked to see a more concise comparison of the two crowdsourcing approaches also with the sophisticated state-of-the-art automated tools. " ;
    linkflows:hasImpact "5"^^xsd:positiveInteger ;
    linkflows:refersTo <http://purl.org/np/RAnVHrB5TSxLeOc6XTVafmd9hvosbs4c-4Ck0XRh_CgGk#articleVersion1> .
}
sub:provenance {
  sub:assertion prov:hadPrimarySource <http://dx.doi.org/10.3233/sw-160239> ;
    prov:wasAttributedTo <https://orcid.org/0000-0001-7069-9804> .
}
sub:pubinfo {
  this: dc:created "2019-11-26T09:05:11+01:00"^^xsd:dateTime ;
    pav:createdBy <https://orcid.org/0000-0002-7114-6459> .
}