This is an old revision of the document!
APIs for persistent storage [[start|Link to API4KB Main Page]] * Could be source text * RDF * OWL * ?? * Could be a triple store or other repository * Open * Read * Write * Close * Need to be able to retract facts * Housekeeping * Truth maintenance (may depend on the reasoner) * Explanation support, at least through the interface mechanism ===== Questions ===== * Need to determine how to address incremental changes to knowledge bases (both in memory and persistent) -- do we take a typical RDBMS approach, whereby a complete transaction must be handled by the DB, or a network perspective? * Need to understand how current KBs implement this, including Clark & Parsia for Pellet, Franz for Allegrograph, Revelytix for Mulgara, etc. * Is a given change a standalone modification or part of a group/set of changes? * To take change management seriously, we would have to go far beyond typical RDBMS changes, including branching, etc. * At a minimum, we would have to be able to expose whatever capability a given back-end has for supporting change management
