Data pool architecture, system, and method for intelligent object data in heterogeneous data environments
First Claim
1. An Intelligent Object Pool for an information technology platform and Intelligent Object data architecture, said Intelligent Object Pool comprising processing components, interfaces, and their comprised structures, definitions, algorithms and methods for a. bi-directional information interchange between core architectural elements of the platform;
- including at least one or some combination of an external Intelligent Object Handler;
comprised Intelligent Objects; and
comprised iPool data subsets;
said information interchange enabled by access interfaces interacting with other access interfaces and/or components, as well as various modules and plug-ins; and
b. bi-directional information interchange between components and access interfaces, such as between a comprised result aggregation engine component, a comprised result aggregation engine interface;
an external master query interface, and an external status management component;
i. said information interchange taking place in automated;
event-driven;
interactive; and
/or user-directed methods for activation and implementation of comprised methods for c. defining and managing Intelligent Object boundaries and access;
d. processing of result aggregation; and
e. storage, processing and management of i. Intelligent Objects, said Intelligent Objects comprising such as vectorized pointers to accessible data content;
meta-data; and
data-enabling methods and processes;
as well as of ii. data pool or “
Pool”
contents, comprising the entity of potentially accessible Intelligent Objects and their data content.
5 Assignments
0 Petitions
Accused Products
Abstract
Data pool architecture, system, method and computer program product, for intelligent object data in heterogeneous data environments. Applications include life sciences, biotechnology, therapeutic diagnostics and intervention, pharmaceuticals, and bioinformatics. Intelligent object data structure.. Intelligent molecular objects (IMO) and data structure include procedural and non-procedural components where non-procedural component has features in common with conventional data and procedural component couples additional information with data and adds functionality and capabilities to system or method utilizing it. Applications handling system, architecture, and framework referred to as the intelligent object handler (IOH). Intelligent object pools (IOP) which comprise a second database structure in addition to the afore described IMO data structure.
324 Citations
193 Claims
-
1. An Intelligent Object Pool for an information technology platform and Intelligent Object data architecture, said Intelligent Object Pool comprising processing components, interfaces, and their comprised structures, definitions, algorithms and methods for
a. bi-directional information interchange between core architectural elements of the platform; - including at least one or some combination of an external Intelligent Object Handler;
comprised Intelligent Objects; and
comprised iPool data subsets;
said information interchange enabled by access interfaces interacting with other access interfaces and/or components, as well as various modules and plug-ins; and
b. bi-directional information interchange between components and access interfaces, such as between a comprised result aggregation engine component, a comprised result aggregation engine interface;
an external master query interface, and an external status management component;
i. said information interchange taking place in automated;
event-driven;
interactive; and
/or user-directed methods for activation and implementation of comprised methods forc. defining and managing Intelligent Object boundaries and access;
d. processing of result aggregation; and
e. storage, processing and management of i. Intelligent Objects, said Intelligent Objects comprising such as vectorized pointers to accessible data content;
meta-data; and
data-enabling methods and processes;
as well as ofii. data pool or “
Pool”
contents, comprising the entity of potentially accessible Intelligent Objects and their data content. - View Dependent Claims (2, 3, 4)
- including at least one or some combination of an external Intelligent Object Handler;
-
5. An object pool for an information technology platform and data object data architecture, said object pool comprising processing components, interfaces, and their comprised structures, definitions, algorithms and methods for
a. bi-directional information interchange between core architectural elements of the platform; - including at least one or some combination of an external data object Handler;
comprised data objects; and
comprised subsets of data objects;
said information interchange enabled by comprised modules, plug-ins, access interfaces and/or components;
b. bi-directional information interchange between components and access interfaces, such as between a comprised result aggregation engine component, a comprised result aggregation engine interface;
an external master query interface, and an external status management component;
c. provision of automated;
event-driven;
interactive; and
/or user-directed methods for activation and implementation of comprised methods for;
i. management and processing of data object boundaries and access;
ii. processing of result aggregation; and
iii. storage, processing and management of 1. data objects, said data objects comprising such as vectorized pointers to accessible data content;
meta-data; and
data-enabling methods and processes;
as well as of2. data pool contents, comprising the entity of potentially accessible data objects and their data content. - View Dependent Claims (6, 7, 8)
- including at least one or some combination of an external data object Handler;
-
9. A set of pool boundary protocols for provision of data security, exchange and integrity, comprising components and access interfaces providing methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of comprised Intelligent Objects, Pool, iPools and an external Intelligent Object Handler; b. defining boundaries for access, security and authentication. - View Dependent Claims (10, 11, 12)
-
13. A set of meta-data index definitions to enable definition and linking of multiple dimensions of data annotation and attributes, to provide analytical functionality and to improve query and analytical efficiency, comprising components and access interfaces providing methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of comprised Intelligent Objects, Pool, iPools and an external Intelligent Object Handler; -
b. providing linking of meta-data index definitions;
c. providing meta-data index-based optimization of queries and processing. - View Dependent Claims (14, 15, 16, 17)
-
-
18. A set of pool content access definitions, comprising components and access interfaces which provide a variety of automated and/or user-directed methods for Pool and iPool accessing and processing, such as for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of comprised Intelligent Objects, Pool, iPools and an external Intelligent Object Handler; - and
b. aggregating results of queries and/or analytical processes applied to batches or sets of Intelligent Object data. - View Dependent Claims (19, 20, 21, 22, 23)
- and
-
24. An iPool security authentication component (iPSA) for provision and implementation of Intelligent Object, Pool and iPool security definitions, authentication and access permissions, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the unified presentation layer; - iPool security authentication interface; and
pool boundary protocol components;
b. definition of access permissions;
c. implementation of criteria for permission or denial of specific access, routing and processing activities;
including at least one or some combination of permission or denial to access and/or route any Intelligent Object data content or property information; and
d. authentication and permission or denial of data access requests according to correspondence of user login information to user definition and administration permissions provided by such as an external Intelligent Object Handler;
iPool access permissions; and
Intelligent Object access permissions. - View Dependent Claims (25, 26, 28, 29)
- iPool security authentication interface; and
-
30. An iPool security authentication interface (iPSAi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool security authentication component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool security authentication; and
c. provision of iPool security authentication component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (31, 32, 33, 34, 35)
- Intelligent Object Pool access interfaces;
-
36. An iPool availability monitoring component (iPAM) for provision and implementation of availability, access and addressing information, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - iPool availability monitoring interface; and
pool boundary protocol components; and
b. availability monitoring for iPool data content availability. - View Dependent Claims (37, 38, 39, 40)
- iPool availability monitoring interface; and
-
41. An iPool availability monitoring interface (iPAMi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool availability monitoring component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool availability monitoring; and
c. provision of iPool availability monitoring component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (42, 43, 44, 45, 46)
- Intelligent Object Pool access interfaces;
-
47. An iPool exchange protocol component (iPEP), for data ownership and data exchange definition and management, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - iPool exchange protocol interface; and
pool boundary protocol components;
b. secure, interactive definition of iPool ownership status; and
c. definition of iPool ownership privileges and parameters. - View Dependent Claims (48, 49, 50, 51)
- iPool exchange protocol interface; and
-
52. An iPool exchange protocol interface (iPEPi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool exchange protocol component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool exchange protocol; and
c. provision of iPool exchange protocol component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (53, 54, 55, 56, 57)
- Intelligent Object Pool access interfaces;
-
58. An object integrity assessment component (OIA) for detection and verification of data integrity, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - object integrity assessment interface; and
pool boundary protocol components;
b. provision of data checksums and checksum reporting; and
c. provision of algorithms for data integrity verification. - View Dependent Claims (59, 60, 61, 62, 63)
- object integrity assessment interface; and
-
64. An object integrity assessment interface (iOIAi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool integrity assessment component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by object integrity assessment; and
c. provision of object integrity assessment component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (65, 66, 67, 68, 69)
- Intelligent Object Pool access interfaces;
-
70. An iPool integrity assessment component (iPIA), for detection and verification of iPool integrity, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - iPool integrity assessment interface; and
pool boundary protocol components;
b. provision of iPool data checksums and checksum reporting; and
c. provision of algorithms for data set integrity verification. - View Dependent Claims (71, 72, 73, 74, 75)
- iPool integrity assessment interface; and
-
76. An iPool integrity assessment interface (iPIAi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool integrity assessment component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool integrity assessment; and
c. provision of iPool integrity assessment component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (77, 78, 79, 80, 81)
- Intelligent Object Pool access interfaces;
-
82. An iPool meta-data index component (iMDX), for generation and provision of iPool meta-data information, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - iPool meta-data index interface; and
meta-data index components;
i. provision of meta-data definitions for iPool data subsets;
such as1. data subset content attributes;
2. data type, structure, and access dependencies;
3. data ownership and access information; and
4. data relationship information;
according to available algorithms for determination of such as, but not limited to similarity;
association;
contiguity;
proximity;
dependency;
functionality;
data activity ranking;
data significance ranking; and
data validation ranking. - View Dependent Claims (83, 84, 85)
- iPool meta-data index interface; and
-
86. An iPool integrity assessment component as in claim xx, comprised as a module within an information technology platform using object-oriented data structures.
-
87. An iPool meta-data index interface (iMDXi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool integrity assessment component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool meta-data indexing; and
c. provision of iPool meta-data index component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (88, 89, 90, 91, 92)
- Intelligent Object Pool access interfaces;
-
93. A real-time meta-data linking component (RML), for dynamic linking of meta-data, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - real-time meta-data linking interface; and
meta-data index components;
b. detection of meta-data presented via actions including automated and/or user-directed queries;
commands; and
processing requests; and
c. linking of meta-data detected corresponding to meta-data comprised within linked meta-data indices. - View Dependent Claims (94, 95, 96, 97)
- real-time meta-data linking interface; and
-
98. A real-time meta-data linking interface (RMLi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following real-time meta-data linking component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by real-time meta-data linking; and
c. provision of real-time meta-data linking component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (99, 100, 101, 102, 103)
- Intelligent Object Pool access interfaces;
-
104. An Intelligent Object-to-Intelligent Object query component (OQM) for meta-data definition of data interrelationships on the individual data object level, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - Intelligent Object-to-Intelligent Object query interface; and
meta-data index components;
b. provision of dynamically updated and/or user-defined meta-data definitions for meta-data linking and query optimization;
of at least one or some combination ofi. Intelligent Object state information;
structure;
function;
type; and
content;
further comprisingii. meta-data information such as content addressing;
content association;
weighting;
sorting; and
ranking;
of such as attributes;
annotations; and
definitions. - View Dependent Claims (105, 106, 107, 108)
- Intelligent Object-to-Intelligent Object query interface; and
-
109. An Intelligent Object-to-Intelligent Object meta-data query interface (OQMi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following Intelligent Object-to-Intelligent Object query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by Intelligent Object-to-Intelligent Object meta-data query optimization; and
c. provision of Intelligent Object-to-Intelligent Object meta-data query component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (110, 111, 112, 113, 114)
- Intelligent Object Pool access interfaces;
-
115. An iPool-to-iPool query component (PPQ) for meta-data definition of data interrelationships on the iPool level, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - iPool-to-iPool query interface; and
meta-data index components;
b. provision of dynamically updated and/or user-defined meta-data definitions for meta-data linking and query optimization;
of at least one or some combination ofi. Intelligent Object state information;
structure;
function;
type; and
content;
further comprisingii. meta-data information such as content addressing;
content association;
weighting;
sorting; and
ranking;
of such as attributes;
annotations; and
definitions. - View Dependent Claims (116, 117, 118, 119)
- iPool-to-iPool query interface; and
-
120. An iPool-to-iPool meta-data query interface (OQMi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by iPool-to-iPool meta-data query optimization; and
c. provision of iPool-to-iPool meta-data query component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (121, 122, 123, 124, 125)
- Intelligent Object Pool access interfaces;
-
126. An aggregate meta-data index generator component (aMDX), for generating meta-data indices based upon aggregated information and processing results, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - aggregate meta-data index generator interface; and
pool content access components; and
b. generation of meta-data definitions for iPool data subsets;
including at least one or some combination of automatically provided and/or user-defined information regarding Intelligent Object and iPool data. - View Dependent Claims (127, 128, 129, 130, 131)
- aggregate meta-data index generator interface; and
-
132. An aggregate meta-data index generator interface (aMDXi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by comprised methods and processes for meta-data index generation and optimization; and
c. provision of aggregate meta-data index generator component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (133, 134, 135, 136, 137)
- Intelligent Object Pool access interfaces;
-
138. An aggregate real-time significance generator component (aRSG), for comparison;
- correlation;
significance detection; and
significance generation of relationships between Intelligent Object data and between iPool subsets, comprising methods fora. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer;
aggregate real-time significance generator interface; and
pool content access components; and
b. application of algorithms for normalized comparison;
correlation;
significance detection and generation of information including at least one or some combination of Intelligent Object properties;
data content properties and values; and
meta-data index content;
according to all valid query parameters. - View Dependent Claims (139, 140, 141, 142)
- correlation;
-
143. An aggregate real-time significance generator interface (aRSGi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by comprised methods and processes for significance generation and optimization; and
c. provision of real-time significance generator component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (144, 145, 146, 147, 148)
- Intelligent Object Pool access interfaces;
-
149. A result aggregation engine component (RAE), for aggregation of significant results of queries or analytical processing applied to any content of the Intelligent Object Pool, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - result aggregation engine interface; and
pool content access components; and
b. aggregation of significant results provided by an aggregate significance generator module and/or other application, module, component and access interface according to requests for result aggregation submitted via automated; and
/or user-directed queries;
commands;
processing requests;
alerts;
updates; and
reports. - View Dependent Claims (150, 151, 152, 153)
- result aggregation engine interface; and
-
154. A result aggregation engine interface (aRAEi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by comprised methods and processes for result aggregation and optimization; and
c. provision of real-time result aggregation activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (155, 156, 157, 158, 159)
- Intelligent Object Pool access interfaces;
-
160. An IMO Zoom component (IMO-Z) for interactive user viewing, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - IMO Zoom interface; and
pool content access components;
b. accessing and routing of graphical viewing information for user viewing and interactivity. - View Dependent Claims (161, 162, 163, 164, 165)
- IMO Zoom interface; and
-
166. An IMO Zoom interface (IMO-Zi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following IMO Zoom component; - Intelligent Object Pool access interfaces;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. detection of graphical content provided by said Intelligent Objects and their data content;
Intelligent Object Pool;
iPools;
components; and
access interfaces;
c. accessing and routing of graphic information via such as vectorized data field pointers; and
meta-data index definitions and linking provided by IMO Zoom viewing processes; and
provision of access control for information interchange to and from said Intelligent Objects, Intelligent Object Pool, iPools, components and interfaces. - View Dependent Claims (167, 168, 169)
- Intelligent Object Pool access interfaces;
-
170. A distributed learning engine component (DLE), for automated and/or interactive computer learning in a distributed data and applications environment, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - distributed learning engine interface; and
pool content access components.b. application of automated and/or interactive learning processes including at least one or some combination of i. simulation;
prediction, hypothesis generation, testing, result assessment and comparison;
interactive result optimization and feedback;
ii. data and user workspace definition;
assessment;
organization;
customization;
iii. data and user workspace relationship definition;
assessment;
organization;
customization; and
/oriv. optimization of accessing, routing and processing protocols for user workspaces;
Intelligent Objects;
Intelligent Object Pools; and
iPools. - View Dependent Claims (171, 172, 173, 174, 175)
- distributed learning engine interface; and
-
176. A distributed learning engine interface (DLEi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by comprised methods and processes for distributed learning and optimization; and
c. provision of real-time distributed learning component activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (177, 178, 179, 180, 181)
- Intelligent Object Pool access interfaces;
-
182. A knowledge extraction engine component (KEE), for automated and/or interactive knowledge extraction, comprising methods for
a. bi-directional information interchange with components and access interfaces including at least one or some combination of the following unified presentation layer; - knowledge extraction engine interface; and
pool content access components;
b. application of automated and/or interactive knowledge extraction processes including at least one or some combination of i. active data attribute searching, detection and extraction;
ii. similarity and significance assessment and comparison;
iii. hypothesis generation;
iv. report generation;
v. interactive result optimization and feedback;
vi. data, annotation and user workspace definition;
assessment;
organization and customization; and
vii. data, annotation and user workspace relationship definition;
assessment;
organization; and
customization. - View Dependent Claims (183, 184, 185, 186)
- knowledge extraction engine interface; and
-
187. A knowledge extraction engine interface (KEEi) providing conventions used to enable communication between components and optionally other interfaces, comprising automated and/or interactive methods for
a. bi-directional information interchange with components and access interfaces such as the following iPool-to-iPool query component; - Intelligent Object Pool access interfaces;
data Pool;
iPools;
Intelligent Object Handler; and
Intelligent Molecular Objects;
b. interchange of information required for and/or provided by comprised methods and processes for knowledge extraction and optimization; and
c. provision of real-time knowledge extraction activity information to access interfaces and components as required for synchronization, recordation, auditing and validation of said information interchange and activity. - View Dependent Claims (188, 189, 190, 191, 192)
- Intelligent Object Pool access interfaces;
-
193. A system comprising an object pool for an information technology platform and data object data architecture;
-
2. a set of pool boundary protocols for provision of data security, exchange and integrity;
3. a set of meta-data index definitions to enable definition and linking of multiple dimensions of data annotation and attributes defined and implemented at levels of individual Intelligent Objects as well as data set or subset iPools;
4. a set of pool content access definitions, comprising components and access interfaces which provide methods for Pool and iPool accessing and processing;
5. an iPool security authentication component (iPSA) for provision and implementation of Intelligent Object, Pool and iPool security definitions, authentication and access permissions;
6. an iPool security authentication interface (iPSAi) providing conventions used to enable communication between components and optionally other interfaces;
7. an iPool availability monitoring component (iPAM) for provision and implementation of availability, access and addressing information;
8. an iPool availability monitoring interface (iPAMi) providing conventions used to enable communication between components and optionally other interfaces;
9. an iPool exchange protocol component (iPEP), for data ownership and data exchange definition and management;
10. an iPool exchange protocol interface (iPEPi) providing conventions used to enable communication between components and optionally other interfaces;
11. an object integrity assessment component (OIA) for detection and verification of data integrity;
12. an object integrity assessment interface (iOIAi) providing conventions used to enable communication between components and optionally other interfaces;
13. an iPool integrity assessment component (iPIA), for detection and verification of iPool integrity;
14. an iPool integrity assessment interface (iPIAi) providing conventions used to enable communication between components and optionally other interfaces;
15. an iPool meta-data index component (iMDX), for generation and provision of iPool meta-data information;
16. an iPool meta-data index interface (iMDXi) providing conventions used to enable communication between components and optionally other interfaces;
17. a real-time meta-data linking component (RML), for dynamic linking of meta-data;
18. a real-time meta-data linking interface (RMLi) providing conventions used to enable communication between components and optionally other interfaces;
19. an Intelligent Object-to-Intelligent Object query component (OQM) for meta-data definition of data interrelationships on the individual data object level;
20. an Intelligent Object-to-Intelligent Object meta-data query interface (OQMi) providing conventions used to enable communication between components and optionally other interfaces;
21. an iPool-to-iPool query component (PPQ) for meta-data definition of data interrelationships on the iPool level;
22. an iPool-to-iPool meta-data query interface (OQMi) providing conventions used to enable communication between components and optionally other interfaces;
23. an aggregate meta-data index generator component (aMDX), for generating meta-data indices based upon aggregated information and processing results;
24. an aggregate meta-data index generator interface (aMDXi) providing conventions used to enable communication between components and optionally other interfaces;
25. an aggregate real-time significance generator component (aRSG), for comparison;
correlation;
significance detection; and
significance generation of relationships between Intelligent Object data and between iPool subsets;
26. an aggregate real-time significance generator interface (aRSGi) providing conventions used to enable communication between components and optionally other interfaces;
27. a result aggregation engine component (RAE), for aggregation of significant results of queries or analytical processing applied to any content of the Intelligent Object Pool;
28. a result aggregation engine interface (aRAEi) providing conventions used to enable communication between components and optionally other interfaces;
29. an IMO Zoom component (IMO-Z) for interactive user viewing;
30. an IMO Zoom interface (IMO-Zi) providing conventions used to enable communication between components and optionally other interfaces;
31. a distributed learning engine component (DLE), for automated and/or interactive computer learning in a distributed data and applications environment;
32. a distributed learning engine interface (DLEi) providing conventions used to enable communication between components and optionally other interfaces;
33. a knowledge extraction engine component (KEE), for automated and/or interactive knowledge extraction; and
34. a knowledge extraction engine interface (KEEi) providing conventions used to enable communication between components and optionally other interfaces.
-
Specification