[Animo-open] Animo ideas

[Dmitriy S. <sha...@gm...>]

Hello,

Time to show more... :-)

THE A - is point in animo space, that is not a simple node on graph, but
several relations & node. Let's call it object.

IS create some sort of categories space.

Object can have properties, HAVE used for that, same time object under HAVE
is THE-like. This require example to understand:

*the personA is male.*
*the personB is female.*

*the personC have parent (an personA) (an personB).*

As you can see personB is mother for personC ONLY. It possible to add simple
object: *the mother (is parent) (is female).* And question: *?is personC
have mother personB*. will be answered *the yes.*
*
*
I did use reference AN, this one is direct one. There are also ANY (one or
nothing), ALL (we didn't clear this one. It can be all by IS topology or
just leafs)
+ predicates: *all book with any author with name "Stanisław Lem"*.* *(working
to simplify this type of statements)
note:  *Stanisław Lem** books *can be parsed to animo statement, but that
have two (as minimum) minings "as owner" & "as author" (only is graph have
that!!!). This can be solved by question back to interlocutor, or base on
context, or ...*
*

That was declarative part of language. It do have functional part too, very
close to lisp. Biggest difference in GET or ever so called empty GET, answer
searching at context or call stack. That is a bit hard to understand by
simple to use. The main reason for that is "know what require, but don't
know where to get".
Example:

GET with defined context
the A have B "C". the Z get B an A.  => the Z have B "C".

empty GET
the A have B "C". the Z get B. an Z an A. =>  the Z have B "C".

GET also use IS topology:
the A have B "C". the B is C. the Z get C an A.  => the Z have B "C".

Complex example:
the A have B get C.
the D have E get B.
the x an D an A have C ":". =>   the X the D have E have B have C ":"
There much more but I have to stop and look around =)

=================

So, you can see that this is mix of your ideas. "mental operations" I do see
as question operations. It should be possible to link them to different type
of questions.
Also, I do want to "serialize" subgraph to language. That should be very
interesting, because I do want to use pure animo to reach that target.

Any comments or questions?

-- 
Dmitriy Shabanov