So far as I know, there are no authoritative definitions of what are meant by programming plans, but might I suggest that we resolve to not be content with overloading the term "plan" any more than necessary? Dr. Brooks likens a plan to (1) an architect's plan for a house and (2) a procedure for accomplishing a goal/function (find). Anybody else find these quite different in character? Sure, I would say either connotation is schematic and therefore aptly called a "schema", however the latter is more *specifically* a schematic description of a procedure. The notion of programming plan from the MIT (Shrobe/Rich/Waters) and Yale (Soloway et. al.) procedural schemas. I think its wise to continue this more specific use. It is also consonant with Schank's scripts. I propose #1's term be weakened to simply "schema" unless a more specific denotation can be figured out. This is along the same lines as Detienne's excellent summary on schematic programming knowledge in the PPIG book. Andrew - Automatic footer for [EMAIL PROTECTED] ---------------------------------- To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss To join the announcements list, mail [EMAIL PROTECTED] subscribe announce To receive a help file, mail [EMAIL PROTECTED] help This list is archived at http://www.mail-archive.com/discuss%40ppig.org/ If you have any problems or questions, please mail [EMAIL PROTECTED]
