opencog-dev team mailing list archive

["David Hart" <hart@xxxxxxxxxxxx>]

This is a housekeeping message to move this thread to
opencog-developers@xxxxxxxxxxxxxxxx.

Please remove opencog-dev@xxxxxxxxxxxxxxxxxxx from the CC in the next reply.

Thanks,

-dave

---------- Forwarded message ----------
From: Linas Vepstas <linasvepstas@xxxxxxxxx>
Date: Tue, Nov 4, 2008 at 9:05 AM
Subject: Re: [Opencog-dev] Tutorial: Unification methods in PLN code
To: joel.pitt@xxxxxxxxx
Cc: opencog-dev <opencog-dev@xxxxxxxxxxxxxxxxxxx>


Hi,

2008/11/1 Joel Pitt <joel.pitt@xxxxxxxxx>:

> 1. You've mentioned a couple of times that the atom class is obsolete.
> Do vtrees now essentially fulfill all the tasks expected of the atom
> class in PLN, such that it's just a matter of replacing atoms with
> vtrees in most places (and maybe making a few changes to the methods
> called etc.)...

I'm coming in very late to what must have been a long
discussion, but ... what is a vtree, and why would it replace
an "atom class"?

Perhaps I'm naive; currently, opencog has a class called
"Atom" that is a base class for Node and Link ...surely,
this is not going away?

I'm representing a broad variety of relationships using
Nodes and Links, does this "vtree" stuff affect me? Or
is this more about some internal representation used
only in the guts of PLN, and has no impact to outsiders?

--linas

_______________________________________________
Mailing list: https://launchpad.net/~opencog-dev<https://launchpad.net/%7Eopencog-dev>
Post to     : opencog-dev@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~opencog-dev<https://launchpad.net/%7Eopencog-dev>
More help   : https://help.launchpad.net/ListHelp