OKBC, A Rich API on the Cheap

From Tetherless World Wiki

Jump to: navigation, search

Citation: J. P. Rice. (1998) OKBC, A Rich API on the Cheap. In KSL-98-29, April,1998.

Publication techreport ( Edit )
type Technical Report
bibtype techreport
Bibtex basics
author J. P. Rice
title OKBC, A Rich API on the Cheap
number KSL-98-29
institution Knowledge Systems, AI Laboratory
address Palo Alto, CA
year 1998
month April
Bibtex more
Access Paper
abstract The development of sophisticated knowledge bases and knowledge-based applications has traditionally been hampered by the idiosyncratic implementation of both the knowledge in these systems and the representation systems in which they are implemented. The lack of standards and the desire of each implementor to exploit different technologies has made it very difficult to leverage existing knowledge bases or existing tools, since these tools have traditionally been very tightly bound to a single representation system. Because representation systems differ in significant and interesting ways, it seems unlikely that we will ever be able to have a grand unified representation system that will ensure portability. Nevertheless we would like to avoid the terrible costs associated with reinventing tools and representation systems, just as we would like to be able to reuse existing knowledge bases. The desire for reuse becomes especially strong as our knowledge bases grow and we would like to extract the data-rich, though often ontologically impoverished, OKBC (Open Knowledge Base Connectivity) is an API (Applications Programming Interface) (Chaudhri et al. 1998) specifically designed to allow developers to access knowledge content in a wide variety of systems, and to allow application developers to develop sophisticated, portable and reusable applications. However, in order for OKBC to be successful, it must rely on bindings for OKBC being provided for a large number of content providers as well as relying on the API being simple, powerful and convenient enough for application developers to see a pay-off in using it. The desire to provide a powerful and flexible API is clearly incompatible with the desire to make it easy to provide bindings for systems. In this paper we show how OKBC has been designed specifically to overcome this

KSL Technical Report ID: KSL-98-29
Facts about OKBC, A Rich API on the CheapRDF feed
Abstract The development of sophisticated knowledg … The development of sophisticated knowledge bases and knowledge-based applications has traditionally been hampered by the idiosyncratic implementation of both the knowledge in these systems and the representation systems in which they are implemented. The lack of standards and the desire of each implementor to exploit different technologies has made it very difficult to leverage existing knowledge bases or existing tools, since these tools have traditionally been very tightly bound to a single representation system. Because representation systems differ in significant and interesting ways, it seems unlikely that we will ever be able to have a grand unified representation system that will ensure portability. Nevertheless we would like to avoid the terrible costs associated with reinventing tools and representation systems, just as we would like to be able to reuse existing knowledge bases. The desire for reuse becomes especially strong as our knowledge bases grow and we would like to extract the data-rich, though often ontologically impoverished, OKBC (Open Knowledge Base Connectivity) is an API (Applications Programming Interface) (Chaudhri et al. 1998) specifically designed to allow developers to access knowledge content in a wide variety of systems, and to allow application developers to develop sophisticated, portable and reusable applications. However, in order for OKBC to be successful, it must rely on bindings for OKBC being provided for a large number of content providers as well as relying on the API being simple, powerful and convenient enough for application developers to see a pay-off in using it. The desire to provide a powerful and flexible API is clearly incompatible with the desire to make it easy to provide bindings for systems. In this paper we show how OKBC has been designed specifically to overcome this een designed specifically to overcome this
Address Palo Alto, CA  +
Author J. P. Rice  +
Bibtype techreport  +
Has author J. P. Rice  +
Has identifier KSL-98-29  +
Has publishing details April,1998  +
Has title OKBC, A Rich API on the Cheap  +
Has where published KSL-98-29  +
Has year 1998  +
Institution Knowledge Systems, AI Laboratory  +
Ksl tr id KSL-98-29  +
Month April  +
Number KSL-98-29  +
Process note NO  +
Title OKBC, A Rich API on the Cheap  +
Year 1998  +
Retrieved from "http://tw.rpi.edu/wiki/OKBC%2C_A_Rich_API_on_the_Cheap"
Personal tools