Knowledge information management toolkit and method

• US 7,092,958 B2
• Filed: 01/29/2003
• Issued: 08/15/2006
• Est. Priority Date: 01/29/2003
• Status: Expired due to Fees

• Current Assignee: Battelle Energy Alliance LLC (Battelle Memorial Institute)
• Original Assignee: Battelle Energy Alliance LLC (Battelle Memorial Institute)
• Inventors: Brown, Kenneth L., Hempstead, Antoinette R.
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US10/354,328
• Publication Number:
  US 20040148304A1
• Time in Patent Office: 1,294 Days
• Field of Search: 707/1, 707/5, 707/10, 707/200, 707/203, 707/101, 707/102, 704/270, 704/275, 715/513, 719/316
• US Class Current: 706/50
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A system is provided for managing user entry and/or modification of knowledge information into a knowledge base file having an integrator support component and a data source access support component. The system includes processing circuitry, memory, a user interface, and a knowledge base toolkit. The memory communicates with the processing circuitry and is configured to store at least one knowledge base. The user interface communicates with the processing circuitry and is configured for user entry and/or modification of knowledge pieces within a knowledge base. The knowledge base toolkit is configured for converting knowledge in at least one knowledge base from a first knowledge base form into a second knowledge base form. A method is also provided.

Claims

1. A system for managing user entry/modification of knowledge information into a knowledge base file having an integrator support component and a data source access support component, comprising:

processing circuitry;

memory communicating with the processing circuitry and configured to store at least one knowledge base comprising a data source access knowledge base;

a user interface communicating with the processing circuitry and configured for user entry/modification of knowledge pieces within a knowledge base; and

a knowledge base toolkit that takes information entered by a user via the user interface, translates the information into a very small interpreter (VSI) language, and stores the VSI translated information within an object definition language (ODL) knowledge base, the knowledge base toolkit enables a user via the user interface to define a range of simple to complex virtual attributes, wherein virtual attributes comprise attributes that do not reside in the data source, but are derived from literals, other real attributes, or a combination of literals or other real attributes.

2. The system of claim 1 wherein the at least one knowledge base comprises an integrator knowledge base.

3. The system of claim 2 wherein the integrator knowledge base comprises object model information that defines objects in an integrated view for presentation to a client application.

4. The system of claim 3 wherein the knowledge base toolkit receives information entered by a user via the user interface, translates the information into an object definition language (ODL) syntax for the integrator knowledge base, and stores the ODL syntax in a respective flat file.

5. The system of claim 2 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into C language integrated production system (CLIPS) rules for the integrator knowledge base, and stores the CLIPS rules in a respective flat file format.

6. The system of claim 2 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into a configuration syntax for the integrator knowledge base, and stores the configuration syntax in a respective flat file format.

7. The system of claim 2 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into a Common Object Request Broker Architecture (CORBA) syntax for the integrator knowledge base, and stores the CORBA syntax in a respective flat file.

8. The system of claim 1 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into a configuration syntax for the data source access knowledge base, and stores the configuration syntax in a respective flat file format.

9. The system of claim 1 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into a Common Object Request Broker Architecture (CORBA) syntax for the data source access knowledge base, and stores the CORBA syntax in a respective flat file.

10. The system of claim 1 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into a database registration syntax for the data source access knowledge base, and stores the database registration syntax in a respective flat file format.

11. The system of claim 1 wherein the knowledge base toolkit takes information entered by a user via the user interface, translates the information into an object definition language (ODL) syntax for the data source access knowledge base, and stores the ODL syntax in a respective flat file.

12. The system of claim 1 wherein the knowledge base toolkit enables a user via the user interface to translate an object model from an associated data source access component into a form having a specific syntax that is recognized by the integrator support component.

13. The system of claim 12 wherein the knowledge base toolkit has a domain translation capability that stores the domain translation syntax in a respective flat file.

14. A method for translating knowledge information into a knowledge base having an integrator component and a data source access component, comprising:

providing processing circuitry, memory communicating with the processing circuitry and configured to store at least one knowledge base comprising a data source access knowledge base, and a knowledge base toolkit for generating code into a desired knowledge base format having a desired syntax from a source of knowledge information;

receiving user input at the knowledge base toolkit via an interface comprising at least one of user entry of knowledge information and user modification of knowledge information; and

with the knowledge base toolkit, converting the user input knowledge information from a first knowledge base format into a second knowledge base format having a second syntax that is compatible with a desired data integration distributed application suite;

converting the user input knowledge information comprises translating the information into a very small interpreter (VSI) language and storing the very small interpreter (VSI) translated information within an object definition language (ODL) knowledge base; and

via the interface, defining a range of simple to complex virtual attributes the virtual attributes comprising attributes that do not reside in a data source, but are derived from literals, other real attributes, or a combination of literals or other real attributes.

15. The method of claim 14 wherein receiving user input comprises providing a user interface communicating with processing circuitry and memory for storing at least one knowledge base and entering knowledge pieces within a knowledge base of the at least one knowledge base.

16. The method of claim 14 wherein receiving user input comprises providing a user interface communicating with processing circuitry and memory for storing at least one knowledge base and modifying knowledge pieces within a knowledge base of the at least one knowledge base.

17. The method of claim 14 wherein receiving user input comprises a user entering knowledge information via the interface.

18. The method of claim 14 wherein receiving user input comprises a user modifying knowledge information via the interface.

19. The method of claim 14 further comprising reading the user input knowledge information from memory, before converting the user input knowledge information.

20. The method of claim 14 wherein the knowledge base comprises an integrator knowledge base.

21. The method of claim 20 wherein the integrator knowledge base comprises object model information and further comprising defining objects in an integrated view.

22. The method of claim 21 wherein converting the user input knowledge information comprises translating the user input knowledge information into the second knowledge base format in an object definition language (ODL) syntax, and further comprising storing the ODL syntax in a respective flat file.

23. The method of claim 20 wherein converting the user input knowledge information comprises translating the information into a configuration syntax for the integrator knowledge base, and further comprising storing the configuration syntax in a respective flat file format.

24. The method of claim 20 wherein converting the user input knowledge information comprises translating the information into a Common Object Request Broker Architecture (CORBA) syntax for the integrator knowledge base, and further comprising storing the CORBA syntax in a respective flat file format.

25. The method of claim 14 wherein converting the user input knowledge information comprises translating the information into a configuration syntax for the data source access knowledge base, and further comprising storing the configuration syntax in a respective flat file format.

26. The method of claim 14 wherein converting the user input knowledge information comprises translating the information into a Common Object Request Broker Architecture (CORBA) syntax for the data source access knowledge base, and further comprising storing the CORBA syntax in a respective flat file format.

27. The method of claim 14 wherein converting the user input knowledge information comprises translating the information into a database registration syntax for the data source access knowledge base, and further comprising storing the database registration syntax in a respective flat file format.

28. The method of claim 14 wherein converting the user input knowledge information comprises translating the information into an object definition language (ODL) syntax for the data source access knowledge base and storing the object definition language (ODL) syntax in a respective flat file.