RE: [unrev-II] Fwd: Fw: Re: [PORT-L] Goguen's Semiotic Morph isms

From: Jack Park (
Date: Tue Apr 03 2001 - 09:19:46 PDT

  • Next message: Dennis E. Hamilton: "RE: [unrev-II] Email based on invitation & introduction"

    TSC spawns a task: fillinNextEpisode on some Episode (in the beginning,
    Rules Fire,each constructing a task: publishNewEpisode
    TSC scans to see if the new episode matches (subset, superset, equal) any
    prior episode in the graph.
             If so, a loop is detected and the "backlink" to prior episode is
    now given to the found episode and the new episode is destroyed.
             If now, backlinking takes place and TSC spawns a new task to
    fillinNextEpisode on the new episode.
    At the same time, TSC also runs a different set of rules -- originally
    called CommonSenseRules (SenseRules for short) which look for stopping
    conditions, clean up other aspects of inferences and so forth.

    SenseRule firing offers the opportunity to do analogical explorations as


    At 05:06 PM 4/3/2001 +0100, you wrote:
    > >When loops are detected, there will be more links to
    >priorEpisode and to mechanism (rule that fired). That's the really big
    >Literally? As in, monitoring this provides the capacity for
    >abstraction/analogical reasoning?
    >Not sure if I made the leap to the big picture(?).
    >-----Original Message-----
    >From: Jack Park
    >Sent: 4/3/01 2:52 PM
    >Subject: RE: [unrev-II] Fwd: Fw: Re: [PORT-L] Goguen's Semiotic Morph
    >TSC was originally written in Forth on a Macintosh. You can read a bit
    >it's history in my paper at
    >which describes the process a bit.
    >Basically, TSC was a frame-based system as you correctly assume here. QP
    >rules are also frames. In fact, in that system everything is
    >as a frame; the system was patterned after Douglas Lenat's program
    >It's agenda based (everything wraps up in tasks). QPT asks that you set
    >some initial conditions (in my parlance, you "set a stage") and then ask
    >rules to fire against those conditions. One or more rules will fire (or
    >else you don't have a match between the universe as described in your
    >rules). Each rule firing creates a new frame, called an Episode, with a
    >link to its predecessor (in time) by a link and a reference is made to
    >rule that fired. When loops are detected, there will be more links to
    >priorEpisode and to mechanism (rule that fired). That's the really big
    >You can then query the Envisionment (graph made by rulefiring) to see
    >happened. You can also use that envisionment to monitor dataflow in some
    >experiment and watch for "expectation failures" which mean the data
    >are not modeled in the envisionment, meaning, a new task is posed to
    >that expectation failure.
    >Will TSC be available? Yup. Not yet, however. It's now jTSC and will
    >a part of the Nexist project at
    >That project is a testbed for an OHS-like system. Here, OHS refers to
    >Open Hyperdocument System about which this list discusses. Source code
    >Nexist is expected to go into the sourceforge CVS sometime this week.
    >At 02:27 PM 4/3/2001 +0100, you wrote:
    > > indeed. especially the mail dating from 1998 about QPT and TSC from
    > >Jack Park that popped up. (awesome.)
    > >
    > >So how are the state transitions defined in TSC? Guessing: it sounds
    >like a
    > >process is an operator on objects, and so can be defined as a something
    > >query + rules over a set of frame properties to create a new object.
    > >you also use that process to determine whether an object has changed in
    > >certain way? Guessing yes again.
    > >
    > >e.g. cow + slaughtering (process) => chunks of beef
    > >
    > >I.e. I know it was slaughtering because the mapping between cow and
    > >of beef matches the slaughtering process operation.
    > >
    > >Is that how TSC works?
    > >
    > >Where can I get a copy of TSC to play with?
    > >
    > >atb,
    > >P

    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

    ------------------------ Yahoo! Groups Sponsor ---------------------~-~>
    Do you have 128-bit SSL encryption server security?
    Get VeriSign's FREE Guide, "Securing Your
    Web Site for Business." Get it now!

    Community email addresses:
      Post message:
      List owner:

    Shortcut URL to this page:

    Your use of Yahoo! Groups is subject to

    This archive was generated by hypermail 2b29 : Tue Apr 03 2001 - 09:31:51 PDT