You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I understood the documentation correctly, calling rdfs.closure() should only store the inferred triples in a temporary set. They should only be added to the graph when calling the flush_stored_triples() method.
However, this method is already called at the end of the closure() method.
Is there a possibility to not add the triples directly to the graph? Is this behavior on purpose?
The text was updated successfully, but these errors were encountered:
@JanKalo
I believe this is a documentation error. Due to the cyclic nature of the way the RDFSClosure (and OWLRLClosure) patterns work in this library, it is necessary for the tool to flush all triples to the graph at the end of each cycle, so they can be available in the graph for the subsequent cycle.
I do plan to add a new feature in OWL-RL in the coming weeks, that will allow you to specify a separate named graph within an rdflib Dataset where all new triples will be added.
When I understood the documentation correctly, calling rdfs.closure() should only store the inferred triples in a temporary set. They should only be added to the graph when calling the flush_stored_triples() method.
However, this method is already called at the end of the closure() method.
Is there a possibility to not add the triples directly to the graph? Is this behavior on purpose?
The text was updated successfully, but these errors were encountered: