MKE + TAP

I continued working on the MKR language 
interface today, and I'm really pleased 
with it now.
Note that the shell scripts GetData,
GetResource, PutData provide an RDF language
interface which can be used without MKE.

1. The pipe interface between MKE and the TAP
   Java client seems really solid
2. Output is minimal for easy readability.
   No more "count =" except when it's zero.
   All "extra" labels are comments, i.e.,
   they begin with "#".
3. The shell script GetData "speaks RDF", using
   the same arguments as your GetData() method.
   For example

        GetData Person subClassOf yes

   generates the subClasses of Person.
   Output can be piped into other programs.
   GetData output is generated directly from the
   Java program.  It is sorted by the enclosing
   shell script.
4. The results (internal to MKE) are saved in
   the "dval" list just like kbmode=mkr results.  
   At the user level, the list is stored in the
   "Question" variable, and can be assigned, e.g.
        
        x := ? has name = Jordan;

5. The MKE/TAP interface is invoked simply by

        set kbmode = tap;

   For minimal output, you also want to 

        set echo = off;

6. TAP Knowledge base is specified by environment 
   variable KBDATA.  It defaults to

        http://tap.stanford.edu/data/

7. The shell script GetResource "speaks RDF"
   with the same arguments as your
   GetResourcesNamed() method.  For example

        GetResource Athlete Jordan

   generates all Athletes named Jordan.
8. Last, but not least, the assertion function.
   Statements are recorded in a local RDF file
   which is specified by environment variable
   KBFILE.  It defaults to

        "$KEHOME/data/tap.rdf"

   The shell script PutData "speaks RDF", with 
   the same arguments as your PutData() method.
   For example

        PutData Athlete subClassOf Person


Dick McCullough
knowledge := man do identify od existent done;
knowledge haspart proposition list;