Re the recent discussion of OpenCog -- this recent post I made to the OpenCog mailing list may perhaps help clarify the intentions underlying the project further.
-- Ben ---------- Forwarded message ---------- From: Benjamin Goertzel <[EMAIL PROTECTED]> Date: Dec 27, 2007 11:07 AM Subject: Re: Project Questions To: [EMAIL PROTECTED] On Dec 27, 2007 9:27 AM, Pat <[EMAIL PROTECTED]> wrote: > > Ben, > > Thank you for the link to the paper. My thinking has been that in > order to develop a machine capable of general intelligence, a > specification would need to be developed which outlines the > functionality of a thinking machine, separate from any implementation > issues. I totally agree -- and, I have tried to do that in a 350-page manuscript, which I plan to release online sometime in the first half of 2008. HOWEVER, even though I am a big fan of my AI design, it's obvious that there are going to be many lessons learned during the course of working out more detailed designs of subcomponents and experimenting with implementations. This is a useful conversation, because I'm seeing that it in talking about OpenCog it will be valuable to distinguish -- OpenCog core -- Specific AGI designs that can be built on the OpenCog core, generally in a modular fashion (each AGI system comprising a certain set of MindAgents and a certain set of functional units) The OpenCog core may be used for a load of different AGI designs My own AGI design is one particular design that can be built on the OpenCog core. The AGI design that I will advocate for building on top of the OpenCog core is a variant of the Novamente design, I'm not sure what to call it, but it will get a name before the OpenCog launch... However, I also want to explicitly encourage the creation of other AGI designs on top of OpenCog. Hopefully there can be crosspollination of different approaches. > I can see where your approach of taking diverse contributions of > software and integrating them around a framework could be instrumental > in the exploration and discovery of the specification (among other > benefits). As I hope I've clarified above, -- I do have a fairly precise specification I'm interested in using OpenCog to explore, which is closely related (but not identical) to my Novamente specification -- However, I don't intend OpenCog to be restricted to the implementation. exploration of this specification of mine Thanks for your questions, they are certainly good ones... -- Ben ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?member_id=8660244&id_secret=79828670-a37b2c
