I think it might make sense to separate things so that we have -- requests that refer to a specific Atomspace that has already been instantiated and populated
-- requests to load certain data into an Atomspace as separate sorts of requests... Then one could have patterns of usage such as -- query an existing Atomspace known to be populated with certain types of information already -- load in some data to an Atomspace, and then submit some queries based on that data *** Also, should the response contain the recursive information necessary to be usable in a standalone manner, or would it generally require additional requests to the API to assemble related information about the entities contained in it? *** Perhaps that would be an option that could be set as part of each request? I guess there are use cases for either option, right? ben On Fri, Apr 11, 2014 at 7:58 PM, Cosmo Harrigan <[email protected]> wrote: > Thanks, this is interesting and will provoke further thought and > elaboration. > > In general, should it be assumed that a request is referring to a specific > atomspace that has already been instantiated and populated? Some calls > implicitly assume that there is a populated atomspace that will be used as > the context to form a response, while other functions can produce their > response based solely on their inputs. For instance, some calls have a > "dataset" parameter that is passed as part of the request, whereas other > calls necessitate that a remote state already exists. And, some calls have a > "situation" parameter, which could either be a fully specified situation, or > an encapsulation of a situation by some token. > > Also, should the response contain the recursive information necessary to be > usable in a standalone manner, or would it generally require additional > requests to the API to assemble related information about the entities > contained in it? > > Thanks, > Cosmo > > > > On Fri, Apr 11, 2014 at 4:28 PM, Ben Goertzel <[email protected]> wrote: >> >> I have thought a bit about what kind of API might be generally useful >> for application developers to use to interface with a proto-AGI >> systems.... >> >> I put my initial notes at >> >> http://wiki.opencog.org/w/A_Cognitive_API >> >> As notes there, these should be taken as a sketch of some initial >> thoughts rather than an actual detailed API proposal. I think the >> semantics of the suggested API calls are about what is needed, but I >> haven't tried to make a serious proposal regarding the syntax yet (and >> I may not be the best person to do so) >> >> -- Ben >> >> >> -- >> Ben Goertzel, PhD >> http://goertzel.org >> >> "In an insane world, the sane man must appear to be insane". -- Capt. >> James T. Kirk >> >> "Emancipate yourself from mental slavery / None but ourselves can free >> our minds" -- Robert Nesta Marley >> >> -- >> You received this message because you are subscribed to the Google Groups >> "opencog" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/opencog. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "opencog" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/opencog. > For more options, visit https://groups.google.com/d/optout. -- Ben Goertzel, PhD http://goertzel.org "In an insane world, the sane man must appear to be insane". -- Capt. James T. Kirk "Emancipate yourself from mental slavery / None but ourselves can free our minds" -- Robert Nesta Marley ------------------------------------------- AGI Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-f452e424 Modify Your Subscription: https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-58d57657 Powered by Listbox: http://www.listbox.com
