Re: Storing data and code in a Db with LISP-like interface

>> Neo: One can't know the requirements ahead of time in AI-type apps. Thus one would like a system that is the least impacted in terms of schema/scripts/queries/code by the need to meet future requirements. .
> So, generality prevents (hopefully) the need for change if a future requirement is discovered. So, the reason for wanting this requirement is "I don't know what I'll need in the future, and it seems to me to be common sense that we want to be able to extend the represented information". Is that a fair conclusion?

:) You got it! Let me refine, one can't know the exact requirements ahead of time in AI-type apps. The requirements are very general (ie be able to represent/process anything). A very general/flexible/sytematic method minimizes the impact on existing code/data and provides a consistent/systematic method to meet new requirements (which will be implemented by the droid himself and not the original designer).

>> Neo: To achieve this, anything that is represented in a db, should be treated the same as all the other things represented in the db. .
> So the rules and relationships that are encoded in the schema itself has to be available for extension.

To build the ultimate droid, yes. Received on Tue May 09 2006 - 22:40:18 CEST