<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Ontology Reasoners and Rule Engines are
quite different, can be integrated under some assumptions, <br>
but are definitely not easily interchangeable.. (unique name
assumption, closed world assumption, etc..)<br>
Which one is better pretty much depends on the use case, which
also dictates the required level of <br>
expressiveness of the language - even Fact++, Hermit and Pellet do
not support full FOL...<br>
<br>
This said, your case seems very interesting.. would you mind
sharing a few more details or a concrete example?<br>
We would then be able to assess whether Drools is appropriate or
not, and which constructs could be<br>
used (e.g. traits, hybrid chaining queries, tms, ...) to tackle
the complexity.<br>
<br>
Or maybe we could take it as a use case to improve the engine
capbilities :)<br>
<br>
Best<br>
Davide<br>
<br>
<br>
<br>
<br>
On 04/11/2013 05:01 AM, Upali Kohomban wrote:<br>
</div>
<blockquote cite="mid:5166A61B.7070705@codegen.co.uk" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Thanks a lot again, you made my life
easy with the build instructions :)<br>
<br>
Yes I'm trying to do an integration. I have some experience with
ontologies and want to experiment with drools as an alternative.<br>
<br>
OWL with reasoners like Fact ++ are pretty much good for the
job, except for the fact that they handle individual data bits
in quite a cumbersome way. It was because of this reason that I
wanted to experiment on other ways of modeling a knowledge
structure with better facilities for querying large amounts of
factual data. I'm giving drools a try, but I'm not entirely sure
if drools can do things as powerful as a reasoner.<br>
<br>
Basically, I'd like to be able to let the data lie (without
firing any "events" until necessary) and query the inferences
in a first-order logic like manner. This is very space-efficient
in data-heavy scenarios. I know that this isn't the traditional
way drools is designed to work. I'm trying to solve the
inference problem by dynamically adding semantic classes to each
object to store all the possible inferences about it, so they
can be queried later. Problem with this approach is that it gets
out of hand very quickly, because the enumerated number of such
inferences can be HUGE even for a moderate KB. Backward chaining
will eventually solve this problem, but it seems that the
constructs available for that in drools queries are not too
matured at the moment. For instance they don't seem to support
numerical inequality operators (or I am wrong, which is also
very likely).<br>
<br>
Thank you again for the quick help,<br>
Upali<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 11/04/2013 14:14, Davide Sottara wrote:<br>
</div>
<blockquote cite="mid:516677D1.9000009@gmail.com" type="cite">
<pre wrap="">You should be able to
git clone ...
the droolsjbpm repository, then
git checkout -t origin/5.5.x
this should switch to 5.5.1-SNAPSHOT (you can check the pom in the root
folder)
eventually, mvn clean install should do the trick.
See also the readme.md in github
Btw, it seems that you're working with rule/ontology integrations..
would you
be interested in sharing thoughts?
Davide
On 04/11/2013 01:29 AM, upalik wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Davide,
Thanks a lot for the information and your time spent on troubleshooting the
scenario with a test case.
I'm using 5.5.0; as I mentioned, I'm a newbie. I'll try to get 5.5.1
compiled and running (on windows), I'm reading whatever the documentation I
can find on how to do this. Github source seems to be on 6.0.0, I'll try
with that one if all else fails.
I'm loading the rule base using a KnowledgeBuilder, and yes I do check for
errors explicitly after building. The rule file with the problem I mentioned
does not produce any errors, other than the result that doesn't make sense.
Thanks again,
Upali
--
View this message in context: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://drools.46999.n3.nabble.com/drools-queries-strange-dependency-tp4023320p4023323.html">http://drools.46999.n3.nabble.com/drools-queries-strange-dependency-tp4023320p4023323.html</a>
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
rules-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<p style="font-family: Calibri, Verdana, Arial, Helvetica,
sans-serif;font-size: 11px;"> <span style="font-size: 12px;"><strong>Upali
Kohomban</strong>, PhD</span><br>
Research Fellow<br>
<span style="color: #808080">CodeGen International<br>
29 Breybrooke Street, Colombo 02, Sri Lanka<br>
<b>T:</b> +94 112 470 740 <b>F:</b> +94 112 470 749 <b>W:</b>
<a moz-do-not-send="true" href="http://codegen.net">http://codegen.net</a></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a></pre>
</blockquote>
<br>
</body>
</html>