On Wed, Mar 15, 2017 at 11:47 AM, Ben Goertzel wrote:
> I guess the argument for having a link type "BeliefLink" is that Sumit
> created specific quantitative truth value formulas to deal with
> BeliefLink Of course these formulas could also be used together
> with
I guess the argument for having a link type "BeliefLink" is that Sumit
created specific quantitative truth value formulas to deal with
BeliefLink Of course these formulas could also be used together
with "PredicateNode 'belief' " as well, but so far typically when we
have specific math
I updated the wiki page to mention it, and also mention that a BeliefLink
is the same as EvaluationLink Predicate "belief". Not only would a port
into the current PLN infratructure be useful, but that should be followed
by a tutorial/example, and there should also be a hookup into the chatbot.
Hmm, OK, it's been a while since that work was done and almost as long
since I looked at it
The crux of Sumit's work was to modify the PLN truth value formulas to
work sensibly for these modal-logic operators (belief, etc.). That
part was solid and I remember it. But the choice of link types he
I just skimmed that code, and it does not seem to make use of the KR
structures described in http://wiki.opencog.org/w/Claims_and_context and
instead invents new link types .. e.g. BeliefLink. This leads to a
proliferation: you'd need BeliefLink, SayLink,
TellLink,UseToBeleiveInThePastLink,
Code and theory for extending PLN to handle modal reasoning regarding
beliefs, knowledge and so forth is here:
https://github.com/sumitsourabh/opencog/tree/patch-1/opencog/reasoning/pln/rules/epistemic-reasoning
This was carefully worked out by Sumit Sourabh and Matt Ikle' a few years ago.
The
Here:
this page tells you about how to repesent the internal state of other
speakers (this includes beleifs, demands, ettc.)
http://wiki.opencog.org/w/Claims_and_contexts
---linas
On Wed, Mar 15, 2017 at 11:07 AM, Linas Vepstas
wrote:
>
>
> On Sat, Mar 11, 2017 at
On Sat, Mar 11, 2017 at 10:25 PM, Alex wrote:
> Hi!
>
> There can be modalities (which are usually expressed as diamonds or boxes
> (operators) in modal logic):
> DUTY_TO_PERFORM_ACTION(agent, action, time horizone) - agent should
> perform action within time horizon
>
Hi!
There can be modalities (usually spelled as diamonds or boxes in modal
logics):
DUTY_TO_PERFORM_ACTION(agent, action, time horizon) - agent should perform
action in time horizon
BELIEF(agent, fact, time instant) - agent believes in fact at time instant
Such modalities are necessary to
Hi!
There can be modalities (which are usually expressed as diamonds or boxes
(operators) in modal logic):
DUTY_TO_PERFORM_ACTION(agent, action, time horizone) - agent should perform
action within time horizon
BELIEF(agent, statement, time instant) - agent believes in statement at the
time
There are many ways of doing this. The simplest one is probably this:
(EvaluationLink
(PredicateNode "Vishnu's special ID43")
(InheritanceLink (stv 0.9 0.9)
(ConceptNode "Einstein")
(ConceptNode "man"
which is conceptually the same thing as
(VishnuSpecialLink
On Fri, Mar 3, 2017 at 10:51 PM, 'Nil Geisweiller' via opencog <
opencog@googlegroups.com> wrote:
> PLN doesn't have any rule to reason about AssociativeLinks. To have some
> we'd need to define its semantics.
>
I think they're called association links.
It might be interesting to have a demo
Hi,
I tried DefineLink. But the problem is i can define my ID only once. Since
it is used to give an unique name.
(DefineLink
(DefinedSchemaNode "ID1")
(InheritanceLink (stv 0.9 0.9)
(ConceptNode "Einstein")
(ConceptNode "man")))
(DefineLink
(DefinedSchemaNode "ID1")
(ListLink
13 matches
Mail list logo