Re: Contexts and firstname.lastname@example.org (Robert MacGregor)
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 31 May 1995 17:11:46 -0800
To: email@example.com (John F. Sowa), firstname.lastname@example.org, email@example.com,
From: firstname.lastname@example.org (Robert MacGregor)
Subject: Re: Contexts and views
Cc: email@example.com, firstname.lastname@example.org, email@example.com
Our notion of contexts would seem to be rather different than John's.
In our system, its not possible to look inside of a context from
outside. Instead, to "see" the facts, definitions, etc. in a context,
you must be in it, or in one of its children. This is in accord
with normal scoping rules.
Also, we support
multiple inheritance -- our context hierarchies are not limited
to trees. We have quite a few users (mostly in the NL domain)
who use the multiple inheritance feature. One way to reason
with two different views/contexts is to create a new context
that inherits both of them.
We have also identified (but not yet implemented) a need for
an export feature (lifting). Often, one would like to reference some
of the objects in a context without inheriting that context.
That provides a second means for interviewing the contents
of a context without being in or below it.
Robert M. MacGregor firstname.lastname@example.org
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292 (310) 822-1511