GLOBAL INFORMATION NETWORK ARCHITECTURE

• US 20100070504A1
• Filed: 11/20/2009
• Published: 03/18/2010
• Est. Priority Date: 06/30/2006
• Status: Active Grant

• Current Assignee: Big Kahuna Technologies, LLC
• Original Assignee: XSLENT, LLC
• Inventors: Tinsley, David, Busalacchi, Frank, Bressler, Paul, Skinner, Wesley, Yarbrough, Eric
• Granted Patent: US 8,290,988 B2
• Time in Patent Office: Days
• US Class Current: 707/737
• 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 (GINA) 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. GINA 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. GINA 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 implementing a vector as an object that effects a relationship between a set of information objects of a first type and a set of information objects of a second type according to a description of the relationship, the method comprising the steps of:

describing the relationship, the first type of information object and second type of information object, and a type of the vector,

relating a vector type with information objects defined to implement the vector type,

describing characteristics of the vector to define a functional runtime relationship of the information objects, including properties and methods of the relationship between the information objects to be implemented by the vector, and

creating the vector according to the type of the vector and the characteristics of the vector.

2. The method of claim 1, further comprising the step of returning an information object of the second type when given an information object of the first type.

3. The method of claim 1, wherein the descriptions are expressible as information objects.

4. The method of claim 1, wherein one type of vector is defined by one or more properties that are shared by information object types.

5. The method of claim 1, wherein one type of vector is defined by a transitive composition of a vector from the set of information objects of the first type to a set of information objects of a third type and a vector from the set of information objects of the third type to the set of information objects of the second type.

6. The method of claim 1, wherein one type of vector from the set of information objects of the first type to the set of information objects of the second type is defined by another vector from the set of information objects of the first type to set of information objects of the second type and a constraint on either the instances of the information objects of the first or second types.

7. The method of claim 1, wherein one type of vector from the set of information objects of the first type to the set of information objects of the second type is defined when any property of an information object of the first type shares a value with a corresponding property of any information object of the second type.

8. A method of creating user interfaces that operate in a universal information object management environment, the method comprising the steps of:

defining information objects that represent user-interface objects, and

mapping the user-interface objects to information objects whose data is to be presented in the user interface by a vector representing a relationship from a set of information objects of a first type to a set of information objects of a second type, and

assembling user interfaces per the user-interface objects.

9. The method of claim 8, wherein the information interfaces are collected as by

defining applications as information objects that represent collections of user-interfaces,

defining systems as information objects that represent collections of applications, and

assembling applications and systems per the defined applications and defined systems.

10. A method of describing access a user has to a first information object, the method comprising the steps of:

defining a user as a user information object,

defining a vector between the user and the first information object,

defining a vector between the user and components of the first information object, and

assembling a second information object defined on the first information object by assembling only the components specified by the vector, which in turn act on the components of the first information object.