On 1/16/20 3:22 PM, Alexander Gabriel wrote:
Yes, that's cause you need URE rules to deal with And, Or, Not links as
well. See
https://github.com/opencog/pln/tree/master/opencog/pln/rules/crisp/propositional
<https://github.com/opencog/pln/tree/master/opencog/pln/rules/crisp/propositional>
https://github.com/opencog/pln/tree/master/opencog/pln/rules/propositional
<https://github.com/opencog/pln/tree/master/opencog/pln/rules/propositional>
for examples of such rules.
So, from looking at the AndLink, I gather that it can only be applied
to EvaluationLinks, InheritanceLinks, OrLinks, NotLinks,
and ExecutionLinks. Is there a preferred way of how to apply it (and its
brethren) to StateLinks, (and PresentLinks, AlwaysLinks and so on)?
I suppose so, just copy/paste it and modify it to your needs. Make sure
the variables are typed. Type restriction is used to speed up the
queries, and in some cases even avoid infinite recursions.
Note the TypeInhNode
https://wiki.opencog.org/w/TypeInhNode
that allows to match subtypes as well (I've never used it, but I assume
it works fine).
Also, are you sure you want to use StateLink? I tend to think reasoning
works better on immutable structures.
Nil
Best,
Alex
--
You received this message because you are subscribed to the Google
Groups "opencog" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/opencog/f831e81c-262e-4b12-9676-2da3e30b2ae6%40googlegroups.com
<https://groups.google.com/d/msgid/opencog/f831e81c-262e-4b12-9676-2da3e30b2ae6%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/opencog/d574f968-9de8-ba22-74bc-5bcc047977b7%40gmail.com.
