In this article, we present a programming language for expressing classificatory problem solvers. CSRL (Conceptual Structures Representation Language) provides structures for representing classification trees, for navigating within those trees, and for encoding uncertainly judgments about the presence of hypotheses. We discuss the motivations, theory, and assumptions that underlie CRSL. Also, some expert systems constructed with CSRL are briefly described.

In this article, we present a programming language for expressing classificatory problem solvers. CSRL (Conceptual Structures Representation Language) provides structures for representing classification trees, for navigating within those trees, and for encoding uncertainly judgments about the presence of hypotheses. We discuss the motivations, theory, and assumptions that underlie CRSL. Also, some expert systems constructed with CSRL are briefly described.

Expert system projects are often based on collaboration with single domain expert. This leads to difficulties in judging the suitability of the chosen task and in acquiring the detailed knowledge required to carry out the task. This anecdotal article considers some of the advantages of using a diverse collection of domain experts.

Early this year fifty people took an experimental course at Xerox PARC on knowledge programming in Loops. During the course, they extended and debugged small knowledge systems in a simulated economics domain called Truckin. Everyone learned how to use the environment Loops, formulated the knowledge for their own program, and represented it in Loops. The punchline to this story is that almost everyone learned enough about Loops to complete a small knowledge system in only three days.

Early this year fifty people took an experimental course at Xerox PARC on knowledge programming in Loops. During the course, they extended and debugged small knowledge systems in a simulated economics domain called Truckin. Everyone learned how to use the environment Loops, formulated the knowledge for their own program, and represented it in Loops. At the end of the course a knowledge competition was run so that the strategies used in the different systems could be compared. The punchline to this story is that almost everyone learned enough about Loops to complete a small knowledge system in only three days. Although one must exercise caution in extrapolating from small experiments, the results suggest that there is substantial power in integrating multiple programming paradigms.