On 11/17/2015 16:32, [email protected] wrote:
I created a simple ontology in free TopBraid Composer and added some
spin rules. When I run inference all worked just fine. So it is when I
worked with this ontology with the help of TopBraid API.
I decided to use OWL RL in order to inference subclass relation on the
base of property restriction. I switched on the corresponding profile
and under TopBraid Composer all worked as well as before. I mean that
I run inference and get the expected inferred triple.
To use OWL RL while inference I made the same things as in the
OWLRLExample.java. So I get the expected triple. But it is inferencing
notably slowly more than 8000 triples. Without OWL RL it gives only 4
triples (of course, without the expected).
Is it possible to somehow decrease inference time and result?
TopBraid Composer displays fewer inferences because it is removing many
"trivial" inferences, such as
?x owl:sameAs ?x .
and
?c rdfs:subClassOf ?c .
This may explain why you are seeing more triples with the SPIN API.
However, it does not explain a difference in performance (run time).
Could you give some of idea of how much the time difference is?
Holger
--
You received this message because you are subscribed to the Google Group "TopBraid
Suite Users", the topics of which include Enterprise Vocabulary Network (EVN),
Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
