Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1999-02-19
2001-09-04
Choules, Jack (Department: 2177)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000
Reexamination Certificate
active
06286010
ABSTRACT:
TECHNICAL FIELD
The present invention relates generally to managing and updating distributed directories; and will specifically be disclosed as methods and apparatuses for interaction between schemata in distributed directories.
BACKGROUND OF THE INVENTION
The virtual explosion of technical advances in microelectronics, digital computers and software have changed the face of modern society. In fact, these technological advances have become so important and pervasive that this explosion is sometimes referred to as “the information revolution.” Through telephone lines, networks, satellite communications and the like, information and resources are ever increasingly being accessed and shared.
When a group of computers are connected to one another, such as in a client/server network, a management service is typically used to organize and administer information and resources across the network. Management services usually access or include a database having a collection of objects that represent a variety of things. For instance, some typical objects represent users, groups, printers, computers, and the like. Objects in a management service are often organized in flat domains such as the SECURITY ACCOUNTS MANAGER (“SAM”) of WINDOWS NT, in a distributed directory such as NOVELL DIRECTORY SERVICES (“NDS”), or in other ways known in the art. Each management service object has at least one associated attribute with one or more associated values. Generally, each attribute has an attribute syntax such that the value associated with the attribute is of a data type corresponding to the attribute syntax. For example, integer values are associated with integer attributes.
Typically, each object is of a particular type and is created from a corresponding class. For example, a User object would be created from a User class, a Printer object would be created from a Printer class, etc. The object classes provide a kind of template to define the various attributes that will be associated with the objects. Building on the prior example, an object created from the User class could have the following attributes: Given Name, Last Name, Title, telephone Number, etc. When an object is created from a class, values are filled into the various attributes of the class, thereby creating an instance of the class. For example, a User object could have the value “Owen” associated with the attribute Given Name.
Typically, the structure of the distributed directory is governed by a schema. The schema defines the rules for adding and managing objects and attributes of objects in the distributed directory. These rules are specified through a data dictionary that provides a standard set of data types or classes from which objects can be created. Each object in the distributed directory belongs to an object class that specifies which attributes are associated with the object. Generally, the schema is extensible so that it may be tailored to modify existing classes or add new classes.
The schema controls not only the structure of the individual objects, but also the relationship among the objects in the distributed directory. In controlling this relationship, the schema specifies subordination among object classes. That is, for every object there is a group of object classes from which subordinate objects can be formed. Objects that can contain other objects are called container objects, which are building blocks of the distributive directory. Objects that cannot contain other objects are known as non-container or leaf objects.
With the growing use of the Internet, there is a need for directories on the Internet to provide support for schema independence. Schema independence means support for storage and retrieval of the desired information in the directory in the way that the user/owner wants to store or retrieve it. For example, one schema may store telephone numbers under the object phone_number and another schema as telephone_number or contact_number. When the first directory wants to access and retrieve the phone_number from the second directory nothing will be returned as the directories are unaware that each directory has named the same information a different name. Therefore, there is a need for adaptive schema supported directories.
SUMMARY OF THE INVENTION
Accordingly, an object of the invention is to provide a method and apparatus for interaction between schemata.
A further object of the invention is to provide an improved data structure for representing objects.
Additional objectives, advantages and novel features of the invention will be set forth in the description that follows and, in part, will become apparent to those skilled in the art upon examining or practicing the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed in the appended claims.
One aspect of the present invention is an object oriented directory for use with a computer network. The object oriented directory has a schema which has a first and second class. An object is instantiated from the first class and another object is instantiated from the second class. A reference is associated with the object from the first class of the schema of one directory with an object from a first class of another schema in a second directory. The reference further relates the objects of the first directory to the objects of the second directory.
Another aspect of the present invention is a method for interacting between a first directory having a first schema and a second directory having a second schema. A first object is instantiated from a first class of a first schema from a first directory. Another object is instantiated from a first class of a second schema from a second directory. The second schema is distinct from the first schema. Equivalence of the objects is determined. The objects are associated to each other if they are determined to be equivalent.
A further aspect of the present invention is the enhancing/associating of the individual schemata of the distributive directories if the objects are equivalent. The first class of the first schema from the first directory is copied to the reference of the first class of the second schema from the second directory. Likewise, the reference of the first class of the second schema from the second directory is copied to the reference of the first class of the first schema from the first directory.
Another further aspect of the present invention is the further enhancing/associating of the individual schema of the distributive directories if the objects are equivalent. The second class of the first schema from the first directory is copied to the second class of the second schema from the second directory. Likewise, the second class of the second schema from the second directory is copied to the second class of the first schema from the first directory.
Yet another aspect of the present invention is a method for determining structural equivalence of the objects. A first comparison class is instantiated from a second class of the first schema from the first directory. This first comparison class contains attributes of the first object of the first directory. A second comparison class is instantiated from a second class of the second schema from the second directory. This second comparison class contains attributes of the first object of the second directory. Structural equivalence of the comparison classes is determined by comparison of the first comparison class with the second comparison class. A structural equivalence match is obtained when greater than a specified percent (configurable by client and/or server) of the attributes of the first comparison class match the attributes of the second comparison class. Another method for structural equivalence can be determined by comparison of the attribute type or syntax of the associated object. If a structural match has been obtained, the objects from the second class of the schemata are associated with each other.
Still other aspects of the present inven
Devi Kompella Anasuya
Modi Vipul Arunkant
Ramachandran Lakshmi
Srivastava Anurag
Choules Jack
Dinsmore & Shohl LLP
Lewis Cheryl
Novell Inc.
LandOfFree
Methods and apparatuses for interaction between schemata does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Methods and apparatuses for interaction between schemata, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Methods and apparatuses for interaction between schemata will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2544692