Henry, would that you shall always play in the same sandbox as I.
----- Original Message -----
From: Henry van Eyken <email@example.com>
Sent: Thursday, December 14, 2000 1:06 PM
Subject: Re: [unrev-II] Use Cases and Ontologies
> I may not yet be able to build me an OHS, but at least Jack knows how to
> concretize (ugly word, that, but a valid one) his ideas. You make a good
> teacher, Jack. And I might even begin to grasp what an ontology is. It
> like mapping back all the world's stage into God's mind from which He,
> little bit of bootstrapping and programmer's luck can make a better world.
> Jack Park wrote:
> > I have been thinking about use cases, ontologies, and scenarios. I
> > these thoughts my experience with qualitative process theory, a
> > representation and inferencing mechanism by which one can express
> > processes in ontological terms.
> > QP theory says that we need to know stuff about the following:
> > actors
> > relations
> > states
> > QP theory allows us to build an 'envisionment' in which a graph
> > very large graph) is built with its origin being a node called 'initial
> > conditions.' I have imported a metaphor about theator into QP theory,
> > one 'sets the stage' by defining initial conditions. There is no
> > on this stage, just process rules, some of which can 'fire' changing the
> > stage setting allowing for other rules to fire. Each 'firing' defines a
> > stage setting (node in the graph). When multiple rules can fire against
> > particular node, you have multiple branches from that node to new nodes.
> > The process continues until no more rules can fire, or until 'stopping
> > rules' --which define some goal stage setting -- fire.
> > Thinking in newtonian terms, moving from one node to the next along some
> > means that the arc represents some 'mechanism' or presence of a causal
> > mechanism at work (e.g. the rule that fired). Defining the entire
> > vocabulary of such a QP universe is, indeed, defining an ontology.
> > rules appear as 'axioms' in the ontology.
> > Now, what are use cases? They are simply very course grained
> > Basically, the presence of actors, and a description of the gross change
> > occur between initial conditions (which are not stated in use cases) and
> > final conditions (which are also not stated in use cases).
> > Consider this use case: UC-ActorViewDocument
> > Actors: user, OHS
> > Action: user views document with OHS
> > Rather high level, what?
> > Now, what are scenarios? They are simply finer grained expansions of
> > extremely crude envisionment expressed in a use case.
> > Consider this scenario for UC-ActorViewDocument
> > Before:
> > Actors: user, OHS, Home Page, Desired Document
> > Relations: user sitting at OHS terminal
> > States: OHS 'Home Page' displayed.
> > Actions:
> > In this scenario, the action is a user behavior, not a process
> > firing
> > Actor clicks hyperlink to document.
> > After:
> > Actors: same
> > Relations: same
> > States: Desired Document displayed
> > Why is this interesting? or, why should anyone care about this?
> > Turns out that we now have a shell with which to invent OHS. We can now
> > begin to refine the scenario to include a bunch of rule firings implying
> > behaviors of OHS itself. From that, we get a simulation of OHS in
> > Back to ontologies.
> > Consider this: in the use case arena, there will always be a huge number
> > 'common' use cases, very much like the example above. Once we have all
> > common use cases constructed, we can now begin to layer more specialized
> > cases that imply, or rely on the existence of common use cases. We
> > think of these as 'domain specific' use cases. So, we begin to think of
> > common use cases as the 'roots' of --eventually--a forest of specialized
> > usecases. The common use cases represent the basis for interoperability
> > among the specialty domains.
> > Now, just substitute the term 'ontology' for the term 'use case' and you
> > have the mapping. Bingo. Get the ontology right, and the rest falls out
> > (sm).
> > Summary:
> > I believe that I have outlined the case for:
> > using QP theory as a kind of formalism on which we begin to map out
> > cases and scenarios
> > developing use cases and scenarios, leading to an OHS ontology from
> > which the entirety of OHS can then be developed.
> > What I have not outlined is the need to bring pragmatics and knowledge
> > representation best practices into this picture. For that, film at 11...
> > This message is intended only for the use of the Addressee(s) and may
> > contain information that is PRIVILEGED and CONFIDENTIAL. If you are not
> > the intended recipient, dissemination of this communication is
> > If you have received this communication in error, please erase all
> > of the message and its attachments and notify firstname.lastname@example.org
> > immediately.
> > Community email addresses:
> > Post message: unrev-II@onelist.com
> > Subscribe: unrev-IIemail@example.com
> > Unsubscribe: unrev-IIfirstname.lastname@example.org
> > List owner: unrev-IIemail@example.com
> > Shortcut URL to this page:
> > http://www.onelist.com/community/unrev-II
> Community email addresses:
> Post message: unrev-II@onelist.com
> Subscribe: unrev-IIfirstname.lastname@example.org
> Unsubscribe: unrev-IIemail@example.com
> List owner: unrev-IIfirstname.lastname@example.org
> Shortcut URL to this page:
This message is intended only for the use of the Addressee(s) and may
contain information that is PRIVILEGED and CONFIDENTIAL. If you are not
the intended recipient, dissemination of this communication is prohibited.
If you have received this communication in error, please erase all copies
of the message and its attachments and notify email@example.com
-------------------------- eGroups Sponsor -------------------------~-~>
PLAY GAMES. WIN PRIZES. GUARANTEED.
Get $5 in FREE credits when you register at www.PrizeGames.com.
Play now at
Community email addresses:
Post message: unrev-II@onelist.com
List owner: unrev-IIfirstname.lastname@example.org
Shortcut URL to this page:
This archive was generated by hypermail 2b29 : Thu Dec 14 2000 - 13:39:37 PST