Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1999-02-19
2001-10-02
Choules, Jack (Department: 2177)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000
Reexamination Certificate
active
06298354
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates generally to computer software and database systems. More particularly, the invention relates to object-oriented databases and computer languages.
2. Description of the Related Art
Database systems are serving increasingly important roles in today's society. Modern database systems enable users to gather, manipulate, and maintain massive amounts of information. A mere handful of examples of the myriad uses of database systems includes computerized library systems, automated teller machines, flight reservation systems, computerized parts inventory systems, and configuration databases for computer systems and networks.
Nevertheless, database systems are often difficult to maintain. Relational databases, for example, though powerful, are often accessible only through complicated, formal queries in languages such as SQL (Structured Query Language). It is expensive to hire or train experts with proficiency in such a highly technical field. Storage is also a problem, as data files in a database can become large and unwieldy, consuming finite storage resources. It is therefore an important consideration that a database system be easy to administer, and that the data be easy to enter, retrieve, edit, and store.
Some database systems are implemented using object-oriented techniques. Object-oriented databases, like the object-oriented programming model, are based on objects: units that combine or encapsulate both data and related methods for operating on that data. Often, objects are related to one another in a class hierarchy which allows related objects to inherit attributes from one another. Object-oriented databases thus provide more accurate modeling of “real-world” entities. However, object-oriented databases are often just as difficult to implement, employ, and maintain as other types of databases. Furthermore, the interdependencies and relationships among objects in an object-oriented database complicate the issue of storage and often result in large, bloated database files which store unnecessary information.
One specific type of database is a database employed by an operating system to maintain configuration information that relates to components of software and/or hardware of a computer system. For example, such a configuration database may store configuration information relating to application programs, hardware devices which are coupled to the computer system, and/or elements of the operating system. These configuration databases may be implemented in many different ways. To exploit the advantages of the object-oriented paradigm, configuration databases may be implemented as object-oriented databases. Unfortunately, these configuration databases, object-oriented or otherwise, are associated with the same difficulties as other types of database systems. For instance, if information in a configuration database is generated dynamically upon the start-up of a computer system, then that information will be lost from session to session unless it is stored in a convenient way.
Therefore, it is desirable to provide an intelligent mechanism and process for storing an object-oriented configuration database.
SUMMARY OF THE INVENTION
The problems outlined above are in large part solved by various embodiments of a method and system for transforming an intermediate form of an object-oriented database into an active object-oriented database in accordance with the present invention. In one embodiment, the intermediate form is derived from a grammatical form of an object-oriented database. A grammatical form, an expression of an object-oriented database in a textual form according to a grammar, may be stored in a persistent form such as one or more files on disk. The grammatical form is human-readable and human-editable. The grammatical form can be created by hand, or it can be created from an object-oriented database in transient form through the process of serialization. The grammar is designed to be platform-independent and programming-language-independent and therefore descriptive of any hierarchical object-oriented database.
In one embodiment, the intermediate form is generated from the grammatical form through the process of compilation. In one embodiment, the intermediate form comprises an array of entry objects as would be found in the object-oriented database. The entry objects are intelligent: they encapsulate data with methods for manipulating that data. The methods include creating a database entry, creating a property associated with an entry, creating an attribute associated with an entry or property, querying the last entry, property, or attribute created, and finalizing entry storage. The intermediate form comprises entries as in the object-oriented database but lacks the infrastructure of the database: for instance, the intermediate form is not accessible by application programs as the database is.
In one embodiment, the intermediate form can be used to populate the object-oriented database with entries. Population takes place through a public API for accessing the object-oriented database; in other words, through interfaces which declare methods for navigating the database and adding entries to the database. In one embodiment, both compilation and database population are initiated when a grammatical form embodied in a Java™ object called a StaticTree is passed to a Java™ object called a StaticTreePopulator.
In various embodiments, the invention further provides a database transformation system and method wherein an active object-oriented database is serialized into a persistent form which is described by a grammar, wherein the persistent, grammatical form is compiled into an intelligent intermediate form, and wherein serialization and compilation may be modified to accept complex data types.
In one embodiment, the object-oriented database is an object-oriented configuration database which stores configuration parameters pertaining to the software and hardware of a computer system, such as application programs, device drivers, system services, and other components. In one embodiment, the object-oriented database is a platform-independent one, such as the Java™ System Database, and is therefore configured to be hosted on several different operating systems and computing platforms. In one embodiment, database transformation according to the present invention is implemented as a package of classes and interfaces in the object-oriented Java™ Language.
REFERENCES:
patent: 5551029 (1996-08-01), Jagadish et al.
patent: 5694598 (1997-12-01), Durand
patent: 5758154 (1998-05-01), Qureshi
patent: 6182082 (2001-01-01), Tanaka et al.
patent: 0 631 229 (1994-12-01), None
Tennent,Principles of Programming Languages, Prentice Hall 1981, pp. 9-33.
Majka, “Getting Acquainted with NetInfo,”Nextstep In Focus, Summer 1993, vol. 3, Issue 3, copyright NeXT Computer, Inc. 1993.
Saulpaugh Thomas E.
Slaughter Gregory L.
Traversat Bernard A.
Choules Jack
Conley Rose & Tayon PC
Kivlin B. Noäl
Lewis Cheryl
Sun Microsystems Inc.
LandOfFree
Mechanism and process to transform a grammar-derived... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Mechanism and process to transform a grammar-derived..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Mechanism and process to transform a grammar-derived... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2562598