Writing an OKBC Application--A Case Study
From Tetherless World Wiki
Citation: James Rice. (1998) Writing an OKBC Application--A Case Study. In KSL-98-15, May,1998.
| Publication techreport ( Edit ) | |
| type | Technical Report |
| bibtype | techreport |
| Bibtex basics | |
| author | James Rice |
| title | Writing an OKBC Application--A Case Study |
| number | KSL-98-15 |
| institution | Knowledge Systems, AI Laboratory |
| year | 1998 |
| month | May |
| Bibtex more | |
| Access Paper | |
| abstract | Open Knowledge-Base Connectivity (OKBC) is an API that allows knowledge applications to talk to servers with knowledge content.The API has client implementations in Java, Lisp and C, and server implementations in both Java and Lisp. The OKBC specification contains a specification for what is called the"Front End API", that is, the API used to write applications, as opposed to the API used to establish bindings between OKBC and the knowledge content on a Knowledge Representation System (KRS). The OKBC specification is a thorough and formal document, and although it gives a clear definition of the front end API, in practice it gives the reader no clues about how to set about writing an OKB Capplication. In this paper we show a simple, but non-trivial OKBC application developed in multiple languages - a Knowledge Base (KB)summarizing tool, which given an arbitrary OKBC KB will generate a page of HTML showing the contents of that KB. We develop this application in four different ways to show different aspects of OKBC application authoring, and how an application can be progressively optimized. here. |
| KSL Technical Report ID: KSL-98-15 |
Facts about Writing an OKBC Application--A Case StudyRDF feed
| Abstract | Open Knowledge-Base Connectivity (OKBC) is … Open Knowledge-Base Connectivity (OKBC) is an API that allows knowledge applications to talk to servers with knowledge content.The API has client implementations in Java, Lisp and C, and server implementations in both Java and Lisp. The OKBC specification contains a specification for what is called the"Front End API", that is, the API used to write applications, as opposed to the API used to establish bindings between OKBC and the knowledge content on a Knowledge Representation System (KRS). The OKBC specification is a thorough and formal document, and although it gives a clear definition of the front end API, in practice it gives the reader no clues about how to set about writing an OKB Capplication. In this paper we show a simple, but non-trivial OKBC application developed in multiple languages - a Knowledge Base (KB)summarizing tool, which given an arbitrary OKBC KB will generate a page of HTML showing the contents of that KB. We develop this application in four different ways to show different aspects of OKBC application authoring, and how an application can be progressively optimized. here. tion can be progressively optimized. here. |
| Author | James Rice + |
| Bibtype | techreport + |
| Has author | James Rice + |
| Has identifier | KSL-98-15 + |
| Has publishing details | May,1998 + |
| Has title | Writing an OKBC Application--A Case Study + |
| Has where published | KSL-98-15 + |
| Has year | 1998 + |
| Institution | Knowledge Systems, AI Laboratory + |
| Ksl tr id | KSL-98-15 + |
| Month | May + |
| Number | KSL-98-15 + |
| Process note | NO + |
| Title | Writing an OKBC Application--A Case Study + |
| Year | 1998 + |
Resource > Thing > Entity > Document > Scientific Document > Publication
Resource > Thing > Entity > Document > Scientific Document > Publication > Technical Report
Resource > Thing > Entity > Document > Scientific Document > Publication > Technical Report > KSL Technical Report
