parsing

[Ferenc]

This is the tart of animo parsing algorithm in my understanding:
Step 1 Animo: I expect something turn up on the input side – so I have
a location reserved for that
Input: token
Animo: This looks like one, not divisible. Make a note of not
divisible somewhere. So I will call it one and put it in its location
that I have marked Mark 1
Animo: I am going back to step 1
Input: token (the same as before)
Animo: well, now I m going to use one of my intelligent operations
called “compare” and see if my Mark 1 (one) is the same as this new
guy:
Animo performs evaluation and comes back with the result: well it is
exactly the same thing, but coming a little later than the other copy
(one). So I am going to give it a name Mark 2. But If it is the same
as Mark 1, then Mark 1 WAS divisible, so let us correct that point:
Mark 1 divided by Mark 2 equals Mark 1: or one divided by one yields
one, but on the two sides of the equation or identity symbol/operator
we have two “ones” equaling one. So not to make your life difficult we
shall call Mark 1 an object and Mark 2 a property. But what shall we
call the equal sign between them? Well it is an operation after
division when we check the result, when we measure what has happened
after a computer operation called division, which is fact was not
division, but pattern matching to see if the two tokens were the same.
So we did not halve the tokens as they were elementary, not divisible
or terminal symbols. Nevertheless we got a result without a remaninder
and the result itself had to “represented” or communicated through
another operation that we still have to name. So we call that
Relation, or relating two tokens that are in our sight as input and
which we want to put in whatever locations are available.
Can you follow?

[Dmitriy Shabanov]

On Thu, Dec 15, 2011 at 12:34 PM, Ferenc <genez...@googlemail.com> wrote:

This is the tart of animo parsing algorithm in my understanding:
Step 1 Animo: I expect something turn up on the input side – so I have
a location reserved for that
Input: token

for reference needs lets make it "1" token
 

Animo: This looks like one, not divisible. Make a note of not
divisible somewhere. So I will call it one and put it in its location

not divisible & divisible definitions please?

animo object that I do see: the uuid`

that I have marked Mark 1
Animo: I am going back to step 1
Input: token (the same as before)

Did Animo make any actions? (any output?)
 

Animo: well, now I m going to use one of my intelligent operations
called “compare” and see if my Mark 1 (one) is the same as this new
guy:
Animo performs evaluation and comes back with the result: well it is
exactly the same thing, but coming a little later than the other copy
(one). So I am going to give it a name Mark 2. But If it is the same
as Mark 1, then Mark 1 WAS divisible, so let us correct that point:
Mark 1 divided by Mark 2 equals Mark 1: or one divided by one yields
one, but on the two sides of the equation or identity symbol/operator
we have two “ones” equaling one. So not to make your life difficult we
shall call Mark 1 an object and Mark 2 a property. But what shall we
call the equal sign between them? Well it is an operation after
division when we check the result, when we measure what has happened
after a computer operation called division, which is fact was not
division, but pattern matching to see if the two tokens were the same.
So we did not halve the tokens as they were elementary, not divisible
or terminal symbols. Nevertheless we got a result without a remaninder
and the result itself had to “represented” or communicated through
another operation that we still have to name. So we call that
Relation, or relating two tokens that are in our sight as input and
which we want to put in whatever locations are available.
Can you follow?

--
Dmitriy Shabanov

[Dmitriy Shabanov]

This is the tart of animo parsing algorithm in my understanding:
Step 1 Animo: I expect something turn up on the input side – so I have
a location reserved for that
Input: token

 
for reference needs lets make it "1" token
 

Animo: This looks like one, not divisible. Make a note of not
divisible somewhere. So I will call it one and put it in its location

not divisible & divisible definitions please?

animo object that I do see: the uuid1 name "1". (BTW, we can use "token" instead of "name" to avoid confusion)

that I have marked Mark 1
Animo: I am going back to step 1
Input: token (the same as before)

 
Did Animo make any actions? (any output?)
 

Animo: well, now I m going to use one of my intelligent operations
called “compare” and see if my Mark 1 (one) is the same as this new
guy:
Animo performs evaluation and comes back with the result: well it is
exactly the same thing, but coming a little later than the other copy
(one).

Everything will came later, that is constant property of parsing.
 

So I am going to give it a name Mark 2.

the uuid2 name "1".
 

But If it is the same
as Mark 1, then Mark 1 WAS divisible, so let us correct that point:
Mark 1 divided by Mark 2 equals Mark 1: or one divided by one yields
one, but on the two sides of the equation or identity symbol/operator
we have two “ones” equaling one. So not to make your life difficult we
shall call Mark 1 an object and Mark 2 a property.

do you mean: uuid1 uuid2 (animo statement: uuid2 under uuid1)?
 

But what shall we
call the equal sign between them?

They are equal by "name" topology.
 

Well it is an operation after
division when we check the result, when we measure what has happened
after a computer operation called division, which is fact was not
division, but pattern matching to see if the two tokens were the same.

ok, uuid1 uuid2 is two steps loop:
uuid2 -> the uuid2 -> name(uuid2) -> "1" <- name(uuid1) <- the uuid1 <- uuid1 -> uuid2

So we did not halve the tokens as they were elementary, not divisible
or terminal symbols. Nevertheless we got a result without a remaninder
and the result itself had to “represented” or communicated through
another operation that we still have to name. So we call that
Relation, or relating two tokens that are in our sight as input and
which we want to put in whatever locations are available.
Can you follow?

--
Dmitriy Shabanov

[inference]

----- Original Message -----

From: Dmitriy Shabanov

To: anim...@googlegroups.com

Sent: Thursday, December 15, 2011 9:09 AM

Subject: Re: [animotron] parsing

On Thu, Dec 15, 2011 at 12:34 PM, Ferenc <genez...@googlemail.com> wrote:

This is the tart of animo parsing algorithm in my understanding:
Step 1 Animo: I expect something turn up on the input side – so I have
a location reserved for that
Input: token

for reference needs lets make it "1" token
 

Animo: This looks like one, not divisible. Make a note of not
divisible somewhere. So I will call it one and put it in its location

not divisible & divisible definitions please?

 

If a number is divisible, it means it may be written as a fraction like 1/1, or an integer, as there would be no remainders. It also means to me that a number may represent the highest number in a numeral system of base x, like one in binary system, or 9, in a decimal system

animo object that I do see: the uuid`

uuid is an acronym it sands for .... just to make sure thta we agree

that I have marked Mark 1
Animo: I am going back to step 1
Input: token (the same as before)

Did Animo make any actions? (any output?)

 

Only internal as far as I can guess - but it couls go and output that I am ready, next guest please So the output is DELAYED until the following passage is done
 

Animo: well, now I m going to use one of my intelligent operations
called “compare” and see if my Mark 1 (one) is the same as this new
guy:
Animo performs evaluation and comes back with the result: well it is
exactly the same thing, but coming a little later than the other copy
(one). So I am going to give it a name Mark 2. But If it is the same
as Mark 1, then Mark 1 WAS divisible, so let us correct that point:
Mark 1 divided by Mark 2 equals Mark 1: or one divided by one yields
one, but on the two sides of the equation or identity symbol/operator
we have two “ones” equaling one. So not to make your life difficult we
shall call Mark 1 an object and Mark 2 a property. But what shall we
call the equal sign between them? Well it is an operation after
division when we check the result, when we measure what has happened
after a computer operation called division, which is fact was not
division, but pattern matching to see if the two tokens were the same.
So we did not halve the tokens as they were elementary, not divisible
or terminal symbols. Nevertheless we got a result without a remaninder
and the result itself had to “represented” or communicated through
another operation that we still have to name. So we call that
Relation, or relating two tokens that are in our sight as input and
which we want to put in whatever locations are available.
Can you follow?

--
Dmitriy Shabanov

[inference]

do you mean: uuid1 uuid2 (animo statement: uuid2 under uuid1)?

 

1. Is that an animo statement above? Is that input or utput? what is UNDER? under what?

ok, uuid1 uuid2 is two steps loop:
uuid2 -> the uuid2 -> name(uuid2) -> "1" <- name(uuid1) <- the uuid1 <- uuid1 -> uuid2

2. What are those arrow for WHAT IS THE NAME of the OPERATOR?

 

They are equal by "name" topology.

3. What does it mean "equal BY name topology"? 

----- Original Message -----

From: Dmitriy Shabanov

To: anim...@googlegroups.com

Sent: Thursday, December 15, 2011 9:20 AM

Subject: Re: [animotron] parsing

Is that an animo statement above? Is that input or utput? what is UNDER? under what?
 

But what shall we
call the equal sign between them?

They are equal by "name" topology.
 

Well it is an operation after
division when we check the result, when we measure what has happened
after a computer operation called division, which is fact was not
division, but pattern matching to see if the two tokens were the same.

ok, uuid1 uuid2 is two steps loop:
uuid2 -> the uuid2 -> name(uuid2) -> "1" <- name(uuid1) <- the uuid1 <- uuid1 -> uuid2

So we did not halve the tokens as they were elementary, not divisible
or terminal symbols. Nevertheless we got a result without a remaninder
and the result itself had to “represented” or communicated through
another operation that we still have to name. So we call that
Relation, or relating two tokens that are in our sight as input and
which we want to put in whatever locations are available.
Can you follow?

--
Dmitriy Shabanov