@prefix dcterms: <
http://purl.org/dc/terms/
> .
@prefix this: <
http://purl.org/np/RA4fcBrQcn5f4QvdK_eEQ0RilYDwZkneSlIAj33VCfsT8
> .
@prefix sub: <
http://purl.org/np/RA4fcBrQcn5f4QvdK_eEQ0RilYDwZkneSlIAj33VCfsT8#
> .
@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-7
a
linkflows:ActionNeededComment
,
linkflows:ContentComment
,
linkflows:NegativeComment
,
linkflows:ReviewComment
;
linkflows:hasCommentText
"It should be better explained why the WiseNET ontology redefines part of the content of ifcowl (e.g. properties “aggregates”, “spaceContains”). Why isn’t it enough to extract a fragment of ifcowl and use it in integration with other ontology modules? This would allow to skip a few query+update steps in the proposed methodology." ;
linkflows:hasImpact
"3"^^
xsd:positiveInteger
;
linkflows:refersTo
<
http://purl.org/nanopub/temp/linkflows/sample-paper-3/v1/f3#figure
> , <
http://purl.org/nanopub/temp/linkflows/sample-paper-3/v1/t4#table
> , <
http://purl.org/nanopub/temp/linkflows/sample-paper-3/v1/t5#table
> .
}
sub:provenance
{
sub:assertion
prov:hadPrimarySource
<
http://dx.doi.org/10.3233/SW-180298
> ;
prov:wasAttributedTo
<
https://orcid.org/0000-0000-0000-0000
> .
}
sub:pubinfo
{
this:
dcterms:created
"2019-11-26T09:05:11+01:00"^^
xsd:dateTime
;
pav:createdBy
<
https://orcid.org/0000-0002-7114-6459
> .
}