Jim, I agree, one must design for both high level and low level structures. one must both include pixels, and Memory Organization Packets. A requirement for an AGI then, is to deal with both perception and abstract reasoning from the beginning (rather than hope one follows from the other). Agreed.
~PM (Michael Miller - but you can call me Piaget Modeler. I like it). Date: Tue, 23 Oct 2012 09:04:03 -0400 Subject: Re: [agi] Re: Superficiality Produces Misunderstanding - Not Good Enough From: [email protected] To: [email protected] On Mon, Oct 22, 2012 at 9:28 PM, [email protected] <[email protected]> wrote: So links can act as nodes, basically, as in a generalized hypergraph? That's also built into my system. The Link class is a subclass of the Node class. Nothing particularly difficult or unpleasant there. A story can define a distinction between kinds in my system, but it would do so implicitly, through context, rather than explicitly through a formalized mechanism. While neither the links-as-nodes nor the story-as-concept is specifically used or accounted for in my design, it is easily extensible in both of these directions. What I'm looking for is a particular use case, a reason for paying special attention to this sort of functionality, as opposed to merely including the capability should it later be found to need that special attention. ----------------------------------------- ------------------------------------------- AGI Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-c97d2393 Modify Your Subscription: https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-2484a968 Powered by Listbox: http://www.listbox.com
