The SPIN model of OWL RL is not really optimized for speed, so you
cannot compare it to custom reasoners. Lots of rules need to be
executed, producing many (trivial) intermediate triples. Would your
approach with the OWL Micro Reasoner be an option, leaving SPIN for the
custom rules?
Holger
On 11/18/2015 15:43, [email protected] wrote:
Thank you for reply.
So I make a series of tests to discover the problem. As a positive
result I expect that each test returns two inferred triples. One
triple depends only on SPIN rules, while the second depends on OWL RL
+ SPIN rules inference.
1. The first test is a test without OWL RL importing. Of course, I got
only one triple (negative result). It consumes ~110 ms.
2. The second test is a test with importing OWL RL (it is made as in
the aforementioned example). I got two triples. It consumes ~3200 ms.
3. The third test uses Jena reasoner (OWL Micro Reasoner) to infer OWL
RL rules, then it makes a query to the inferred model to get iferred
triples and adds these triples to the main model. After this step
SPINInferences.run method is called on the main model. I got two
triples. It consumes ~430 ms.
All test's time consumptions do not include time for ontology models
loading and importing.
среда, 18 ноября 2015 г., 3:15:58 UTC+3 пользователь Holger Knublauch
написал:
On 11/17/2015 16:32, [email protected] <javascript:> 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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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.
