Browse Prior Art Database

Three Form Editing

IP.com Disclosure Number: IPCOM000037821D
Original Publication Date: 1989-Jul-01
Included in the Prior Art Database: 2005-Jan-30
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Crehan, DT: AUTHOR

Abstract

This article describes a knowledge base object editing interface that obviates the need to develop a new editor in an expert system tool.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Three Form Editing

This article describes a knowledge base object editing interface that obviates the need to develop a new editor in an expert system tool.

Knowledge Bases are comprised of isolated knowledge objects (e.g., rules, sources). Each object is a collection of attributes. For example, a rule might have attributes: trace, author, rule_text, cost, priority, etc. An 'object editor' is needed to edit such objects. It simply presents all the attributes of an object in a window and allows their individual attributes to be edited. Each of the attributes are by their nature of one of three edit types: multiple choice, one line fill-in, or multiple line fill-in.

An attribute such as 'trace', which has a defined set of possible values (on, off), is edited by presenting a multiple choice menu. The user picks one and that value becomes the current value of that attribute and appears in the edit window.

An attribute such as 'author', which can always be specified in one line, is edited by having a one line prompt appear on the screen. The user keys in the value (overkeying the previous value) and hits 'enter' and the value is replaced in the edit window.

An attribute such as 'rule_text', which can usually extend to multiple lines, is edited by copying the entire multiple line value into a file and invoking the underlying system editor to show it in a new separate window, where it is edited with the commands of that editor.

Disclosed anonymously.

1