Global information architecture

• US 7,647,337 B2
• Filed: 06/30/2006
• Issued: 01/12/2010
• Est. Priority Date: 06/30/2006
• Status: Active Grant

• Current Assignee: Big Kahuna Technologies, LLC
• Original Assignee: XSLENT, LLC
• Inventors: Bressler, Paul, Skinner, Wesley, Yarbrough, Eric, Tinsley, David, Busalacchi, Frank
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Casanova; Jorge A
• Application Number:
  US11/428,202
• Publication Number:
  US 20080005169A1
• Time in Patent Office: 1,292 Days
• Field of Search: 707/102, 707/103.R, 707/104.1, 717/124, 717/137
• US Class Current: 707/792
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level

Abstract

The present invention provides a Global Information Architecture (GIA) to create an object-oriented, software-based modeling environment for the modeling of various data sources and allowing queries and transactions across those sources. The modeling environment is described in itself. Introspection is achieved since the model is described in the model, and early validation that the infrastructure is correct is established in that the infrastructure must execute against itself. Object traversal is done via vectors that describe how an object can be reached from other objects. Objects are linked by describing what type of object (data source) is to be reached and on the basis of what possible attribute values of that object. GIA allows different users to have different views of these data sources depending upon their WorldSpace. A user'"'"'s view of the data source is controlled by his WorldSpace, which are the attributes he has that makes him unique. These attributes can include (among others) his username, roles, language, locale, and organization. These WorldSpace views can also impact the behavior of the data sources. GIA allows for object to object event driven behavior and provides a configuration centric versus coding centric methodology for integrating those various data sources.

Claims

1. A method for creating universal information object management environment as an executable environment description, the method comprising the steps of:

creating descriptions of information sources, associated information objects, object characteristics, and relationships among the information sources, information objects, and object characteristics, where the descriptions are fully functionally described by the descriptions of the information sources, associated information objects, object characteristics, and their relationships;

creating universal components that represent information objects, types of sources, types of characteristics, and types of relationships, which collectively represent the services and behavior of the environment, whose configurations are defined by associated descriptions, including descriptions of associated information objects, object characteristics, and their relationships; and

assembling at runtime instances of information objects defined on information sources by collecting universal components with associated objects, object characteristics, and relationships that represent their behavior and configuration within the network of their described relationships.

2. The method of claim 1, wherein the object characteristics include the types of service, property, event, and relationship.

3. The method of claim 1, further comprising the step of the information objects implementing a common interface, wherein the common interface allows access to instances of information objects by name or position, and allows display of a current instance of the information object.

4. The method of claim 3, further comprising the steps of:

describing an infuriation source as a combination of network access type, message structure, and source characteristics;

creating components that represent the different types of network-accessible sources, message structures, and characteristics and that collectively expose the common information object interface; and

assembling the types of named components related to the descriptions to create an information source with the desired behavior.

5. The method of claim 1, further comprising the step of accessing another instance of a universal information object management environment as collections of information sources.

6. The method of claim 5, further comprising the steps of:

defining a mapping of syntax of a first universal information object management environment to syntax of a second universal information object management environment by describing the vectors that related the syntax of the first environment to that of the second environment,

accessing the universal information object management environment in response to requests made by the non-conforming universal information object management environment.

7. A method for creating wrapper objects that expose and implement an information object interface, the method comprising the steps of:

specifying an information object by a description of the information object, which identifies a type of the information object and named components of the information object, including defining the named components of the information object and types of the named components,

associating an object method of the information object with a collection of named component objects each having defined name components, the object method of the information object to provide a plurality of object characteristics of a particular defined type, the named component objects each have an object method that provides a desired behavior as an implementation of the associated object method, and

executing the associated object method on a component object in the collection of named component objects that has a same name as a name referred to by the object method to provide the desired behavior when the object method for a plurality of object characteristics of a particular type of an information object is invoked.

8. The method of claim 7, further comprising the steps of:

relating the information object type to the component objects as wrapper objects,

creating the wrapper objects per the information object type,

relating the types of named components to component objects that perform the desired behavior, to make the desired behavior invocable via the name of the related named component,

creating component objects per the component types that implement the behavior, and

collecting the created component objects within the wrapper object.

9. The method of claim 8, wherein the named components include at least one property, at least one service, and at least one relationship.

10. The method of claim 9, further comprising the steps of:

acting on at least one event,

defining an association between the at least one event and the at least one service, and

executing the association when the event is raised.

11. The method of claim 8, wherein the component definitions include information descriptions required for executing the desired behavior.

12. The method of claim 8, further comprising the steps of:

defining a service reflexively as another information object including definitions of component services as component information objects, which are implemented by invoking the component services in response to an invocation of the information object.