Closed cmungall closed 2 years ago
I was aware some calls to consume triples were not working, as visible in the logging:
TripleLogger - s=<_:genid-nodeid-node1fhl6m9evx1> p=rdf:type o=owl:Ontology
OWLRDFConsumer - consuming triple failed
TripleLogger - s=<_:genid-nodeid-node1fhl6m9evx2> p=rdf:type o=owl:Restriction
OWLRDFConsumer - consuming triple failed
OWLRDFConsumer - Unparsed triple: https://www.wikidata.org/wiki/Q2306597 -> rdf:type -> _:genid-nodeid-node1fhl6m9evx2
It's taken me quite a bit to realise the unparsed triple is not one where the triple cannot be consumed; rather, for class assertions the consume call is not made at all. The other failures are misleading, as the triples to be consumed are actually dealt with without explicit entries in the maps, and so don't actually need to be consumed. Ironic.
This ttl yields an error
Note that this was in fact generated by the owlapi from simpler functional syntax:
When I parse this using robot using
--strict
with-vvv
I get:I believe this is the OWLAPI rather than robot.
If I leave off
--strict
then it parses this correctly (saving to ofn verifies this). However, it still produces the "unparsed triple" as an INFO level logging. statement. ROBOT intercepts this and logs it as an ERROR which is disturbing to some users.See also #988 where we discuss the strict option.