Database management system

• US 6,976,036 B2
• Filed: 11/06/2001
• Issued: 12/13/2005
• Est. Priority Date: 11/06/2001
• Status: Expired due to Term

• Current Assignee: Leidos, Inc. (Leidos Holdings, Inc.)
• Original Assignee: Science Applications International Corporation
• Inventors: Lau, Yun-Tung, Poon, Peter, Kuchipudi, Kiran, Chipman, Richard
• Primary Examiner(s): Rones, Charles
• Assistant Examiner(s): Veillard, Jacques
• Application Number:
  US09/957,570
• Publication Number:
  US 20030088584A1
• Time in Patent Office: 1,498 Days
• Field of Search: 707 1- 5, 707/8, 707/10, 707/200, 707/100, 707/101, 707/102, 707/103.R, 707/104.1, 704/3, 704/10, 709/315, 709/219, 709/245, 717/137
• US Class Current: 235/462.01
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/949 Inventory
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

The present invention is related to a database management system that is capable of autonomous dynamic ontology management through soft classing. The present invention is further related to a method of database management by dividing attribute data, e.g., price=10 dollars, into class elements containing data, e.g., attribute name=price, type=numeric, default units=dollars, and entry elements containing data, e.g., attribute value=10, to permit dynamic ontology management and evolution in the database through soft classing.

Claims

1. A method for autonomous electronic creation of a database by an ontology database management:

system comprising;

dividing incoming attribute data into a class element comprising data and an entry element comprising data, wherein the class element data comprises an attribute name, the entry element data comprises an attribute value and the attribute value is related to the attribute name;

creating at least one attribute heading with the class element data;

adding the entry element data as at least one entry field under the attribute heading;

after creating at least one attribute heading, dividing subsequent incoming attribute data into a subsequent class element containing data and a subsequent entry element containing data, wherein the subsequent class element data comprises the subsequent attribute name, the subsequent entry element data comprises the subsequent attribute value and the subsequent attribute value is related to the subsequent attribute name;

comparing the subsequent attribute name to the at least one attribute heading already existing in the database;

if the subsequent attribute name is identical to any of the at least one attribute heading already existing, adding the subsequent entry element data under the identical attribute heading;

if the subsequent attribute name is not identical to any of the at least one attribute heading already existing;

in, the database, comparing the subsequent class element data and the subsequent entry element data to existing data in the database to determine whether the subsequent attribute name is the equivalent of the at least one attribute;

heading already existing in the database;

if the subsequent attribute name is the equivalent of the one of the at least one attribute heading, entering the subsequent entry element data under the equivalent attribute heading; and

if the subsequent attribute name is not equivalent to one of the at least one attribute heading, creating a new attribute heading with the subsequent attribute name, discarding the subsequent incoming data, holding collected subsequent incoming data in reserve until a certain number of identical attribute names are obtained then creating a new attribute heading with the subsequent attribute name, prompting for human intervention to determine whether to create a new attribute heading with the subsequent attribute name, or holding collected data in reserve until a certain number of identical attribute names are obtained then prompting for human intervention to determine whether to create a new attribute heading with the subsequent attribute name.

2. The method of claim 1, further including the step of obtaining incoming attribute data by scanning a bar code, traversing web page content, or a combination thereof.

3. The method of claim 1 wherein the ontology database management:

system prompts for human intervention before creating the at least one attribute heading.

4. The method of claim 1 further comprising the step of searching the created database by querying the ontology database management system using attribute names, attribute values, or a combination thereof in the query.

5. A method for dynamically managing the ontology of a database, the method comprising:

dividing incoming attribute data into a class element containing data and an entry element comprising data, wherein the class element data comprises an attribute name, the entry element data comprises;

an attribute value and the attribute value is related to the attribute name;

comparing the attribute name to an at least one attribute heading already existing in the database;

if the attribute name is not identical to any of the at least one attribute heading already existing in the database, comparing the class element data and the entry element data to existing data in the database to determine whether the attribute name is the equivalent of at least one attribute heading already existing in the database;

if the attribute name is the equivalent of one of the at least one attribute heading already existing in the database, entering the entry element data into the database under the equivalent attribute heading; and

if the attribute name is not equivalent to one of the at least one attribute heading, creating a new attribute heading with the attribute name, discarding the incoming attribute data, holding collected incoming attribute data in reserve until a certain number of identical attribute names are obtained then creating a new attribute heading with the attribute name, prompting for human intervention to determine whether to create a new attribute heading with the attribute name, or holding collected data in the reserve until a certain number of identical attribute names are obtained then prompting for human intervention to determine whether to create a new attribute heading with the attribute name.

6. The method of claim 5 further comprising:

if the attribute name is the equivalent of one of the at least one attribute heading, replacing the one of the at least one attribute heading with the attribute name, discarding the attribute name, holding the class element data in reserve until a certain number of same attribute names are obtained then replacing the one of the at least one attribute heading with the attribute name, prompting for human intervention to determine whether to replace the one of the at least one attribute heading with the attribute name, or holding the class element data in reserve until a certain number of same attribute names are obtained then prompting for human intervention to determine whether to replace the one of the at least one attribute heading with the attribute name.

7. A method for autonomous electronic creation of a database by an ontology database management system comprising:

dividing incoming attribute data into a class element comprising data and an entry element comprising data, wherein the class element data comprises an attribute name, the entry element data comprises an attribute value and the attribute value is related to the attribute name;

creating at least one attribute heading with the class element data;

adding the entry element data as at least one entry field under the attribute heading;

after creating at least one attribute heading, dividing subsequent incoming attribute data into a subsequent class element containing data and a subsequent entry element containing data, wherein the subsequent class element data comprises the subsequent attribute name, the subsequent entry element data comprises the subsequent attribute value and the subsequent attribute value;

is related to the subsequent attribute name;

comparing the subsequent attribute name to the at least one-attribute heading already existing in the database;

if the subsequent attribute name is identical to any of the at least one attribute heading already existing adding the subsequent entry element data under the identical attribute heading;

if the subsequent attribute name is not identical to any of the at least one attribute heading already existing in the database, comparing the subsequent class element data and the subsequent entry element data to existing data in the database to determine whether the subsequent attribute name is the equivalent of the at least one attribute;

heading already existing in the database;

if the subsequent attribute name is the equivalent of one of the at least one attribute heading, entering the subsequent entry element data under the equivalent attribute heading; and

if the subsequent attribute name is not equivalent to one of tile at least one attribute heading, creating a new attribute heading with the subsequent attribute name, adding the subsequent entry element data under the new attribute heading.

8. A method for autonomous electronic creation of a database by an ontology database management system comprising:

dividing incoming-attribute data into a class element comprising data and an entry element comprising data, wherein the class element data comprises an attribute name, the entry element data comprises an attribute value and the attribute value is related to the attribute name;

creating at least one attribute heading with the class element data;

adding the entry element data as at least one entry field under the attribute heading;

after creating at least one attribute heading, dividing subsequent incoming attribute data into a subsequent class element containing data and a subsequent entry element containing data, wherein the subsequent class element data comprises the subsequent attribute name, the subsequent entry element data comprises the subsequent attribute value and the subsequent attribute value is related to the subsequent attribute name;

comparing the subsequent attribute name to the at least one attribute heading already existing in the database;

if the subsequent attribute name is identical to any of the at least one attribute heading already existing, adding the subsequent entry element data under the identical attribute heading;

if the subsequent attribute name is not identical to any of the at least one attribute heading already existing;

in the database, comparing the subsequent class element data and the subsequent entry element data to existing data in the database to determine whether the subsequent attribute name is the equivalent of the at least one attribute heading already existing in the database;

if the subsequent attribute name is the equivalent of one of the least one attribute heading, entering the subsequent entry element data under the equivalent attribute heading; and

if the subsequent attribute name is not equivalent to one of the at least one attribute heading, creating a new attribute heading with the subsequent attribute name, holding collected subsequent incoming data in reserve until a certain number of identical attributes names are obtained then creating a new attribute heading with the subsequent attribute name, prompting for human intervention to determine whether to create a new attribute heading with the subsequent attribute name or holding collected data in reserve until a certain number of identical attribute names are obtained then prompting for human intervention to determine whether to create a new attribute heading with the subsequent attribute name.