WO2002054171A2

WO2002054171A2 - System, method, software architecture and business model for an intelligent object based information technology platform

Info

Publication number: WO2002054171A2
Application number: PCT/US2001/047922
Authority: WO
Inventors: Robert A. Stanley; Erich A. Gombocz
Original assignee: Biosentients, Inc.
Priority date: 2000-12-06
Filing date: 2001-12-06
Publication date: 2002-07-11
Also published as: AU2002230765A1; EP1381972A2; EP1381972A4; WO2002054171A3

Abstract

The intelligent object based information technology platform provides a structure to access incompatible applications and data.Intelligent molecular objects (IMOs 200) form a data structure that takes data such as external data (493) and converts tha data to intelligent data that is capable of being functionally untergraded. The IMOs are stored in intelligent object pools (204). An intellugent object handler unifies applications (2020) and provides a framawork to functionally integrate diverse applications (495,495) and data (493) through access interface (2022).

Description

SYSTEM, METHOD, SOFTWARE ARCHITECTURE AND

BUSINESS MODEL FOR AN INTELLIGENT OBJECT BASED

INFORMATION TECHNOLOGY PLATFORM

Inventors:

Robert Allen Stanley Erich Alfred Gombocz

RELATED APPICATIONS

Priority is hereby claimed under 35 U.S.C. 120 and/or 35 U.S.C. 119(e) to the following United States Provisional and Utility Patent Applications, each of which is hereby incoφorated by reference:

U.S. Utility Patent Application Serial No. / (Attorney Docket No.

A-70134/RMA) filed 06 December 2Q01 and entitled Data Pool Architecture, System, And Method For Intelligent Object Data In Heterogeneous Data Environments;

U.S. Utility Patent Application Serial No. / (Attorney Docket No. A-70135/RMA) filed 06 December 2001 and entitled Intelligent Molecular Object Data

Structure and Method for Application in Heterogeneous Data Environments with High Data Density and Dynamic Application Needs;

U.S. Utility Patent Application Serial No. / (Attorney Docket No.

A-70136/RMA) filed 06 December 2001 and entitled Intelligent Object Handling Device and Method for Intelligent Object Data in Heterogeneous Data Environments with High Data

Density and Dynamic Application Needs;

U.S. Utility Patent Application Serial No. __/__, (Attorney Docket No.

A-70310/RMA) filed 06 December 2001 and entitled System, Method, Software Architecture, And Business Model For An Intelligent Object Based Information Technology Platform; U.S. Provisional Application Serial No. 60/254,063 filed 12/06/00 entitled Data Pool

Architecture for Intelligent Molecular Object Data in Heterogeneous Data Environments with High Data Density and Dynamic Application Needs; U.S. Provisional Application Serial No. 60/254,062 filed 12/06/00 entitled Intelligent Molecular Object Data for Heterogeneous Data Environments with High Data Density and Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/254,064 filed 12/06/00 entitled Handling Device for Intelligent Molecular Object Data in Heterogeneous Data Environments with High

Data Density and Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/259,050 filed 12/29/00 entitled Object State Engine for Intelligent Molecular Object Data Technology;

U.S. Provisional Application Serial No. 60/264,238 filed 01/25/01 entitled Object Translation Engine Interface For Intelligent Molecular Object Data;

U.S. Provisional Application Serial No. 60/266,957 filed 02/06/01 entitled System, Method, Software Architecture and Business Model for an Intelligent Molecular Object Based Information Technology Platform;

U.S. Provisional Application Serial No. 60/276,711 filed 03/16/01 entitled Application Translation Interface For Intelligent Molecular Object Data In Heterogeneous

Data Environments With Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/282,656 filed 04/09/01 entitled Result Generation Inteiface For Intelligent Molecular Object Data In Heterogeneous Data Environments With Dynamic Application Needs; U.S. Provisional Application Serial No. 60/282,658 filed 04/09/01 entitled

Knowledge Extraction Engine For Intelligent Object Data In Heterogeneous Data Environments With Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/282,654 filed 04/09/01 entitled Result Aggregation Engine For Intelligent Object Data In Heterogeneous Data Environments With Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/282,657 filed 04/09/01 entitled Automated Applications Assembly Within Intelligent Object Data Architecture For Heterogeneous Data Environments With Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/282,655 filed 04/09/01 entitled System, Method And Business Model For Productivity In Heterogeneous Data Environments;

U.S. Provisional Application Serial No. 60/282,979 filed 04/10/01 entitled Legacy Synchronization Interface For Intelligent Molecular Object Data In Heterogeneous Data Environments With Dynamic Application Needs;

U.S. Provisional Application Serial No. 60/282,989 filed 04/10/01 entitled Object Query Interface For Intelligent Molecular Object Data In Heterogeneous Data Environments

With Dynamic Application Needs; U.S. Provisional Application Serial No. 60/282,991 filed 04/10/01 entitled Distributed Learning Engine For Intelligent Molecular Object Data In Heterogeneous Data Environments With Dynamic Application Needs; and

U.S. Provisional Application Serial No. 60/282,990 filed 04/10/01 entitled Object Normalization For Intelligent Molecular Object Data In Heterogeneous Data Environments

With Dynamic Application Needs; each of which U.S. utility and U.S. provisional patent application is hereby incorporated by reference in its entirety.

Field of Invention

This invention pertains generally to system, method, computer program product, data structure and architecture, data management, and software architecture; and more particularly to system, method, computer program product, and data structure and architecture, data management, and software architecture in the life sciences, biotechnology, therapeutic diagnostic and intervention, pharmaceuticals, and bioinformatics, also extendable to other scientific, business and information-oriented application domains.

BACKGROUND

As demand for effective Information Technology (IT) software to provide global data access and integrated scientific and business solutions has grown, significant challenges have become evident. A central problem poses access, integration, and utilization of large amounts of new and valuable information generated in each of the major industries. Lack of unified, global, real-time or near-real-time data access and analysis is detrimental to crucial business processes, which include new product discovery, product development, decision-making, product testing and validation, and product time-to-market. Additionally, the importance of functionally integrating multiple dimensions of heterogeneous data in the field, such as protein expression data, chemical structure data, bioassay data and clinical text data, is recognized. (See for example, Lin, D., et al.: American Genomic/Proteomic Technology (2001) 1 (1): 38-46.) With the completion ofthe sequence ofthe human genome and the continued effort in understanding protein expression in the life sciences, a wealth of new genes are being discovered that will have potential as targets for therapeutic intervention. As a result of this new information, however, Biotechnology and Pharmaceutical companies are drowning in a flood of data. In the Life Sciences alone, approximately one Terabyte of data is generated per company and day, of which currently the vast majority is unutilized for several reasons. Data are contained in diversified system environments using different formats, heterogeneous databases and have been analyzed using different applications. These applications may each apply different processing to those data. Competitive software, based on proprietary platforms for network and applications analysis, have utilized data platform technologies such as SQL with open database connectivity (ODBC), component object model

(COM), Object Linking and Embedding (OLE) and/or proprietary applications for analysis as evidenced in issued patents, such as for example patents issued or assigned to such companies as Sybase, Kodak, IBM, and Cellomics in US 6161148, US 6132969, US 5989835, and US 5784294, for data management and analysis, each of which patents are hereby incorporated by reference.

Because of this diversity, despite the fact that the seamless integration of public, legacy and new data is fundamentally important and/or crucial to efficient drug discovery and life science research, current data mining tools, methodologies, and technologies cannot handle all data and analyze their functional relationships simultaneously or in an acceptable time frame. There is a significant lack of data handling methods, particularly data handling methods that can utilize these data in a secure, manageable way. Security is important in at least many situations so. as to prevent other competitive investigators from taking advantage of another's investigative strategies, results or queries. The shortcomings of these conventional tools, methodologies, and technologies are evident within heterogeneous software and hardware environments with global data resources. Despite the fact that the seamless integration of public, legacy and new data is crucial to efficient research (particularly in the life sciences), product discovery (such as for example drug, or treatment regime discovery) and distribution, current data mining tools, methods, and technologies cannot handle or validate all (or even a reasonable portion of) diverse data simultaneously or within an acceptable time frame.

With the expansion of high numbers of dense data in a global environment, user queries often require costly massive parallel or other supercomputer-oriented processing in the form of mainframe computers and/or cluster servers with various types of network integration software pieced together for translation and access functionality as evidenced by such companies as NetGenics, IBM and ChannelPoint (see for example US 6125383, US

6078924, US 6141660, and US 6148298, each of which is incorporated by reference herein); packaged in some manner (e.g. Java, CORBA, "wrapping", XML) and networked supercomputing hardware as evidenced by such companies as IBM, Compaq and others in issued patents (see for example, US 6041398, and US 5842031, each of which is incoφorated by reference herein). Even with these expensive software and hardware infrastructures, significant time-delays in result generation remain the norm. In part due to the flood of data and for other reasons as well, there is typically a significant redundancy within the data, making queries more time consuming and less efficient in their results. Tools are not yet in place which can effectively detect data redundancy over heterogeneous data types and network environments, especially of data content subsets within data files, and provide ranked and validated multiple addressing and/or flagging and/or removal of such redundant data. The flood of new and legacy data results in a significant redundancy within the data making queries more time consuming and less efficient in their results.

With the advent of distinct differentiations in the field of genomics, proteomics, bioinformatics, and other information intensive fields, and the need for informed decision making in the life sciences and other disciplines, the state of object data is crucial for their overall validation and weight in complex, multi-disciplinary queries. This is even more important due to inter-dependencies of a variety of data at different states. Furthermore, because biological data frequently describe a "snapshot" representing a unique moment in time of complex processes at a defined state of the organism, data obtained at any time refer to this unique phase of metabolism. Thus, in order to account for meaningful comparison, only data in similar states can or should be utilized. Therefore, there is a growing need for an object data state processing engine, which allows one to continuously monitor, govern, validate and update the data state based on any activities of data or data objects in real-time or near-real-time, or even within an acceptable time frame. Currently, these capabilities are not broadly available for network data structures, and they are not available for data structures integrating heterogeneous data over distributed network environments.

Furthermore, these differentiations in the field of genomics, proteomics, bioinformatics, and other fields and the need for informed decision making in the life sciences, access to all data is crucial for overall validation and weight in complex, multi- disciplinary queries. This is even more important due to inter-dependencies of a variety of data at different states. The current individual data translation approach does not support these needs. Most of these problems require real-time processing; automated, instant data translation of data from different sources; and integration of heterogeneous applications and analytical components for their solutions. Data contained in diversified system environments may use different formats, heterogeneous databases and different applications, each of which may apply different processing to those data. Therefore, there is a growing and unmet need for an automated object data translation methodologies and/or systems and structures or engines, which allows for bi-directional translation of multidimensional data from various sources into intelligent molecular objects in real-time. Currently, data translation processes between different data types are time-consuming and require administrative exchange of information on data structures application programming interfaces (API's) and other dependencies. For example, some ofthe latest technologies such as Ixtcellico's CELL, IBM's DiscoveryLmk, Netgenic's Synergy and Tripos' MetaLayer solutions (see Haas et al 2001) have such requirements. These processes, although available and used, have a number of shortcomings. Despite the fact that the rapid seamless integration of public, legacy and newly emerging data is crucial to efficient drug discovery and life science research, unique "wrappers" or translation layers must currently be designed and programmed in order to translate each of those data sets correctly, and even with this manual integration, multiple data types and dimensions of data interdependencies are not made available, or "functionally integrated" for detailed qualitative and quantitative comparison and analysis across data types and dimensions. These solutions currently require significant effort and resources in both, software development and data processing, and the need for improvements such as those offered by this invention are recognized.

An additional consideration, which is prohibitive to change towards a more homogeneous infrastructure is the missing of fluently definable object representation definition protocols to prepare and present data objects for unified, functionally integrated interaction within heterogeneous environments. There is a lack of defined sets of user interaction and environment definition protocols needed to provide means for intelligent data mining and optimization of multidimensional analysis to achieve validated solutions. Data currently are interacted with and presented in diverse user interfaces with dedicated, unique features and protocols, preventing universal, unified user access. Thus, a homogeneous, unified presentation such as a flexibly network-enabled graphical user interface, which integrates components from diverse applications and laboratory systems environments over a variety of connections and protocols, is highly desirable, but heretofore non-existent for real- time data access and analysis utilizing diverse applications and data.

Finally, an additional consideration, which is prohibitive to change towards a homogenous data and applications infrastructure, is cost. The cost to bring legacy systems up to date, to retool a company's intranet-based software systems, to create a unified environment utilizing existing software products and tools such as CORBA, JAVA, XML, SQL and classic data warehousing techniques, can be time-consuming and expensive.

Conventional practices require retooling and/or translating at both application and hardware layers, as evidenced by the efforts of such companies as Unisys and IBM (See for example, US 6038393 and US 5634015), and may be prohibitively expensive for smaller and medium- sized companies or groups wishing to access this type of functionality. Because of the constraints outlined above, it is nearly impossible to extract useful, functionally integrated information from the entity of data within reasonable computing time and efforts. For these reasons, the development of comprising a unique architecture and system, comprising a unique application framework, data structure, and database structure, is unavailable and needed to overcome these obstacles (see for example, Hobbs, D.W., Chemical and Engineering News, (2001) 79 (13): 266, incoφorated by reference herein). Therefore, there remains a need for a system, method, computer program and computer program product, data structure, architecture, and application framework that overcome these problems and limitations.

LITERATURE Andreoli, J-M., In: Agha G., Wegner P., Yonezawa A.(eds.): Research Directions in

Concurrent Object-Oriented Programming, MIT Press (1993): 260-263; Bertino E., Urban S., Rundensteiner E.A.(eds.): Theory and Practice of Object Systems (1999) 5 (3): 125- 197; Chaudhri A.B., McCann J.A., Osmon P.: Theory and Practice of Object Systems (1999) 5 (4): 263-279; Cai D. , McTear M.F., McClean S.L International Journal of Intelligent Systems (2000): 15 (8): 745-761; Hert C.A., Jacob E.K., Dawson P.: Journal of the American Society for Information Science (2000) 51 (11): 971-988; Hobbs, D.W., Chemical and Engineering News. (2001) 79 (13): 266; Lin, D., et al.: American Genomic/Proteomic Technology (2001) 1 (1): 38-46; Williams R. J., In: Miller W., Thomas I., Sutton R. S., Werbos, P. J. (eds.): Neural Networks for Control, MIT Press (1990): 97- 114; Wilson G. V., Lu P. (eds.): Parallel Programming and C++, MIT Press (1996): 257-

280.; C. N. Lauro, G. Giordano, R. Verde: Applied Stochastic Models and Data Analysis: A multidimensional approach to conjoint analysis (1998) 14 (4): 265-274; Meyer, Bertrand: IEEE Computer. (1999) 32 (1): 139-140.; Chalmers, Mathew: Journal of the American Society for Information Science. (1999) 50 (12): 1108-1118.; Teasley, Stephanie and Steven Wolinsky: Science. (2001, June 22) 292:2254; Haas, L.M., et al: IBM Systems

Journal. (2001) 40 (2): 489-511.; Siepel, A., et al: IBM Systems Journal. (2001) 40 (2): 570-591; and Steiner, S. and Witzmann, F.A.. Electrophoresis. (2000) 21: 2099-2104; each of which publications are incoφorated by reference.

The following United States Patents: US 5596744, US 5867799, US 5745895, US 6076088, US 5706453, US 5767854, US 6035300, US 6145009, US 5664066, US

5862325, US 6016495, US 6119126, US 6088717, US 6052722, US 6064382, US 6134581, and US 6146027; each of which publications are incoφorated by reference. SUMMARY

The invention includes multiple system, structure, apparatus, methodological, computer software/firmware, and business or operating model elements. In one preferred embodiment, these multiple and diverse elements are synergistically combined into a commercial implementation; however, it will be understood that each of the elements and/or aspects of the invention may be used separately or in anyone of the possible combinations to provide utility.

In one of these embodiments, the invention provides a novel data structure referred to as an intelligent molecular object (IMO) or for the sake of brevity an intelligent object. The phrases intelligent molecular object and intelligent object are used interchangeably in this description. Various embodiments of these intelligent molecular objects (EVIO) or intelligent objects are described and may be used alone or in the context of other aspects of the invention. One particularly advantageous embodiment of the IMO includes both procedural (or active) and non-procedural (non-active) components, where the non-procedural component has features in common with (though not the same as) "data" in the conventional sense and the procedural component couples additional information with the "data" and adds functionality and capabilities to a system or method utilizing the "data." The manner in which the non-procedural component of the DVIO differs from conventional data, and the manner in which the IMO is a data structure but not a data structure in the conventional sense are developed elsewhere in this description. The IMO data structure (IMO) may be a local data structure or a distributed data structure, though in its most advantageous and functional form it will be a distributed data structure.

In light of the above, it will be appreciated that in one aspect, the invention provides an intelligent object data structure (IMO) that comprises one or more of components, interfaces, structures, definitions, and methods that takes any data content (such as raw data or data including but not limited to data coupled or associated with any valid type or structure) and turns the data content into intelligent data. The intelligent data is thereby made substantially or entirely capable of any one or combination of the following: self-organizing, self-translating, capable of being processed in a parallel manner, tracked, ranked according to validation, and other features and capabilities as are described elsewhere in this description.

The intelligent data is also capable of being functionally integrated, such as by mapping of data content, extraction of meta-data for each individual data object, and direct linking between objects and objects and applications.

In another one of these embodiments, the invention provides a novel applications handling system, architecture, and framework referred to as the intelligent object handler

(IOH) . The IOH may be analogized to a super-browser, that functionally integrates and validates (ranks or flags according to validation status) homogeneous and heterogeneous applications and data within a unified, globally accessible framework over a variety of networks, network protocols, client or access point hardware and operating systems, and network systems (such as peer-to-peer, client-server, ASP, and other system architecture and topologies as are known in the art). In essence the IOH is hardware, operating system, application program, and network protocol neutral or agnostic. In one embodiment, the IOH applications handling framework comprises processing components, interfaces, definitions, algorithms and methods for functionally integrating and (optionally but desirably) validating diverse applications and data. As with the EVIO (and the IOP described hereinafter) the IOH may be localized or distributed.

In a third primary aspect, the invention provides embodiments of intelligent object pools (IOP) which comprise a second database structure in addition to the afore described IMO data structure. Embodiments of the IOP are like a single global database of whatever data a user or other entity is interested in, that has been made accessible and compatible for analysis. (The ability to perform meaningful analysis may generally depend on the existence of meaningful relationships within the data and/or analysis applications themselves.) The IOP creates a unified, dynamically updated; data pool out of previously incompatible, possibly distributed data, and provides viewing and interactivity according to multiple, dynamically defined data content and property dimensions. Embodiments ofthe IPO may be locally configured or distributed, and may generally comprise one, more than one, or all of processing components, interfaces, and their comprised structures, definitions, algorithms and methods.

Each of the IMO, IOH, and IOP may typically be implemented in computer program software having a set of procedures or functional modules implemented as computer program instructions. These computer software programs executing on either general puφose computers or specialized processors having at least a processing unit and memory form systems that provide connectivity providing a user with access to data and other information via known internet and intranet infrastructures.

While each of the EVIO, IOP, and IOH advantageously support the distributed and heterogeneous integration capabilities described and provide particular advantages, non- distributed (e.g. local) and non-heterogeneous (e.g. homogeneous) operation are clearly supported and provide significant improvements over conventional systems and methods.

In one particular aspect, the invention provides an intelligent object (alternatively referred to as an intelligent Molecular Object or EVIO), which includes data structure and methodological and procedural components and in at least one embodiment is advantageously enabled in or as computer program software. When implemented as computer program software executing on or within processor and memory of one or more general puφose computers, the inventive data structure, database structure, and methodological and procedural components provide a system for data, access, manipulation, and analysis.

At one level, the invention provides system, structure, method, and computer program and computer program product for data and user identification and status management; functional integration of, and access to, potentially diverse data over a variety of computing infrastructures; integration of multiple data types and data dimensions for efficient and accurate multidimensional, parallel queries and analyses for diversified data content and dynamic applications needs in heterogeneous local and/or networked computing and applications environments with particular benefits and applicability to life sciences computing and applications environments.

The data and user identification and status management procedures and/or capabilities include: unified presentation and global unique identification of the Intelligent Object; identification, authentication and logging of users, sessions, and data content activity locally and/or over networks; dynamic routing of root object data, meta-data and data content locally and/or over networks; and data status, data integrity and validation state alerting and management.

The functional integration of, and access to, potentially diverse data over a variety of computing infrastructures procedures and/or capabilities include: functional content and attribute definition for database and application access and routing; automated raw data matrix and matrix structure definition; automated translation of multiple data types and dimensions for unified processing and analysis; and functional integration of multiple data types and dimensions for unified processing and analysis.

The integration of multiple data types and dimensions for efficient and accurate multidimensional, parallel queries and analyses includes procedures and/or capabilities for meta-data indexing and query optimization; direct data-to-data information exchange; vectorized exchange of information subsets; data-enabled parallel processing; non-destructive cache-based processing; graphical data preview and detailed viewing; automated functional integration and launching of applications and activation of data related to Intelligent Object data content; automated assembly of applications and components for viewing and/or analysis relevant to specified data types and contents; and custom text annotation, linking and embedding of existing text. Each of these capabilities and/or procedures may be applied to diversified data content and dynamic applications needs in homogeneous and/or heterogeneous local and/or networked computing and applications environments, and find particular applicability and benefits to life sciences computing and applications environments. The invention also provides methods and procedures for the creation and modification of Intelligent Molecular Objects (or for simplification "Intelligent Objects" or even more simply "Objects") are provided which, upon user initiation, queries, data acquisition protocols or data import requests, invoke the unique object identifier property pane through a unified functional presentation layer. The unique object identifier property pane assigns each new data object a globally unique identification upon creation and generates a minimum set of functional property panes within the object, which account for unified viewing and processing. Once the object's state recording is started, active identification for all connections to and activities on the Intelligent Object are listed within the unique object identifier property pane, containing a real-time record of the entries. Methods and procedures for user and session authentication, permission or denial for data access, security and ownership management, highly selective data access and routing, Intelligent Object handling and storage are immediately provided.

An object root router component defines the origin of the object within the network, directs storage of the object within the database and reports the location of the object to the unique object identifier property pane.

An interactive content routing component defines where data content is located and where query-relevant content and/or results will be directed within the network for analysis or presentation and reports the location of the data content to the unique object identifier property pane.

A status management component provides methods for data status validation, logging, use-tracking, auditing, synchronization, rollback enabled by said command history and non-destructive vector processing, and other state management and alerting protocols. The status management component communicates with an external object state engine component to monitor data integrity and to record the command history according to G*P- compliant LEVIS requirements (such as, for example, GLP, GCP, GMP, ISO-9001, CDER, CFIR) within the object state engine (OSE) property pane, where the information is updated and provided for real-time or substantially real-time viewing. This information includes one or more of detailed activity logging, such as data acquisition state, calibration information, applied transformation or analysis processes, local and remote access attempts, access permission and denial, data integrity alerts, ranking status, and regulatory validation states.

A raw data matrix property pane within the Intelligent Object provides an overview of the full raw data content subset including content attribute information, source location, data type and comments regarding- data content referred to by the Intelligent Object, regardless of originating data type or structure. A matrix structure descriptor component provides methods for data field mapping of heterogeneous raw data to govern access to individual data subsets (byte-level workspace assignment) and to enable direct vectorized access to individual data fields.

A meta-data index property pane within the Intelligent Object provides a viewer for automatically generated or user-defined index information and brief meta-descriptions ("data- about-data") such as, but not limited to, specific data functionality or relationships to other data or data inter-dependencies based upon multi-parametric clustering, queries or application of certain analytical tools or a combination thereof to the data. This pane utilizes a meta-data index interface to communicate with external processing engines to create an index of descriptive data information and to provide this meta-data to the object pane descriptor component, which integrates relevant pane information for access and presentation. Additionally, the meta-data index is used to aggregate and integrate results of clustering and/or other data analyses and provides sets of rules to optimize access and routing based upon dynamically established query relationship trees regarding specific data functionality and/or meta-data description. The meta-data index is also used to rank parameters such as data quality, validation state, significance, recency and accessibility to enable optimized access and routing based on data type, topic and content attributes to predefine analytical queries.

An object pane descriptor component compiles an overview of the Intelligent Object property pane characteristics to provide functional content and attribute definitions to access and route data content and applications. Said object pane descriptor component exchanges the information with components and access interfaces to provide definitions required for dynamic addressing, functional linking and vectorized access and routing of data content and processing results. The application translator link interacts with an external data and applications handler, such as the Intelligent Object Handler, and an object access manager component to provide a dynamic list and interactive overview of applications, application components and data resources. The application translation link enables interactive linking and integration of the applications, applications components and data resources, according to user requirements and available resources.

The object access manager determines relevant property panes and selectively directs their content for functional presentation and access within a given application or database environment. Additionally, the object access manager interacts with external object translation engines to detect, define and address required and/or available data sources and to direct access and routing requests for specific data content to linked applications and/or databases and to functionally integrate data content with a variety of applications. The object access manager also provides content-attribute based algorithms to enable applications integration and inter-application communication.

An object query interface routes results of Boolean comparisons and other algorithms applied to content attributes according to its object pane descriptor relationships. This component also passes aggregated results from object-to-object direct information interchange to an external result aggregation engine for further processing and relays significant query outcomes back to the object pane descriptor property pane for presentation to the user.

An object graph preview property pane is included as limited resolution image/graphics viewer for quick graphical data review of Intelligent Objects, and additionally provides linking to detailed viewing as well as launching of content-specific analysis tools. The object graph preview property pane also includes an object graph preview processing component, which accounts for generation of such a limited resolution image/graphics (sometimes referred to as "thumbnail" images or graphics) from non-graphical raw data content and which passes the image back to the object graph preview property pane.

An optional text annotation property pane within the Intelligent Object provides a location for customized text annotations, referencing, definitions and integration of links to external textual resources. An optional text annotation Interface, which links external components or applications such as text editors to allow for customization, formatting, reviewing and processing of the information through external editors and which allows to pass this information back to the text annotation property pane and to provide integrated support for text mining algorithms utilizing external distributed learning and/or knowledge extraction engines.

In another particular aspect, the invention provides an intelligent object handler (IOH), which includes methodological and procedural elements and in at least one embodiment is advantageously enabled in or as computer program software. When implemented as computer program software executing on or within processor and memory of one or more general puφose computers, the methodological and procedural elements provide or support a system for handling data. Methods and procedures are provided for numerous data handling tasks in both homogeneous and heterogeneous data environments, particularly those with high data density and dynamic application needs. The data handling tasks include, but are not limited to: generation of Intelligent Object data; unified presentation of dynamically customizable functional menus and interfaces such as for user definition, administration and security protocols; secured user interaction, access and presentation based on imported and/or defined user definition, administration and security protocols; data object standardization and normalization; definition of user interaction and computing environment protocols required for data object translation, standardization, access and routing; definition of data type access, translation, presentation and routing protocols for functional data and applications integration; definition of application and/or application components and interface access, translation, presentation and routing protocols for functional data and applications integration; and provision of interactive, unified, functionality for data acquisition, management, viewing and analysis.

In the object creation method and procedure, the Intelligent Object generator extracts relevant data information, routes real-time data from ongoing data acquisitions and transforms device outputs and heterogeneous data types to Intelligent Object data. Data content may be stored remotely from the corresponding Intelligent Object, and both, data content as well as

Intelligent Objects (stored in "Intelligent Object Pools" or Pool subset "iPools") may be stored locally or may be distributed across heterogeneous data storage resources and networks. Components such as the object standardization technique and the object normalization engine standardize and normalize the data by calibration according to standardized empirical criteria.

In the interactive user access and presentation method and procedures, the unified presentation layer provides the web-enabled graphical user interface that integrates the technology defined to unify diverse applications, laboratory systems environments, and Intelligent Object data at the graphic user interface layer. As an example, in the security and access methods, the user menu activates the user definition and administration shell and prompts for user input regarding access privileges environments at login. The master query component then presents security and access protocols to the unified presentation layer and to the object state engine for authentication and permits or denies access to begin fielding user queries and commands for data acquisition, retrieval, or analysis. In the method and procedures for interactive, functionally integrated data acquisition, management, viewing and analysis, user interactivity at the front end is enabled by the unified presentation layer, which is linked to defined processing components and access interfaces.

In the environment definition method and procedures, the application and database definition generator interface dynamically detects application and database requirements and defines the computing environment for the data type translator, the application translation interface, and the application framework.

In the object definition method and procedures, the data type translator defines the data type dependencies for the Intelligent Object generator, the object translation engine and the application framework component according to the applications and database environment defined by the application / database definition generator. At the same time, in the functional integration method and procedures, the Intelligent Object application framework provides functional integration of components, access interfaces and Intelligent Objects of the Intelligent Object Handler, to provide fast, efficient, functionally integrated querying, viewing and analysis. Components and interfaces such as the application and database definition generator interface and the application translation interface provide access and routing protocols to heterogeneous applications and databases.

Additionally, in the method and procedures for functional integration, the Intelligent Object Handler (IOH) enables activities including for example, real-time or near-real-time acquisition, management, viewing and analysis of Intelligent Object data through the utilization of integrated meta-data tags and pointers activated by the master query component and returned via components and access interfaces to the master query interface for presentation to the user.

Automated and/or user-directed interaction with external applications, processing components, instruments and devices is enabled by access interfaces including the master query interface, direct instrument acquisition and control, legacy synchronization interface, and report generation interface.

In a further particular aspect, the invention provides an intelligent object pool (IOP). Methods, procedures, and structures are provided for storage, management, processing and viewing of Intelligent Molecular Objects (EVIO) 200 (also referred to as Intelligent Object or simply Objects) data within defined iPool subsets. The methods and processes include

Pool Boundary Protocol definitions, Meta-data Query Definitions, and Pool Content Access definitions.

The Pool Boundary Protocols enable utility including security authentication, availability and access management, data exchange, data and data set integrity assessment. In an exemplary embodiment of the Pool Boundary Protocol methods, the iPool Security

Authentication module (iPSAc/iPSAi) authenticates iPool data requests according to user login and Intelligent Object data and/or iPool identification. Next, the iPool Availability Monitor module (iPAMc/iPAMi) and iPool Exchange Protocol module (iPEP/iPEPi) presents iPool relationships and availability to the authenticated user. At the same time, the object integrity assessment module (OIAc/OIAi) assesses Intelligent Object integrity for security and quality assurance/quality control and the iPool Integrity Assessment module (iPIAc/iPIAi) assesses data integrity within defined iPools 155 for security and quality assurance/quality control.

In an exemplary embodiment of the Meta-data Query methods, the Real-time Meta- data Link module (RML) comprising a Real-time Meta-data link component (RMLc) and a

Real-time Meta-data link interface (RMLi) provides for rapid relevant data access based on direct linking of query parameters to Intelligent Object and iPool Meta-data Index (MDX) content. Simultaneously, the Intelligent Object-to-intelligent Object (Object-to-Object) Query module (OQMc/OQMi) provides for rapid query optimization based on Intelligent Object and iPool intercommunication regarding query parameters and Meta-data Index (MDX) content. Depending on query parameters, an iPool-to-iPool Query module

(PPQc/PPQi) may be called, which provides for query optimization based on iPool data intercommunication regarding query parameters and Meta-data Index (MDX) content contained within more than one iPool.

In the Pool Content Access methods, the aggregate Real-time Significance Generator module (aRSGc/aRSGi) provides for significance detection based on provided definitions, equations and results; interactive aggregation of reported Intelligent Object attributes within the iPool; and on such as the correspondence of the attributes to queries, processing parameters/or other automated and/or user directed parameters. Next, the aggregate Meta-data Index generator module (aMDXc/aMDXi) provides for meta-data index generation for iPool sets of Intelligent Object meta-data, of values defining aspects of the global Intelligent Object

Pool or accessed iPools 155 based on query parameters; data content, function and relationships; and Meta-data Index (MDX) attribute content. The comprised Result Aggregation Engine module component and interface (RAEc/RAEi) enables results aggregation based on Intelligent Object Meta-data and aggregate Meta-data information and data values, and properties generated as results of automated and/or user-directed queries, commands and applied processes and methods. The Result Aggregation module provides information required for Report Generation, Meta-data Index updating and the like.

An object property-selective pre-sorting and viewing module (EVIO-Zc/IMO-Zi), "EVIO Zoom" which organizes Intelligent Objects based on their relationships within individual iPools 155, to allow for real-time exclusion of irrelevant object data layers and

Intelligent Object relationship viewing.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows diagrammatic representations of two embodiments of an intelligent molecular object Information Technology (EVIO IT) Platform architecture and topology, depicting structural, methodological, and functional relationships between framework, engines, interfaces, and other components, where FIG. 1 A shows a first embodiment of the overall architecture and FIG. IB shows an alternative exemplary embodiment of the EVIO IT architecture having different localizations of components and interfaces, and focusing on the integrated data and applications handling aspect of the EVIO IT Platform. FIG. 2 is a diagrammatic representation of functional relationships between instruments, applications, and intelligent object pool (IOP) 204 and diverse databases within an embodiment ofthe intelligent molecular object (EVIO) architecture and topology.

FIG. 3 is a diagrammatic representation of a typical multi-user network collaborative research effort involving geographically diverse data acquisition and query sites.

FIG. 4 is a diagrammatic representation in the form of a procedure or flow chart showing typical data processing procedures and flows within the EVIO IT architecture to provide a relevant real-time or near-real-time answer to a query.

FIG. 5 is a diagrammatic representation of an exemplary system architecture or hardware configuration for the EVIO(s), IOP, and IOH and its enabling architecture.

FIG. 6 shows diagrammatic representations of several embodiments of an intelligent object or intelligent molecular object (EviO) 200, where FIG. 6A shows an embodiment of the major elements, components, access interfaces and their relationships, showing the relationship of the Intelligent Object to an external Intelligent Object Handler (IOH), its components and access interfaces, the legacy domain of existing data content, applications, and devices, and an external Intelligent Object Pool (IOP), and FIG. 6B shows an embodiment of Intelligent Objects providing a conceptual overview of multiple dimensions of

(or "multidimensional") direct information interchange within and between Intelligent

Objects. FIG. 7 shows diagrammatic representations of several embodiments of an intelligent object pool (IOP) 204, where FIG. 7A shows relationships and interactivity between the intelligent object pool (IOP) and its components and access interfaces, to the intelligent objects (IMOs) 200 provided by the IOP, and to an external intelligent object handler (IOH)

202, and where FIG. 7B shows an intelligent object pool (IOP) and a data subset intra-Pool (iPool) 155.

FIG. 8 shows a diagrammatic representation of an embodiment the intelligent object handler in their relationships comprising a unified presentation layer, components and access interfaces. The figure shows the relationship of the Intelligent Object Handler ("IOH") to its comprised components and access interfaces, such as to the "IOH User", to Intelligent Objects ("EVIO(s)"), to an external Intelligent Object Pool ("IOP") and its comprised components and access interfaces, and to the external "Legacy" domain of existing heterogeneous data content, applications, and devices.

FIG. 9 is a diagrammatic illustration in the form of a chart showing an embodiment of distributed data resources, a Unified Client data subset intra-Pool (iPool) 155, access, and exchange relationships to the data resources, according to aspects of one embodiment of the invention.

FIG. 10 is a diagrammatic illustration depicting a representation of an embodiment of a process model for an exemplary embodiment of the intelligent object pool (IOP) 204, including relationships between legacy data, access protocols, and unified object content and meta-data interaction.

FIG. 11 is a diagrammatic illustration depicting a representation of an embodiment of the graphical user interface window within the unified presentation layer displaying algorithms included for clustering of intelligent object data within the intelligent object pool (IOP) 204, as well as a number of other property panes.

FIG. 12 is a diagrammatic illustration depicting an embodiment of an interface iPool Zoom viewer for viewing iPool data relationships, utilizing techniques that include dendrograms and self-organizing maps (SOM).

FIG. 13 is a diagrammatic illustration depicting an iPool Zoom interface and display screen image for viewing iPool data relationships, utilizing in this example a Principal

Components Analysis (PCA) algorithm.

FIG. 14 depicts an embodiment of the unified user interface of an Intelligent Object showing its unique object identifier (UJD) property pane.

FIG. 15 depicts an embodiment of the user interface of an Intelligent Object showing its object state engine (OSE) property pane with the status management component report.

FIG. 16 depicts an embodiment of the user interface of an Intelligent Object showing the object graph preview (OGP) property pane, comprising a limited resolution image/graphics viewer.

FIG. 17 depicts an embodiment of the unified presentation layer for the Sentient (EVIO) IT Platform, showing the Intelligent Object Handler and a variety of Intelligent

Objects.

FIG. 18 depicts an embodiment of a query dialog within the Intelligent Object Handler utilizing Intelligent Object handle features.

FIG. 19 depicts an embodiment of the object state engine showing its major functions, internal architecture and certain of its relationships to external components.

FIG. 20 depicts an embodiment of the object translation engine showing its relationships to external databases and to required and optional components and access interfaces.

FIG. 21 depicts an alternative embodiment ofthe object translation engine. FIG. 22 is an illustration depicting an embodiment of a first menu. FIG. 23 is an illustration depicting an embodiment of a another menu screen showing various pull-down menu details and options.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS Having described some of the problems and limitations of conventional systems, architectures, methods, procedures, and computer programs and computer program products in the Background section, we now direct some further attention to highlights of some advantages structural, methodological, and operational features of the invention as compared to such conventional systems and methods. As some comparisons necessarily require or benefit from an understanding ofthe invention, this comparison is not conveniently provided in the Background section.

Some Problems and Limitations with Conventional Methods

Speed and efficiency for accessing and analysis of global data remains a serious challenge in Life Science and biological computing. Existing software methods have relied on prohibitively expensive computing hardware to provide the heavy lifting required for complex biological computing. Existing software often routes entire raw data files for processing and generally require data locking when shared files are accessed. Mass spectrometry data, for example, may present files of 100 megabytes or more. Additionally, existing techniques for data translation and integration require "wrapping" software that further bloats programming and processing overhead, with resulting performance hits.

To address this data-intensive processing, expensive database back-ends, mainframe computers and / or cluster servers are bundled with functional but inefficient network integration software offered by such companies as Oracle, IBM (DiscoveryLink/DB2) and Compaq (Alpha Systems). These hardware and database back-end resources can range be very costly and even with these massive hardware infrastructures, significant time-delays in result generation remain the norm (Einstein, 2000). Clearly more efficient access, integration and processing techniques, to reduce hardware expense and to speed up results on any system, will be valuable to the industry. A "functionally integrated" computing environment, wherein meaningfully related data may be directly compared and subjected to unified processing and detailed analysis by potentially heterogeneous applications, remains a goal for Life Science computing. Existing software methods fail to provide for analysis of complex, dynamic analysis utilizing "functionally integrated" analysis of multiple relationships between globally available data, utilizing heterogeneous applications. Existing data structures offer limited attribute definitions, disparate and inflexible annotation standards, and fail to dynamically define attributes for unified processing in heterogeneous environments. Limitations such as these restrict comparability of heterogeneous data and the dimensionality for functional analysis and viewing.

Companies such as Array Genetics and Nonlinear Dynamics provide tools for detailed analyses of specified structures, activities and their multidimensional interrelationships within homogenous environments. However, the need to analyze data based on more flexibly defined multidimensional dependencies using heterogeneous data and applications is recognized. For example, Cellomics has recently acquired software which provides the multidimensional analytical functionality to "extract cellular knowledge from multiparameter biological measurements integrated with facets of chemical structure information" (Cellomics, 2001). Another advanced software initiative, by the National Center for Genome Research (NCGR), is currently attempting to meet these goals in a limited manner by developing Integrated SYStems (ISYS) software, that: promotes loose coupling of independent components through a flexible, semistructured data model that supports run-time association of attributes with objects, and allows different components to maintain different

"views" ofthe same object (Seipel et al, 2001).

Like other competitive software, this model fails to provide for data interoperability with diverse applications without manual programming and processing-intensive "wrapping" for translation. Competitive software designed to integrate diverse data generally requires software wrapping to meet translation and interoperability requirements, with resulting processing overhead and dependency on additional human and hardware resources (e.g. DiscoveryLmk, Java, CORBA, XML). Even with software wrapping, direct interaction between flexibly associated attributes of diverse data and between this data and diverse applicastions, is limited. Although the goal is recognized, the need remains for software capable of efficiently supporting analysis of complex dynamic relationships, between multiple data dependencies, from diverse global sources.

Detailed security and persistent data auditing, tracking, regulatory validation and alerting remain a problem in global Life Science computing. Existing software methods fail to provide sufficient security and regulatory compliant validation for management and of exchange sensitive biological information over global networks. No company provides byte- level security and access control and few provide the guaranteed raw data integrity required to maintain patient confidentiality and clinical validation over any network.

Leading software technology such as IBM's DB2/DiscoveryLink technology and Oracle's 9i database, for example, fail to provide security to the tightest level. These companies draw on structured query language (SQL) techniques and provide their finest grained security to the row level. Virtual Private Database (VPD), an Oracle database feature, offers fine-grained access control or row level security. It allows multiple communities of users to share the same database, yet only access the row(s) of data that pertain to each individual user or community of users. (Oracle Coφoration, 2001). Additionally, only a few companies, such as LabVantage and Telecation provide for network-oriented regulatory validation based on CDER/CFIR/G*P (GLP, cGMP, GCP) compliant data tracking and history. Products that integrate global data resources are unable to maintain detail data state history over networks to maintain compliance with strict laboratory information management (LEVIS) protocols. Overall, the current lack of techniques such as tightly defined access controls, assured integrity of raw data, and strict data history and tracking remain a hindrance for data sharing and collaboration, both for new drug development, and especially well for clinical data acquisition and clinical trials success. Improved security techniques are called for in software for Life Sciences.

Some Exemplary Benefits and Advantages

The inventive Sentient IT platform (also called "EVIO IT Platform") and architecture, a particular implementation and embodiment of a more generalized and generic IT platform and architecture, and its comprised components and access interfaces provide a number of important benefits to bioinformatics computing in particular, and to distributed and Life Science computing in general. These include benefits for access and processing speed involving terabytes or even petabytes of data, previously unavailable multidimensional analytical functionality, flexible distributed computing, and unmatched methods for security, reliability and regulatory validation.

The Sentient IT Platform as well as other embodiments of the inventive IT platform, offers significant benefits for improved speed and efficiency. This enhanced speed and processing efficiency is made possible by techniques for interactive content routing and direct comparison of data content vectors, as well as meta-data and data annotations, to allow for direct parallel data-to-data communication and self-organizing data. Vector subset "workspace" techniques for access and routing, wherein subsets of data content as small as 1 byte may be specified for queries, minimize network transfer and processing load and provide faster, more meaningful access to terabytes databases.

As is commonly known, increased processing power can increase speed, and the Sentient IT Platform's unique ability to enable a variety of distributed supercomputing infrastructures, such as for grid-based or peer-to-peer (any-to-any) processing will be useful. Biosentients unique methods for efficient data-enabled parallel processing and resource availability monitoring across distributed environments will extend and enhance the speed benefits offered by distributed computing infrastructures.

Additionally, the Sentient IT Platform offers techniques for faster and more efficient data type translation and applications integration and new applications assembly. The current state ofthe art requires "wrapping" of existing data files for translation and integration, which invariably adds processing overhead. In contrast, the invention provides unique methods for translation based on nested vector look up tables, which generally reduce the processing overhead and improve performance for accessing of existing data files.

In addition to speed benefits, the Sentient IT Platform offers significant benefits for improved analytical functionality across data types. The Sentient IT Platform automates integration of heterogeneous data dependencies and relationships as well as related validated and ranked annotation and literature. Recent techniques for data integration such as by InCellico and Skila provide unified environments for data relationship viewing, clustering and data sharing. In contrast, the Sentient IT Platform enables direct comparison of data content and annotation across data types and structures utilizing heterogeneous analytical applications, for "functionally integrated" analysis of multiple variable interdependencies.

In addition to unmatched functional integration and interconnectivity between heterogeneous related data, the platform provides for easy plug-in of existing analysis tools and automated new applications assembly. Interactive user customization and automated applications assembly include a unified environment for applications component modeling and linking, and efficient automated application integration made possible by a functional module comprised within the Intelligent Object application framework, comprising the Intelligent Object application framework component, automated applications assembly component, application translation interface and object translation engine. Additional analytical benefits for analysis follow from Sentient IT Platform methods for self-organizing data, distributed data learning, and for applications such as dynamic, kinetic visualization, simulation and prediction based on direct comparison of relevant data content vectors and meta-data to in silico experiments and models. Integrated knowledge aggregation and distributed learning engines can provide analytical tools for automated, forecasting, alerting and data-driven simulations.

Security benefits include improved control to accessing and routing of data. In contrast to current state of the database art, such as Oracle's "9i"database structure, which provide "finely grained" row-level data access control, the Sentient IT Platform provides unique methods for controlling access to the level of a workspace vector subset as small as a single byte. Even if identification and e-signature encryption techniques enabled by the

Sentient IT Platform for unique data, user, session and machine identification and access permission were subverted for an intercepted transmission, the interceptor would normally find only a small subset of data, meaningless outside ofthe context provided by the Intelligent Object, Intelligent Object Handler and Intelligent Object Pool.

Benefits for reliability include permanently logged, always-on, detailed activity histories for every data object. In contrast to technologies such as Mercury Prime's Razius" and Sparta System's "Trackwise", which required tightly delimited network connectivity scenarios to enable data tracking and auditing, the Sentient IT Platform assures that comprehensive data state activity tracking and history is always available, over flexible network architectures, whether analysis is localized on a single workstation or over wide area or global networks. These improved data management and data state rollback options are made possible by components and interfaces such as the object state engine, status management component, and cache-based non-destructive overlay processing methods. Nondestructive processing methods and one-click integrity assessment assures that raw data integrity is maintained at all times, and any data manipulation can be rolled back to any previous data state.

The Sentient IT Platform also offers unmatched support for regulatory compliance and validation over the complete data and applications life-cycle. The object state engine, status management component and legacy synchronization interface comprise methods for maintaining persistent (always-on or immediately updated) end-to-end data history, automated compliance status reporting and alerting and full (GLP/GCP/GMP/ISO

9000/CDER CFR/CFER.) validation support. Utilization ofthe application translation interface and Intelligent Object application framework will make it possible to efficiently generate new, or integrate existing interactive clinical and regulatory report interfaces.

Compared to systems for scientific, distributed and biological computing more broadly defined, the Sentient IT Platform provides a number of benefits. For example, the

Sentient IT Platform provides unified, real-time bi-directional user interactivity within "any- to-any" network connectivity environments, an improvement over systems such as internet portals and web-based applications services (ASPs) provided by Entigen's Bionavigator or LabBook's eLabBook. Network options may be automatically configured, according to detected network profiles and custom user preference profiles. Flexible options for network connectivity include distributed grid and peer-to-peer super-computing, along with more traditional client-server, server-server and other custom network connectivity options. These tools enable more powerful collaboration and analytical capabilities as, for the first time, all data and applications may be securely integrated over any network and processing configuration and are instantly available anywhere, any time. The Sentient IT Platform provides unique methods for data and applications translation and processing, providing an advantage for speed, efficiency and functionality over current systems for data and applications integration such as provided by Lion Biosciences and IBM's DiscoveryLmk. These advantages in speed and efficiency parallel the unrealized functional interconnectivity providing marked improvements for direct comparison and analysis of meaningfully related dimensions of data content, even across previously incompatible data types. Vectorized access, unique translation technologies and data-enabled parallel processing provide real time answers, without requiring programming-intensive, inefficient data or database "wrapping", dedicated database technology or massive parallel mainframe / cluster server expenses. For the first time, terabytes of complex, heterogeneous data can be analyzed in an affordable, unified environment, for real-time answers to drug discovery questions.

The Sentient IT Platform provides functional integration of existing analytical and data query tools with new tools and previously incompatible data, without requiring compliance to specific data annotation standards or data warehousing specifications. This is an advantage over traditional analytical tool or data access systems such as SwissProt's Melanie or Edinburgh Biocomputing Systems' MPSRCH. In the Sentient IT Platform, direct vectorized data access and translation look up tables provides highly efficient, validated, normalized data and applications interoperability. For the first time, all existing and new data and applications are integrated for real-time multidimensional analysis of heterogeneous data, in a globally accessible and completely unified user environment.

While the complete Sentient IT Platform offers the widest range of advantages, functional modules comprising one or more processing components and / or access interfaces may be utilized to enable specific functionality in key areas. Together, the Intelligent Object, Intelligent Object Handler and Intelligent Object Pool provide performance, functionality, security and validation previously unavailable to bioinformatics and Life Sciences computing.

Having described some of the features and advantages of the inventive system, method, and information technology (IT) platform, attention is now directed to a more detailed description of a particular embodiment of the inventive IT platform and architecture, referred to as the Intelligent Molecular Object Information Technology Platform (EVIO IT), or alternatively in some embodiments as the Sentient Information Technology Platform (Sentient IT).

The inventive Intelligent Molecular Object Information Technology (EVIO IT) Platform and its constituent subsystems, methods, procedures, and computer software algorithms, solves the diversified data and format as well as the heterogeneous database and applications problems by integrating unique components, processes, engines and interfaces such as networked data type, database, and application type detection and table generation, coupled with multidimensional table lookup and pointers. These components, processes, engines and interfaces work within the EVIO IT architecture at the data object level to provide such advantages as automated, real-time access and translation capabilities, thus enabling instant handling of diverse data in heterogeneous applications environments.

The EVIO IT Platform also solves these and other problems and limitations of conventional systems and methods by integrating unique components, processes, engines and interfaces such as workspace vector subset selection, dynamic meta-data indexing at the data object and data subset levels, as well as direct information interchange at the data object and data subset levels. These components, processes, engines and interfaces, work within the EVIO

IT architecture to provide significant advantages for efficient analysis of high numbers of high density data, allowing for true real-time data acquisition and analysis in a global data environment.

The EVIO IT Platform technology, in contrast to conventional existing technologies described in the background, does not reproduce or alter the raw data in any way, thus eliminating data redundancy while simultaneously enabling multiple queries on a single data object simultaneously. By using meta-data reference tables, pointers and tags to provide realtime translation and integration, which efficiently refers only to the aspects of any raw data relevant to a specific query, the EVIO IT Platform avoids data redundancy and data access locking requirements. This provides significant advantages over currently existing technologies as described by such companies as Oracle and Sybase, for example, in US 6105030 and US 5832484; each of which is hereby incoφorated by reference.

Furthermore, in contrast to the conventional practices requiring retooling and/or translating at application and hardware layers, described in the Background, the EVIO IT Platform enables translation, applications integration and validation of existing systems, in real-time, at the data object level. This allows for efficient scalability, interoperability and applications development without retooling existing, systems, and provides for data-enabled validation of existing hardware and software systems. i one aspect, the inventive methods and procedures remedy these constraints and limitations by providing an architecture allowing interactive, object-based intelligent communication in-between the data itself to extract all relevant content in a fast, unique and automated manner, within complex network environments without the need of upgrading or replacing current computer systems.

These methods and procedures, also remedy these constraints and limitations by allowing interactive, object-based intelligent communication in-between the data itself to extract all relevant content in a fast, unique and automated manner, within complex network environments without the need of upgrading or replacing current computer systems. The Intelligent Molecular Object 200 technology provides a flexible global standard, which allows for seamless integration and real-time answers to complex, multidimensional and interdependent queries. The intelligent molecular object technology provides a framework for scale-up and dynamically changing application needs in bioinformatics and the life sciences.

They also remedy these constraints by allowing interactive, object-based intelligent communication between object data based on an unified presentation layer, an user definition and administration shell and an automated application/database definition generator interface which accounts for seamless integration into the intelligent molecular object technology. They further remedy these constraints by allowing interactive, parallel, object-based intelligent communication in-between the data itself to extract all relevant content in a fast, unique and automated manner, within complex network environments without the need of upgrading or replacing current computer systems. The intelligent molecular object pool technology provides seamless integration and real-time answers to complex, multidimensional and interdependent queries, but still maintains boundaries of data subsets to govern a secure, inter-data communicative global access. The intelligent molecular object pool technology also provides a framework for scale-up and dynamically changing application needs in bioinformatics and the life sciences.

Having now described some ofthe features, benefits, and advantages ofthe invention, attention is now directed to descriptions of various facets and embodiments of the invention.

Some of the major subsystems and procedures contributing to this operation and the advantages that follow therefrom are now described in greater detail.

Software Architecture For An Information Technology Platform Using Intelligent Objects

The software architecture for an information technology platform using intelligent objects such as Intelligent Molecular Object (EVIO), software and processing method addresses all or selected steps ad procedures of data processing from data acquisition through diverse sources and instrumentation to final output of diverse data analysis results. In the first step, this technology uses engine components to standardize and/or normalize data from diverse sources to make those otherwise different data comparable. The engines provide a means to accurately compare, thus allowing one to test for identity, increase or decrease in values or functional relevancy and the like. In particular, algorithms for tracking and normalization of object data (Object Normalization Engine, ONE) or image data (Global Image Normalization, GUST) are provided. These algorithms allow one to extract variable and non-variable regions within a set of data and generate a global standard to which all data can be referred. By applying these algorithms, adjustments to all necessary parameters in a multidimensional data set can be made automatically and simultaneously. Within the described architecture, these algorithms can be applied in external modules or plug-in-format for other applications as well as for access via intranet or Internet. Next, the architecture uses uniquely defined data objects, the "Intelligent Molecular

Object 200" (EVIO) as its data records. Each the object consists of sets of functional layers (property panes). These property panes are activated or disabled via a Property Pane Controller (PPC). Each object is represented by a Unique Identifiers (UID), which governs object data security and access permissions via the Object Access Manager (OAM), and additional layers which define origin of the object within the network (Object Root Router,

ORR) and route content and results interactively (Interactive Content Router, ICR) across the network in a standardized fashion. A Status Management Component (SMC) monitors data integrity, command history and GLP/GMP-compliance via a table-based Object State Engine (OSE). The object state engine provides control for any object activity in real-time, logs activity records, provides GLP/GMP compliant experiment state assignment, state management for object data on the network, information request ranking and vectorized, direct addressing of data subsets (Vector Subsets, VSS) to minimize network traffic. This processing engine also handles external query submission and result synchronization for inter- object queries. All these processes allow the object to communicate intelligently via VSS, and keep track of their interactions. Using Meta-data Indices (MDX), workspace-oriented VSS and Object Pane Descriptors (OPD) accounts for quick and direct communication with diversified applications and databases via an Object Query Interface (OQI). An integrated Application Translator Link (ATL) communicating via the OAM allows for application integration. Additionally, functionality is provided for Direct Information Interchange (DJJ) between objects, graphical preview of the object data (Object Graph Preview, OGP) and raw data matrix structure description (Raw Data Matrix, RDM; Matrix Structure Definition, MSD).

Next, the architecture provides an applications framework within the EVIO technology, the Intelligent Object Handler 202 (IOH), describing sets of user interactions and object environment definition protocols. This IOH 202 is comprised in general of a set of processing engines and access interface protocols. These protocols provide methods and functions for preparation and presentation of data objects (EVIO Application Framework, EVIO-A) for interaction within heterogeneous environments. A Unified Presentation Layer (UPL) within the IOH 202 provides a web-enabled Graphical User Interface (GUI) to integrate components or modules from diverse applications, laboratory systems environments, and to act as handler for EVIO data (EVIO Handler, EVIO-H). Additional components include a User Definition Administration Shell (UDA), a Master Query Component (MQC) and an interface to automate the query of application and database requirements via an Application Definition Generator (ADG). The creation and initiation of new EVIO data is provided via an integrated EVIO Generator (EVIO-G). A Direct Instrument Acquisition & Control Interface (DIAC) and a component for Automated Application Assembly (AAA) provide integration of real-time data acquisition and analysis. Data Type Translators (DTT) are provided to integrate automated transformation from heterogeneous data sources into EVIO data in real-time. Automated normalization of data by calibration with standardized empirical criteria within the workspace EVIO Standardization Technique (EVIO-S) is managed through integrated meta- data tags and pointers. Several access interfaces are also integrated at the IOH level. Next, an

Object Translation Engine (OTE) is integrated, which governs interactions (such as transformation, integration and information access) between EVIO data and other diverse data environments to enable real-time communication. Such processes automatically determine other data structures, look up functional information of the data, create descriptors which correspond to object property panes and determine application type and access to EVIO's in real-time. All the engines and interfaces establish the connection to the legacy world and provide bi-directional, multidimensional, secure access to applications (Application Translation Interface, ATI), for queries via OQI, for result generation (Result Generation Interface, RGI) and for synchronization with offline legacy systems (Legacy Synchronization Interface, LSI). Additionally, learning engines such as a Knowledge Extraction Engine (KEE) or Distributed Learning Engine (DLE) and the like can be implemented within the IOH 202.

Next, the architecture provides processes, which govern a global virtual data pool, the Intelligent Object Pool (IOP) 204. The processes contain definitions for subsets, called Intra- Pools (iPools) 155 regulated by boundary protocols, which define integrity and persistence of EVIO relationships. IOP components comprise iPool boundary interfaces, iPool meta-data query and content access interfaces and iPool content ordering definitions and protocols. iPool boundary interfaces include the iPool Security Authentication (iPSA) component, which provides security authentication; the iPool Integrity Assessment (iPIA) and Object Integrity Assessment (OIA) components, which provide data integrity and persistence; and the iPool Availability Monitoring (iPAM) and iPool Exchange Protocols (iPEP) components, which define and control availability and exchange at the EVIO level. IPool Meta-data query definition interfaces are provided by Object-to-Object Query Meta-data (OQM), Real-Time Meta-data Link (RML), iPool Meta-data Index (iMDX), and iPool-to-iPool Query (PPQ) components. These processes apply interactive presorting and exclusion algorithms, provide object clustering, object result clustering and object-to-object interaction rules, and enable rapid, relevant data access via real-time meta-data queries ordered within the iPool on the DVIO level. iPool content access and ordering definitions and protocols include an Aggregate Meta-data Index (aMDX), Aggregate Real-time Significance Generator (aRSG) which integrate result merging algorithms and real-time answer generation. These iPool content access protocols and order definitions allow for object-to-analysis tools interactions, real-time result aggregation and real-time exclusion of irrelevant object data layers. Additional components include an EVIO Zoomer (EVIO-Z), which defines the proximity of individual EVIO data within the IOP and enables multidimensional EVIO data viewing and functional ranking.

Through the functionality detailed above, the IOP provides an engine for global result aggregation (Result Aggregation Engine, RAE) and instant answer output across diversified data subsets and an interface to assess integrity of iPools 155 within the virtual, global data pool.

Engines, interfaces and components comprising methods, functions, and definitions are provided, to define and describe a unique, data-enabling software architecture (EVIO IT Platform). These engines, interfaces and components implement an information technology platform which utilizes Intelligent Molecular Object (EVIO™) data and consists of a common framework comprising always-on as well as event-driven processing engines, access interfaces, plug-in modules and other components.

The EVIO IT Platform architecture defined and described below addresses all steps of data processing from data acquisition through diverse sources and instrumentation to final output of diverse data analysis results reports.

The EVIO IT Platform utilizes uniquely defined data objects, "Intelligent Molecular Object" data objects as its data records. Each EVIO consists of sets of functional layers (property panes), describing content and providing certain functionalities to the object. These property panes are dynamically activated or disabled via a Property Pane Controller (PPC), function of which is to allow or block access based on user privileges, data pool definitions and the like.

Each EVIO is represented by an Unique Identifier (UED) contained within the identity pane, so it can be addressed and identified on any network directly via its ED. The identity pane also governs object data security and access permissions via the Object Access Manager

(OAM), an integrated part of the PPC to initiate object communication. Next, each EVIO contains a layer, which contains information defining the origin of the object within the network (Object Root Router, ORR) and its owner. Next, each EVIO contains a layer, which routes content and results interactively (Interactive Content Router, ICR) across the network using standardized protocols. Next, a Status Management Component (SMC) monitors data integrity and command history in GLP/GMP-compliance via a table-based Object State Engine (OSE). The Object State Engine consists of processes which control any object activity in real-time, log activity records, provide GLP/GMP compliant experiment state assignment and state management for object data on stateless networks. In addition, the Object State Engine handles information request ranking and vectorized, direct addressing of data subsets (Vector Subsets, VSS) to minimize network traffic. This processing engine also handles external query submission and result synchronization for inter-object queries by providing routing, property pane access clearance and direct, workspace-oriented VSS addressing. All these processes allow the object to communicate intelligently via VSS, and keep track of their interactions.

Next, the EVIO includes Meta-data Indices (MDX) layer for rapid access, and Object Pane Descriptors (OPD) which allow for quick and direct communication with diversified applications and databases via an Object Query Interface (OQI), which allows for object-level direct Information Interchange (DID between objects. An integrated Application Translator Link (ATL), communicating via the OAM and

ICR, accounts for integration of external applications and/or remote application status inquiries. Next, functionality is provided for graphical preview of the object data (Object Graph Preview, OGP) and raw data matrix structure description (Raw Data Matrix, RDM; Matrix Structure Definition, MSD). The architecture defines an applications framework within the EVIO technology, the

Intelligent Object Handler 202 (IOH), which provides sets of user interactions and object environment definition protocols for the O data. This IOH 202 is comprised in general of a set of processing engines and access interfaces. A Unified Presentation Layer (UPL) within the IOH 202 provides a web-enabled Graphical User Interface (GUI), which integrates data, components and/or analytical and processing modules from diverse applications and laboratory systems environments. In general, these protocols provide for preparation and presentation of data objects for interaction within heterogeneous environments (EVIO Application Framework, EVIO-A).

To ensure automated, real-time normalization of data using one or several calibrations with empirical criteria within the workspace, the EVIO Standardization Technique (MO-S) is provided, which activates engine components for standardization and normalization through utilization of integrated meta-data tags and VSS pointers. These engine components are defined by the following methods and functions, which standardize and/or normalize data from diverse sources to make those otherwise different data comparable. The engines provide a means to accurately compare, thus allowing to test for identity, increase or decrease in values or functional relevancy and the like. The following algorithms for tracking, standardization and/or normalization of object data (Object Normalization Engine, ONE) or image data (Global Image Normalization, GIN) are defined. These algorithms allow for the extraction of variable and non-variable regions within a set of data and generate a global standard to which all data can be referred. In the case of ONE, which is described in but not restricted to the following example in the field of Life Sciences, the data are comprised of numeric matrices, text annotations, chemical structure information, chirality information, spectral information, sequence information and the like.

In the case of GEN, described by but not limited to the following example in the field of Life Sciences, the data are information contained in fluorescent and/or otherwise visibly stained ID or 2D gel electrophoresis images, array images, microscopic images and the like, all of which may differ in image acquisition parameters, detection technique, intensity, color, positional distortions of zones, bands, spot or other regular or irregular objects contained in the images which, in consequence, relate to certain macromolecule properties, such as size/molecular weight, isoelectric point, concentration, biological activity and the like. By applying algorithms, which define a vector subset for workspace selection in a single or a set of images, only those, typically relatively small areas of the images are processed which are needed to achieve relevant comparison. Such, data transfer between different objects and for temporary storage and processing via normalization, is reduced to the subsets for speed and efficiency. By reference to either a common, global standard or a dynamically obtained,

« averaged reference from all data included within the comparison query, adjustments to all necessary parameters in a multidimensional data set can be made automatically and simultaneously in parallel. Since those processes apply only to temporarily extracted small data subsets, several different request on the same object may be processed at the same time. Since in each case only vector subset are generated, no raw data alteration occurs and

GLP/GMP-compliant data integrity is maintained. Within the described architecture, the algorithms can be applied as processing engines, in external modules or in plug-in-formats for other applications as well as for remote access via intranet or Internet.

Engines, interfaces and components provided within the IOH 202 to provide an integrated analytical framework, including but not limited to the following. A User Definition

Administration Shell (UDA) interface is provided, which creates, modifies and administers user profiles and privileges and defines rules for users within individual subsets of data, called Intra-Pools (iPools) 155, as well as group memberships and topic-related access rights. A Master Query Component (MQC), is provided, which creates complex, multidimensional queries, containing pre-defined, configurable subsets of forms commonly used, but not restricted to, in diverse areas of Life Sciences. An Application Definition Generator (ADG) component is provided, which automates the query of application and database requirements and is comprised within related translation components to generate tables required for integrated real-time property pane presentation at the data object level. An EVIO Generator (EVIO-G) component is provided, which creates new EVIO data from existing data resources, or from newly acquired instrumentation data. An EVIO handler (EVIO-H) component is provided, which initiates user commands and queries at the EVIO level via the use of integrated meta-data tags and pointers. A Direct Instrument Acquisition & Control Interface (DIAC) is provided, which enables bi-directional real-time communication between the IOH 202, the EVIO 200 and diverse instrumentation. An Automated Application Assembly (AAA) component is provided, which enables integration of real-time data acquisition and analysis functionality through just-in-time (JIT) module linking. A Data Type Translation (DTT) component is provided, which integrates translation tables from the ADG from heterogeneous data sources into EVIO data in real-time. The DTT are comprised of dynamically generated sets of reference tables to provide rapid access through data structure definitions. Several engines and access interfaces integrated at the IOH level are defined, which utilize the meta-data tags and pointers to pass information between internal and external components. All the engines and interfaces establish the connection to the legacy world. An Object Translation Engine (OTE) is included, which governs interactions (such as transformation, integration and information access) between intelligent object data and other diverse data environments to enable real-time communication. Such processes automatically determine other data structures, look up functional information of the data, create descriptors which correspond to object property panes and determine application type and access to EvIO's in real-time. An Application Translation Interface, (ATI) is defined, which provides bi-directional, multidimensional, secure access to applications for queries via OQI. A Result Generation Interface (RGI) is defined, which provides validated, assembled, ranked and tabulated results to the RAE, enabling the generation of output reports across diversified data subsets. A Legacy Synchronization Interface (LSI) is defined, which provides synchronization with offline legacy data. Additionally, learning engines such as a Knowledge Extraction Engine (KEE) or Distributed Learning Engine (DLE) and the like can be implemented within the IOH 202.

Next, the architecture provides the following interfaces, component processes and engines which enable and govern a global virtual data pool comprised of EVIO data, the Intelligent Object Pool (IOP) 204. The component processes contain definitions for subsets, called Intra-Pools (iPools) 155, regulated by boundary protocols, which define integrity and persistence of EVIO relationships. IOP components are defined, which comprise iPool boundary interfaces, iPool meta-data query and content access interfaces and iPool content ordering definitions and protocols. iPool boundary interfaces are defined, which include the iPool Security Authentication (iPSA) component, which provides security authentication; the iPool Integrity Assessment (iPIA) and Object Integrity Assessment (OIA) components, which provide data integrity and persistence; and the iPool Availability Monitoring (iPAM) and iPool Exchange Protocols (iPEP) components, which define and control availability and exchange at the EVIO level. iPool Meta-data query definition interfaces are provided by Object-to-Object Query Meta-data (OQM), Real-Time Meta-data Link (RML), iPool Meta-data Index (iMDX), and iPool-to-iPool Query (PPQ) components. These processes apply interactive presorting and exclusion algorithms, provide object clustering, object result clustering and object-to-object interaction rules, and enable rapid, relevant data access via real-time meta-data queries ordered within the iPool on the EVIO level. iPool content access and ordering definitions and protocols are provided, which include an Aggregate Meta-data Index (aMDX), Aggregate Real-time Significance Generator (aRSG) which integrate result merging algorithms and real-time answer generation. These iPool content access protocols and order definitions allow for object-to-analysis tools interactions, real-time result aggregation and real-time exclusion of irrelevant object data layers. Additional components include an EVIO Zoomer (EVIO-Z), which defines the proximity of individual EVIO data within the IOP and enables multidimensional EVIO data viewing and functional ranking.

It is evident from the above description, that this EVIO IT architecture allows for decision empowering, real-time answers to complex, multidimensional, interdependent queries by providing the infrastructure for a global, comprehensive analysis of otherwise not accessible vast, inconsistent sets of data.

The following examples are offered by way of illustration and not by way of limitation. In a typical life sciences example, a 2-dimensional electrophoretic protein separation is carried out and the silver-stained separation pattern is introduced in an imaging workstation to obtain a high resolution, high dynamic range image representation of the spot pattern (typically, about 2500 - 6000 individual protein spots/image). Each of those spots represents a single protein at a defined expression stage in a specific cell environment, e.g. in this example, human liver cells. These pattern reflect also genetic differentiations and/or modifications, e.g. in case of human samples, the origin ofthe cell, gender, age, race, physical condition ofthe individual and the like. It is obvious from the above, that such pattern represent in inherent multidimensional complexity, all of which even more expressed by laboratory-to-laboratory deviations in performing the analytical procedure, sometimes also on different types of instrumentation. To analyze such a pattern for, for instance the increase or decrease in concentration based on a pathological disease condition or for drug-induced changes on certain proteins in enzyme-, immunological activity and the like, non-patient specific data have to be separated from those common in all pattern. A large series of such gels must be analyzed, standardized and compared to achieve this goal.

In the example, the EVIO platform technology will do the following: A scientist on a laptop (1) in site A in the USA logs onto the EVIO platform; the UDA within the IOH 202 verifies the login, sets user permissions and encryption level, generates a session ID and starts a session for (1) in the IOH 202. Next, the scientist (1) uses the menu in the UPL to acquire instrument data, in this example gel image data. The DIAC within the IOH 202 communicates with the imaging workstation (2) to remotely start image acquisition, the EVIO- G creates a new data objects for the currently acquired image. This new EVIO consists now of a UID pane, which uniquely identifies the EVIO via a 10-character key across the network. The UTD pane also defines object type, contains information about the origin (ORR) on the network (on 1), the owner (creator) of the EVIO, how content (the raw image data in this case) is routed (ICR) interactively on the network (in this case, the raw image file at the imaging workstation (on 2)), of an OSE pane, in which the first 2 entries are created via the SMC (an object creation record, and the current data state entry, "data acquisition in progress", an indexed multi-digit number from the GLP/GMP state assessment table), a OPD pane describing which panes are functionally defined, a dynamically updated OGP (displaying a progressive thumbnail view of the image in real-time as it is acquired) and a RDM pane consisting essentially only of file type description and pointers to the original image file, thus there is no data redundancy anywhere on the entire network. When image acquisition is complete, the SMC on the EVIO adds another status entry "data acquisition completed" to the EVIO state history log and adds final data MSD's to the RDM pane.

Simultaneously, another scientist (3) in site 2 in Japan logs onto the IMO platform; the UDA within the IOH 202 verifies the login, sets user permissions and encryption level, generates a session ID and starts a session for (3) in the IOH 202. Next, the scientist (3) uses the menu in the UPL to submit a global query about gel image data, in this case, describing a defined disease-related change in protein expression of peptides with an iso-electric points around 5.5 and a molecular size ranging between 80k DA - 120k DA in liver cells from white, human males with an age above 50. The MQC within the IOH 202 analyzes the query by providing the EVIO-H with VSS for the appropriate workspace definitions within the 2D gel image data (based on the entered pi and size constraints, only a small fraction of each images is relevant to the query), which, in turn, gates the query to EVIO's via OQI. Based on MDX links, the PPC will only inquire those iPools 155 and EVIO's with matching OPD's. The OAM on each such EVIO checks access privileges, triggers the PPC, sends update request to the OSE, extracts partial image information from the original RDM for temporary storage to be processed via ONE and GIN for image workspace normalization and comparison. Standardized comparisons (in this case, the protein spot location in the individual EVIO RDM subset, and its concentration, represented by its integrated, optical density calibrated intensity) within the VSS are reported back via ICR in each EVIO to the RGI at the IOH level, which creates ranked output. Similarly, MDX-based, the OTE at the IOH level performs data translation of workspace data from other databases using the ATI to integrate those relevant data into the result-ranking. During this time, another scientist (4) in site B in the USA logs onto to the EVIO platform, and performs a similar, but not identical query. The DLE immediately addresses the MQC to define a new VSS only within the already addressed, active EVIO's RDX's. The RAE at the IOP aggregates the EVIO results, sorts them based on relevancy and similarity, reports to the KEE and DLE for dynamic MDX update, and posts the final tabulated answer back to the IOH 202 via RGI. Proximity of integrated data is related to the EVIO-Z for graphical representation. The UPL now presents the aggregated, ranked answers to the query in several graphical and numerical windows to the scientist (3), including the newly generated image from scientist (1). On a different location and network, at the same time the local UPL in scientist's (4) computer displays the aggregated answer for his query. In the above example, for scientist (1) 212 peptides and for scientist (4) 96 peptides were identified, which differ in their expression level, amongst a set of > 500000 relevant 2D gel images with approx. 3000 individual spots each. It is noted, that in a conventional database environment, processing of the query would require the analysis of the entire gel images and their annotations, at the required resolution typically at file sizes around 2-5 MB each, and the alignment (normalization) ofthe image in its entity, thus, requiring enormous amounts of data to be processed. The EVIO IT platform technology's dynamic workspace definitions via VSS reduces this so significantly, that alignment, matching and comparison are reduced to, in this example, about 40-60kB data each (or approximately, by 60-fold), allowing real-time result aggregation.

In light of the description provided here and in the following more detailed description as well as the appurtenant figures, it will be appreciated that the invention provides an architecture, business model and method of doing business related to searching for and analyzing data generally and in particular relative to biological, chemical, and life sciences type information. Several exemplary embodiments are now described by way of example, but not limitation.

In one aspect, the invention provides a software architecture for an information technology platform, comprising of always-on and event-driven, engines, interfaces and processes and using intelligent molecular software data objects for interactive data records.

In another embodiment, this architecture is further defined such that the architecture further comprises one or more of: a. an Intelligent Molecular Object 200 (IMO), a versatile, data-enabling software object, which provides for real-time translation, integration, and object-to-object/object-to-analysis tools communication at the object data level, to allow multidimensional, platform-independent complex queries in real-time; b. an Intelligent

Object Handler 202 (IOH), which provides the application framework and user interface for EVIO data, to allow for seamless integration of their benefits into legacy systems; and c. an Intelligent Object Pool (IOP) 204, comprising one global virtual data pool comprised of EVIO data, which integrates diverse data resources on any system or network to provide result aggregation and instant answers across diversified data subsets.

In another aspect, the IMP ofthe architectural method and platform is further defined to include one or more of: a. a unique identifier (UID), comprising a property pane layer created at EVIO generation, which provides typically a 10 byte, alphanumeric unique identification on any system or network; b. an object access manager (OAM), a property pane layer which governs data security and access according to UID permissions; c. an object root router (ORR), a property pane layer which contains information to define the origin of the object within the system or network; d. an interactive content router (ICR), a property pane layer which routes content and results interactively across the system or network; e. a status management component (SMC), comprised of an object state engine and certain interfaces, which monitors data integrity and command history in GLP/GMP-compliance via state history and governs table lookup actions via the ICR; f. a property pane controller (PPC), which controls the initiation of EVIO communication according to activation by 3 a through 3d, above; g. vector subsets (VSS) for automatic, dynamic, or user-defined workspace definitions, which provide vectorized, direct addressing of data subsets for the ICR to minimize network traffic; h. meta-data indices (MDX), to provide efficient access via dynamically updated meta-data description relevant to extant data queries and definitions; i. object pane descriptors (OPD), which provide information about each object property pane and their function as required for direct communication with diversified applications and databases; j. an interface for direct information interchange (DID, which provides the interface to communication at the object level; k. an application translator link (ATL), which activates the OAM and ICR to determine the property panes for functional presentation and access within a given application or database environment; 1. an object graph preview (OGP) pane, comprising a limited resolution image and graphics viewer for quick graphical data review, particularly of image data and spectral datasets; m. a raw data matrix (RDM), comprising a property pane which provides the full information subset for any data format or structure; and, n. matrix structure definitions (MSD), which allows for data field mapping and enables vector access to specific data fields.

In another aspect, the architecture is further defined such that the architecture and accompanying process and method include the IOH 202 where the IOH further includes: a. a unified presentation layer (UPL), which provides a web-enabled graphical user interface (GUI) to integrate components and/or modules from diverse applications, laboratory systems environments and to act as handler for EVIO data; b. a user definition administration shell (UDA), which sets ups and governs access privileges to individual EVIO data at the user- defined level and is accessible within heterogeneous network environments; c. at least one engine for data object normalization and standardization, image normalization and standardization, EVIO data translation, distributed learning, and knowledge extraction; d. at least one access interface to and in-between instruments, data and applications, comprising interfaces which include, but are not limited to, direct instrument acquisition and control, application translation, direct object query, result generation, and legacy synchronization; e. a master query component (MQC), create complex, multidimensional queries, containing pre- defined, configurable subsets of forms commonly used, but not restricted to, in diverse areas of Life Sciences; f. an EVIO generator (EVIO-G), an event-driven component to acquire data from heterogeneous data resources, including from ongoing data acquisition, in real-time and transforms device outputs and heterogeneous data types to EVIO data; g. an EVIO handler (EVIO-H), which enables user management of EVIO data utilizing integrated meta-data tags and pointers; h. an EVIO application framework (EVIO-A), which provides integration and access protocols to heterogeneous applications and databases on the object level; i. an application definition generator (ADG), which automates the query and generation of application and defines computing environments for the EVIO data translation; j . at least one data type translator (DTT), which define the data type dependencies for the EVIO-G according to the applications and database environments defined by the ADG; and k. an automated application assembly component (AAA), which provides for just-in-time (JIT) module linking.

In yet another embodiment or aspect, the architecture is further defined such that the IOP includes one or more of: a. sets of fritra-Pools (iPools) 155, regulated by boundary protocols, which provide data subset management and the define integrity and persistence of

EVIO relationships; b. iPool security authentication protocols (iPSA), which authenticates iPool data requests according to user login and object data identification; c. iPool availability monitoring protocols (iPAM), which define the iPool availability and access requirements of diverse data subsets; d. iPool exchange protocols (iPEP), which determine and govern iPool data exchange protocols according to user-defined criteria; e. an object integrity assessment component (OIA), which assess object integrity for security and QA/QC; f. sets of engines and interfaces to access and generate ranked results within the IOP, including but not limited to an integrity assessment interface, a real-time meta-data linking interface and an iPool-to- iPool query interface; g. an iPool meta-data index (iMDX), which provides dynamic, automated, and user-defined meta-data indices at the iPool level; h. an aggregate meta-data index (aMDX), which provides dynamic, automated, and user-defined meta-data indices at the aggregate EVIO level, inclusive of all relevant data resources; i. an object-to-object query meta-data sorter (OQM), to generate temporary tables based on dynamic, automated, and user-defined meta-data indices; and j. an aggregate real-time significance generator (aRSG), which provides for significance detection of values based on query parameters, meta-data indices when relevant, and EVIO data ranking.

In one additional particular embodiment, the engines within the architectural platform and method are further defined to include: a. an object state engine (OSE), which provides a continuously-running (always on) set of processes, which monitor and govern activities of EVIO data, performing real-time recording, updating and logging functions in GLP/GMP- compliant format.

In another alternative embodiment, one or more engines within the architecture are further defined to include one or more of: a. a set of EVIO standardization techniques (EVIO- S), comprising engines which provide algorithms for tracking, standardization and/or normalization of object data; b. an generic object normalization engine (ONE), which extracts variable and non-variable regions within any set of object data and generates a global standard to which all data can be referred; c. an engine for global image normalization (GUST), which extracts variable and non-variable regions within any set of image data and generates a global standard to which all data can be referred; d. an object translation engine (OTE), which is comprised of methods and functions for real-time meta-data extraction and table generation of raw data matrix, data object, data field, data structure, data functional information, data type, database type, and application type definitions for the OPD; e. a distributed learning engine (DLE), which provides algorithms for dynamic, automated, and user-defined hypothesis generation utilizing global data resources; and, f. a knowledge extraction engine (KEE), which provides algorithms for dynamic, automated, and user-defined significance discovery and report generation. In a further embodiment of the architecture, the engines may include: a. a result aggregation engine (RAE) 224, 475, to validate, assemble, rank and tabulate results passed from the IOH 202 and to generate output reports across diversified data subsets.

In yet a further embodiment ofthe architecture, the interfaces may include: a. a direct information interchange interface (DII), which allows for rapid analysis and results aggregation by providing the interface for object-to-object and object-to-analysis tools via such related interfaces and engines including, but not limited to the OQI, OTE, and the DLE.

In yet a further embodiment of the architecture, the interfaces may include one or more of: a. a graphical user interface (GUI), utilizing web-enabling standards including but not limited to Java and XML; b. a direct instrument acquisition and control interface (DIAC), which provides bi-directional real-time communication between the IOH 202, the EVIO 200 and diverse instrumentation; c. an application translation interface (ATI), to provide automated real-time detection of diverse data and applications and gate bi-directional access to the OTE, thus enabling functional, standardized integration of EVIO data within heterogeneous data and applications environments; d. an object query interface (OQI), comprising an interface for direct information interchange (DII) with EVIO data, which initiates query analysis and results aggregation; e. a result generation interface (RGI) to provide validated, assembled, ranked and tabulated results to the RAE, thus enabling the generation of output reports across diversified data subsets; and f. a legacy synchronization interface (LSD, to provide persistence and synchronization of offline legacy data.

In still another embodiment of the architecture, the interfaces are further defined to include one or more of: a. an iPool integrity assessment interface (iPIA), to asses data integrity within a defined iPool for security and QA/QC; b. a real-time meta-data link interface (RML), which provides for rapid relevant data access based on query parameters and MDX information; c. a pool-to-pool query interface (PPQ), which provides for query optimization based on query parameters and relevant iPool data and meta-data intercommunication; and, d. an EVIO Zoomer (EVIO-Z), which defines proximity and functional ranking of individual EVIO data within the IOP and enables multidimensional EVIO data viewing to represent object relationships within the pool and in relationship to other iPools 155.

In another embodiment, the invention provides a software or combination software and hardware architectural platform that uses objects for real-time, efficient, multidimensional, interdependent intelligent queries.

In yet another embodiment, this software architectural platform and the associated methods and procedures are implemented on general puφose computers, information appliance^'s, and the like information and/or computation devices, at least some of which are coupled to similar devices and servers on an interconnected network, such as the Internet.

When implemented as software, the software may be resident within a memory ofthe computer or information device and execute within a processor, microprocessor, or CPU of such device. Any conventional computer or information appliance having suitable memory, processor, and interface capabilities may be used, many of which types are known in the art.

An alphabetic list of EVIO Information Technology Platform acronyms as used in this description is listed below. In some instances these acronyms are modified by prefixes or suffixes but the meaning is generally clear from the description or drawing in which it appears and all variations are not provided in this in the interest of brevity.

AAA Automated Application Assembly

ADG Application Definition Generator aMDX Aggregate Meta-data Index aRSG Aggregate Real-time Significance Generator

ATI Application Translation Interface

ATL Application Translator Link

DIAC Direct Instrument Acquisition & Control Interface

DII Direct Information Interchange

DLE Distributed Learning Engine

DTT Data Type Translators

GIN Global Image Normalization

GUI Graphical User Interface

ICR Interactive Content Router iMDX iPool Metadata Index

IMO Intelligent Molecular Object

IMO-A IMO Application Framework

IMO-G IMO Generator

IMO-H IMO Handler

IMO-S IMO Standardization Technique

IMO-Z IMO Zoomer

IOH Intelligent Object Handler

IOP Intelligent Object Pool iPAM iPool Availability Monitoring iPEP iPool Exchange Protocols iPIA iPool Integrity Assessment iPooI Intra-Pool (data subsets) iPSA iPool Security Authentication

KEE Knowledge Extraction Engine

LSI Legacy Synchronization Interface

MDX Meta-data Indices

MQC Master Query Component

MSD Matrix Structure Definition

OAM Object Access Manager

OGP Object Graph Preview

OIA Object Integrity Assessment

ONE Object Normalization Engine

OPD Object Pane Descriptors

OQI Object Query Interface

OQM Object-to-Object Query Meta-data

ORR Obj ect Root Router

OSE Object State Engine

OTE Obj ect Tr nslation Engine

PPC Property Pane Controller

PPQ Pool-to-Pool Query

RAE Result Aggregation Engine

RDM Raw Data Matrix

RGI Result Generation Interface

RML Real-Time Metadata Link

SMC Status Management Component

UDA User Definition and Administration Shell

UID Unique Identifier

UPL Unified Presentation Layer

VSS Vector Subsets

Attention is now directed to particular embodiments of the inventive structure and method, including exemplary embodiments of the intelligent object pool (IOP) as well as aspects and embodiments of intelligent objects (EVIO) and intelligent object handler (IOH).

System, methods, procedures, computer programs and computer program products are provided that define and describe exemplary embodiments of an information technology platform system and architecture utilizing an Intelligent Object or Intelligent Molecular Object (IMO) 200, Intelligent Object handler (IOH) 202 and Intelligent Object Pool (IOP) 204 and Intelligent Object data structures as core processing components.

At least in part because textual description is a linear or sequential process, the inventive methods, procedures, and techniques as well as computer program and operation where such methods, procedures, and/or techniques are implemented in such computer programs, these methods, components and processes will be described in a fashion that may not always describe every facet of an action, operation, or process as it occurs when such are simultaneous or concurrent, and/or interactive actions as they occur. However, it should be noted that the system and method herein described includes bi-directionally or multi- directionally interactive components, processes, and interfaces which perform certain tasks simultaneously, concurrently with overlap, or in a rapidly alternating fashion.

Examples of exemplary enabling computer software or firmware program code are provided to define and describe a particular exemplary embodiment, which utilizes Microsoft C++ as the exemplary programming language. Additionally, software development tools for some embodiments include Visual C++, Microsoft Foundation Classes (MFC), DEB image transformations and matrix-based graphical content generation. The features, capabilities, methods, and structures described herein are not limited to any particular programming language or code, and those workers having ordinary skill in the art will in conjunction with the description provided herein appreciate that other conventional programming languages may be used, and that as new programming languages appear, such languages will also likely support the inventive methods and procedures described herein. It will also be appreciated that the overall architecture, its application across varied domains, its processing engines and its access interfaces are in no way limited to the utilization of Microsoft C++ or the Windows 32-bit operating system environment. It will further be appreciated that other enabling software codes or enabling techniques may also be used, including for example Java, XML and other markup languages, and/or other similar techniques; and that other operating systems such as UNIX-based, Linux-based, or Windows-based, Macintosh Apple-based, or other operating systems may be utilized and/or are interoperable with aspects and features of the inventive system and method. FIG. 1A is a diagrammatic representation of an embodiment of a general EVIO IT architecture, depicting relationships between framework, component engines, interfaces and external data and applications resources.

FIG. IB is a diagrammatic representation of another embodiment of the EVIO IT architecture having different localizations of components and interfaces, and focusing on the integrated data and applications handling aspect ofthe EVIO IT Platform. FIG. 2 is a diagrammatic representation of an embodiment of the invention showing some functional relationships between instruments, applications, and intelligent object pool (IOP) 204 and diverse databases within an embodiment of the intelligent molecular object (EVIO) architecture and topology. FIG. 3 is a diagrammatic representation of an embodiment of a typical multi-user network collaborative research effort involving geographically diverse data acquisition and query sites.

FIG. 4 is a diagrammatic representation of a flow chart of typical data processing within the EVIO IT architecture. The illustration in FIG. 5 is a diagrammatic representation of an exemplary hardware configuration for he intelligent object pool (IOP) 204 and its enabling architecture. All major elements within the diagram below may be bi-directionally connected over a variety of network protocols. The minimum hardware requirement is defined by a single machine. In an exemplary embodiment, as below, two laptop computers are connected in a client/server configuration to a workstation, to each other in a peer-to-peer manner, and via the workstation directly to a laboratory instrument, such as a gene sequencer or gel electrophoresis machine.

With further reference to FIG. 5, dotted bi-directional lines 248 represent options for "any-to-any" network connectivity enabled via use of intelligent objects as central accessing and routing components. Any-to-any options include but are not limited to LAN, WAN, peer- to-peer (e.g. data, applications, memory and processor sharing between two or more laptops, workstations, etc.), server-server, Portal, ASP and other unified, distributed, parallel and grid network options. Connectivity protocols include and are not limited to PPP, http, TCP/UP, and ftp over multiple platforms.

FIG.6A is a diagrammatic representation showing the relationship of the intelligent object to an external intelligent object handler ("IOH"), its components and access interfaces, the legacy domain of existing data content, applications, and devices, and an external intelligent object pool (IOP) 204.

In FIG. 6A, unbroken lines ending with arrows on each end 490 represent bidirectional communication between exemplary property panes, components and access interfaces. Dashed lines ending with arrows on each end 492 represent bi-directional communication between optional property panes, components and access interfaces. Crossed lines do not represent connections.

FIG. 6B is a diagrammatic representation of Intelligent Objects providing a conceptual overview of interactive content routing for multiple dimensions of (or "multidimensional") direct information interchange within and between Intelligent Objects. With further reference to FIG. 6B, each property pane provides an overview of certain properties of the comprised data and its relationships. For example, property panes describe Intelligent Object ownership and activity history, but also complex, multiple relationships to other data and applications. Vectorized data content information and results of data content comparison and analysis, data annotation, text references, validation status and the like may be flexibly interconnected in a functional manner via these panes and their related components and access interfaces. User viewing and interactivity to define or refine (without writing to the data content) Intelligent Object property pane content presentation and relationship connectivity for new queries, customization and the like takes place through property panes presented at the unified presentation layer.

FIG. 7A is a diagrammatic illustration depicting aspects and embodiments of the invention including exemplary embodiments comprising a Unified Presentation Layer, modules comprising components and access interfaces, and their relationships; as well as the relationship of the Intelligent Object Pool ("IOP") to its architectural elements, such as for example an external Intelligent Object Handler 202 and/or Handlers (IOH) 202 and to their components, access interfaces and users, to Intelligent Objects ("EVIOs"), and via the Intelligent Object Handler 202 and Intelligent Objects to the external "Legacy" domain of existing heterogeneous data content or databases, applications, systems and/or devices.

With further reference to the embodiment in FIG. 7A, unbroken lines ending with arrows on each end 490 represent bi-directional communication between exemplary property panes, components and access interfaces. Dashed lines ending with arrows on each end 492 represent bi-directional communication between optional property panes, components and access interfaces. (Generally, crossed lines 491 do not represent connections.)

FIG. 7B is a diagrammatic representation of an intelligent object pool (IOP) comprising intelligent objects (EVIO) 200 and a data subset intra-Pool (iPool) 155 of intelligent objects defined according to ownership, similarity or other boundary definitions.

FIG. 8 is a diagrammatic representation of an exemplary embodiment of the claimed elements and their relationships, showing the relationship of the Intelligent Object Handler to Intelligent Objects, comprised components and access interfaces, the legacy domain of existing data content, applications, and devices, and an external Intelligent Object Pool

("IOP").

In FIG. 8, unbroken lines ending with arrows on each end 490 represent bi-directional communication between exemplary property panes, components and access interfaces. Dashed lines ending with arrows on each end 492 represent bi-directional communication between optional property panes, components and access interfaces. (Generally, crossed lines

491 do not represent connections.) With reference to FIG. 9, in a global, heterogeneous environment, data from diversified sources are functionally integrated via intelligent objects and their intelligent object pool (IOP) 204, utilizing automated access definition protocols, multiple alias integration and addressing, data field mapping and state management to allow for integrated data access, analysis and exchange utilizing distributed data content presented within the

Client iPool.

The chart in FIG. 9 depicts user relationships to the data on database and iPool levels.

In the figure, the upper section ofthe diagram (i.e. "Client iPool", "Restricted", "Client Data",

"Resources") depicts data within intranets, LANs and the like, while the lower, larger part of the diagram contains several different forms of public and/or otherwise web-accessible data sources.

The depiction below in FIG. 10 represents a process model describing interactions of modules for an exemplary embodiment ofthe intelligent object pool (IOP) 204.

In FIG. 10, data from a global data resource are passed through an access interface consisting of a security layer 404, a set of access and/or exchange protocols 406 and integrity assessment procedures 408, to the intelligent objects comprised within the intelligent object pool 204 for unified queries and analyses. The pathways involved in unified direct intelligent object-to-intelligent object 455-456 and iPool-to-iPool 457-458 data interaction generate the real-time answer and pass it back through processes including aggregate meta-data indexing 422, significance generation and aggregation 473-476 and security 404 to the intelligent object handler 202.

The depiction below in FIG. 11 is a representation of the graphical user interface window within the unified presentation layer displaying algorithms included for clustering of intelligent object data. A number of property panes showing dendrograms results are seen behind the clustering algorithms menu in FIG. 11.

The depiction below in FIG. 12 shows an interface iPool Zoom viewer for viewing iPool data relationships, utilizing techniques that include dendrograms and self-organizing maps (SOM).

Attributes and interactions between individual intelligent object (EVIO) data within the set of objects are outlined in the margins of this exemplary display, FIG. 12.

The depiction below in FIG. 13 shows an iPool Zoom interface for viewing iPool data relationships, utilizing Principal Components Analysis (PC A).

In one exemplary and advantageous embodiment the Intelligent Object Pool (IOP) 204, comprised by an information technology platform (ITP) 151 (such as for example, the

Sentient IT Platform version 1.0.4beta, made by Biosentients, Inc. of 1325 61^st Street, Emeryville, CA 94608-2117) advantageously enabled in software, provides an organizational architecture and framework for Intelligent Object (EVIO) data architecture. Core architectural elements of the information technology platform 151 include the Intelligent Object Pool 204, an external Intelligent Object Handler 202, and Intelligent Objects 200, each comprising some combination of components, access interfaces, some or all coupled or otherwise interacting via included methods and processing routines and subroutines. In some embodiments, intra-Pools (iPools) 155, comprising subsets of Intelligent Object Data within the Intelligent Object Pool 204 data pool may also be considered as a core architectural element. Some functionally meaningful combinations of components and / or access interfaces may also be defined as stand-alone modules or as customizable plug-ins to other architectures or systems. Other optional elements may also be provided within or coupled with the core architectural elements.

Having now described some overall system architecture and structure as well as methodological and operational aspects of embodiments of the invention, we now separately describe embodiments of the IOP, EVIO, and IOH realizing that in at least certain embodiments their operations are intertwined. First the IOP is described in detail, followed by the EVIO, and IOH. It will be understood throughout this description that section headers are merely for convenient reference and that in general, aspects of the invention are describd thoughout the specification and drawings.

INTELLIGENT OBJECT POOL 204

With reference to an embodiment illustrated in FIG. 7A, the Intelligent Object Pool 204 comprises Intelligent Objects, representing the global entity (or portion subset of global entity called an intra-Pool or iPool 155) of accessible Intelligent Object 200 data content presented within a functionally integrated Unified Presentation Layer 206. In addition to interaction with the Intelligent Objects 200, the Intelligent Object Pool 204 may be activated and directed by the Intelligent Object Handler 202. It is noted that in FIG. 7 A, unbroken lines ending with arrows on each end represent bi-directional communication between exemplary property panes, components and access interfaces; dashed lines ending with arrows on each end represent bi-directional communication between optional property panes, components and access interfaces; and lines that may cross do not represent connections.

The Intelligent Object Pool 204, Intelligent Object Handler 202 and Intelligent Objects (EVIO) 200 comprise a unified presentation layer; components comprising defined methods, procedures, and processes; and access interfaces. The access interfaces provide unique conventions used to allow communication between components and in some cases other interfaces, for direct linking of vectorized pointers to accessible Intelligent Objects (EVIO) 200 data content, for direct linking of meta-data; and for linking and activation of component information and processes.

Other optional but advantageous data-enabling methods and processes may for example include one or more of the following, such as for example the customizable exchange of various combinations of information required for queries and commands within heterogeneous data and applications environments, and modules for such as automated distributed learning (DLE) and knowledge extraction (KEE).

The inventive information technology platform architecture utilizes Intelligent Object data content properties and values for core functionality, such as for example, aggregation, organization and other processing of results of vectorized data content analysis, or other information interchanged via components and interfaces, such as dynamically definable metadata definitions.

With reference to FIG. 6A a raw data matrix property pane (RDM) 1042 included within Intelligent Objects (EVIO) defines data content addressing and provides vectorized access information for linking of diverse types of data content. Additionally, the matrix structure descriptor (MSD) 1046 provides processes required by the application / database definition router (ADDR) 1028 and data link insertion component (DLI) 1044 for data field mapping and gating of vectorized access to individual data fields between objects, applications and databases. Examples of exemplary enabling code for the raw data matrix property pane (RDM) 1042 and matrix structure descriptor (MSD) 1046 interface are provided in a concurrently filed copending United States Utility Patent Application Serial No.

09/ , (Attorney Docket No. A-70135/RMA) entitled and describing among other subject matter embodiments of an Intelligent Object (EVIO) 200 application. Vectorized access, routing, translation, linking and comparison of data content include, for example data content information such as RGB values or data field contents such as literature reference pointers and data content subsets ("workspaces") defined to granularity from entire data files to data content subsets as small as single byte workspaces, such as a single band, spot or a set of bands or spots in a gel electrophoresis pattern. Direct interchange of information between data objects and between data objects, heterogeneous applications and a various combinations of components, access interfaces, and presentation layers includes processing information, commands, queries, meta-data, data content and said defined workspace subsets. Meta-data includes, for example, alphanumeric information defining the data content and its relationships, definitions for linking Intelligent Objects according to their detected functional or semantically defined relationships, and lookup tables for data content definition and presentation information. Comprised meta-data index information may be utilized to optimize linking, organization and direction of the vectorized data content access and routing requests, processing commands, and information interchange between such as Intelligent Objects, heterogeneous and/or homogeneous data objects and data content, applications, data resources and/or databases. An object pane descriptor (OPD) provides an overview of information for any particular Intelligent Object state and its relationships, for easy user review and interactivity with functional linking and vectorized accessing and routing of data content, meta-data and information such as queries, reports and processing results.

A status management component (SMC) within each Intelligent Object (EVIO) 200 initiates direct object-to-object interchange of information including data content, meta-data, queries and processing commands in parallel with corresponding Intelligent Objects via their comprised object query interfaces. The status management component (SMC) directs the interactive content routing of specified data vectors and/or meta-data index information between object query interfaces and of other Intelligent Objects for linking, comparison and relationship definition according to comprised algorithms described and defined elsewhere, and relays the data content information to the external object state engine (OSE) and result aggregation engine interfaces (RAEi) within the Intelligent Object Pool (IOP) 204.

Direct information interchange (DID may include various methods, procedures, and processes that provide such functionality such as one or more of: (a) activity synchronization, (b) generation of authentication and availability states, (c) verification of integrity states for quality assurance, (d) maintenance of exchange and ownership histories, and (e) status updating.

Activities may for example include one or more of the following: fielding and permission for access privileges; recordation and reporting of royalties or fees for data exchange; including recordation of detail including data attributes accessed, requests for linking of data attributes; assessment of Intelligent Object (EVIO) 200 data integrity, of the integrity of the entire Intelligent Object Pool contents, and/or of iPool data subsets; or other activities provided by the system.

In one embodiment, activity synchronization states may include for example information required for synchronizing two or more processes that depend upon the simultaneous or closely linked occurrence of specific related events in time, or that comprise closely related properties or functions, such as for example: synchronized linking for common responses to queries; commands for window scrolling linked across data; requests for batch information updating; automated batch information updating; linking to common timing signals; and the like. Activity synchronization states may be required by and provided to various combinations of Intelligent Objects, components and access interfaces and are generated, for example, by the object state engine (OSE) 208 within the Intelligent Object Handler (IOH) 202, interacting with the status management component (SMC) 1016 of the Intelligent Molecular Object (EVIO) 200. Activity synchronization may also be generated by additional components and interfaces such as are comprised within the Intelligent Object Pool (IOP) 204 for synchronization of meta-data linking (RML) and (RMLi), and for synchronizing iPool-to-iPool queries (PPQ) and (PPQi).

Availability states may include for example, on-line or offline status; ranked or otherwise sorted aliases and / or multiple addresses for data content access; validation ranking to determine availability of data for such as regulatory filing requests; and the like. Availability states are provided to the comprised iPool Availability Monitor by external components and access interfaces, such as for example the object access manager (OAM) 1036 comprised within the Intelligent Object (EVIO) 200; the application / database definition generator (ADG) and legacy synchronization interface (LSI) 2018 comprised within the Intelligent Object Handler (IOH) 202; and the iPool availability monitor (iPAM) and (iPAMi) comprised within the Intelligent Object Pool (IOP) 204.

Authentication states may include for example, the status of verification regarding the unique identity of an Intelligent Object, a person, a machine, a session or a process; the access or availability status ofthe uniquely identified Intelligent Object, person, machine, or process; verification that information, queries or commands really come from their stated source; and the like. The generation of authentication states involves processes comprised within the

Intelligent Object Handler (IOH) 202 such as for user definition and administration (UDA) 2000; within the Intelligent Object (EVIO) 200 such as for unique identification, accessing and routing (1006-1012) and status management (SMC) 1016; and within the Intelligent Object Pool (IOP), such as for the iPool security authentication module comprising iPSA and iPSAi . Integrity states for quality assurance may for example include or be selected from one or more of the following integrity states: data integrity verified; data integrity altered; alerts regarding Intelligent Object integrity violation status; alerts regarding processes that may or will violate Intelligent Object integrity; activation of an interactive user interface providing a description of the alert; provision of optional processing methods and/or cancellation of the processes in case of integrity violation alerts; and the like. Verification of these integrity states for quality assurance involves processes comprised within the Intelligent Object Handler (IOH) 202 such generated by the object state engine (OSE) 208 and legacy synchronization interface (LSI) 2018; within the Intelligent Object (EVIO) 200 such as for status management (SMC) 1016 and raw data matrix definition (RDM) 1042; and within the Intelligent Object Pool (IOP), such as for Intelligent Object integrity assessment (OIA) and

(OIAi), and iPool integrity assessment (iPIA) and (iPIAi). Exchange and ownership histories include for example histories chronicling: Intelligent Object and iPool ownership status; Intelligent Object and iPool ownership privileges and parameters for exchange; recorded criteria for exchange such as licensing, subscription, royalty or fee agreements; histories of Intelligent Object data attribute access and attribute linking; calculated exchange charges, fees or royalties; or other records of exchange accounting. Generation and maintenance of exchange and ownership histories involves processes comprised within the Intelligent Object Handler (IOH) 202 such as for example, the user definition and administration (UDA) 2000 component and object state engine (OSE) 208; within the Intelligent Object (EVIO) 200 such as for unique identification and (UID) 1006 and (UIDi) 1012; and within the Intelligent Object Pool (IOP), such as for implementing and monitoring exchange protocols (iPEP) and (iPEPi).

Additionally the Intelligent Object Pool 204 comprises methods, procedures, and processes for one or more of the following: fielding queries, iPool 155 boundary management, iPool data integrity management, data exchange management, data integrity assessment, data definition, query and processing optimization, data and data subset management, significance generation, result aggregation, and data relationship viewing. These methods, procedures, or processes are activated and implemented according to predetermined or dynamically determined rules, policies, and procedures. The rules, policies, and procedures may be any one or more of automated, event-driven, interactive, and/or user- directed, secure, audited, and validated.

Methods for result aggregation (RAE), and (RAEi) are generally provided in a minimal embodiment of the invention, while other methods including for example exchange protocols (iPEP, (iPEPi); meta-data indices methods (PPQ), and (PPQi) ; and / or pool content access methods (DLE), and (DLEi) are optional but advantageous in most cases. Additionally, stand-alone functional modules constructed out of the defined components and access interfaces may be assembled to provide customized functionality.

With further reference to the embodiment of the Intelligent Object Pool 202 in FIG. 7B, at a top-level, the Intelligent Object Pool 204 comprises methods, protocols, and definitions that enable the functionality and utilization ofthe Intelligent Object Pool 204 and data subset iPools 155. Recall that, in at least one embodiment of the invention, iPools 155 describe any subset of Intelligent Object data comprised within an Intelligent Object Pool 204. The iPools may be flexibly defined by the user according to a variety of parameters including ownership, data attributes, experimental design, and the like. The protocols, definitions, and methods include Pool boundary protocols 402, meta-data indices indices 410 and definitions 411, and pool content access methods and processes 420, as represented in

FIG. 7A. In one particular embodiment, an information technology platform provides an object pool enabled in computer program software for any object-oriented data architecture so that the object pool architecture and methodology are not limited only to the particular intelligent objects or intelligent molecular objects specifically described elsewhere herein, but are merely exemplary.

In other embodiments, additional modules, components, and interfaces for a one or more optional but advantageous distributed learning engines and/or knowledge extraction are provided. In the description that follow and that are provided elsewhere in this specification, the terms modules, components, and interfaces are used to describe aspects of embodiments of the invention. While some differences may generally exist between these modules, components, and interfaces as the terms apply to difference aspects of the inventive structure, method, and computer program and computer program product, the following guidelines (though not definitions) in understanding these phrases is provided.

A module is a top-level definition that defines an instance of indicated functionality which may or may not be required and provided for a specific user installation. Modules may be compiled separately and a module's implementation can be changed without requiring changes to other components, interfaces, or modules. A module usually includes a component and an interface or some combination of these, and may be designated by a "m" suffix following the module acronym (such as RAE for the Results Aggregation Engine component or RAEm for the Results Aggregation Engine module). Components provide core processing activity required for given functionality, comprising methods generic to the overall architecture for advertising and enabling its functionality, whether via interactive methods such procedures, routines, or information interchange with some combination of components and / or access interfaces. An interface provides unique conventions used to allow communication between components and in some cases other interfaces, for direct linking of vectorized pointers to accessible Intelligent Objects (EVIO) 200 data content, for linking and activation of meta-data; and for linking and activation of component information and processes, and may be designated by a "i" suffix following the module acronym (such as RAEi for the Results Aggregation Engine interface). It will be . appreciated that as each module, component, and interface is different, reference should be made to the detailed descriptions of each particular module, component, and interface to ascertain its structure, function, and operation.

Also, for puφosed of clarity, certain modules, components and access interfaces may be grouped into functionally related sets, such as Pool boundary protocols (PBP), Meta-Data Indices (MDX), and Pool Content Access (PCA) definitions and methods. Pool boundary protocols (PBP) 402

In one aspect, the pool boundary protocols (PBP) 402 are primarily responsible for providing data security, providing and enabling data exchange, and providing data integrity assessment. The Pool boundary protocol (PBP) 402 methods and definitions described herein generally provide (i) pool security protocols and procedures 404 that provide data security,

(ii) pool boundary exchange protocols and procedures 406 that provide definitions for data ownership, royalty agreements, data access fee agreements and enable detailed use-tracking and reporting to enable accurate charging of fees, auditing of revenue, and other detailed assessment and control for access and exchange of data subsets, or iPools 155, and (iii) Pool integrity protocols and procedures 408 that provide and maintain data integrity assessment for individual data objects as wells as data subset iPools 155. Recall that the intelligent object data includes data content stored in global and/or local data resources of potentially heterogeneous type and/or structure. In one embodiment, the pool boundary protocols (PBP) 402 include a plurality of functional modules comprising components and access interfaces as described in greater detail elsewhere herein.

In one embodiment, a set of pool boundary protocols (PBP) 402 are provided, comprising a plurality of modules: (i) an iPool Security Authentication module (IPSAm), (ii) an iPool Availability Monitor module (EPAMm), (iii) an iPool Exchange Protocol module (EPEPm), (iv) an Object integrity assessment module (OIAm), and (v) an iPool Integrity

Assessment module (JJPIAm).

The iPool Security Authentication module (IPSAm) authenticates and permits or rejects iPool data requests according to user login and object data identification, and in the embodiment of FIG. 7A comprises an iPool security authentication component (iPSAc) 431, and an iPool security authentication interface (iPSAi) 432).

The iPool Availability Monitor module (EPAMm) assures availability of iPool data content, and in the embodiment of FIG. 7A comprises an iPool Availability Monitor component (iPAMc) 433, and an iPool Availability Monitor interface (iPAMi) 434).

The iPool Exchange Protocol module (IPEPm) governs and manages data ownership and exchange, and in the embodiment of FIG. 7A comprises an iPool Exchange Protocol component (iPEPc) 435, and iPool Exchange Protocol interface (iPEPi) 436.

The Object integrity assessment module (OIAm) assesses object integrity for auditing, security, validation, and quality assurance/quality control; and in the embodiment of FIG. 7A comprises an Object integrity assessment component (OIAc) 437, and an Object integrity assessment interface (OIAi) 438. Finally, the iPool Integrity Assessment module (IPIAm) assesses data integrity within a defined iPool for security and quality assurance and quality control and which provides alerts regarding iPool validation status, and in the embodiment of FIG. 7A comprises an iPool Integrity Assessment component (IPIAc) 439, and an iPool Integrity Assessment interface (JJPIAi) 440, which assesses data integrity within a defined iPool for security and quality assurance and quality control and which provides alerts regarding iPool validation status.

Where the functionality provided by a particular module is not required for a particular application, its provision is optional to the IOP 204 and not required by these embodiments of the invention. Furthermore, additional modules such as modules comprising components 441, 443, and/or interfaces 442, 444 may optionally be provided as the system, architecture, topology, and methodology are adaptable and expandable to add additional capabilities as the need arises.

In an exemplary embodiment, a set of Pool boundary protocols 402 provided within the Intelligent Object Pool 204 includes a set or sets of computer program software instructions enabling unidirectional and preferably bi-directional information interchange with other system components and access interfaces including but not limited to components and interfaces associated with the external Intelligent Object Handler 202 (IOH), Intelligent Object Pool (IOP) 204, iPools 155, and Intelligent Objects including Intelligent Molecular Objects (EVIO) 200. Recall that although this description focuses on particular embodiment of the EVIO and IOH as described elsewhere herein, the structure and methods described relative to the IOP and components of the IOP are applicable to other objects and object handlers.

Defined data subsets or intra-Pools (iPools) 155, comprise subsets of Intelligent Object data within the Intelligent Object Pool 204. When the user requests access to the entire available data included within the Intelligent Object Pool, or is accessing the entire content of their Intelligent Object Pool for integrity verification, the terms data pool, or simply pool may be used to describe the entity of Intelligent Object data and their contents included within the Intelligent Object Pool database structure. Normally, however, the term iPool is used to describe any set of data which has been defined, recognizing that even all data comprised within the Intelligent Object Pool database structure does not the define the global entity of data, but is rather a subset (or intra-Pool) of the global data resource, or global data pool. In most cases, iPool is used to define subsets of data delimited within the Intelligent Object Pool 204 by Pool boundary protocols such as ownership, conditions for access or exchange, data interdependencies and content-based relationships, and the like. Pool boundary protocols, Meta-data Indices, and Pool Content Access definitions provide descriptive headings referring to groupings of included components and access interfaces within a functional block of the Intelligent Object Pool 204. The Pool boundary protocols, for example, comprise components and access interfaces, which together may comprise functional modules for Pool boundary protocols, definitions and activities and iPool boundary protocols, definitions and activities. For example, the combination of iPSA and iPSAi comprise a Pool boundary protocol module for security. In analogous manner, the combination of iPAM with iPAMi comprise a Pool boundary protocol module for security and exchange. The pool boundary protocols (PBP) comprise modules, interfaces, components, methods and processes which enable data subset pools or iPool 156 boundary definitions and user interactivity with these data subset iPools 156. Generally, Pool boundary protocols (PBP) provide access control, tracking, recordation and management of data exchange, and data set integrity assessment required for iPool subset 156 boundaries and parameters . In particular, Pool boundary protocols allow for unified definition and management of data subsets via included component and access interface for (a) access and security; (b) integrity assessment and verification for Intelligent Objects 200 and iPools 155; (c) management of data content access for exchange and auditing; (d) access and routing of global and/or local Intelligent Object data; (e) data source availability management and provision of the information to components and access interfaces as required for state management of Intelligent Objects

200, iPools 155, and data content information interchange.

Additionally, Pool boundary protocols may be utilized to provide the same or similar functionality for the entire entity of data comprised within the Intelligent Object Pool 202 database structure, in which case the entity of data may be called a data Pool or Pool. Because iPools 156 are subsets ofthe full data "Pool", iPools may be flexibly defined according to the properties of comprised data in relationship to access, availability, ownership, integrity, and the like.

In one embodiment, the Pool boundary protocols desirably and advantageously utilize object-oriented data structures, while other embodiments use other than object-oriented data structures. The use of object-orientated data structures is advantageous in some information technology platform implementations, including the Sentient Platform described in detail herein elsewhere, in part because of the broad acceptance and existence heterogeneous object- oriented data structures currently, and also because of the existence of certain valuable data annotation, meta-data, or other data-enabling techniques provided by the object-oriented data structure. On the other hand, non-object-oriented data structures may also be used in part because of the broad acceptance and existence heterogeneous non-object data currently, and also because the technologies defined herein are ideally suited to accessing and defining non- object data content, and to translating the data content for presentation within a variety of environments, both object-oriented and non-object-oriented.

iPool Security Authentication Component (iPSAc) 431

The iPool Security Authentication component (iPSAc) 431 is primarily responsible for permitting or denying a request for access to features and capabilities of the system and modules, components, and interfaces of the system, and/or to contents of the system; optionally including a level of access when any such access is permitted. hi an exemplary embodiment, an iPool Security Authentication component (iPSAc)

431 contains a set of Security Authentication software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following: Unified Presentation Layer; iPool Security Authentication interface; and Pool boundary protocol components. Additionally, a set of comprised definitions provide automated and/or interactive methods and processes including definition of iPool access permissions; definition of iPool ownership and privileges and criteria for permission or denial of specific access, routing and processing activities; including but not limited to permission or denial to access and/or route subsets of data content defined to the level of single bytes by activation of vectorized pointers to the data content. Additionally, the iPool Security Authentication component desirably includes methods and processes including permission or denial to access and or route iPool meta-data information and definitions; including but not limited to iPool content overviews; and iPool relationship information. Furthermore, included methods and processes desirably include automated and/or interactive authentication and permission or denial of iPool access requests according to correspondence of user login information; user definition and administration permissions provided by an interface to an external Intelligent Object Handler 202; iPool access permissions; and comprised Intelligent Object data identification.

In an exemplary embodiment, the iPool Security Authentication component (iPSAc) 431 comprises a iPool Security Authentication module (IPSAm) within an information technology platform 151 for Intelligent Objects. In another exemplary embodiment, the iPool

Security Authentication module (IPSAm) optionally but advantageously comprises a module within an information technology platform using object-oriented data structures.

iPool Security Authentication Interface (iPSAi) 432 In one aspect, the iPool Security Authentication interface (iPSAi) 432 is primarily responsible for enabling detection and extraction of information required for security authentication by the iPool Security Authentication component (iPSAc) 431 from intelligent objects and their data content, the IOP 204, iPools 155, and components and interfaces thereof. It may also be responsible for routing information derived by iPSAc 431 directly to IOP 204, iPools 155, and components and interfaces thereof. Additionally, methods and processes are provided, which route information derived from the iPool Security Authentication component directly to the Intelligent Object Pool 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces; provision of iPool Security Authentication component activity information to access interfaces and components as required for utility including but not limited to synchronization ofthe component information interchange and activity; recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, an iPool Security Authentication interface (iPSAi) 432 includes a set of Security Authentication interface computer software code instructions including Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to one, more, or all of the following: an iPool Security Authentication component; one or more

Intelligent Object Pool access interfaces; an Intelligent Object Handler 202 (IOH); and Intelligent Molecular Objects 200 (IOM).

Information detection and extraction methods, procedures, and processes are provided, which enable detection and extraction of information required for iPool Security Authentication, provided by the Intelligent Objects and their data content; Intelligent Object

Pool 204 ; iPools 155; components and access interfaces. The information includes but is not limited to one, more, or all of: Intelligent Object data content to be accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations; and/or other data- enabling information; provided directly to the iPool Security Authentication component.

Additionally, methods and processes may be provided, which route information derived from the iPool Security Authentication component directly (preferred) or indirectly to the Intelligent Object Pool 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object

Pool 204, iPools 155, components and interfaces; provision of iPool Security Authentication component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity; recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, the iPool Security Authentication interface (iPSAi) is comprised as a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Security Authentication interface comprises a module within an information technology platform using object-oriented data structures.

iPool Availability Monitoring Component (iPAMc 433

The iPool Availability Monitoring component (iPAMc) 433 is primarily responsible for one or more of the following: monitoring availability of iPool data content, managing access for iPool data content, managing alias nomenclature, ranking and managing multiple addressing, maintaining persistent meta-data definition availability, and data and data subset cache definitions for data. Depending upon system configuration and desired capabilities one, several, or all of these responsibilities may be optional. It may also optionally be responsible for data content backup for specified or often used data and multiple-content addressing for specified or often used data. hi an exemplary embodiment, an iPool Availability Monitoring component (iPAMc)

433_contains or comprises a set of software instructions for Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; iPool Availability Monitoring interface; and Pool boundary protocol components. A set of Pool boundary protocol definitions are included, which provide automated and/or interactive methods and processes including availability monitoring for iPool data content; access management for iPool data content; nomenclature alias management; multiple addressing ranking and management; maintenance of persistent meta-data definition availability; and data and data subset cache definitions for data including but not limited to specified Intelligent Object data; Intelligent Object data content; offline Intelligent Object data; and for data including but not limited to user defined; often used; and recently used. An additional set of Pool boundary protocol definitions may be provided which enable or provide automated and/or interactive methods and processes including data content backups for specified or often used data and multiple-content addressing for specified or often used data. In an exemplary embodiment, the iPool Availability Monitoring component (iPAMc)

433 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the iPool Availability Monitoring component comprised as a module within an information technology platform using object-oriented data structures.

iPool Availability Monitoring Interface (iPAMi) 434 The iPool Availability Monitoring interface (iPAMi) 434 is primarily responsible for detecting and extracting direct information required for availability monitoring, such as may be provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, and/or other components, and/or interfaces. The iPAMi 434 may also be responsible for routing information derived from the iPool Availability Monitoring component directly to the Intelligent Object Pool 204, iPools 155, and components and access interfaces. It may further optionally be responsible for providing the iPool Availability Monitoring component activity information to access interfaces and components as required for utility. The utility desired may for example include one or more of: synchronization of component information interchange, activity recordation of both the component information interchange and activity, auditing of the component information interchange and activity, validation of the component information interchange and activity, or other utility that may be desired and provided within the system and method.

In an exemplary embodiment, an iPool Availability Monitoring interface (iPAMi) 434 contains a set of software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following iPool Availability Monitoring component; Intelligent Object Pool access interfaces; Intelligent Object Handler 202 and Intelligent Objects. Methods and processes are provided, which detect and extract direct information required for availability monitoring, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations and other data- enabling information; provided directly to the iPool Availability Monitoring component. Additionally, methods and processes are provided, which route information derived from the iPool Availability Monitoring component directly to the Intelligent Object Pool 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of the iPool Availability Monitoring component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity. In an exemplary aspect, the iPool Availability Monitoring interface (iPAMi) 434 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the iPool Availability Monitoring interface comprised as a module within an information technology platform using object-oriented data structures.

iPool Exchange Protocol Component (iPEPc) 435

The iPool Exchange Protocol Component (iPEPc) 435 is primarily responsible for defining iPool ownership status; defining iPool ownership privileges and parameters; and for providing detailed definitions regarding criteria for data and/or data attribute or other information exchange. The iPEPc 435 may also be responsible for managing user ownership, user ownership recordation, authentication and permission or denial of iPool access requests, and other administrative functions.

In an exemplary embodiment, an iPool Exchange Protocol component (iPEPc) 435 contains a set of software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; iPool

Exchange Protocol interface; and Pool boundary protocol components. A comprised set of Pool boundary protocol definitions provide automated and/or interactive methods and processes including secure and interactive definition of iPool ownership status; definition of iPool ownership privileges and parameters; and detailed definition regarding criteria for exchange, including protocols and/or algorithms for Intelligent Object data attribute access; protocols and/or algorithms for such as ownership, licensing, and subscriptions; protocols and/or algorithms for such as exchange charges, and royalties; protocols and/or algorithms for exchange accounting; and account definitions. Additionally, a set of Pool boundary protocol definitions are comprised which provide automated and/or interactive methods and processes including user ownership management user ownership recordation; authentication and permission or denial of iPool access requests; according to correspondence of user ownership verification to comprised definitions such as for access, routing and processing; user exchange activity history provided by an interface to an external Intelligent Object Handler 202; data attribute access and linking activities; ownership, licensing, and subscription status; fees, charges and royalty status; including previewing of fees, charges and/or royalty terms and conditions according to proposed queries and/or user commands. In an exemplary embodiment, the iPool Exchange Protocol component (iPEPc) 435 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Exchange ProtocoJ component is optionally but advantageously comprised as a module within an information technology platform using object-oriented data structures.

iPool Exchange Protocol Interface (iPEPi) 436

The iPool Exchange Protocol Interface (iPEPi) 436 is primarily responsible for detecting and extracting direct information required for exchange protocols, provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, and various components and access interfaces. The iPool Exchange Protocol Interface (iPEPi) 436 may additionally be responsible for routing information derived from the iPool Exchange Protocol component directly to the Intelligent Object, Intelligent Object Handler 202, Pool 154 and iPools 155, components and access interfaces. It may further optionally be responsible for providing access and/or other control for information interchange to and from the Intelligent

Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. It may additionally be responsible for providing iPool Exchange Protocol component activity information to access interfaces and components as required for utility. The utility required or otherwise provided it not required, may for example include one or more of the following: synchronization of the component information interchange, activity recordation of the component information interchange and activity, auditing of the component information interchange and activity, validation of the component information interchange and activity, and combinations thereof.

In an exemplary embodiment, an iPool Exchange Protocol interface (iPEPi) 436 contains a set of software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following iPool Exchange Protocol component; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for exchange protocols, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including one or more of Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data- enabling information; provided directly to the iPool Exchange Protocol component. Additionally, methods and processes are provided, which route information derived from the iPool Exchange Protocol component directly to the Intelligent Object, Intelligent Object Handler 202, Pool 154 and iPools 155, components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object

Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of iPool Exchange Protocol component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity.

In an exemplary embodiment, the iPool Exchange Protocol interface (iPEPi) 436 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Exchange Protocol interface optionally comprises a module within an information technology platform using object-oriented data structures.

Object Integrity Assessment Component (OIAc) 437

The Object Integrity Assessment Component (OIAc) 437 is primarily responsible for the application of comprised methods and processes to Intelligent Object state histories and/or data content status, such as for example data checksums; and review of Intelligent Object state histories in order to provide one or more of auditing, security, validation, and quality assurance/quality control. It may also be responsible^, for providing alerts regarding Intelligent Object integrity violation status and alerts regarding processes that may or will violate Intelligent Object integrity, and optionally for activating an interface for the alert and optionally providing processing methods and/or cancellation of the processes for which the alert was generated.

In an exemplary embodiment, an object integrity assessment component (OIAc) 437 contains a set of software instructions comprising pool boundary protocols methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following unified presentation layer; iPool Integrity

Assessment interface; and other Pool boundary protocol components. A set of Pool boundary protocol definitions are included, which provide automated and/or interactive methods and processes including assessment of Intelligent Object and data content integrity based on techniques including but not limited to iPool checksums; and application of comprised methods and processes to iPool histories and status, including auditing; security; validation; and quality assurance/quality control. Additionally, a set of Pool boundary protocol definitions are included, which provide automated and/or interactive methods and processes including alerts regarding iPool integrity violation status; alerts regarding processes that may or will violate iPool integrity; and activation of an interactive user interface providing a description of the alert and providing optional processing methods and/or cancellation of the processes.

In an exemplary aspect, the Object integrity assessment component comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Object integrity assessment component comprised as a module within an information technology platform using object-oriented data structures.

Object Integrity Assessment Interface (OIAi) 438

The Object Integrity Assessment Interface (OIAi) 438 is primarily responsible for detecting and extracting direct information required for object integrity assessment provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155 and components and access interfaces; where the information may include but not be limited to

Intelligent Object data content accessed via vector pointers, meta-data indices, meta-data for content information, attribute information, relationship information, protocols, ontologies, annotations, and other data-enabling information provided to the Object integrity assessment component. It may also be responsible for routing information derived from the Object integrity assessment component directly to the Intelligent Object, Intelligent Object Handler

202, Pool and iPools 155, components and access interfaces. It may further be responsible for providing access control for information interchange to and from the Intelligent Objects,- Intelligent Object Pool 204, iPools 155, components and interfaces. It may additionally be responsible for providing object integrity assessment component activity information to access interfaces and components as required for utility. Such utility may for example include but not be limited to synchronization of the component information interchange, and activity recordation of the component information interchange and activity, auditing of the component information interchange and activity, validation of the component information interchange and activity, and combinations thereof. In an exemplary embodiment, an Object integrity assessment interface "(OIAi) 438 contains a set of software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Object integrity assessment component; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for object integrity assessment provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Object integrity assessment component.

Additionally, methods and processes are provided, which route information derived from the Object integrity assessment component directly to the Intelligent Object, Intelligent Object Handler 202, Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object

Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Object integrity assessment component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity. hi an exemplary aspect, the iPool Object integrity assessment interface (OIAi) 438 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Object integrity assessment interface comprised as a module within an information technology platform using object-oriented data structures.

iPool Integrity Assessment Component (iPIAc) 439

The iPool Integrity Assessment Component (iPIAc) 439 is primarily responsible for assessment of Intelligent Object and data content integrity, such as assessing intelligent object and data content integrity using iPool checksums, and iPool related auditing, security, validation, and quality assurance/quality control. It may also be responsible for generating and/or processing alerts regarding iPool integrity violation status, alerts regarding processes that may or will violate iPool integrity, and activation of a user interface for identifying the nature of the alert and presenting options for processing the alert and or the process generating the alert.

In an exemplary embodiment, an iPool Integrity Assessment component 439 contains a set of software instructions comprising Pool Boundary Protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; iPool Integrity Assessment interface; and Pool Boundary Protocol components. A set of Pool Boundary

Protocol definitions are comprised, which provide automated and/or interactive methods and processes including assessment of Intelligent Object and data content integrity based on techniques including but not limited to iPool checksums; and application of comprised methods and processes to iPool histories and status, including auditing; security; validation; and quality assurance/quality control. Additionally, a set of Pool Boundary Protocol definitions are comprised, which provide automated and/or interactive methods and processes including alerts regarding iPool integrity violation status; alerts regarding processes that may or will violate iPool integrity; and activation of an interactive user interface providing a description of the alert and providing optional processing methods and/or cancellation of the processes. In an exemplary embodiment, the iPool Integrity Assessment component (iPIAc) 439 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Integrity Assessment component comprises a module within an information technology platform that optionally uses object-oriented data structures.

iPool Integrity Assessment Interface (iPIAi) 440

The iPool Integrity Assessment Interface (iPIAi) 440 is primarily responsible for detecting and extracting direct information used for iPool integrity assessment provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, and components and access interfaces, and provided directly to the iPool Integrity Assessment component. The information may include or be selected from (but not limited to) the set of information consisting of Intelligent Object data content accessed via vector pointers, metadata indices, including meta-data for content information attribute information, relationship information, protocols, ontologies, annotations, and other data-enabling information. The iPool Integrity Assessment Interface (iPIAi) 440 may also be responsible for routing information derived from the iPool Integrity Assessment component directly to the Intelligent

Object, Intelligent Object Handler 202, Pool and iPools 155, and components and access interfaces.

In an exemplary embodiment, an iPool Integrity Assessment interface (iPIAi) 440 contains a set of software instructions comprising Pool boundary protocols, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following iPool Integrity Assessment component; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for iPool integrity assessment provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the iPool Integrity Assessment component.

Additionally, methods and processes are provided, which route information derived from the iPool Integrity Assessment component directly to the Intelligent Object, Intelligent

Object Handler 202, Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of iPool Integrity Assessment component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation o the component information interchange and activity. In an exemplary aspect, the iPool Integrity Assessment interface (iPIAi) 440 comprised as a module within an information technology platform for Intelligent Objects, i an optional aspect, the iPool Integrity Assessment interface comprised as a module within an information technology platform using object-oriented data structures.

Meta-data Indices, Methods, Procedures, and Processes

The meta-data indices are primarily responsible for enabling Intelligent Objects to communicate via data-enabling meta-data algorithms.

Embodiments of the meta-data indices and meta-data indices associated methods, procedures, and processes defined herein comprise the components and access interfaces defined and described in detail below, which enable Intelligent Objects to communicate via data-enabling meta-data algorithms, which include for example data object attribute definition, attribute linking, access optimization, routing optimization and processing optimization. Meta-data indices include modules comprising components and access interfaces for automated, semi-automated, and/or manual or interactive meta-data indexing, dynamic meta-data linking, active object-to-object query meta-data and iPool-to-iPool metadata indices protocols.

In one embodiment, the Meta-data Indices include one or more of the following modules: an iPool Meta-data Index module (iMDXm) , a Real-time Meta-data Link module (RMLm), an Object-to-Object Query module (OQMm), and an iPool-to-iPool Query module (PPQm). The iPool Meta-data Index module (iMDXm), comprising an iPool Meta-data Index component (iMDXc) 451, and an iPool Meta-data Index interface (iMDXi) 452, provides

Meta-data definitions for iPool data subsets based on global object meta-data index content such as data field information, data annotation and other existing meta-data information further defined and described below.

The Real-time Meta-data Link component (RMLc) 453, provides for relevant data access based on query parameters and Intelligent Object meta-data index based on global object meta-data index content such as data fields, data annotation and other existing metadata information further defined and described below. The Object-to-Object Query component (OQMc) 455, provides for query optimization and data-enabled parallel processing based on data object intercommunication regarding query parameters and global object meta-data index content such as data fields, data annotation and other existing meta-data information further defined and described below.

The iPool-to-iPool Query component (PPQc) 457, provides for data-enabled parallel processing and query optimization based on data object intercommunication regarding query parameters and iPool data intercommunication, global object meta-data index content such as data fields, data annotation and other existing meta-data information provided by and interchanged between iPool Meta-data Indices as further defined and described below.

In an exemplary embodiment, a set of meta-data indices contain sets of software instructions that provide or enable definitions, methods, procedures and/or processes, and include bi-directional information interchange with components and access interfaces including but not limited to an external Intelligent Object Handler 202, Intelligent Object Pool 204, iPools 155, and Intelligent Objects. The meta-data indices definitions interact with the Intelligent Object Handler 202 and Intelligent Objects to acquire and direct information required for methods and processes including but not limited to Intelligent Object data definition, translation and integration; integration of analytical processes; and meta-data based optimization of queries and processing at the level of Intelligent Objects; and iPools 155; and optimized methods for Intelligent Object-to-Intelligent Object and iPool-to-iPool intercommunication; utilizing Intelligent Object meta-data and aggregated iPool meta-data applied to interactive presorting and exclusion algorithms, object clustering algorithms, metadata definition and linking modules; and object-to-object and iPool to iPool meta-data interaction definitions. In an optional aspect, the meta-data indices are comprised within an information technology platform using object-oriented data structures that include but are not limited to Intelligent Objects.

iPool Meta-data Index Component (iMDXc) 451 The iPool Meta-data Index Component (iMDXc) 451 is primarily responsible for enabling optimized result aggregation and real-time exclusion of irrelevant object data layers. It may also be responsible for the provision of meta-data definitions for iPool data subsets.

In an exemplary embodiment, an iPool Meta-data Index component (iMDXc) 451 contains a set of software instructions comprising meta-data indices methods and processes including bi-directional information interchange with components and access interfaces including but not limited to a Unified Presentation Layer; iPool Meta-data Index interface; and meta-data indices components to enable optimized result aggregation and real-time exclusion of irrelevant object data layers. A set of meta-data indices definitions, which provide automated and/or interactive methods and processes including provision of meta-data definitions for iPool data subsets; including but not limited to automatically provided and/or user-defined information regarding data subset content attributes; legacy data type, structure, and access dependencies; data ownership and access information; and data relationship information made available 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; data validation ranking; query optimization based on correspondence of query parameters to iPool Meta-data index content; provision of iPool meta-data information required for methods and processes including but not limited to iPool activation, iPool sorting, iPool-to-iPool queries, iPool data presentation and result generation.

In an exemplary embodiment, the iPool Meta-data Index component (iMDXc) 451 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Meta-data Index component optionally comprises a module within an information technology platform using object-oriented data structures.

iPool Meta-data Index Interface fiMDXT) 452

The iPool Meta-data Index Interface (iMDXi) 452 is primarily responsible for detecting and extracting direct information required for meta-data indices, provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, components, and access interfaces. In some embodiments the information includes or is selected from (but is not limited to) Intelligent Object meta-data indices including meta-data for content information, attribute information, relationship information, protocols, ontologies, annotations and other data-enabling information. Typically, the information is provided directly to the iPool Meta-data Index component. It may also be responsible for routing information derived from the iPool Meta-data Index component to the Intelligent Object Pool

204, iPools 155, components and/or access interfaces. It may further be responsible for controlling access for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, and/or components and interfaces; and/or for provision of the iPool Meta-data Index component activity information to access interfaces and components as required for desired utility. In an exemplary embodiment, an iPool Meta-data Index interface (iMDXi) 452 contains a set of software instructions comprising meta-data indices definitions, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following iPool Meta-data Index component; Intelligent Object Pool access interfaces; Intelligent Object Handler 202 and Intelligent Objects. Methods and processes are provided, which detect and extract direct information required for meta-data indices, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations and other data-enabling information; provided directly to the iPool Meta-data

Index component.

Additionally, methods and processes are provided, which route information derived from the iPool Meta-data Index component directly to the Intelligent Object Pool 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of the iPool Meta-data Index component activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, the iPool Meta-data Index interface (iMDXi) 452 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool Meta-data Index interface (iMDXi) 452 optionally comprises a module within an information technology platform using object-oriented data structures.

Real-time Meta-data Link component fRMLc) 453

The Real-time Meta-data Link component (RMLc) 453 is primarily responsible (along with real-time meta-data link interface (RMLi) 454 for linking ofthe Intelligent Object

(EVIO) 200 data according to: (i) their own meta-data definitions, (ii) their participation within data subset iPools, and (iii) optionally to other data access and/or applications definitions (e.g. other meta-data) regarding relationships and interdependencies; so that the data is organized automatically according to its characteristics, provides information to each data object regarding its position within the overall data environment, and provides a dynamically and automatically organized environment for optimal accessing and querying of data and optimized, functional interaction between heterogeneous data objects and applications.

The real-time meta-data link component (RMLc) 453 and interface (RMLi) 454 provide the functionality required for linking of the Intelligent Object (EVIO) 200 data according to their own meta-data definitions, according to their participation within data subset iPools and according to other useful data access and / or applications definitions regarding relationships and interdependencies commonly understood as meta-data. This provides for automated organization of the data according to its characteristics, provides information to each data object regarding its position within the overall data environment, and provides a dynamically and automatically organized environment for optimal accessing and querying of data and optimized, functional interaction between heterogeneous data objects and applications. h an exemplary embodiment, a Real-time Meta-data Link component (RMLc) 453 contains a set of software instructions comprising meta-data indices methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the unified presentation layer; real-time meta-data link interface

(RMLi) 454 and meta-data indices components.

A set of meta-data indices definitions provide automated and/or interactive methods and processes including detection, fielding and organization of meta-data presented via external components, access interfaces, application and user actions including automated and/or user-directed queries; commands and processing requests to provide automated and organized activation of methods and processes corresponding to the meta-data. These metadata definitions may include validation and integrity rankings; data attributes; annotations; definitions; tables; lists; addressing protocols; access and routing protocols; processing protocols; histories of query parameters presented and provide for optimized provision of relevant data access and activities based on correspondence of the query and/or processing request meta-data parameters to the pre-organized Intelligent Object (200) and iPool linking of said meta-data definitions. A set of methods and processes are advantageously provided which interact with a Real-time Meta-data Link interface, to provide updating of meta-data index linkages for optimization of information interchange between Intelligent Objects (EVIO) 200, and between Intelligent Objects (EVIO) 200, iPools 155, and related applications, components and interfaces. The information interchange is enabled for example as an object state engine (OSE) 208 included within the Intelligent Object Handler (IOH) 202; and a status management component (SMC) 1016 and object query interface (OQI) 1018 comprised within Intelligent Objects (EVIO) 200 which provide for direct comparison of data content accessed via vector subset pointers; as well as of meta-data information; and provision of the data content information and meta-data information for updating ofthe meta-data indices.

In an exemplary embodiment, the Real-time Meta-data Link component (RMLc) 453 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the Real-time Meta-data Link component (RMLc) 453 optionally comprises a module within an information technology platform using object-oriented data structures.

Real-time Meta-data Link interface (RMLi) 454

The Real-time Meta-data Link interface (RMLi) 454 is primarily responsible for detecting and extracting direct information required for meta-data linking and automated organization of Intelligent Objects according to criteria provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, components, access interfaces, and/or specific automated or user-directed queries or commands. It may also be responsible for routing information derived from the Real-time Meta-data Link component to the Intelligent Object Pool 204, iPools 155, and components and access interfaces. It may further be responsible for controlling access for information interchange to and from the Intelligent

Objects, Intelligent Object Pool 204, iPools 155, components and interfaces; and/or for the provision of the Real-time Meta-data Link component activity information to access interfaces and components as required for organization and optimization of processes.

In an exemplary embodiment, an Real-time Meta-data Link interface (RMLi) 454 contains a set of software instructions comprising meta-data index definitions and methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Real-time Meta-data Link component; other Intelligent Object Pool access interfaces; Intelligent Object Handler 202 and Intelligent Objects. Methods and processes are provided, which detect and extract direct information required for meta-data linking and automated organization of Intelligent Objects according to criteria provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces, and specific automated and / or user-directed queries or commands. The information required for organization of data and received by the real-time meta-data link interface (RMLi) includes for example Intelligent Object data content accessed via vector pointers; meta-data index definitions including metadata for content information, attribute information, and other relationship information; accessing, routing and exchange protocols; data ontologies; software routines comprising predefined experimental procedures; data annotations and other data-enabling information; and is provided directly to the Real-time Meta-data Link component.

Additionally, methods and processes are provided, which route information derived from the Real-time Meta-data Link component directly to the Intelligent Object Pool 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of the Real-time Meta- data Link component activity information to access interfaces and components as required for organization and optimization of processes such as for example synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity. hi an exemplary aspect, the Real-time Meta-data Link interface (RMLi) 454 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Real-time Meta-data Link interface comprised as a module within an information technology platform using object-oriented data structures.

Intelligent Object-to-Intelligent Object Query component (OOMc) 455

The Intelligent Object-to-Intelligent Object Query component (OQMc) 455 is primarily responsible for detailed mapping and integration of Intelligent Object meta-data and provides the organizational activities needed or desired for the real-time meta-data linking (RML and RMLi), and optionally for other activities. This mapping and integration may further provide for updating meta-data definitions for Intelligent Object(s), to enable components for meta-data linking and query optimization. It may also be responsible for Intelligent Object-to-Intelligent Object meta-data information interchange optimization. The Intelligent Object-to-Intelligent Object Query meta-data interface (OQMi) may also be responsible for providing information required for the real-time meta-data linking (RML) actions including direct meta-data to meta-data linking between objects, and meta-data information interchange corresponding to automated and/or user-directed queries.

In an exemplary embodiment, an Intelligent Object-to-Intelligent Object Query component (OQMc) 455, provides a set of software instructions comprising meta-data indices methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; Intelligent Object-to-Intelligent Object Query interface (OQMi) 456 and meta-data indices components.

The Object-to-Object Query meta-data index component (OQM) provides detailed mapping and integration of Intelligent Object meta-data and provides the organizational activities required for the real-time meta-data linking (RML and RMLi), as well as for other activities. Methods are comprised acquisition and provision of dynamically updated and/or user-defined meta-data definitions for each comprised Intelligent Object, to enable components for meta-data linking and query optimization; including but not limited to definitions for Intelligent Object state; Intelligent Object data and data content addressing; association; linking; weighting; sorting; ranking of such as attribute; annotation; structure; function; type; matrix definition; field mapping and vector pointers. These meta-data definitions for Intelligent Object-to-Intelligent Object information interchange comprise for example such as previously mentioned validation and integrity rankings; data attributes; annotations; definitions; tables; lists; addressing protocols; access and routing protocols; processing protocols; and histories of query parameters presented. This information may be provided via meta-data comprised within object data comprised within Intelligent Object data, as well as by various components and access interfaces. Processing is provided for Intelligent Object-to-Intelligent Object meta-data information interchange optimization; comprising organization of the Intelligent Object meta-data linking according to information including but not limited to content attributes; validation state; ranking; relationships; associations; and the like, and for query optimization; based on dynamic updating of the Intelligent Object organization and linking for information interchange; according to correspondence between the information and queries; query histories; commands; command histories; and/or other access, routing and processing actions. Additionally, the Intelligent Object-to-Intelligent Object Query meta-data interface (OQMi) provides information required for the real-time meta-data linking (RML) actions including direct meta-data to meta-data linking between objects; and meta-data information interchange corresponding to automated and/or user- directed queries.

In an exemplary embodiment, the Intelligent Object-to-Intelligent Object Query component (OQMc) 455 comprises a module within an information technology platform for

Intelligent Objects. In another embodiment, the Intelligent Object-to-Intelligent Object Query component (OQMc) 455 comprises a module within an information technology platform optionally using object-oriented data structures. Intelligent Obiect-to-Intelligent Object Query interface (OOMf) 456

The Intelligent Object-to-Intelligent Object Query interface (OQMi) 456 is primarily responsible for detecting and extracting direct information desired and/or required for object- to-object queries provided by the Intelligent Objects and their data content; Intelligent Object Pool 204, iPools 155, components, and access interfaces; where the information may include but is not limited to Intelligent Object data content accessed via vector pointers, meta-data indices (including meta-data for content information), attribute information; relationship information, protocols, ontologies, annotations and other data-enabling information. As with several of the other inventive interfaces, this information may advantageously be provided directly, in this case directly to the Intelligent Object-to-Intelligent Object Query component.

It may also be responsible for routing information derived from the Intelligent Object-to- Intelligent Object Query component to the Intelligent Object Pool 204, iPools 155, components and access interfaces; and/or, for providing access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces.

In an exemplary embodiment, an Intelligent Object-to-Intelligent Object Query interface (OQMi) 456 contains a set of software instructions comprising meta-data indices definitions, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Intelligent Object-to-Intelligent Object Query component (OQMc) 455; Intelligent Object Pool access interfaces; Intelligent Object Handler 202 and Intelligent Objects 200. Methods and processes are provided, which detect and extract direct information required for object-to- object queries provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations and other data-enabling information; provided directly to the Intelligent Object-to-Intelligent Object Query component.

Additionally, methods and processes are provided, which route information derived from the Intelligent Object-to-Intelligent Object Query component directly to the Intelligent

Object Pool 204; iPools 155; components and access interfaces. Automated and or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of the Intelligent Object-to-Intelligent Object Query component (OQMc) 455 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation ofthe component information interchange and activity; auditing ofthe component information interchange and activity; validation of the component information interchange and activity.

In an exemplary aspect, the Intelligent Object-to-Intelligent Object Query interface (OQMi) 456 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Intelligent Object-to-Intelligent Object Query interface (OQMi) 456 comprised as a module within an information technology platform using object-oriented data structures.

iPool-to-iPool Query component (PPQc) 457

The iPool-to-iPool Query component (PPQc) 457 is primarily responsible for query optimization based on provision of meta-data definitions for accessing, routing, and processing, of direct iPool-meta-data to iPool-meta-data information interchange, utilizing direct interchange of linked meta-data index information; corresponding to automated and/or user-directed queries and/or processing requests.

In an exemplary embodiment, an iPool-to-iPool Query component (PPQc) 457 contains a set of software instructions comprising meta-data indices methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; iPool-to-iPool Query interface ; and meta-data indices components. A set of meta-data indices definitions, which provide automated and/or interactive methods and processes including query optimization based on provision of meta-data definitions for accessing; routing and processing; of direct iPool meta-data-to-iPool meta-data information interchange; utilizing direct interchange of linked meta-data index information; corresponding to automated and/or user-directed queries and/or processing requests. A set of meta-data indices definitions, which provide automated and/or interactive methods and processes including EPool-to-IPool information interchange optimization based on organization of the Pool content and meta-data linking according to information including but not limited to content attributes; validation state; ranking; relationships; associations; and the like, and for query optimization based on dynamic updating of the IPool organization for information interchange according to correspondence between the meta-data information and queries; query histories; commands; command histories; and/or other access, routing and processing actions. A set of meta-data indices definitions, which provide automated and/or interactive methods and processes including query optimization based on user defined updating and management ofthe IPool organization for information interchange. In an exemplary aspect, the iPool-to-iPool Query component (PPQc) 457 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the iPool-to-iPool Query component (PPQc) 457 comprised as a module within an information technology platform 151 using object-oriented data structures.

iPool-to-iPool Query interface (PPOi) 458

The iPool-to-iPool Query interface (PPQi) 458 is primarily responsible for detecting and extracting direct information desired or required for iPool-to-iPool queries provided by the Intelligent Objects 200 and their data content, Intelligent Object Pool 204, iPools 155, components, and access interfaces; where the information may include but not limited to one or more of meta-data indices including meta-data for content information, attribute information, relationship information, protocols, ontologies, annotations and other data- enabling information; provided directly to the iPool-to-iPool Query component. It may also be responsible for routing information derived from the iPool-to-iPool Query component (PPQc) 457 directly to the Intelligent Object Pool (IOP) 204, iPools 155, components and access interfaces. ha an exemplary embodiment, an iPool-to-iPool Query interface (PPQi) 458 contains a set of software instructions comprising meta-data indices definitions, methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following iPool-to-iPool Query component (PPQc) 457;

Intelligent Object Pool access interfaces; Intelligent Object Handler 202 and Intelligent Objects 200. Methods and processes are provided, which detect and extract direct information required for iPool-to-iPool queries provided by the Intelligent Objects 200 and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to meta-data indices; including meta-data for content information; attribute information; relationship information; protocols; ontologies; annotations and other data-enabling information; provided directly to the iPool-to-iPool Query component.

Additionally, methods and processes are provided, which route information derived from the iPool-to-iPool Query component (PPQc) 457 directly to the Intelligent Object Pool

(IOP) 204; iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects 200, Intelligent Object Pool 204 , iPools 155, components and access interfaces. Methods and processes also include provision of the iPool-to-iPool Query component (PPQc) 457 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity.

In an exemplary embodiment, the iPool-to-iPool Query interface (PPQi) 458 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the iPool-to-iPool Query interface (PPQi) 458 comprises an optional module within an information technology platform (ITP) 151 using object-oriented data structures 152.

Other modules, components, and interfaces 459, 460, 461, 462, 463, 464 may optionally be provided to satisfy particular application, data handling, processing, interfacing, or other needs as the system and architecture, as well as the method are readily expandable.

Exemplary Pool Content Access Architecture, Methods and Protocols

The Pool Content Access architecture, methods and protocols are primarily responsible for providing content access and presentation definitions for significance detection, meta-definition aggregation, and result aggregation, results generation, and relationship viewing. It may also provide for distributed learning and knowledge extraction.

The Pool Content Access architecture and Pool Content Access methods defined herein provide content access and presentation definitions for significance detection, result aggregation and results generation. Pool Content Access protocols include modules comprising components and access interfaces for aggregate meta-definition, result aggregation and relationship viewing. In optional and preferred embodiments, the Pool Content Access Protocols may include modules for distributed learning and knowledge extraction; such as Distributed Learning Engines (DLEc/DLEi) 479, 480 and Distributed Extraction Engine interfaces (DLEi) 480; and/or Knowledge Extraction Engines

(KEEc/KEEi) 481, 482 and Knowledge Extraction Engine interfaces (KEEi) 482.

Data Pool Content Access and Presentation Protocols 420

The Data Pool Content Access and presentation protocols 420 are primarily responsible for one or more of the following: providing meta-data index generation of aggregated Intelligent Object meta-data based on query parameters, significance detection of values located within the global data pool based on query parameters and global object metadata index content, organizing meta-data index based object relationships within individual iPools to allow for real-time result aggregation and real-time exclusion of irrelevant object data layers, and optionally distributed learning and knowledge extraction. In one embodiment of the inventive system, method, and computer program product, the Data Pool Content Access and presentation protocols, comprise: (a) an Aggregate Metadata Index Generator which provides for meta-data index generation of aggregated Intelligent Object meta-data, based on query parameters; (b) an Aggregate Real-time Significance Generator which provides for significance detection of values located within the global data pool based on query parameters and global object meta-data index content; (c) an Object Property-Selective Pre-sorting Tool referred to as the EVIO Zoom (EVIO-Z), which organizes meta-data index based object relationships within individual iPool s to allow for real-time result aggregation and real-time exclusion of irrelevant object data layers; and (d) in optional and advantageous embodiments, additional modules that provide for distributed learning and knowledge extraction.

In an exemplary embodiment, a set of Pool Content Access definitions contains sets of software instructions comprising methods and processes, including bi-directional information interchange with components and access interfaces including but not limited to the following: an external Intelligent Object Handler 202 (IOH); Intelligent Object Pools

(TOP) 204; iPools 155; and Intelligent Objects or Intelligent Molecular Objects 200. The Pool Content Access definitions include automated and/or user-directed processes, methods and algorithms including but not limited to real-time significance detection; results aggregation; methods application; relationship viewing; and report generation utilizing results generated by the Pool Content Access definition modules including by object-to-analysis tools interactions; real-time significant answer generation; result merging algorithms and clustering algorithms; utilizing calculation methods not limited to Jacquard coefficient; Dice coefficient; Jeffrey coefficient; Pearson coefficient; simple matching; product moment correlation coefficient; mean square difference and absolute difference; and clustering methods not limited to minimum variance; single, complete, average and weighted average linking; median method; centroid method; neighbor joining method; Fitch-Margoliash least square method and Fitch-Margoliash evolutionary clock method.

In advantageous and optional embodiments, modules including one or more of learning and knowledge extraction algorithms are provided. In another embodiment, the Pool Content Access definitions are provided within an information technology platform (ITP) 151 using object-oriented data structures 152.

Aggregate Meta-data Index Generator component (aMDXc) 471

The Aggregate Meta-data Index Generator component (aMDXc) 471 is primarily responsible for providing Pool Content Access enabling bi-directional information interchange with components and access interfaces, and providing automated and/or interactive methods and processes including generation of meta-data definitions for iPool data subsets.

In an exemplary embodiment, an Aggregate Meta-data Index Generator component (aMDXc) 471 contains a set of software instructions comprising Pool Content Access enabling bi-directional information interchange with components and access interfaces including but not limited to Unified Presentation Layer; Aggregate Meta-data Index Generator interface (aMDXi) 472; and Pool Content Access components. Additionally, a set of Pool Content Access definitions are comprised which provide automated and/or interactive methods and processes including generation of meta-data definitions for iPool data subsets; including but not limited to automatically provided and/or user-defined information regarding

Intelligent Object and iPool data Intelligent Object data content accessed via vector pointers and meta-data index definitions; including meta-data for iPool subset attributes; annotations; protocols; ontologies; content attributes; data type, structure, and access dependencies; ownership and access information; relationship information; activity ranking; significance ranking and validation ranking.

For meta-data index generation, the information is organized, sorted and ranked according to comprised algorithms for determination of such as not limited to structure, function, validation, dependency, similarity; association; contiguity; proximity, weight and frequency, for such as query optimization requirements, based on correspondence of submitted query parameters; and query histories; to iPool Meta-data index content; and iPool access organization. Generation of iPool meta-data information required for methods and processes including but not limited to iPool activation; iPool sorting; iPool-to-iPool queries; iPool data presentation and result generation.

In an exemplary aspect, the Aggregate Meta-data Index Generator component (aMDXc) 471 comprised as a module within an information technology platform for

Intelligent Objects. In an optional aspect, the Aggregate Meta-data Index Generator component (aMDXc) 471 comprised as a module within an information technology platform using object-oriented data structures.

Aggregate Meta-data Index Generator interface (aMDXi) 472

The Aggregate Meta-data Index Generator interface (aMDXi) 472 is primarily responsible for detecting and extracting direct information required for meta-data index generation, provided by the Intelligent Objects 200 and their data content; Intelligent Object

Pool 204, iPools 155, components and access interfaces. It may also be responsible for routing information derived from the Aggregate Meta-data Index Generator component (aMDXc) 471 directly to the Intelligent Object 200, Intelligent Object Handler 202, Pool, and iPools 155, components and access interfaces.

In an exemplary embodiment, an Aggregate Meta-data Index Generator interface (aMDXi) 472 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following Aggregate Meta-data Index Generator component (aMDXc) 471; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for meta-data index generation, provided by the Intelligent Objects 200 and their data content; Intelligent

Object Pool 204 ; iPools 155;components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Aggregate Meta-data Index Generator component (aMDXc) 471.

Additionally, methods and processes are provided, which route information derived from the Aggregate Meta-data Index Generator component (aMDXc) 471 directly to the Intelligent Object 200, Intelligent Object Handler 202 , Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the

Intelligent Objects 200, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Aggregate Meta-data Index Generator component (aMDXc) 471 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity.

In an exemplary aspect, the Aggregate Meta-data Index Generator interface (aMDXi) 472 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Aggregate Meta-data Index Generator interface (aMDXi)

472comprised as a module within an information technology platform using object-oriented data structures.

Aggregate Real-time Significance Generator component (aRSGc) 473 The Aggregate Real-time Significance Generator (aRSGc) 473 is primarily responsible for the application of algorithms and procedures, such as applications and procedures that perform normalized comparison, generate correlation and significance detection information including but not limited to Intelligent Object properties, data content values, and meta-data index content; based on query parameters. It may also be responsible for organizing or enabling organization of Intelligent Object and iPools. In an exemplary embodiment an Aggregate Real-time Significance Generator component (aRSGc) 473 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer, Aggregate Real-time Significance Generator interface (aRSGi) 474 and Pool Content Access components. Additionally a set of Pool Content Access definitions are included, which provide automated and/or interactive methods and processes including application of algorithms for normalized comparison; correlation and significance detection information including but not limited to Intelligent Object properties; data content values and meta-data index content; based on parameters fielded by all valid queries. The Aggregate Real-time Significance Generator enables organization of Intelligent Object(s) and iPools, utilizing methods and processes including assembly; ranking; classification; and/or tabulation of Intelligent Objects; according to comparison of normalized parameters such as data content values; and meta-data index properties provided by direct Intelligent Object-to-Intelligent Object; and iPool-to-iPool information interchange; via addressing including but not limited to vector subset pointing; meta-data index addressing; and activated by such as query submissions, user preference rules and/or viewing instructions.

The Aggregate Real-time Significance Generator component (aRSGc) 473 enables organization of data utilizing methods and processes including assembly; ranking; classification; and/or tabulation of Intelligent Objects; based on the significance of results generated by external applications; components; access interfaces; and activated by query submissions, user preference rules and/or viewing instructions.

In an exemplary embodiment, the Aggregate Real-time Significance Generator component (aRSGc) 473 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the Aggregate Real-time Significance Generator component optionally comprises a module within an information technology platform using object-oriented data structures.

Aggregate Real-time Significance Generator interface (aRSGi) 474

The Aggregate Real-time Significance Generator interface (aRSGi) 474 is primarily responsible for detecting and extracting direct information required for significance generation provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, components and access interfaces. It may also be responsible for information derived from the Aggregate Real-time Significance Generator component (aRSGc) 473 directly to the Intelligent Object Pool 204, iPools 155, components, and access interfaces; and for access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. It may further be responsible for aggregate real-time or near-real-time significance generation activity information to access interfaces and components as required for utility.

In an exemplary embodiment, an Aggregate Real-time Significance Generator interface (aRSGi) 474 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following Aggregate Real-time Significance Generator component (aRSGc) 473; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200 . Methods and processes are provided, which detect and extract direct information required for significance generation provided by the Intelligent Objects and their data content; Intelligent Object Pool

204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Aggregate Real-time Significance Generator component.

Additionally, methods and processes are provided, which route information derived from the Aggregate Real-time Significance Generator component (aRSGc) 473 directly to the Intelligent Object Pool 204; iPools 155; components; and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object

Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Aggregate Real-time Significance Generator component (aRSGc) 473 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation ofthe component information interchange and activity; auditing ofthe component information interchange and activity; validation of the component information interchange and activity.

In an exemplary aspect, the Aggregate Real-time Significance Generator interface (aRSGi) 474 comprised as a module within an information technology platform for Intelligent Objects. In an optional aspect, the Aggregate Real-time Significance Generator interface (aRSGi) 474 comprised as a module within an information technology platform using object-oriented data structures.

Result Aggregation Engine Component (RAEc) 224, 475 The Result Aggregation Engine Component (RAEc) 224, 475 is primarily responsible for aggregation of results provided by the aggregate significance generator module based on input or generated parameters and/or inquiries, such as for example queries, commands, processing requests, alerts, updates, and reports; such as may be presented by an object handler such as by Intelligent Object Handler 202. It may also be responsible for generating customized meta-data profiles, and/or generating aggregated meta-data outputs and updates such as iPool definition updates, iPool relationship definitions, Intelligent Object definition updates, and Intelligent Object relationship definitions pertaining to Intelligent Object and iPool properties and values provided by the Aggregate Significance Generator module. It may also be responsible for results assembly, validation, ranking, classification, and tabulation; for example, according to significance and relationship information provided by the Aggregate Significance Generator module.

In an exemplary embodiment, a Result Aggregation Engine component (RAEc) 224, 475, which contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; Result

Aggregation Engine interface (RAEϊ) 225, 476, and Pool Content Access components. The Result Aggregation Engine Component is responsible for aggregation of results provided by the Aggregate Significance Generator module, according to parameters submitted via automated; and/or user-directed queries; commands; processing requests; alerts; updates; and reports; and presented via an external Intelligent Object Handler 202; and to generate customized meta-data profiles; and/or generate aggregated meta-data outputs and updates such as iPool definition updates; iPool relationship definitions; Intelligent Object definition updates; and Intelligent Object relationship definitions pertaining to Intelligent Object and iPool properties and values provided by the Aggregate Significance Generator module. A set of methods and processes, which provide results assembly, validation, ranking, classification, and tabulation; according to significance and relationship information provided by the Aggregate Significance Generator module.

In an exemplary embodiment, the Result Aggregation Engine component (RAEc) 475 comprised as a module within an information technology platform for Intelligent Objects. hi another embodiment, the Result Aggregation Engine component (RAEc) 475 comprises a module within an information technology platform using object-oriented data structures. Result Aggregation Engine Interface (RAEi) 225. 476

The Result Aggregation Engine Interface (RAEi) 225, 476 is primarily responsible for detecting and extracting direct information required for result aggregation, provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, components, and access interfaces. It may also be responsible for routing information derived from the Result Aggregation Engine component (RAEc) 475 to the Intelligent Object, Intelligent Object Handler, Pool and iPools, and components and access interfaces. It may further be responsible for access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces.

In an exemplary embodiment, a Result Aggregation Engine interface (RAEi) 476 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following Result Aggregation Engine component (RAEc) 475; Intelligent Object Pool access interfaces; Intelligent Object

Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for result aggregation, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Result Aggregation Engine component (RAEc) 475. Additionally, methods and processes are provided, which route information derived from the Result Aggregation Engine component (RAEc) 475 directly to the Intelligent Object, Intelligent Object Handler 202, Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Result Aggregation Engine component (RAEc) 224,475 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation ofthe component information interchange and activity. In an exemplary embodiment, the Result Aggregation Engine interface (RAEi)

225, 476 comprised as a module within an information technology platform for Intelligent Objects. fn an optional aspect, the Result Aggregation Engine interface (RAEi) 476 optionally comprises a module within an information technology platform using object- oriented data structures.

IMO Zoom component (TMO-Zc) 477

The EVIO Zoom component (EVIO-Zc) 477 is primarily responsible for access, extraction, processing and addressing of information including of graphical viewing information; including but not limited to data relationship information and overviews, self- organizing maps, similarity clustering, dendrograms, charts, tables, and/or additional graphical representations, and combinations thereof. It may also be responsible for enabling thumbnail viewing of Intelligent Object data content, iPool data content, according to correspondence of data content attributes to automated and/or user-directed queries and/or commands. It may further be responsible for enabling graphical pre-sorting and sorting of Intelligent Object data content, and iPool data content, according to correspondence of data content attributes to automated and/or user-directed queries and/or commands.

An EVIO Zoom component (TMO-Zc) 477 contains a set of software instructions comprising Pool Content Access methods and processes including but not limited to bidirectional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer; EVIO Zoom interface (TMO-Zi) 478; and Pool Content Access components. Comprised methods and processes also include access; extraction; processing and addressing of graphical viewing information; including but not limited to data relationship information and overviews; self-organizing maps, similarity clustering; dendrograms; charts; tables; and/or additional graphical representations. Additionally, a set of instructions enable thumbnail viewing of such as Intelligent Object data content; iPool data content; according to correspondence of data content attributes to automated and/or user-directed queries and/or commands. Additionally, a set of instructions enable user-directed and/or automated graphical pre-sorting and sorting of such as the Intelligent Object data content; iPool data content; according to correspondence of data content attributes to automated and/or user-directed queries and/or commands. The information being accessed from and routed to the Intelligent Object data; Intelligent Object

Pool 204 data; iPool data; modules, components, and access interfaces.

Example of Code for Clustering of Intelligent Object Data within an IOP

The following example df computer program software code for clustering of Intelligent Object data within the Intelligent Object Pool 204 for viewing and analysis utilizes content attributes and attribute flags of the corresponding objects. The Cluster Dialog box, which is evoked below, allows for selection of the adequate calculation method for the similarity coefficient (e.g. Jacquard, Dice, Jeffrey, Pearson, and/or other algorithms or procedures as are known in the art), the parameter the clustering is performed upon (e.g. spot intensity, spot volume, spot color, spot position, band position, band concentration, band molecular weight, band iso-electric point, and the like), and the method for clustering applied to display numerically and/or graphically the data relationships (such as Minimum Variance [MVAR], Minimum Variance Hierarchy [MNVR], Single Link [SLNK], Complete Link [CLNK], Average Link [ALNK], Weighted Average Link [WLNK], Median Method, Centroid Method, Minimum Spanning Tree [MST], Neighbor- Joining Method, FMLS, FMLS with Evolutionary Clock and the like). User preferred clustering parameters can be saved and reloaded to be applied to similar data objects consequently.

Table I. Exemplary computer program code for performing the procedure

Table I. Exemplary computer program code for performing an embodiment of the procedure.

// CClusterDlg dialog class CClusterDlg : public Cdialog

{

// Construction public:

CClusterDlg(CWnd* Parent = NULL); //standard constructor

//Dialog Data

//{{AFX_DATA(CClusterDlg) enum { IDD = IDDjCLUSTER }; int m iCalibMethod;

//}}AFXJ)ATA

// Overrides

// ClassWizard generated virtual function overrides

//{{AFX_VIRTUAL(CClusterDlg) protected: virtual void DoDataExchange(CDataExchange * pDX); // DDX/DD V support

//jjAFX IRTUAL

//Implementation protected:

// Generated message map functions //{{AFX_MSG(CClusterDlg) //}}AFXJΛSG DECLARE_MESSAGE_ MAP() // CClusterDlg dialog

CClusterDlg: :CclusterDlg(CWnd* pParent /*=NULL*/) : CDialog(CClusterDlg::IDD, pParent)

{

//{{AFX_DATA_INIT(CclusterDlg) mjiCalibMethod = 0;

//}}AFX_DATAJNIT

void CClusterDlg: :DoDataExchange(CDataExchange * pDX)

{

//{{AFXJDATAjMAP(CclusterDlg)

DDX_CBIndex(pDX, IDCjCALIBMETHOD, mjiCalibMethod);

//}}AFX_DATA_MAP

}

BEGIN_MESSA GEJΛAP (CClusterDlg, Cdialog) //{{AFX_MSG_MAP '(CClusterDlg) //}}AFX_MSG_MAP

ENDJ4ESSA GE_MAP()

BEGIN_MESSAGE_MAP(CcontentAttribDlg, CDialog) //{{AFX_MSG_MAP(CcontentAttribDlg) //}}AFX_MSG_MAP

END_MESSAGEJvIAP()

CContentAttribDlg:: CcontentAttribDlg(CW7id* pParent /*=NULL */) : CDialog(CcontentAttribDlg::IDD, pParent)

{

//{{AFXJDATAJNIT(CcontentAttribDlg)

//NOTE: the ClassWizard will add member initialization here

//}}AFX_DATAJNIT

}

void CcontentAttribDlg: :DoDataExchange(CDataExchange * pDX)

{ //{{AFX DATAJIAP(CcontentAttribDlg)

DDX_Control(pDX, IDC TREEl, mJreeContentAttrib);

//}}AFX_DATAJΛAP

}

BOOL CcontentAttribDlg: :OnInitDialog()

parent = mJreeContentAttrib. GetParentltem(parent); parent = mJreeContentAttrib.GetParentltem arent); parent = mJreeContentAttrib. GetParentltem arent) ;

} if(βag & 32)

{ parent — mJreeContentAttrib. GetParentItem(parent); parent = mJreeContentAttrib. GetParentltem(parent) ; parent — mJreeContentAttrib. GetParentItem(parent) ; parent = mJreeContentAttrib.GetParentItem(parent);

}

} } } (End Code Example)

hi an exemplary embodiment, the EVIO Zoom component (IMO-Zc) 477 comprises a module within an information technology platform for Intelligent Objects. In another embodiment, the EVIO Zoom component (TMO-Zc) 477 optionally comprises a module within an information technology platform using object-oriented data structures.

IMO Zoom interface (TMO-Zi) 478

The EVIO Zoom interface (IMO-Zi) 478 is primarily responsible for detection of graphical content provided by the Intelligent Objects 200 and their data content, Intelligent

Object Pool 204, iPools 155, components and access interfaces; accessing and routing of the information via such means as vectorized data field pointers, and meta-data index definitions, and provided by the EVIO Zoom component. It may also be responsible for routing graphical information derived from the EVIO Zoom component (EVIO-Zc) 477 to the Intelligent Object Pool 204, iPools 155, components, and access interfaces (interfaces or module/component interfaces). It may further be responsible for providing and/or enabling information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces.

An EVIO Zoom interface (IMO-Zi) 478 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following EVIO Zoom component (IMO-Zc) 477; Intelligent Object Pool access interfaces; Intelligent Object Handler 202 ; and Intelligent Molecular Objects 200. Methods and processes are provided comprising detection of graphical content provided by the Intelligent Objects 200 and their data content; Intelligent Object Pool 204 ; iPools 155; components; and access interfaces; accessing and routing of the information via such as vectorized data field pointers; and meta-data index definitions; and provided by the EVIO Zoom component 477.

Additionally, methods and processes are provided, which route graphical information derived from the EVIO Zoom component (IMO-Zc) 477 to the Intelligent Object Pool 204; iPools 155; components; and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of EVIO Zoom component (IMO-Zc) 477 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, the EVIO Zoom interface (TMO-Zi) 478 comprises a module within an information technology platform 151 for intelligent Objects. In another embodiment, the EVIO Zoom interface (EVIO-Zi) 478 comprises a module within an information technology platform using object-oriented data structures.

Distributed Learning Engine Component (DLEc) 479 The Distributed Learning Engine Component (DLEc) 479, when optionally present, is primarily responsible for knowledge extraction and is optionally provided in the inventive system, method, and computer program.

In one embodiment, a Distributed Learning Engine component (DLEc) 479 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces including but not limited to the following Unified Presentation Layer, Distributed Learning Engine interface (DLEi) 480 and Pool Content Access components. Methods and processes for knowledge extraction utilizing automated and/or user-directed interactive application of comprised protocols, functions and algorithms to information and actions including but not limited to user queries; automated queries; customized sets of queries; data objects such as the

Intelligent Object; data handlers such as the Intelligent Object Handler 202; data pools such as the Intelligent Object Pool 204; iPools 155; the global data entity; and/or data subsets therein. Methods and processes are provided for the automation of learning processes including but not limited to simulation; prediction, hypothesis generation, testing, result assessment and comparison; interactive result optimization and feedback; data and user workspace definition; assessment; organization; customization; data and user workspace relationship definition; assessment; organization; customization; and/or optimization of accessing, routing and processing protocols for user workspaces; Intelligent Objects; Intelligent Object Pools and iPools 155; utilizing a comprised set of Pool Content Access definitions, which may include but are not limited to Cross-reference clustering; Boolean network algorithms; Bayesian network algorithms; neural network algorithms; iterative learning algorithms; time series analysis algorithms; pattern matching algorithms; structure matching algorithms; and rule induction algorithms. Methods are provided for the application of the algorithms to the information to enable such as automated, dynamic and/or interactive iterative processing; significance detection; tabulation; validation; ranking; assembly; and/or other forms of distributed learning.

In another embodiment, the Distributed Learning Engine component (DLEc) 479 comprised as a module within an information technology platform for Intelligent Objects. In another embodiment, the Distributed Learning Engine component (DLEc) 479 optionally comprises a module within an information technology platform using object-oriented data structures.

Distributed Learning Engine Interface (DLEi) 480

The Distributed Learning Engine interface (DLEi) 480, when optionally present, is primarily responsible for detecting and extracting direct information required for distributed learning, provided by the Intelligent Objects and their data content, Intelligent Object Pool

204, iPools 155, components and access interfaces, and is optionally provided in the inventive system, method, and computer program.

In an optional embodiment, a Distributed Learning Engine interface (DLEi) 480 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following Distributed Learning Engine component (DLEc) 479; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for distributed learning, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Distributed Learning Engine component (DLEc) 479. Additionally, methods and processes are provided, which route information derived from the Distributed Learning Engine component (DLEc) 479 directly to the Intelligent Object, Intelligent Object Handler 202, Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Distributed Learning Engine component (DLEc) 479 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation of the component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, the Distributed Learning Engine interface (DLEi) 480 comprised as a module within an information technology platform for Intelligent Objects. In another exemplary embodiment, the Distributed Learning Engine interface comprises a module within an information technology platform optionally using object-oriented data structures.

Knowledge Extraction Engine component (KEEc) 481

The Knowledge Extraction Engine component (KEEc) 481, when optionally present, is primarily responsible for knowledge extraction utilizing automated and/or user-directed application of protocols, functions and algorithms to information and actions including but not limited to user queries, automated queries, customized sets of queries, data objects such as the Intelligent Object, data handlers such as the Intelligent Object Handler 202, data pools such as the Intelligent Object Pool 204, iPools 155, the global data entity, and/or data subsets therein. In an optional embodiment, a Knowledge Extraction Engine component (KEEc) 481, which contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces including but not limited to Unified Presentation Layer; Knowledge Extraction Engine interface (KEEi) 482; and Pool Content Access components. Methods and processes for knowledge extraction utilizing automated and/or user-directed interactive application of comprised protocols, functions and algorithms to information and actions including but not limited to user queries; automated queries; customized sets of queries; data objects such as the Intelligent Object; data handlers such as the Intelligent Object Handler 202; data pools such as the Intelligent Object Pool 204; iPools 155; the global data entity; and/or data subsets therein. Methods and processes are provided for the automation of knowledge extraction processes including but not limited to active data attribute searching, detection and extraction; similarity and significance assessment and comparison; hypothesis generation; report generation; interactive result optimization and feedback; data annotation and user workspace definition, assessment, organization and customization and/or optimization; data annotation and user workspace relationship definition, assessment, organization and customization and/or optimization of accessing, routing and processing protocols for user workspaces;

Intelligent Objects; Intelligent Object Pools and iPools 155; utilizing a comprised set of Pool Content Access definitions, which may include but are not limited to the following Cross- reference clustering; Boolean network algorithms; Bayesian network algorithms; neural network algorithms; iterative knowledge extraction algorithms; time series analysis algorithms; pattern matching algorithms;, structure matching algorithms; and rule induction algorithms. Methods are provided for the application of the algorithms to the information to enable such as automated, dynamic and/or interactive iterative processing; significance detection; tabulation; validation; ranking; assembly; and/or other forms of knowledge extraction. In an exemplary embodiment, the Knowledge Extraction Engine component (KEEc)

481 comprised as a module within an information technology platform for Intelligent Objects. In an optional embodiment, the Knowledge Extraction Engine component (KEEc) 481 comprised as a module within an information technology platform using object-oriented data structures.

Knowledge Extraction Engine interface (KEEP 482

The Knowledge Extraction Engine interface (KEEi) 482, when optionally present, is primarily responsible for detecting and extracting direct information required for knowledge extraction, provided by the Intelligent Objects and their data content, Intelligent Object Pool 204, iPools 155, components, and access interfaces; . provided directly to the Knowledge

Extraction Engine component (KEEc) 481. The information may include one or more of but not limited to Intelligent Object data content accessed via vector pointers, meta-data indices, including meta-data for content information, attribute information relationship information, protocols, ontologies, annotations, and other data-enabling information. hi an optional embodiment, a Knowledge Extraction Engine interface (KEEi) 482 contains a set of software instructions comprising Pool Content Access methods and processes including bi-directional information interchange with components and access interfaces of and/or including but not limited to the following Knowledge Extraction Engine component (KEEc) 481; Intelligent Object Pool access interfaces; Intelligent Object Handler 202; and Intelligent Molecular Objects 200. Methods and processes are provided, which detect and extract direct information required for knowledge extraction, provided by the Intelligent Objects and their data content; Intelligent Object Pool 204; iPools 155; components; and access interfaces; the information including but not limited to Intelligent Object data content accessed via vector pointers; meta-data indices; including meta-data for content information; attribute information relationship information; protocols; ontologies; annotations; and other data-enabling information; provided directly to the Knowledge

Extraction Engine component (KEEc) 481.

Additionally, methods and processes are provided, which route information derived from the Knowledge Extraction Engine component (KEEc) 481directly to the Intelligent Object, Intelligent Object Handler 202, Pool and iPools 155; components and access interfaces. Automated and/or interactive methods and processes are provided, including but not limited to access control for information interchange to and from the Intelligent Objects, Intelligent Object Pool 204, iPools 155, components and interfaces. Comprised methods and processes also include provision of Knowledge Extraction Engine component (KEEc) 481 activity information to access interfaces and components as required for utility including but not limited to synchronization of the component information interchange and activity recordation ofthe component information interchange and activity; auditing of the component information interchange and activity; validation of the component information interchange and activity.

In an exemplary embodiment, the Knowledge Extraction Engine interface (KEEi) 482 comprises a module within an information technology platform for Intelligent Objects.

In another embodiment, the Knowledge Extraction Engine interface (KEEi) 482 comprises a module within an information technology platform optionally using object-oriented data structures.

Through provision of the architecture, methods, and modules, the infrastructure is provided for secure, unified object storage and object-to-object and iPool-to-iPool query- based interaction, to allow for a comprehensive real-time analysis of otherwise inaccessible, inconsistent data sets. It is evident from the above description that the data pool architecture and methods described above allow for efficient real-time processing of terabytes of complex, multidimensional, interdependent data, thereby providing real-time answers to queries within heterogeneous data environments with high data density and dynamic application needs.

Embodiments of the Intelligent Object Pool 204 implemented as computer software program code may be compiled to run on any one or more of multiple platforms and/or operating system environments known in the art as well as those reasonably expected to develop in the future, including, but not limited to, UNLX and UNIX-based platforms and/or environments, Linux and Linux-based platforms and/or environment, Macintosh operating systems (such as OS 9 and OS 10) and Macintosh-based based platforms and/or environments, or any Windows platform and/or Windows-based platforms such as Microsoft Windows 98, ME, 2000, NT, XP and extensions and modifications thereof, and/or environment such as any Window 32-bit operating system, platform, or environment.

The hardware and system descriptions provided herein are intended define and describe the requirements for a specific exemplary embodiment, implemented for a 32-bit

Microsoft Windows environment. However, it will be appreciated that a broad class of general puφose computing systems may be utilized and that the inventive methods, procedures, and architectures are by-and-large hardware, operating system, and network or connectivity agnostic. With reference to illustration in FIG. 9, in a global, heterogeneous environment, data from diversified sources are functionally integrated via Intelligent Objects and their Intelligent Object Pool 204, utilizing automated access definition protocols, multiple alias integration and addressing, data field mapping and state management to allow for integrated data access, analysis and exchange utilizing distributed data content presented within the Client iPool.

The chart depicts user relationships to the data on database and iPool levels. In FIG. 9, the upper section of the diagram (the section that includes the labels "Client iPool", "Restricted", "Client Data", "Resources", and the like) depicts data within intranets, LANs and the like, while the lower, larger part of the diagram contains several different forms of public and/or otherwise web-accessible data sources. Other examples of data resources are depicted in the diagram and are merely exemplary and not limiting in any way.

With reference to FIG. 10, it represents another exemplary embodiment of a process model describing interactions of required or included modules for an exemplary embodiment ofthe Intelligent Object Pool 204. In this exemplary process model, data from a global data resource (or any part of a global data resource) are passed through an access interface, in this example an access interface having a security layer and a set of access and/or exchange protocols and integrity assessment procedures, to the Intelligent Objects. Lastly, the pathways involved in unified direct Intelligent-Object-to-Intelligent Object and iPool-to-iPool data interaction generate the real-time answer and pass it back through security to the Intelligent Object Handler 202.

By real time answer we generally mean an answer or results are received within a relatively short period of time so that a user inputting a query may wait for a response to the query and not find the wait objectionable to be contrasted with a batch processed query or other query that has significant waiting time. In many instances the results will be generated in less than a second so that there will be no apparent wait; however, for some queries the delay in receiving a response with results may be a few seconds, several seconds, and perhaps several minutes. The invention is not limited to any particular response time.

With reference to FIG. 11, there is illustrated a representation of the graphical user interface window and display screen image within the unified presentation layer displaying algorithms included for clustering of Intelligent Object data. In this example, a number of property panes showing dendrograms results are seen behind the clustering algorithms menu.

En this example, and in some of the examples and screen displays that follow, data from a local subset iPool of Intelligent Objects were queried against specific protein expressions based on 2-dimensional gel electrophoresis (2DE) data. During the real-time answer-finding process, object-to-object interactions are represented via a graphical iPool

Viewer (EVIO Zoom), which also accesses relevancy of individual result contributions to generate a unique, exact, relevant real-time answer.

With reference to FIG. 12, there is illustrated an example of an interface iPool Zoom viewer and displayed image for viewing iPool data relationships, utilizing implemented techniques, including for example techniques that include one or more of dendrograms and self-organizing maps (SOM). Attributes and interactions between individual Intelligent Object

(EVIO) data within the set of objects are outlined in the margins of this exemplary display.

With reference to FIG. 13, there is illustrated an example of an iPool Zoom interface for viewing iPool data relationships, utilizing Principal Components Analysis (PCA).

INTELLIGENT MOLECULAR OBJECT

The method described herein remedies problems and constraints identified in the Background by allowing interactive, Intelligent Object-based communication directly between functionally related attributes of heterogeneous data. This allows for comparison and extraction of all relevant content in a fast, unique and automated manner, within diverse network environments, without the need of upgrading or replacing current computer systems. The Intelligent Molecular Object technology provides a flexible global standard, which allows for seamless integration and real-time answers to complex, multidimensional and interdependent queries. Intelligent Molecular Object technology provides a framework for highly efficient scale-up and dynamically changing application needs in bioinformatics and the life sciences.

Methods are provided to define and describe a specific embodiment of architecture for Intelligent Object (EVIO) 200 data structures. Intelligent Objects contain hierarchical, multi-layered property panes (Property Panes) 1000 for unified user presentation and functional interactivity, as well as components (Components) 1002 and access interfaces (Interfaces) 1004 to provide data status management, self-organizing data, and parallel data- to-data information interchange and processing, within local computing environments and / or over heterogeneous global computing networks. This exemplary embodiment ofthe Intelligent Object (EVIO) 200 provides interactive, secure, property-driven functional access to and integration of data content queried, presented and analyzed, utilizing a variety of raw data sources, applications and analytical components.

More particularly, aspects and embodiments of the invention provide (among others) an Intelligent Object, advantageously enabled in software, provides methods for: (1) Data and user identification and status management, including:

• Unified presentation and global unique identification ofthe Intelligent Object;

• Identification, authentication and logging of users, sessions, and data content activity locally and / or over networks;

• Dynamic routing of root object data, meta-data and data content locally and / or over networks;

• Data status, data integrity and validation state alerting and management;

(2) Functional integration of, and access to, potentially diverse data over a variety of computing infrastructures, including:

• Functional content and attribute definition for database and application access and routing;

• Automated raw data matrix and matrix structure definition;

• Automated translation of multiple data types and dimensions for unified processing and analysis;

• Functional integration of multiple data types and dimensions for unified processing and analysis;

(3) Integration of multiple data types and dimensions for efficient and accurate multidimensional, parallel queries and analyses, including:

• Meta-data indexing and query optimization;

• Direct data-to-data information exchange; • Vectorized exchange of information subsets;

• Data-enabled parallel processing;

• Non-destructive cache-based processing;

• Graphical data preview and detailed viewing;

• Automated functional integration and launching of applications and activation of data related to Intelligent Object data content; • Automated assembly of applications and components for viewing and / or analysis relevant to specified data types and contents; and

• Custom text annotation, linking and embedding of existing text.

These features and capabilities may be applied to diversified data content and dynamic applications needs in heterogeneous local and / or networked Life Sciences computing and applications environments, as well as to other applications and environments.

The invention provides structure, method, computer program and computer program product for an intelligent object. An Intelligent Object, advantageously enabled in computer program software code or instructions, provides methods for: data and user identification and status management; functional integration of, and access to, potentially diverse data over a variety of computing infrastructures; integration of multiple data types and dimensions for efficient and accurate multidimensional, parallel queries and analyses; for diversified data content and dynamic applications needs in heterogeneous local and/or networked computing and applications environments, especially in Life Sciences computing and applications environments.

Methods for creation of Intelligent Objects are provided which, upon user initiation, queries, data acquisition protocols or data import requests invoke the unique object identifier property pane through a unified functional presentation layer. The unique object identifier property pane assigns each new data object a globally unique identification upon creation and generates a minimum set of functional property panes within the object, which account for unified viewing and processing. Once the object's state recording is started, active identification for all connections to and activities on the Intelligent Object are listed within the unique object identifier property pane, containing a real-time record of the entries. Methods for user and session authentication, permission or denial for data access, security and ownership management, highly selective data access and routing, Intelligent Object handling and storage are immediately provided.

An interactive content routing component defines where data content is located and where query-relevant content and/or results will be directed within the network for analysis or presentation and reports the location of the data content to the unique object identifier property pane. A status management component provides methods for data status validation, logging, use-tracking, auditing, synchronization, rollback enabled by the command history and non-destructive vector processing, and other state management and alerting protocols. The status management component communicates with an external object state engine component to monitor data integrity and to record the command history according to G*P- compliant LEVIS requirements (such as, for example, GLP, GCP, GMP, ISO-9001, CDER, CF R.) within the object state engine (OSE) property pane, where the information is updated and provided for real-time viewing. This information includes detailed activity logging, such as data acquisition state, calibration information, applied transformation or analysis processes, local and remote access attempts, access permission and denial, data integrity alerts, ranking status and regulatory validation states. A raw data matrix property pane within the Intelligent Object provides an overview of the full raw data content subset including content attribute information, source location, data type and comments regarding data content referred to by the Intelligent Object, regardless of originating data type or structure.

A matrix structure descriptor component provides methods for data field mapping of heterogeneous raw data to govern access to individual data subsets (byte-level workspace assignment) and to enable direct vectorized access to individual data fields.

A meta-data index property pane within the Intelligent Object provides a viewer for automatically generated or user-defined index information and brief meta-descriptions ("data- about-data") such as, but not limited to, specific data functionality or relationships to other data or data inter-dependencies based upon multi-parametric clustering, queries or application of certain analytical tools or a combination thereof to the data. This pane utilizes a meta-data index interface to communicate with external processing engines to create an index of descriptive data information and to provide this meta-data to the object pane descriptor component, which integrates relevant pane information for access and presentation. Additionally, the meta-data index is used to integrate results of clustering and/or other data analyses and provides sets of rules to optimize access and routing based upon dynamically established query relationship trees regarding specific data functionality and/or meta-data description. The meta-data index is also used to rank parameters such as data quality, validation state, significance, recency and accessibility to enable optimized access and routing based on data type, topic and content attributes to predefine analytical queries.

An object pane descriptor component compiles an overview of the Intelligent Object property pane characteristics to provide functional content and attribute definitions to access and route data content and applications. The object pane descriptor component exchanges the information with components and access interfaces to provide definitions required for dynamic addressing, functional linking and vectorized access and routing of data content and processing results. The application translator link interacts with an external data and applications handler, such as the Intelligent Object Handler, and an object access manager component to provide a dynamic list and interactive overview of applications, application components and data resources. The application translation link enables interactive linking and integration of the applications, applications components and data resources, according to user requirements and available resources.

The object access manager determines relevant property panes and selectively directs their content for functional presentation and access within a given application or database environment. Additionally, the object access manager interacts with external object translation engines to detect, define and address required and/or available data sources and to direct access and routing requests for specific data content to linked applications and/or databases and to functionally integrate data content with a variety of applications. The object access manager also provides content-attribute based algorithms to enable applications integration and inter-application communication. An object query interface routes results of Boolean comparisons and other algorithms applied to content attributes according to its object pane descriptor relationships. This component also passes aggregated results from object-to-object direct information interchange to an external result aggregation engine for further processing and relays significant query outcomes back to the object pane descriptor property pane for presentation to the user.

An object graph preview property pane is included as limited resolution image/graphics viewer for quick graphical data review of Intelligent Objects, and additionally provides linking to detailed viewing as well as launching of content-specific analysis tools. The pane also includes an object graph preview processing component, which accounts for generation of such a limited resolution image/graphics ("thumbnail") from non-graphical raw data content and which passes the image back to the object graph preview property pane.

An optional text annotation property pane within the Intelligent Object provides a location for customized text annotations, referencing, definitions and integration of links to external textual resources. An optional text annotation Interface, which links external components or applications such as text editors to allow for customization, formatting, reviewing and processing of the information through external editors and which allows to pass this information back to the text annotation property pane and to provide integrated support for text mining algorithms utilizing external distributed learning and/or knowledge extraction engines. For reasons of explanation, these methods, components and processes will be described in a fashion that does not represent the entity of simultaneous and/or interactive actions as they occur. However, it should be noted that the system herein described is composed of bi-directionally interactive components and interfaces which perform certain tasks simultaneously, or in a rapidly alternating fashion.

Examples of enabling code are provided to define and describe a single exemplary embodiment, which utilizes Microsoft C++ as the exemplary programming language.

Additionally, software development tools not limited to Visual C++, Microsoft Foundation Classes (MFC), DEB image transformations and matrix-based graphical content generation were utilized to enable this specific embodiment. The overall architecture, its application across varied domains, its processing engines and its access interfaces are in no way limited to the utilization of Microsoft C++ or the Windows 32-bit operating system environment. It is readily apparent to anyone skilled in the art that other enabling software codes or enabling techniques may also be used, including for example Java, XML and other markup languages, and/or other similar techniques.

The Intelligent Object may be compiled to run on multiple platforms, including, but not limited to, UNIX, Linux, Macintosh OS 9 and 10, or any Window 32-bit operating systems. The following hardware specifications are provided to define and describe the requirements for a specific exemplary embodiment, implemented for a 32-bit Microsoft Windows environment.

The inventive system, architecture, method, and computer program and computer program product of the Intelligent Object as well as other core elements and modules described herein and in the related applications identified herein, may be used in a variety of computing and network or connectivity environments as are known in the art and advantageously are hardware and operating system agnostic. For example, the invention may be practiced with the great majority of contemporary personal computers, workstations, mainframes, as well as notebook and other portable computing devices and all manner of information appliances.

It is clear to anyone skilled in the art that these requirements are provided by way of instruction regarding a specific embodiment ofthe technology, and that the implementation of the Intelligent Object is not limited only to the particular embodiments described. Aspects and features of the invention are now demonstrated and described relative to the interaction a scientist or other investigator or user would have with the inventive system, method, and computer program or computer program interface. In this demonstration example, data from 2-Dimensional Gel Electrophoresis (2DE) typically exhibit an intrinsic complexity due to the reproducibility challenges inherent in this multi-step experimental technique. Each of such gel comprises over 2000 individual peptide spots that relate in its entity to a defined stage in the cell metabolism. Such image data were used in a global query to obtain characteristics of significant protein expression in human liver cells at different disease states. Only larger peptides with isoelectric points (pi's) between 5.0 - 7.0 and within a size range of > 96000 Dalton (DA) were of therapeutic interest and only validated experiments were included. With reference to FIG. 14, there is shown a representation of the user interface implementation of an Intelligent Object (EVIO) showing its unique object identifier pane (UJD). It contains Intelligent Object creation data; the location ofthe Intelligent Object on the network; information routing information; user data, session and connection verification and security settings such as specific encryption level, password protected or locally restricted data access.

The depiction in FIG. 15 is a representation ofthe user interface implementation of an Intelligent Object (EVIO) showing its object state engine (OSE) property pane and its comprise status management component. In the displayed example, the experimental state is validated and the raw data integrity verified. Means for a quick review of the Intelligent Object history are provided including significant events since its creation such as calibration, analysis and annotation as well as alerts such as access violations.

The illustration in FIG. 16 depicts an intelligent object graph preview (OGP) property pane example for 2-Dimensional Gel Electrophoresis protein expression data. The low-resolution image viewer depicts an overview of the entire gel. The tree-styled content attribute in the right side of the upper part in the object pane describes the analytical techniques used in the experiment. A button "View And Analyze" launches appropriate application modules and/or analytical tools for non-destructive data analysis. The lower part of the pane contains descriptive comments about the content inserted by the creator of the Intelligent Object. With reference to FIG. 6A, one embodiment of the inventive intelligent object, also or alternatively referred to as the intelligent molecular object (EVIO), is described. Other embodiments may include selected elements from the FIG. 6A embodiment, and/or have additional added elements. The depiction in FIG. 6A represents elements of the invention and their relationships, showing the relationship of the Intelligent Object to an external Intelligent Object Handler (IOH), its components and access interfaces, the legacy domain of existing data content, applications, and devices, and an external Intelligent Object Pool (IOP). In the figure, unbroken lines ending with arrows on each end represent bi-directional communication between exemplary property panes, components and access interfaces; dashed lines ending with arrows on each end represent bi-directional communication between optional property panes, components and access interfaces; and, crossed lines do not represent connections.

In order that there be some appreciation for the manner in which computer hardware, local and/or global networks, public and private data resources and databases interoperate, FIG. 5, FIG. 1A, and FIG. 6B represents exemplary hardware and architecture configuration for the Intelligent Object and its enabling architecture and interactive content routing features. With reference to FIG. 5, all major elements within the diagram below may be bi- directionally connected over a variety of network protocols. The minimum hardware requirement is defined by a single machine. In an exemplary embodiment, as below, two laptop computers are connected in a client / server configuration to a workstation to one another in a peer-to-peer configuration, and via the workstation directly to a laboratory instrument, such as a gene sequencer or gel electrophoresis machine. In this figure, dotted bidirectional lines 248 represent options for "any-to-any" connectivity enabled via use of Intelligent Objects as central accessing and routing components. Any-to-any options include but are not limited to LAN, WAN, peer-to-peer (e.g. data, applications, memory and processor sharing between two or more laptops, workstations, etc.), server-server, Portal, ASP and other unified, distributed, parallel and grid network options. Connectivity protocols include and are not limited to PPP, http, TCP/IP, and ftp over multiple platforms.

With reference to FIG. 1A, there is illustrated a representation of an embodiment of Intelligent Objects comprised within an exemplary software platform architecture (Sentient IT Platform). This embodiment depicts the Intelligent Object (EVIO) comprised as a core element group, along with components (Processing Engines) and access interfaces required for the Sentient IT Platform.

FIG. 6B depicts an embodiment of Intelligent Objects providing a conceptual overview of interactive content routing for multiple dimensions of (or "multidimensional") direct information interchange within and between Intelligent Objects. In the embodiment of FIG. 6B, each property pane provides an overview of certain properties of the comprised data and its relationships. For example, property panes describe Intelligent Object ownership and activity history, but also complex, multiple relationships to other data and applications. Vectorized data content information and results of data content comparison and analysis, data annotation, text references, validation status and the like may be flexibly interconnected in a functional manner via these panes and their related components and access interfaces. User viewing and interactivity to define or refine (without writing to the data content) Intelligent Object property pane content presentation and relationship connectivity for new queries, customization and the like takes place through property panes presented at the unified presentation layer.

The following exemplary embodiment is defined by a core set of processing components and access interfaces described in detail below. Alternative embodiments may or may not have corresponding or additional processing components, access interfaces and property panes with unique, functionality-driven properties, hi this exemplary embodiment, the set of property panes 1000, processing components 1002 and their corresponding access interfaces 1004 are defined as follows.

A unique object identifier (UID) 1006 property pane enables unified user viewing of object creation information, e-signature authentication, access privilege information and common security elements related to each data object and to corresponding data content. This information comprises a 128-bit, alphanumeric, globally unique intelligent object identification string, unique user identification, unique computer identification, unique session identification, login time, user network address, and date and time record of the start of the last connected session (See

FIG. 15). The Intelligent Object's (IMO) 200 creator/owner, routing information and content attributes as well as information on currently connected users, current session information, access permissions, authentication, routing and are reported to and presented via this pane and are updated dynamically. An interactive content router (ICR) 1008 component bi-directionally communicates with the unique object identifier and also interacts with the object pane descriptor (OPD) 1026 to define where data content is located, where and how it will be accessed and directed within the network, and which distributes data content according to a given queries, reporting the specific content origination and routing information to the unique object identifier (UID) 1006 property pane.

An object root router (ORR) 1010 component bi-directionally communicates with the unique object identifier interface (UIDi) 1012 and interactive content router (ICR) 1008 to define the origin of the Intelligent Object (EvIO) 200 within the network, addresses object queries and reports this information to the unique object identifier (UID) 1006 property pane. The object root router (ORR) 1010 enables secure local and/or remote identification of and interactive access to the Intelligent Object, utilizing and reporting access and routing information comprising the unique object identifier, data content and data object ranking and ownership information, object root addressing and routing information, activity logging and reporting of all connected users. A unique object identifier access interface (UEDi) 1012 gates direct access and routing to all or selected areas ofthe data content, according to authentication and permission and / or denial based on unique data, user and session authentication, and Intelligent Object (EVIO) 200 security and content routing permissions. An example of enabling code for the implementation of the unique object identifier

(UID) 1006 property pane is shown in the following.

Various selected aspects and features of the invention are now described relative to six examples. It will be appreciated that these examples are not intended to cover, address, or describe all of the inventive features. Example 1 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment of the unique object identifier (UID) processing component. Example 2 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment of the interactive content router (ICR) processing component. Example 3 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment ofthe object state engine (OSE) property pane and its status management component. Example 4 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment for opening of multiple object data with similar content within a defined Intelligent Object directory. Example 5 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment of the object graph preview (OGP) property pane and its module launch component. Example 6 shows a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment of the raw data matrix (RDM) property pane and its data link insertion component.

EXAMPLE 1 Using message mapping, the EVIO UED pane is initialized to receive the following

CString data via DoDataExchange command: a unique object UID as a 128 bit global identifier string; an entry on the last connection to the object, including login time, date, network, computer address and user identifier; a counter for concurrent connections to the object and a list containing information on each connection; and the object creator string containing the unique user global identifier

This information is then displayed within the UID pane and refreshed on update:

DWORD flags = mJistConnection.GetExtendedStyle(); mJistConnection.SetExtendedStyletflags | LVSJEX_FULLROWSELECT \ LVS_βXJ}RIDLINES); mJistConnection.InsertColumn(0, _T("User"), L VCFMTJEFT); mJistConnection.InsertColumn(l, _ T(" Computer Name "), L VCFMTJEFT); mJistConnection.InsertColumn(2, _T("Login Time"), LVCFMTJEFT); mJistConnection.InsertColumnβ, __T("IP Address "), L VCFMTJEFT); mJistConnection.InsertColumn(4, _T("Session ID"), LVCFMTJEFT); mJistConnection.SetColumn Width(0, L VSCW__A UTOSIZEJJSEHEADER); mJistConnection.SetColumn Width(l, L VSCW_A UTOSIZEJJSEHEADER); mJistConnection.SetColumn Width(2, L VSCW__A UTOSIZEJJSEHEADER); mJistConnection.SetColumn Widthβ, L VSCW_A UTOSIZEJJSEHEADER); mJistConnection.SetColumn Width(4, L VSCWJ. UTOSIZEJJSEHEADER);

UpdateData(FALSE);

return TRUE; //return TRUE unless you set the focus to a control //EXCEPTION: OCX Property Pages should return FALSE

(End Example 1)

Object root routing and interactive content routing are permitted or denied according to unique user, session, data object and data content identification enabled by the object root router (ORR) 1010 and interactive content router (ICR) 1008 components to provide finely grained access and routing control, definable as narrowly as to single bytes of data content. The interactive content routing (ICR) 1008 component also assures via the data content access and routing protocols that analytical and / or write requests are not allowed to the created data file content, but rather are implemented utilizing cache-based non-destructive overlay processing methods enabled via an external Intelligent Object Handler (IOH) 202.

Additional methods of data encryption may be provided in optional embodiments, to protect the Intelligent Object (EVIO) 200 and its contents from unauthorized access. The methods of data encryption are well known in the art and examples of comprised data encryption methods include RSA Data Security software solutions of Redwood City, CA, USA.

An example of enabling code for the interactive content routing component (ICR) 1008 is shown in the following.

EXAMPLE 2 Interactive content routing involves calls to the document manager to filter information based on its content attribute and to activate loading of certain raw data structures and/or applications selectively without user interaction.

BOOL CDocManagerEx::DoPromptFileName(CString&fιleName, UINT nlDSTitle, DWORD IFlags,

BOOL bOpenFileDialog, CDocTemplate* pTemplate)

{ CFileExDlg digFileφOpenFileDialog); //dialog with a preview

CString title;

VERIFY(title.LoadString(nIDSTitle));

dlgFϊle.m fn. Flags |= IFlags;

CString strFilter;

CString stiDefault; if (pTemplate != NULL)

{ ASSERT__ VALID Template); _AjxAppendFilterSufflx(strFilter, dlgFile.mjyfn, pTemplate, &strDefault);

} else

{ //do for all doc template POSITION pos = m templateList.GetHeadPosition();

BOOL bFirst = TRUE; while (pos /= NULL)

{ CDocTemplate* pTemplate = (CDocTemplate*)mJemplateList. GetNex os); _AfxAppendFilterSuflix(strFilter, dlgFϊle.m_ofn, pTemplate, bFirst ? &strDefault : NULL); bFirst = FALSE; }

A function is provided for content-based load and preview of files within the EVIO content panes. The content descriptor is located in "section 4" ofthe structure.

//open file and look inside CFilef;

VERIFY(f.Open(ff.GetFilePath(), CFile: :modeRead));

if(CMainDoc::IsFileValid(&f) == FALSE) continue;

1/ don't support automatic opening for version 1 iflCMainDoc: :GetFileVersion(&f) < 2) continue;

TRY

{ //Descriptor is at section 4 f.Seek(3 + ((4 - 1) * sizeof (DWORD)), CFile:. -begin); D WORD position = 0; f.Read(&position, sizeof (position));

//seek to the right position and start reading f.Seekφosition, CFile:. -begin);

I / section version BYTE version = 0; f.Read(&version, sizeof (version)); ASSERTfversion == 1);

CObjectPaneDescriptorArray opd;

CArchive ar(&f, CArchive:. -load \ CArchive: .bNoFlushOnDelete); ar.mjpDocument = NULL; ar.mJForceFlat = FALSE; opd.Serialize(ar) ; ar.CloseQ;

iflopd.GetSi∑e() <= 0) continue;

if(opd[0] .shTechnique != mjiCurrContentAttrib) continue;

}

CATCH(CException, e) { TRACE("Could not read thisflle: %s\n ", ff.GetFilePathQ); continue;

} ENDJOATCH

TRACE("Otherfile to open: %s\n", ff.GetFilePathQ); m nrayFileName.Add(ff.GetFilePath()); count ++;

return FALSE;

}

A preview thumbnail ofthe data is contained in "section 5" ofthe structure.

// thumbnail is at section 5 f.Seekβ + ((5 - 1) * sizeof (DWORD)), CFile: .begin);

DWORD position = 0; f.Read(&position, sizeof (position));

//seek to the right position and start reading f.Seekφosition, CFile: .-begin);

//section version BYTE version = 0; f.Read(&version, sizeof (version)); ASSERT(version == 1);

// thumbnail image

BYTE raw_data[240 * 240 * 3] = {0}; f.Read(raw_data, sizeof (r aw _ data));

LJZreateBitmap(&mJitmap Tlmmbnail, TYPEJOONV, 240, 240, 24, ORDER J3GR, NULL, TOP EFT); int width = BITMAPWIDTHf&mJitmapThumbnail); int height = BITMAPHEIGHT(&mJitmapThumbnail); RGBTRIPLE* rgb = (RGB RIPLE '*)raw_data; for (int row = 0; row < height; J-OW++) forfint col = 0; col < width; col++)

{ COLORREF cr = RGB(rgb[(row * height) + colJ.rgbtRed, rgb [(row * height) + col] .rgbtGreen, rgb [(row * height) + colj.rgbtBlue); L_PutPixelColor(&mJitmapThumbnail, row, col, cr);

}

(End Example 2)

An object state engine (OSE) 1014 (also see FIG. 15) property pane is enabled by the status management component (SMC) 208 and an object state list (Table 1) to provide realtime user viewing and integrity verification of object state and object command history information including access attempts, access permission and denial, detailed activity logging, data integrity alerts, ranking status and regulatory validation states. Table 1 is an exemplary representation of the object state list, showing the coded table references utilized to minimize overhead for regulatory-compliant state synchronization and logging.

A status management component (SMC) 208 communicates with an external object state engine component (OSE) 212 to monitor data integrity and command history according to industry specific, regulatory compliant parameters. The status management component (OSE) 208 provides information including data acquisition state (instrument parameters, acquisition completion, etc.), calibration information, applied transformation or analysis processes and validation state (object state list - Table 1). Information and contained herein is used for data integrity protection, regulatory validation, auditing and logging, rollback.

An object query interface (OQI) 1018 (OQI) 1018 receives query requests from the external object state engine (OSE) 212 and initiates Intelligent Object (EVIO) 200 meta-data analysis and provides access interfaces between Intelligent Object (EVIO) 200 processing components and external processing components and access interfaces, according to the correspondence of meta-data indices and detected content attributes to a given query. These components and interfaces may include but are not limited to a report generation interface (RGI) 220, a result aggregation engine (RAE) 204, validated and/or functionally ranked analytical processing components and the object query interfaces (OQI) 1018 of related data.

Additionally, the object query interface (OQI) 1018 enables object-to-object direct information interchange by directing interactive content routing of specified data vectors directly between Intelligent Objects (EVIO) 200 and relaying results of direct object-to-object communication and comparison to an external result aggregation engine (RAE) 204 component and external report generation interface (RGI) 220.

Examples of enabling code for the implementation of the object state engine (OSE) 1014 property pane and status management component (SMC) 208 are shown in the following.

EXAMPLE 3

The object state engine property pane (OSE) 1014 handles state-related information for access and validation. CStrings for state history record counter, alert counter and current state records are created.

void CPageOseDlg::DoDataExchange(CDataExchange* pDX) f CString count _str = _T("N/A "); CString alert_str = ("N/A ");

CString alert ountjtr = JT("N/A ");

CString currjtatejtr = _T("N/A ");

ifφDX->mJSaveAndValidate == FALSE) {

CDialogView* view = (CDialogView*)GetParentQ; CMainDoc* doc = (CMainDoc*)view->GetDocwnent(); ASSERT _ VALID(view); ASSERT VALID(doc);

iff :Is WindowφiJistObjectHistory. mji Wnd))

{ //do the list mJistObjectHistory.DeleteAUItems();

int alert = 0; int last dert = 0; int last state = 0; - I l l - timej lastjilertjime = 0; timej last tatejime = 0; CString text = _T(""); CTime time = 0; UUIDWSTR uuidjtr = (0);

BYTE flag = 0; CString temp = _T(""); int txt vidth = 0; int col vidth = 0; int count = doc->m nrayStateHistoιγ. GetSizeQ; for (int i = 0; i < count; i++)

{ GetLutObjState(doc->mjιrrayStateHistory[i].wState, temp, flag);

ASSERT(((flag & 8) && (flag & 16)) .'= TRUE); mJistObjectHistory.SetItemData(i,flag); if((flag & 8) \\ φlag & 16))

{ alert '++; lastjύert — doc->m_ arrayStateHistory[i].wState; lastjilertjime = doc->mjtrrayStateHistoιγ[i].timeDate; }

//set the list count and alerts count _str.Format(JT("%d"), count); alert joιιntjtr.Format(JT("%d"), alert);

//set the text for last alert if (alert > 0) {

GetLutObjState(last_alert, temp, flag); time = lastjilertjime; alert jtr.Format(JT("%s on %s"), temp, time.Format(_ T("%x")));

} else alert tr = Jf("None");

//set text for the state the object is in iflcount > 0) { GetLutObjStateParent lastjtate, temp, flag); time = lastjtatejime; currjtatejtr.Format(_T("%s on %s"), temp, time.Format(_T("%x")));

else curr tate tr = JT("None"); } }

The status management component (SMC) 208 uses a hierarchical tree-style lookup table (LUT) for state assignment.

// create the tree

BYTE flag = 0; CString str = __T(""); HTREEITEM parent = NULL; forφnt i = 0; i < WOO; i++) {

GetLutObjStateft, str, flag); if (Istr.IsEmptyQ)

{ ASSERT(«flag & 8) && (flag & 16)) != TRUE);

if(flag & l)

{ parent = mJreeObjectSate.Insertltem(str); mJreeObjectSate.SetItemData(parent,flag); continue;

}

if(flag & 2)

{ CString fint = __T(""); fint.Format( T("(%.3d) - %s"), i, str);

HTREEITEM item = mJreeObjectSate.Insertltemφnt, parent); mJreeObjectSate.SetItemData(item,flag); continue; ASSERT(FALSE);

}

(End Example 3)

A meta-data index property pane (MDX) 1022 enables unified user viewing and customization of object meta-data definitions for optimized query processing. Meta-data information includes specific data functionality, content attributes and relationships to other data derived from a variety of statistical comparisons such as clustering and self-organizing maps, as well as from query histories and other user-based information, to predefine searching and analysis of Intelligent Objects (EVIO) 200.

A meta-data index access interface (MDXi) 1022 allows for fast access to the Intelligent Object (EVIO) 200 based on data content, functionality and description. The metadata index interface provides direct linking to indexed and ranked "data-about-data" information to enable optimized access and routing. An object pane descriptor property pane (OPD) 1024 provides an interactive overview of the Intelligent Object's (EVIO) 200 property panes, data content, location, structure and functional relationships of linked applications and linked databases provided by an application / database definition router interface.

An object pane descriptor component (OPDc) 1026 compiles an overview of Intelligent Object (EVIO) 200 property pane (Property Panes) 1000 characteristics to provide functional content and attribute definitions to access and route data content and applications. The object pane descriptor component (OPDc) 1026 exchanges this information with components and access interfaces including but not limited to the interactive content router component (ICR) 1008, the status management component (SMC) 208, the object query interface (OQI) 1018, the meta-data access interface (MDXi) 1022, an object access manager component (OAM) 1036, an application / database definition router (ADDR) 1028 and an application translation linking component (ATL) 1034 to provide definitions required for dynamic addressing, functional linking and vectorized access and routing of data content and processing results.

An application / database definition router (ADDR) 1028 enables the detection, definition and addressing of required and / or available data sources and directs access and routing requests to specific data content, linked applications and linked databases. The application / database definition router (ADDR) 1028 interactively provides this information as required for a given context and query, interacting with the application translation linking component (ATL) 1034, the interactive content routing component (ICR) 1008 and the object query interface (OQI) 1018 to call proper analysis tools based on the Intelligent Object (EVIO)

200 property pane information (Property Panes) 1000 available.

An object graph preview property pane (OGP) 1030 within the Intelligent Object (EVIO) 200 includes linking to detailed viewing and analysis tools (See FIG. 16), as well as a limited resolution image / graphics ("thumbnail") viewer for quick graphical review of the raw data corresponding to the Intelligent Object (EVIO) 200.

An object graph preview interface (OGPi) 1032 routes content attribute information, comments, and a limited resolution graphic view of any selected raw data file to the object graph preview property pane (OGP) 1030. Additionally, specific content attributes and comments may be viewed, as well as subsets of data with corresponding content attributes, upon user request.

Examples of enabling code for the implementation of the object graph preview property pane (OGP) 1030 and module launching methods are shown in the following.

EXAMPLE 4 The object graph preview property pane (OGP) 1030 provides a thumbnail graphical preview of the data content within the object based on information in the object pane descriptor (OPDc) 1026 regarding technique and content attribute.

if(doc->mjxrrayObjectPaneDescriptor. GetSizeQ > 0) {

BOOL create = FALSE; iflm trContentAttrib.IsEmptyQ == FALSE)

{ int indexl = doc->mjrrayObjectPaneDescriptor[0].shTechnique; ' int index2 - atoi(m trContentAttrϊb.Mid(l,3)); iflindexl /= index2) create = TRUE;

} else create = TRUE;

iflcreate == TRUE) CreateContentAttrϊbStringQ; } }

The content is referred to according to a hierarchical tree-style attribute lookup table (LUT) similar to the one used for object state management. Bit-flags are provided to define the depth ofthe tree branches.

//look up info in the tree

GetLutContentAttιib(doc->m_arrayObjectPaneDescriptor[0].sh Technique, str, flag); m strContentAttrib.Format(_ T("(%.3d) \\%s"), doc-

>m arrayObjectPaneDescriptor[0J.shTechniqιιe, str); parent = tree. GetParentItem(item); whileφarent)

{ m strContentAttrib.Insert(6, _T("\\") + tree.GetltemTextφarent)); parent = tree.GetParentltemφarent);

The object graph preview access interface (OGPi) 1032 contains instructions for module launching, used for dynamic, content-attribute based launch of appropriate analysis tools. Applications are called according to their index grouping via a dynamically generated command line string.

void CPageOgpDlg: : OnAnalyzeQ

{ CDialogView* view = (CDialogView*)GetParent();

ASSERT ALID(view);

CMainDoc* doc = (CMainDoc*)view->GetDocument(); ASSERT _VALID(doc); // make we have the right analysis tools before we continue CArray<int, int> range; int docjittrib = doc->mjxrrayObjectPaneDescriptor[0].shTechnique; ASSERT(docjιttrib != 0);

ASSERTφange.GetSizeQ == 0); if ((docjittrib >= 210) && (docjittrib <= 269))

{ forφit i = 210; i <= 269; i++) range.Add(i);

} else if((doc_attrib >= 280) && (docjttrib <= 314))

{ for(int i = 280; i <= 314; i++) range.Add(i);

}

// analysis not supported iflrange.GetSizeQ == 0)

{ AfxMessageBox(IDS_ERRORJVRONGCONTENT ATTRIB); return;

}

//get the executable file path

TCHARfile__Oath[J4AXJ³ATH] = {0};

VERIFY(GetModuleFileName(AfaGetApp()->mJInstance, filejath, __MAX__PA TH));

TCHAR drive[JΛAX_DRIVE] = {NULL}; TCHAR dir[J4AXJ)IR] = {NULL};

TCHAR title[__MAX_FNAMEJ = {NULL};

TCHAR extfjMAXJEXT] = {NULL};

Jsplitpathφϊlejath, drive, dir, title, ext); mfdefined(_DEBUG) CStringfn = _T(""); fit += title;

ASSERTφι.CompareNoCase("Platform.exe") == 0); #endif CString process jath = _ T(""); process _path += drive; process >ath += dir; proces __path += _ T(" Analyze.exe");

// convert command line string par am. TrimRightQ;

TCHAR* icr = new TCHAR[param.GetLengthQ + lj; memsetftcr, NULL, sizeof (TCHAR) * (param.GetLengthQ + 1));

Jcscpy(icr, param);

// invoke process

PROCESS JNFORMATION pi = {0}; STARTUPINFO si = {0}; si.cb = sizeoflsi);

CreateProcessφrocessjath, icr, NULL, NULL, FALSE, CREATE_NEW_CONSOLE, NULL, NULL, &si, &pi);

//release buffer deleteQ icr;

}

(End Example 4)

Additionally, the object graph preview interface (OGPi) 1032 detects data objects with corresponding content attributes to present limited resolution graphic previews of related data objects upon user request. Further, the object graph preview interface (OGPi) 1032 ' provides linking to analytical tools for detailed viewing.

Examples of enabling code, providing instructions utilized for the exemplary embodiment, for opening of multiple object data with similar content within a defined Intelligent Object (EVIO) 200 directory are shown in the following. EXAMPLE 5

A dynamic loading based on content is provided which allows to allocate and open all EVIO data of similar content attributes simultaneously.

IMPLEMENT J)YNAMIC(CFileExDlg, CFileDialog)

BEGINJfESSA GEJ4AP(CFileExDlg, CFileDialog) //{{AFXjMSGJMAP(CFileExDlg) ONJ¥M_PAINTQ ON_BN_CLICKED(IDC_OPENALLCURRENTATTRIB, OnOpenAllSameAttrib)

//}}AFX_MSGJ4AP ENDJΛESSA GEJΛAPO

CFileExDlg::CFileExDlg(BOOL bOpenFileDialog, CWnd* /* pParentWnd */) CFileDialogφOpenFileDialog)

{ m fn.Flags = m fn.Flags \ OFN_FILEMUSTEXIST \ OFN_PATHMUSTEXIST \ OFN_EXPLORER \ OFN _ENABLETEMPLATE; mjfn.Flags &= ~OFN_ENABLESIZING; m fn.lpTemplateName = MAKEINTRESOURCE(CFileExDlg::IDD);

//{{AFXjDA TAJNIT(CFileExDlg) m strComments = __T(""); m trContentAttrϊb = _T(""); lnJOpenAUSameAttiib = FALSE; mJOpenAϊl = FALSE; //}}AFXJ)A TAJNIT

m Curr Content Attrϊb = -1; m rrayFileName.RemoveAUQ; memset(&mJitmapThumbnail, NULL, sizeof (mJitmapTliumbnail));

}

void CFileExDlg: :DoDataExchange(CDataExchange * pDX) {

CFileDialog: :DoDataExchange(pDX);

//{{AFX_DATA_MAP(CFileExDlg)

DDX ControlφDX, IDCJΗUMBNAILFRAME, m vndThumbnail); DDXJTextφDX, IDCJJOMMENTS, m tr Comments); DDXJTextφDX, IDC CONTENTATTRIB, m trContentAttiib); DDXjCheckφDX, IDCjDPENALLCURRENTA TTRIB, mJOpenAUSameAttrib); //}}AFX_DATA_MAP

BOOL CFileExDlg::OnInitDialog()

{ CFileDialog: :OnInitDialog();

ClearPreviewQ;

Preview the selected EVIO data's graphical thumbnails:

//find out the bitmap dimensions and set the frame size to the bitmap size m_wndThumbnail.SetWindowPos(NULL, 0, 0,

BITMAPWIDTH(&mJitmapThumbnail), BITMAPHEIGHT(&mJitmapThumbnail),

SWPJVOMOVE I SWPJIOZORDER);

//paint the thumbnail CCHentDC wnd_ dc(&m_wndThumbnail);

HP ALETTE hp = L_CreatePaintPalette(wnd_dc.GetSafeHdc(), &mJitmapThumbnail); CPalette *oldjpal = wndjlc.SelectPalette(CPalette::FromHandleβp), FALSE); wndjic.RealizePaletteβ;

Lj°aintDC(wnd_dc. GetSafeHdcQ, &m_ bitmapThumbnail,

NULL,

CRect , 0, BITMAPWIDTH(&mJitmapThumbnaU), BITMAPHEIGHT(&mJitmapThumbnail)), NULL,

SRCCOPY); wnd_dc.SelectPalette(old >al, FALSE); DeleteObjectφp);

} (End Example 5)

An application translation link property pane (ATL) 1034 is linked to the object access manager component (OAM) 1036 to provide an interactive, unified user overview of applications components and relationships required and/or available, depending on the data content, functional data relationships, analytical requirements, translation requirements and specific user queries. This property pane is linked to an external component for automated applications assembly to enable quick and seamless application integration and to provide the functionality for automated and dynamic development of new applications.

An object access manager processing component (OAM) 1036 provides algorithms to allow for applications integration and inter-application communication, depending on data content attributes (Table 2 — Content Attribute List). Table 2 is a representation of an embodiment or representation of the content attribute list, showing the coded table references utilized to minimize overhead for applications linking and object-to-object direct information interchange. Additionally, the object access manager (OAM) 1036 is linked to an external object translation engine (OTE) 214 component and application translation interface (ATI) 216 which optimize translation of the Intelligent Object (EVIO) 200 and functionally integrate data content with a variety of applications.

A raw data matrix property pane (RDM) 1042 containing path and vectorized access information to diverse types of data content is provided. The raw data matrix (RDM) 1042 property pane provides an interactive interface to, in this exemplary embodiment, an external Intelligent Object Handler (IOH) 202 and a data link insertion (DLL) 1044 component to provide a unified user overview ofthe full information subset ofthe data content structure and format, including data content attribute information, data source location, data source type and comments regarding data content.

Through the data link insertion component (DLI) 1044, data are distinguished and defined within this pane by their type membership (e.g., file, database record, application, life data acquisition, ...), their transport and routing protocol and communication mechanism to the raw data (e.g., via PPP over TCP/IP, P2P, C|S,S|S; and/or via http, ftp, or other protocols via automatic multi-transport protocol detection) and their content attribute.

A matrix structure descriptor (MSD) 1046 component contains the full information subset, regarding the formatting and/or structure of the data content. This information is provided by an external object translation engine (OTE) 214 and applications translation interface (ATI) 216 and is relayed by the matrix structure descriptor (MSD) 1046 to the raw data matrix (RDM) 1042 property pane. Additionally, the matrix structure descriptor (MSD) 1046 provides processes required by application / database definition router (ADDR) 1028 and data link insertion component (DLI) 1044 for data field mapping and gating of vectorized access to individual data fields between objects, applications and databases. Examples of enabling code for the raw data matrix property pane (RDM) 1042 and matrix structure descriptor (MSD) 1046 interface follow.

EXAMPLE 6

The raw data matrix property pane (RDM) 1042 contains such as data routing, data source type, data type definition, data content attributes and comment information. It also provides a mechanism linked to the matrix structure descriptor interface (MSD) 1046 for data authenticity and integrity checking.

//{{AFXjDA TAjMAP(CPageRdmDlg) DDX ControlφDX, IDCJ IALOGSIZE, mJuttDialogSize);

DDXJTextφDX, IDC_FILEPATH, fllejath);

DD VJΛaxCharsφDX, filejath, J4AX_PA TH);

DDXJTextφDX, IDCJ ATASOURCETYPE, m trDataSource);

DDXJTextφDX, IDC CONTENTATTRIB, m trC^' ontentAttrib); DDXJTextφDX, IDCJJOMMENTS, comments);

DDV MaxCharsφDX, comments, 320);

//}}AFXJ)A TAJvfAP

mjiDataSource = sf.GetSourceTypeQ;

ASSERT(mjιDataSource >= 0); switch(m ιDataSource)

{ case 0: mjtrDataSource = Ji'C'File"); break; case 1: m tiDataSource = _T(" Application"); break; case 2: mjtrDataSource = Jf("Database"); break; case 3: mjtrDataSource = Jf(" Instrument"); break; default: ASSERT(FALSE);

}

If raw data of any type are assigned to the Intelligent Object (EVIO) 200 the first time, an integrity check is performed and a verifier created. // set data integrity check switch(mjιDataSource)

{ case 0: {

UUIDWSTR uuid tr = {0};

StringFromGUID2(doc->m uidObject, uuidjtr, sizeof (uuid tr)); CString objjiuid = uuidjtr;

CString result = CRawCheckSum::CheckRawDataffilename, uuidjtr); ASSERTφesult. GetLengthQ == 32); doc->m trDataIntegrity = result;

TRACE(_ T("Integrity Check for %s is %s. Length = %d \n"), filename, result, result. GetLengthQ); break;

case 1: case 2: case 3: default: ASSERT(FALSE);

doc->m trIcr = filename; UpdateData(FALSE);

mJDataLoaded = TRUE; if((mJ)DataLoaded == TRUE) && (mJContentAttribLoaded == TRUE)) doc->mJHasRawData = TRUE;

AddToStateHistoryQ; doc->GenerateThumbnail(); doc->SetModifiedFlag(); doc-> UpdateAUViews(NULL); }

(End Example 6)

An automatically or user evoked dynamic load function provides automated dynamic loading of Intelligent Objects (EVIO) 200 containing similar content including a graphical preview ofthe Intelligent Object's (EVIO) 200 content. An optional text annotation property pane (TAN) 1038 provides a location for customized text annotation, integrated text viewing and definition and integration of links to external textual resources.

An optional text annotation interface (TANi) 1040 provides processing for customized text annotation, integration of linked data for viewing, formatting and support for integration of links to external text resources. Text annotation and viewing can be enabled by linking directly to the user's text editor of choice, by translation of text via external components to meet existing application requirements, or by calling the required text annotation application for viewing and editing of specified text. Additionally, the text annotation interface (TANi) 1040 provides an interface for text mining algorithms provided by external software components for distributed learning and knowledge extraction.

Additional optional property panes and their related processing components and access interfaces not shown in this exemplary embodiment, may include, for example, a knowledge extraction engine property pane comprising links to a set of "intelligent" algorithm for automated text and data searching, analysis and report generation.

It is evident from the above description, that this Intelligent Object (EVIO) 200 architecture allows for real-time answers to complex, multidimensional, interdependent queries by providing the infrastructure for a global, comprehensive analysis of otherwise not accessible vast, inconsistent data sets. Although the foregoing invention has been described in some detail by way of illustration and example for puφoses of clarity of understanding, it will be readily apparent to those of ordinary skill in the art in light of the teachings of this invention that certain changes and modifications may be made thereto without departing from the spirit or scope of the appended claims.

The following examples are offered by way of illustration and not by way of limitation.

TABLE1: OBJECT STATE TABLE

Tree branching flag bits:

0 = nothing 1 = beginning of the section

(open tree branch) 2 = section entry 4 = last section entry (close tree branch) Validation flag bits:

8 = Alert - Red

16 = Warning - Orange 32 = Approved - Green

000 ("Creation")

001 ("Object Created")

002 ("Sample Recorded") 005 ("Data Insert From File") 006 ("Data Insert From Application")

007 ("Data Insert From Database")

010 ("Data Acquisition") ,

011 ("hi Progress") 012 ("Interrupted")

013 ("Continued")

014 ("Completed")

020 ("Data Type Definition") 021 ("Raw")

022 ("Matrix")

023 ("Structure")

024 ("Vector")

025 ("Pointer") 026 ("Path")

027 ("Binary")

028 ("ASCII")

030 ("Database Record") 035 ("Relative Calibrations")

036 ("Relative Migration Distance (Rf)") 037 ("Relative Isoelectric Point (Rpl") 038 ("Relative Mass (Rm)")

039 ("Relative Mobility (u)")

040 ("Biological Calibrations")

041 ("Concentration (Quantitation)")

042 ("Retention Time (Rf)")

043 ("Molecular Mass") 044 ("Molecular Size")

045 ("Isoelectric Point (Charge)")

046 ("Enzyme Activity")

047 ("Immunological Activity") 048 ("Other Bio-Activity") ("Image Calibrations")

051 ("Optical Density (OD)") 052 ("Fluorescence Intensity")

053 ("Luminescene Intensity")

054 ("White Balance")

055 ("Li ht Intensity")

056 ("Dynamic Range Verification") ("Measurement Calibrations")

061 ("Origin")

062 ("Size X")

063 ("Size Y") 064 ("Position X")

065 ("Position Y")

066 ("Position Z")

067 ("Length")

068 ("Width") 069 ("Depth") ("Annotations")

071 ("Descriptive Text")

072 ("Base Designation (DNA Sequence)") 073 ("Aminoacid Designation (Protein Sequence)")

074 ("Molecular Type")

075 ("Molecular Function")

076 ("Molecular Structure")

077 ("Clinical Trial Information") ("Functionality Information")

081 ("Organism")

082 ("Molecular Classification")

083 ("Metabolic Phase") 084 ("Disease Relationship") ("Metadata")

091 ("Metadata Index Generated")

092 ("Metadata Index Updated") ("Standardization / Normalization")

101 ("Threshold")

102 ("Base Function")

103 ("Base Plane") 104 ("Relative Location") ("Experiment Validation")

301 ("Invalid Conditions")

302 ("Invalid Experiment") 303 ("Invalid Inteφretation")

304 ("Invalid Analysis Tool Applied")

306 ("Raw Data Integrity Verified")

307 ("Raw Data Integrity Violated") 308 ("Unsigned Raw Data")

310 ("Unsure Result")

311 ("Unsure Conditions")

312 ("Unsure Method") 315 ("Approved Method")

316 ("Certified Method")

320 ("Validated Method")

321 ("Validated Analysis") 325 ("Validated Annotation") 330 ("Validated Experiment")

340 ("Forensic Experiment")

350 ("Certified Experiment") ("Output Request") 410 ("Numerical Output Generated")

411 ("Graphical Output Generated")

420 ("Remote Output Sent")

430 ("Output Printed") ("Access Information")

901 ("Access Denied")

902 ("Time Limit Exceeded")

903 ("User Limit Exceeded")

910 ("Inter-Object Communication Granted") 911 ("User Access Granted")

920 ("Full Access Granted")

930 ("Limited Access Granted")

940 ("Local Access Granted")

941 ("Local Access Denied") 942 ("Local Access Restricted")

950 ("Remote Access Granted")

951 ("Remote Access Denied")

952 ("Remote Access Restricted")

TABLE 2: CONTENT ATTRIBUTE LIST

Tree branching flag bits: 0 = nothing

1 = beginning ofthe section

(open tree branch)

2 = section entry 4 = one up 8 = two up

16 = three up

000 ("Life Sciences"),

010 ("Experimental Planning"),

011 ("Scope"),

012 ("Requirements"),

013 ("Resources And Costs"), 015 ("Materials And Methods"),

020 ("Instrumentation"),

030 ("Experiment Optimization"), 050 ("Literature Services"),

051 ("ISIS"),

052 ("Current Contents"), 060 ("Medline"), 100 ("Sample Information"),

101 ("Sample Origin"),

102 ("Sampling Technique"),

103 ("Organism"),

104 ("Type"), 105 ("Description"),

106 ("Storage Requirements"),

107 ("Amount Available"),

130 ("Sample Preparation"), 131 ("Selective Dissolution"),

145 ("Solvent Extraction"), 150 ("Acetone Dry Powder"),

200 ("Analytical Methods And Tools"), 201 ("Atomic Absoφtion"),

202 ("Aminoacid Analysis"),

203 ("Chromatography"),

204 ("DC, TLC"),

205 ("LC, HPLC"), 206 ("GC"),

209 ("Electrophoresis"), 210 ("Electrophoresis, 1 DE Gels, Native"), 211 ("Visible stains"),

212 ("Silver"),

213 ("Coomassie Blue"), 5 214 ("Amido S"),

215 ("Fast Green SF"),

216 ("Auto Radiography"), 220 ("Fluorescent stains"),

221 ("Ethidium Bromide"),

10 222 ("TOTO / YOYO"),

223 ("SYPRO Orange"),

224 ("SYPRO Ruby"),

225 ("SYBR Green"),

226 ("DAPI"),

15 230 ("Electrophoresis, IDE Gels, Denaturing"),

231 ("Visible Stains"),

232 ("Silver"),

233 ("Coomassie Blue"),

234 ("Amido S"),

20 235 ("Fast Green SF"),

236 ("Auto Radiography"), 240 ("Fluorescent Stains"),

241 ("Ethidium Bromide"),

242 ("TOTO / YOYO"), 25 243 ("SYPRO Orange"),

244 ("SYPRO Ruby"),

245 ("SYBR Green"),

246 ("DAPI"),

250 ("Electrophoresis, IDE EEF, Ampholytes"), 30 251 ("Visible stains"),

252 ("Silver"),

253 ("Coomassie Blue"), 255 ("Fluorescent stains"),

256 ("Ethidium Bromide"), 35 257 ("TOTO / YOYO"),

260 ("Electrophoresis, IDE IPG, Immobilzed"), 261 ("Visible stains"),

262 ("Silver"),

263 ("Coomassie Blue"), 40 265 ("Fluorescent stains"),

266 ("Ethidium Bromide"),

267 ("TOTO / YOYO"), 270 ("Electrophoresis, MADGE"),

271 ("Visible stains"), 45 272 ("Silver"),

273 ("Coomassie Blue"), 275 ("Fluorescent stains"),

276 ("Ethidium Bromide"),

277 ("TOTO / YOYO"), 50 278 ("SYPRO Ruby"),

280 ("Electrophoresis, 2DE Gels, Ampholyte Focused"), 281 ("Visible Stains"), 282 ("Silver"), 283 ("Coomassie Blue"), 290 ("Fluorescent Stains"),

291 ("Ethidium Bromide"),

292 ("TOTO / YOYO"), 293 ("Cy Dyes"),

294 ("SYPRO Orange"), 300 ("Elecfrophoresis, 2DE Gels, EPG Focused"), 301 ("Visible Stains"), 302 ("Silver"), 303 ("Coomassie Blue"),

310 ("Fluorescent Stains"),

311 ("Ethidium Bromide"),

312 ("TOTO / YOYO"),

313 ("Cy Dyes"), 315 ("Elecfrophoresis, CE"),

316 ("U VIS Detection"),

317 ("Fluorescence Detection"),

318 ("Other Detection"), ("Spectroscopy"), 321 ("UVNIS"),

322 ("Infrared (IR)"),

323 ("NMR"),

324 ("ESR"), ("Mass Spectrometry (MS)"), 326 ("MALDI-ToF"),

327 ("SELDI"),

328 ("Quadrupol"),

330 ("Combined MS Techniques"), 331 ("LC-MS"), 335 ("CE-MS"),

340 ("MS-MS"), ("Sequencing"),

351 ("Nucleic Acids"),

352 ("Proteins"), 353 ("Glycopeptides, Carbohydrates"), ("Kinetics"),

361 ("Enzymes"),

362 ("Substrates"), 365 ("Metabolites"), 370 ("Immunoturbidimetry"), ("Microbiology"),

376 ("Colony Counting"),

377 ("Colony Differentiation"), ("Bioassays"), 381 ("Antibiotics Inhibition"),

385 CTmmunoaffinity"),

386 ("Binding Coefficients"), ("Chemical Structure"),

391 ("X-ray Crystallography"), ("Microscopy"),

396 ("Light/Polarisation Microscopy"),

397 ("Fluorescence Microscopy"),

398 ("Electron Microscopy"), 400 ("Macro / Micro Arrays"),

401 ("Microtiter Plates (96/384 Wells)"),

402 ("Agar Punchplates (6x6/8x8/12x12 Holes"),

405 ("CHIP-based Arrays"),

406 . ("High Density Arrays"),

410 ("Screening"),

460 ("Synthesis"),

500 ("Drug Discovery"),

600 ("Drug Development"), 680 ("Toxicology"),

700 ("Regulatory Compliance"),

701 ("Pre-clinical Trial"), 710 ("Clinical Trial, Phase I"), 720 ("Clinical Trial, Phase II"),

730 ("Clinical Trial, Phase IE"), 740 ("Post-Trial Compliance Compilation"),

750 ("QC/QA: Reproducibility"),

780 ("Method Reliability Tests"),

781 ("Accuracy"),

782 ("Repeatability"), 800 ("Generic Statistics Tools"),

801 ("Correlation"),

802 ("Regression"),

810 ("Pairwise Comparison"),

820 ("Similarity Clustering (Dendrograms)"), 830 ("Experiment Congruence (SimPlots)"),

840 ("Principal component Analysis"),

850 ("Self-organizing Map (SOM)"),

900 ("Modeling And Prediction"), 901 ("Separation Profile Forecast"),

910 ("Structure-Based Function"), 920 ("Clinical Trial Simulation"), INTELLIGENT OBJECT HANDLER

Methods are provided to define and describe an exemplary embodiment of an information technology platform architecture utilizing an Intelligent Object Handler (IOH) 202 and Intelligent Object (EVIO) 200 data structures as core processing components. The Intelligent Object Handler (IOH) 202 comprises a unified presentation layer (UPL) 206 to enable user interactivity, component processing engines and access interfaces required to enable interactive, secure, efficient, property-driven functional access to data content queried, presented and analyzed, utilizing a variety of raw data sources, applications and analytical components. Additionally, optional embodiments define and describe an information technology platform architecture utilizing the Intelligent Object Handler (IOH) 202 for any object data structures as core processing components.

For reasons of explanation, these methods, components and processes will be described in a fashion that does not represent the entity of simultaneous and/or interactive actions as they occur. However, it should be noted that the system herein described is composed of bi-directionally interactive components and interfaces which perform certain tasks simultaneously, or in a rapidly alternating fashion.

Examples of enabling code are provided to define and describe a single exemplary embodiment, which utilizes Microsoft C++ as the exemplary programming language. Additionally, software development tools not limited to Visual C++, Microsoft Foundation Classes (MFC), DIB image transformations and matrix-based graphical content generation were utilized to enable this specific embodiment. The overall architecture, its application across varied domains, its processing engines and its access interfaces are in no way limited to the utilization of Microsoft C++ or the Windows 32-bit operating system environment. It is readily apparent to anyone skilled in the art that other enabling software codes or enabling techniques may also be used, including for example Java, XML and other markup languages, and/or other similar techniques.

The Intelligent Object Handler (IOH) 202 may be compiled to run on multiple platforms, including, but not limited to, UNIX, Linux, Macintosh OS 9 and 10, or any Window 32-bit operating systems. The following hardware specifications are provided to define and describe the requirements for a specific exemplary embodiment, implemented for a

32-bit Microsoft Windows environment.

The depiction in FIG. 17, represents an embodiment of a graphical user interface (and the display image available via that interface) for interaction with Intelligent Object data. The dynamically defined menu bar shows extensible options in a standard order, consisting of, but not limited to, drop-down menu items such as file, edit, view, options, objects, selection, query, analysis, link, user, window and help-functions. Within the common user interface window, several independent sub-windows show a depiction of the Intelligent Objects, as well as related query and/or analysis tools and the real-time answer window, which presents the relevant results in their significance numerically and/or graphically.

The depiction in FIG. 18, represents an embodiment of a typical query profiler (and the screen display image resulting therefrom) utilizing Intelligent Object technology. Such queries can be performed using pre-definable templates, subsets of common, industry-specific questions, and/or by free form, user-defined entries and graphical "drag-and-drop" query definition.

The inventive system, architecture, method, and computer program and computer program product of the Intelligent Object Handler (IOH) as well as other core elements and modules described herein and in the related applications identified herein, may be used in a variety of computing and network or connectivity environments as are known in the art and advantageoulsy are hardware and operating system agnostic. For example, the invention may be practices with the great majority of contemporary personal computers, workstations, mainframes, as well as notebook and other portable computing devices and all manner of information appliances. Exemplary computing devices and components are for example illustrated in the embodiments illustrated in FIG. 8, FIG. 5, and FIG. 1 A.

It will be apparent to anyone skilled in the art in light of the description provided herein that these requirements are provided by way of instruction regarding a specific embodiment of the technology, and that the implementation of the Intelligent Object Handler

(IOH) 202 is not limited to the particular embodiments shown in the drawings as many optional components that provide optional and enhanced features are shown that are not required.

An overview of major presentation, processing and interface methods are provided below to describe and define, in an exemplary embodiment, the Intelligent Object Handler

(IOH) 202 comprised by information technology architecture for user interaction, viewing, analysis, and other automated and/or interactive data handling activities utilizing Intelligent Object (EVIO) 200 data as core components. In an optional embodiment, and Intelligent Object Handler (IOH) 202 utilizing a variety of object data is defined and described. The embodiment of the system, architecture, and method in FIG. 8, represents an exemplary embodiment of the inventive elements and their relationships, showing the relationship of the Intelligent Object to an external Intelligent Object Handler (IOH), its components and access interfaces, the legacy domain of existing data content, applications, and devices, and an external Intelligent Object Pool (IOP). Unbroken lines ending with arrows on each end 490 represent bi-directional communication between exemplary property panes, components and access interfaces. Dashed lines ending with arrows on each end 492 represent bi-directional communication between optional property panes, components and access interfaces. Forked lines 491 at or near the "interface to external legacy domain" were utilized for clarity due to the complexity of the figure, and represent unbroken bi-directional connectivity between opposed arrows. Crossed lines do not represent connections in this figure.

The depiction in FIG. 5, represents an exemplary embodiment of a hardware configuration for the Intelligent Object Handler and its enabling architecture. All major elements within the diagram below may be bi-directionally connected over a variety of network protocols. The minimum hardware requirement is defined by a single machine. In an exemplary embodiment, as below, two laptop computers are connected in a peer-to-peer configuration and in a client/server configuration to a workstation and via these workstation directly to a laboratory instrument, such as a gene sequencer or gel electrophoresis machine. Other connectivity schemes may alternatively or additionally be provided. In FIG. 5, dotted bi-directional lines 248 represent options for "any-to-any" connectivity enabled via use of Intelligent Objects as central accessing and routing components. Any-to-any options include but are not limited to LAN, WAN, peer-to-peer (e.g. data, applications, memory and processor sharing between two or more laptops, workstations, etc.), server-server, Portal, ASP and other unified, distributed, parallel and grid network options. Connectivity protocols include and are not limited to PPP, http, TCP/IP, and ftp over multiple platforms.

The depiction in FIG. 1A, represents an embodiment ofthe Intelligent Object Handler comprised within an exemplary software platform architecture (Sentient IT Platform). This embodiment depicts minimal core elements for the Intelligent Object Handler, along with the Intelligent Object, Intelligent Object Pool, and other components (Processing Engines) and access interfaces required by or desired in the Sentient IT Platform.

In an exemplary embodiment advantageously enabled in software, sets of structures and methods are provided for; unified, functionally integrated and user-directed interactivity with previously heterogeneous data and applications; applications environment and data definition and translation; and functional integration of heterogeneous and or homogeneous data objects and their contents with comprised and/or external as well as local and/or remote applications; including one or more of:

• An information technology platform, such as the Sentient (EVIO) IT Platform illustrated in FIG. 8 and FIG. 1A, comprising methods for user interactivity, applications environment and data definition and functional data and applications integration o utilizing Intelligent Objects (EVIO) 200 as core components; o providing interactive, dynamically defined menus, toolbars and user interface panes presented within a unified presentation layer (UPL) 206 to enable an interactive, functionally integrated graphical user interface; and o providing integration of heterogeneous data content for analysis by internal components and access interfaces as well as components and interfaces of other external applications or devices, over a variety of local and/or distributed connectivity protocols.

• Intelligent Object Handler (IOH) 202, comprising methods for one or more of: o enabling user interactivity within the Sentient IT Platform (See FIG. 1A); o providing interactive, dynamically defined menus, toolbars and user interface panes presented within the unified presentation layer (UPL) 206; and o providing functional integration of corresponding components and access interfaces, which comprise data-enabling methods for handling of Intelligent Objects (EVIO) 200 and their data content.

• User definition and administration (UDA) 2000 interface shell component, comprising methods for one or more of: o enabling its related menus and a user interface for user definition and privilege administration presented within the unified presentation layer (UPL) 206 comprised by the Intelligent Object Handler (IOH) 202, o providing issuance and regulation of access privileges within the entity of heterogeneous data network environments for Intelligent Objects (EVIO) 200.

• Intelligent Object generator (EVIO-G) 2002, comprising methods for one or more of: o automated generation of Intelligent Objects (EVIO) 200 corresponding to newly acquired, imported, or queried data content from laboratory devices

(Instrumentation) 1076 and/or heterogeneous data types; and o generation of initial Intelligent Object (EVIO) 200 state history records.

• Object state engine (OSE) 212 component, comprising methods for one or more of: o continuously monitoring, governing, synchronizing, recording and activating alerts for all activities of Intelligent Objects (EVIO) 200 in real-time and/or within latency environments; and o synchronization with and updating of a comparable continuously running status management component (SMC) 208 or comparable component comprised within a data structure. • Object standardization technique (EVIO-S) 2004, comprising methods for one or more of: o basic calibration of a variety of data content by calibration with standardized empirical criteria according to comprised algorithms; and o linking to additional components which normalize the data content, such as the object normalization engine (ONE) 210.

• Object normalization engine (ONE) 210, comprising methods for one or more of: o normalization of scientific data contained in objects for comparison independent of procedural errors resulting from variation in experimental and inherent in multiple datasets of different origins.

• Direct instrument acquisition and confrol (DIAC) 2006 interface, comprising methods for one or more of: o enabling its related menus, toolbars and user interface presented within the unified presentation layer (UPL) 206 comprised by the Intelligent Object (EVIO) 200 and linked via the master query component (MQC) 2012; and o providing for remote and/or local instrument control and/or data acquisition.

• Data type translator (DTT) 2008 component, comprising methods for o Defining and integrating heterogeneous data content, data types and structures as data content for Intelligent Objects (EVIO) 200, without writing to the data content.

• Object translation engine (OTE) 214, comprising methods for one or more of: o provision of nested vector table lookup and translation to enable required data type translation according to interactivity requirements of heterogeneous computing environments; o presentation of translated and defined data type dependencies to components which generate required representations ofthe data content; and o provision of varying data content access, routing and presentation protocols to components and interfaces required for functional integration of data and applications. • Application / database definition generator (ADG) 2010, comprising methods for o detection, extraction and definition of requirements for functional interaction with external applications, components, access interfaces and heterogeneous data resources.

• Master query component (MQC) 2012 , comprising methods for one or more of: o enabling its related menus, toolbars and user interface presented within the unified presentation layer (UPL) 206 comprised by the Intelligent Object Handler (IOH) 202, o fielding and directing automated and/or user queries and commands for data acquisition, retrieval, or analysis.

• Master query interface (MQI) 218, comprising methods for one or more of: o linking, accessing and routing of bi-directional vectorized data content pointers and meta-data tags between Intelligent Objects (EVIO) 200; and o directing of accessing and routing to and between linked processing components and access interfaces.

• Intelligent Object handle (EVIO-H) 2014 component, comprising methods for one or more of: o enabling its related menus, toolbars and user interface presented within the unified presentation layer (UPL) 206 comprised by the Intelligent Object Handler (IOH) 202 and linked via the master query component (MQC) 2012; o presentation and functional integration of the Intelligent Object (EVIO) 200 data with the user interface layer and its described functionality; via activation of external o methods for dynamic updating, activation, accessing and routing of bi- directional vectorized data content pointers and meta-data tags.

• Report generation interface (RGI) 220, comprising methods for one or more of: o assembly, tabulation, validation and ranking, according to information received from external processing engines and access interface components, of Intelligent Object (EVIO) 200 and data content information; and o relaying of generated results to external processing engines, access interfaces and pane descriptor components.

• Intelligent Object application framework (EVIO-A) 2016, comprising methods for one or more of: o user-directed functional assembly and functional integration of processing components and access interfaces comprised within the Intelligent Object

Handler (IOH) 202 as applications, modules or plug-ins; and optionally further comprising a component for o automated applications assembly according to dynamic, automated and/or user-directed processing requirements. • Application translation interface (ATI) 216, which comprises methods for o interface linking and translation for functional integration of applications, to provide user interactivity for Intelligent Object (EVIO) 200 data within heterogeneous data and applications environments.

In an optional embodiment, a set of interaction protocols are also provided, which may include one or any combination ofthe following:

• An IT Platform supporting the requirements ofthe inventive system and method, such as for example, the Sentient IT Platform illustrated in FIG. 1A, comprising methods for one or more of: o using data objects other than Intelligent Objects (EVIO) 200 as core components; o comprising menus, toolbars and user interface panes presented within a unified presentation layer (UPL) 206 to enable an interactive, functionally integrated graphical user interface; and o integrating internal components and access interfaces as well as components and interfaces of other external applications or devices over a variety of local and/or distributed connectivity protocols.

• A data object and applications handler (IOH) 202, comprising methods for o providing a core data and applications handling framework within an IT Platform (See FIG. 8 and FIG. 5), o provision of interactive menus, toolbars and user interface panes presented within a unified presentation layer (UPL) 206; and o provision of corresponding components and access interfaces, which comprise data-enabling methods for handling of various data objects and their data content.

The following embodiments defined and described in enabling detail by minimal set of processing components and access interfaces below as well as certain optional and advantageous embodiments. Alternative embodiments may or may not have corresponding or additional processing components, access interfaces and property panes with unique, functionality-driven properties. In this exemplary embodiment, the set of property panes, processing components and their corresponding access interfaces are defined as follows.

In an advantageous and exemplary embodiment, an information technology platform architecture such as for example the "Sentient IT Platform" (See FIG. 1A), as described here or in one or more of the related applications identified herein, advantageously enabled in software, comprises a unified presentation layer (UPL) 206 graphical user interface, processing components and access interfaces to enable functionally integrated user interactivity. The presentation layer, interfaces and components comprise sets of instructions for methods, processes and/or protocols including user interaction; data content definition, accessing, unified viewing, processing and routing; environment definition, accessing, unified viewing, processing and routing; to provide unified functionality within previously homogeneous and/or heterogeneous data and applications environments. The information technology platform allows for fast, efficient, functionally integrated, multidimensional accessing, routing; viewing; querying; analyzing; and other data-enabling operations via the utilization of comprised methods and/or processes including vectorized data content accessing and routing; direct information interchange between data objects; data-enabled parallel processing via organization, ranking and result generation of the information interchanged, according to Boolean and other statistical analyses; nested vector table translation; and nondestructive cache "overlay" processing.

The architecture utilizes Intelligent Objects (EVIO) 200 as core accessing; routing; and processing elements; and provides a set of components and access interfaces including but not limited to definition of Intelligent Object (EVIO) 200 and data content according to methods including but not limited to data object and content definition; data matrix structure definition; application requirements definition; data resource (database, data storage) definition; and preparation of Intelligent Object (EVIO) 200 and data content according to methods including but not limited to data content and activity synchronization; standardization; translation; validation; ranking; automated and/or interactive data organization; cache-based non-destructive processing; analysis and presentation of Intelligent Object (EVIO) 200 and data content according to methods including but not limited to direct data-to-data information interchange; vectorized accessing and routing of data content; metadata learning and optimization; to enable fast, efficient, functionally integrated interaction of Intelligent Object (EVIO) 200s within homogeneous and/or heterogeneous data and applications environments. h an advantageous and exemplary embodiment, an Intelligent Object Handler (IOH) 202, advantageously enabled in software, comprises a unified presentation layer (UPL) 206 graphical interface, processing components and access interfaces to enable functionally integrated user interactivity. These unified presentation layer (UPL) 206, components and interfaces comprise methods not limited to Intelligent Object (EVIO) 200 data as core elements, which provide methods advantageous for Intelligent Object handling, including but not limited to automated and/or interactive data and data resource access, routing, processing, translation, analytical integration, viewing, analysis and management. The Intelligent Object Handler (IOH) 202 comprises a multi-platform graphical user interface which functionally integrates plug-ins; components; modules; applications; interfaces; from sources not limited to diverse scientific; business; manufacturing; academic; manufacturing; and laboratory systems environments. The unified presentation layer (UPL) 206 provides methods advantageous for data Object Handling and analysis of data content, dynamically presented within the Handler to enable user interactivity, including but not limited to sets of customizable toolbars; user menus; and various analytical interfaces at the unified presentation layer (UPL) 206 , such as File New; Open; Open All (in directory); Close; Close All; Print preview; Print; (...); Edit; Undo; Redo; Cut; Copy; Paste; Select; Select All; as well as additional and easily extensible options for user interactivity and automated functionality. Owing at least in part to the significant operational advantages provided by the inventive system, architecture, method, and computer program and computer program product, the structure, function, and operation of aspects of the invention are described in the context of a series of experiments so that the manner in which a scientist or other investigator would utilize and interact with the system and method are clearly set forth. Elements of various structural, methodological, and computer program facets of the invention are described in this context.

In this description, data from protein expression studies based on 2-dimensional gel elecfrophoresis (2DE) are complex to inteφret due to the limited reproducibility of the experimental procedure, which typically does not allow for direct comparisons regarding spot position and quantity. Within the inventive intelligent object or intelligent molecular object EVIO technology, such object queries can be performed in real-time at an individual spot level.

The attached images of the user interface handling input/output operation between the Intelligent Objects demonstrate the effective, interactive real-time answer generation process.

Three examples are also described. "Example 1" depicts a specific embodiment of enabling code, providing instructions utilized for the exemplary embodiment of dynamic menu configuration for the Intelligent Object Handler's (IOH) main routing menu. "Example

2" depicts a specific embodiment of enabling code, providing instructions utilized in the user definition and administration (UDA) Shell. "Example 3" depicts a specific embodiment of enabling code, providing instructions utilized in the direct instrument data acquisition and control (DIAC) interface to remotely operate and/or monitor connected instrumentation in real-time. Functions such as status of the instrumentation, parameter queries, start-stop or pause-resume and the like are provided. A remote-control styled dialog and message handler are implemented.

Three examples showing specific instantiation of computer software program code are now described.

EXAMPLE 1 Example 1 shows a specific instantiation of enabling code, providing instructions utilized for the exemplary embodiment of dynamic menu configuration for the Intelligent Object Handler's (IOH) 202 main routing menu.

IMPLEMENT J YNCREATE(CMainDoc, COleDocument)

BEGIN JvIESSA GEJvIAP(CMainDoc, COleDocument) //{{AFXJvISGj AP(CMainDoc) 0NJJPDATEJ20MMANDJJI(ID_ANALYZE_STAT_SIMCLUSTER, On UpdateAnalyzeStatSimCluster)

ONjOOMMAND(ID_ANALYZE_STAT SIMCLUSTER, OnAnalyzeStatSimCluster) ONJJPDATE_COMMANDJJI(ID_FILEjSAVE, OnUpdateFileSave) ONjOOMMAND(IDJvALIDATE_RA WDATAJNTEG, On ValidateVerifylntegrity) ONJUPDA TE_COMMAND_UI(ID_VALIDA TE_RA WDA TAJNTEG, On Update Validate Verifylntegrity)

//}}AFX__MSG__MAP

//Enable default OLE container implementation ON_UPDATE_COMMAND_UI(IDJ DIT_PASTE, COleDocument: :OnUpdatePasteMenu)

ON_UPDATE_COMMAND_UI(IDJEDIT_PASTEJINK, COleDocument: : On UpdatePasteLinkMenu)

ONJJPDATE_COMMAND_UI(IDjDLE_EDITjOONVERT, COleDocument: : On UpdateObject VerbMenu) ONJOOMMAND(ID_OLE_EDIT_CONVERT, COleDocument: :OnEditConvert)

ON_UPDATE_COMMANDJJI(ID_OLE_EDITJLINKS, COleDocument: : On UpdateEditLinksMenu)

ON JCOMMAND(IDJDLE_EDITJJINKS COleDocument: :OnEditLinks) ONJJPDATEJOOMMANDJJI_RANGE(IDJDLE_VERB_FIRST, IDJDLE_VERB_LAST, COleDocument:. -OnUpdateObjectVerbMenu)

ENDJvIESSAGEJvIAPQ

hi a typical IOH configuration, the following menus as illustrated in FIG. 22 and FIG. 23 are available: File, Edit, View, Select, Options, Control, Analyze, Query, Validate, Report, Link, User, Maintain, Window, and Help. In FIG. 23, the menu of FIG. 22 is expanded using a menu pull-down feature. The FILE menu provides selections such as for creating, opening, closing, import or export of data; for printing, print preview or setup and to logout for user changes. The EDIT menu provides selections such as for cutting, copying, pasting, object insertion, linking and such for Undo ofthe last operation. The VIEW menu provides selections such as those for enabling of diverse toolbars, viewing of connections, graphical thumbnails; and such for viewing of specific lookup tables (LUTs) in individual windows such as object state, content attributes, database list, sample definitions, calibration functions and the like. The SELECT menu provides selections such as those for connection type, database or instrument integration and such to select devices for live data acquisition. The OPTIONS menu provides selections to preview individual results, aggregate results, enable distributed learning or to customize result aggregation. The CONTROL menu provides selections to control diverse instruments, cameras, imagers and for setup of experimental parameters in the analyzers or imagers. The ANALYZE menu provides selections for analytical modules, plug-ins or tools which provide content-specific analytical functions and data viewer. The QUERY menu provides selections to perform queries in form-based or graphical drag-and-drop fashion and a selection to launch a query profiler. The VALIDATE menu provides selections to verify data authenticity and integrity and to electronically sign object and raw data sets. The REPORT menu provides selections for a variety of reporting options as displayed in the example. The LESIK menu provides selections to link experiments, libraries, public resources and external applications.

The USER menu provides selections for user management as described for user definition and administration (UDA) 2000. The MAINTAIN menu provides selections such as those for backup, redundancy removal, manual metadata index update and performance-related parameter monitoring. The WINDOW menu provides selections such as those for arrangement of diverse windows across the main application window and a list of currently open windows. The HELP menu provides selections such as those for generic help topics, acronyms, contact, web link, check for updates and version information.

These components and access interfaces comprise methods for automated and/or interactive applications access, routing, translation, integration, viewing and management; automated and/or interactive data and data resource access, routing, processing, translation, integration, viewing, analysis and management.

The user definition and administration (UDA) 2000 component is functionally linked to a "User" menu comprised by the unified presentation layer (UPL) 206 within the Intelligent Object Handler (IOH) 202. The user definition and administration (UDA) 2000 component provides a set of instructions, advantageously enabled in software, comprising methods including bi-directional information interchange with components and access interfaces including the User menu, Intelligent Object generator (EVIO-G) 2002 component; object state engine (OSE) 208 component; and master query component (MQC) 2012; and which provides a user interface and functionality to set up and govern User preferences and privileges, including but not limited to password settings; look preference; color preference; local cache size; local cache clear; import settings; auto setup; connectivity profile (peer-to- peer, client/server, etc.); database access preference; applications list; personal data storage; and global user administration including a dynamically update list of user names; a dynamically update list of user levels including; Add User; Edit User; Export User; Import User; Lock/Unlock User; Retire User; Clear User; and Set Password.

EXAMPLE 2

Example 2shows a specific instantiation of enabling code, providing instructions utilized in the user definition and adminisfration (UDA) 2000 Shell. A process provides arrays for connection, user access tracking, logging and displaying.

{

CPlatformApp* app = (CPlatformApp*)AfxGetApp(); TCHAR computer jiamefMAXjCOMPUTERNAME JLENGTH + lj = {0}; DWORD size = M AX COMPUTERNAME JLENGTH + 1; GetComputerName(computer_name, &size);

CONNECTEDUSERS cu = {0}; Jcscpyφu.szComputerName, computer jiame); Jcscpyφu.szName, app->mjtUser.szName); Jcscpy(cu.szSessionID, app->mjtUser.szSessionID);

Jcscpy(cu.szlp Address, app->m trHostIp); cu.uuid = app->m_stUser.uuid; cu.timeLoginTime = app->m tUser.ti?neLoginTime;

mjιrrayConnectedUsers.Add(cu); // add to list

for(int i - 0; i < 3; i++) //write to file

{ CONNECTEDUSERS tmpj u = (0); key.Formatφnt, i);

GetPrivateProflleStruct(_T(" Connection"), key, &tmp u, sizeofftmp u), fileName); if(jcslen(tmp u.szSessionID) == 0)

{ WritePrivateProfileStruct(_T(' 'Connection"), key, &cu, sizeoflfcu), fileName); break;

The User Definition and Administration (UDA) shell provides dialog-based tools to add, edit, export, import, lock, unlock, retire user or to clear or request renewal of user passwords.

BEGIN_MESSAGE_MAP(CAdministrationDlg, CDialog)

//{{AFXJvISGj AP(CAdministrationDlg) ON__NOTIFY(LVNJTEMCHANGED, IDCJJSERLIST, OnltemChangedUserList) ONJ3N_CLICKED(IDC_CLEARPASSWORD, OnClearPassword)

ON_BNjOLICKED(IDC_EDITUSER, OnEditUser)

ONJ3N_CLICKED(IDCJJELETEUSER, OnDeleteUser)

ON_BN_CLICKED(IDC 4DDUSER, OnAddUser)

ONJ3NJCLICKED(IDCJOCKUSE OnLockUser) ONJ3NJOLICKED(IDC_SHOWACTIVE, OnS ow Active)

ONJ3N_CLICKED(IDC_SHOWALL, OnShowAll)

ON_BNjCLICKED(IDC_SHO WIN A CTIVE, OnShowInactive)

ON_BNj LICKED(IDC_EXPORTUSER, OnExportUser)

ON_BN_CLICKED(IDCJMPORTUSER, OnImportUser) //}}AFXjvISGj IAP

ENDJdESSAGEjvIAPQ

void C Admin istrationDlg: :Init UserListQ { mJistUser.DeleteAUItemsQ; mJistUser.DeleteColumn(5); mJistUser.DeleteColumn(4); mJistUser.DeleteColumnβ); mJistUser.DeleteColumn(2); tnJistUser.DeleteColumn(l); mJistUser.DeleteColumn(O);

DWORD flags = mJistUser.GetExtendedStyleQ; mJistUser.SetExtendedStyle ags | LVS_EX_FULLROWSELECT \ LVS_EX_GRIDLINES);

mJistUser.InsertColumn(0, _ T("User"), LVCFMTJJEFT); mJistUser.InsertColumn(l, _T("Level"), LVCFMTJJEFT); mJistUser.InsertColumn(2, _ T("Group"), LVCFMTJJEFT); mJistUser.InsertColumnβ, _ T("Status"), L VCFMTJJEFT); mJistUser.InsertColumn(4, _ T("Creation "), L VCFMTJLEFT); mJistUser.InsertColumnβ, _T("Termination "), L VCFMTJLEFT); mJistUser.SetColumn Width(0, L VSCWji UTOSIZEJJSEHEADER); mJistUser.SetColumn Widthβ, L VSCWji UTOSIZEJJSEHEADER); mJistUser.SetColumn Width(2, L VSCWji UTOSIZEJJSEHEADER); mJistUser.SetColumn Widthβ, L VSCWji UTOSIZEJJSEHEADER); mJistUser. SetColumn Width(4, L VSCWji UTOSIZEJJSEHEADER); mJistUser. SetColumn Widthβ, L VSCW__A UTOSIZEJJSEHEADER);

int txt vidth = 0; int col vidth = 0; for (int i = 0; i < mjtrrayUsers.GetSizeQ; i++)

{ if((mjιShowUsers == SHOWUSERS__ACTIVE) && (m_arrayUsers[iJ.byteStatus != USERSTATUS iCTIVE) || (mjiShowUsers == SHOWUSERSJN ACTIVE) && (mjirrayUsersfiJ.byteStatus ==

USERSTATUSjiCTIVE)) continue;

int index = mJistUser.InsertItem(i, m_aιτayUsers[i] .szUser); mJistUser. SetItemData(index, i); txt λήdth = mJistUser. GetStringWidth(m jirrayUsersfij .szUser) + 15; coljvidth = mJistUser. GetColumn Width(O); if (txtjvidth > coljvidth) mJistUser. SetColumnWidthfO, txtjvidth);

CString str = JT(""); switch(m ιrrayUsers[i].byteLevel) { case 1: str = JT(" Assistant"); break; case 2: str = JT("Technician "); break; case 3: str = _T("Researcher"); break; case 4: str = _T("Validator") ; break; case 5: str = _T("Chief); break; case 8: str = _T(" Department Head"); break; case 16: str = _ T("Maintenance") ; break; case 20: str = _T("Internal Technical Support"); break; case 32: str = _T(" Administrator"); break; case 64: str = __T("Super User"); break; default: ASSERT(FALSE);

} mJistUser. Setltemβndex, 1, LVIFJTEXT, str, 0, 0, 0, 0); txtjvidth = mJistUser.GetStringWidth(str) + 15; coljvidth = mJistUser. GetColumnWidth(l); ifftxt vidth > coljvidth) ?nJistUser.SetColumnWidth(l, txt vidth);

switch(m_arrayUsers[ij.byteType) { case 1: str — JT(" Administration"); break; case 2: str = JTβFinance"); break; case 3: str = _ T("Human Resources "); break; case 4: str = JT("Inventory"); break; case 5: str = _T("Logistics") ; break; case 6: str = _T("Management") ; break; case 7: str - _T("Marketing") ; break; case 8: str - _T("Production"); break; case 9: str = JT(" Pur chasing"); break; case 10: str = JT ("Regulatory Compliance"); break; case 11: str — JT("Research & Development") ; break; case 12: str = _T("Quality Control / QA") ; break; default: ASSERT(FALSE) ;

} m_listUser.SetItem(index, 2, LVIFJTEXT, str, 0, 0, 0, 0); txtjvidth = mJistUser. GetStήngWidfhφtr) + 15; col vidth = mJistUser. GetColumnWidth(2) ; if(txt__width > coljvidth) mJistUser.SetColumnWidth(2, txtjvidth);

switch(mjtrrayUsers[i].byteStatus) { case 0: str = _ T("Locked") ; break; case 1: str = _ T(" Active"); break; case 255: str = JT("Retired"); break; default: ASSERT (FALSE);

mJistUser.SetItem(index, 3, LVIFJTEXT, str, 0, 0, 0, 0); txtjvidth — mJistUser.GetStringWidth(str) + 15; coljvidth = mJistUser.GetColumnWidihβ); if(txt vidth > coljvidth) mJistUser.SetColumnWidthβ, txt vidth);

if(m_ arrayUsers[i] .timeCreation > 0)

{ CTime t(mjirrayUsers[i] .timeCreation); str = t.Format("%B %d, %Y"); mJistUser. Setltemfindex, 4, LVIFJTEXT, str, 0, 0, 0, 0); txtjvidth - mJistUser.GetStringWidth(str) + 15; coljvidth = mJistUser.GetColumnWidth(4); if(txt vidth > coljvidth) mJistUser. SetColumnWidth(4, txtjvidth);

}

if(m__arrayUsers[i].timeTermination > 0)

{ CTime t(mjιrrayUsers[i].timeTermination); str = t.Format("%B %d, %Y"); mJistUser.SetItem(index, 5, LVIFJTEXT, str, 0, 0, 0, 0); txtjvidth = mJistUser.GetStringWidth(str) + 15; coljvidth = mJistUser.GetColumnWidthβ); if(txtjvidth > coljvidth) mJistUser.SetColumnWidthβ, txtjvidth);

} mjiCurListlndex = 0; mJistUser.SetltemStatefmjtCwListlndex, L VIS_SELECTED, L VISJSELECTED); }

Subsequently, the user definition and adminisfration (UDA) 2000 shell component also handles user-selective preference setting. An example of such preferences, the output selection for a specific user profile is listed below.

CDialog) //{{AFXJvISGJvIAP(CPreferenceDlg)

ONJ3N_CLICKED(IDC_OUTPUTJ3ROADCAST, OnOutputBroadcast) ONJ3N_CLICKED(IDCjDUTPUT_FILELOCAL, OnOutputFileLocal) ONJ3N_CLICKED(IDC_OUTPUT_FILEPRINT, OnOutputFilePrint) ONJ3N_CLICKED(IDC_OUTPUT_PRINTER, OnOutputPrinter) ON_BNjCLICKED(IDCjDUTPUTjSCREEN OnOutputScreen)

//jJAFXJvISGJvIAP ENDj lESSAGEjvlAPQ

Additionally, the user definition and adminisfration (UDA) 2000 shell component provides a unified environment for user interactivity, importation and/or information entry regarding access and user privileges for local and/or remote data sources; applications; and other user activities within heterogeneous and/or homogeneous computing and/or network information environments.

A master query component (MQC) 2012 comprises methods including bi-directional information interchange with components and access interfaces including the unified presentation layer (UPL) 206, including but not limited to menus; toolbars; and query interfaces; object state engine (OSE) 208 component; Intelligent Object handle ( O-H) 2014 component; Intelligent Object application framework (EVIO-A) 2016 component; master query interface (MQD 218; direct instrument acquisition and confrol (DIAC) 2006 interface; and object translation engine (OTE) 214. The Master Query component presents externally defined security, access and interactivity protocols to the appropriate menus, toolbars and/or other elements comprised within the unified presentation layer (UPL) 206; and fields and directs automated and/or user-directed queries and commands, including but not limited to data acquisition; retrieval; viewing, and/or analysis. An Intelligent Object generator (EVIO-G) 2002 (EVIO-G) component comprises methods including bi-directional information interchange with components and access interfaces including the user definition and adminisfration (UDA) 2000 component; direct instrument acquisition and control (DIAC) 2006 component; object state engine (OSE) 208 component; and data type translator (DTT) 2008 component. The Intelligent Object generator ( O-G) 2002 interacts with the data type translator (DTT) 2008 component to automate transformation of heterogeneous data sources and types into Intelligent Object (EVIO) 200 data in real-time. Additionally, the Intelligent Object generator (EVIO-G) 2002 interacts with such as the user definition and administration (UDA) 2000 shell, the unified presentation layer (UPL) 206 and the Object State engine to field such as data import requests; user-based queries and/or commands; and/or automated queries provided by components and access interfaces, and to dynamically generate Intelligent Objects (EVIO) 200 based on fielded requirements and available data resources. Simultaneously, this Intelligent Object generator (EVIO-G) 2002 activates and updates the object state history via the object state engine (OSE) 208.

An exemplary embodiment of an object state history comprised of time-sequential set of object activity records is depicted in Table I. The table represents an embodiment of the object state history, comprising an object activity record. A typical record is shown from data object creation prior to data acquisition from an analytical instrument, several steps of calibrated analysis carried out by different users within and outside the local network. Note, that same state codes can occur within the object state history for different users, for example, output requests and the like.

With reference to FIG. 19, there is illustrated an embodiment of an object state engine (OSE). The central element of the object state engine is the active listening process (ALM), an processing thread or set of threads that is "always-on" or nearly always on, that is, running whenever the host machine is active. (Some non-on time may be provided for maintenance, power-savings, or according to some other rules or policies.) The object state engine governs activity on the object data level, via interaction with the status management component contained within an external Intelligent Object.

In FIG. 19, the two state processing elements are query state processing and object access processing, which handle Intelligent Object root addressing and interactive content routing, object-to-object interaction states, data information interchange definitions and workspace vector assignment. Object state processing includes storage of current state, history update functions, assignment of GLP/GMP-compliance via lookup table and ranking based on validation assessments. The outer pane represents the universal presentation layer (UPL), which contains non-time critical components for I/O operation and utilizes the state provided from the OSE for tasking. Object creation processes are only triggered by the OSE, but may be carried out within UPL for specific tasking such as user entry of ownership terms, or the like.

TABLE 1 depicts an embodiment of an object state history, comprised of time- sequential set of object activity records.

Object:

State User/level Network Date/time stamp (Explanation)

000 RAS/05 00220 12/20/2000 14:33:05 (object created)

011 WUD/02 00220 12/20/2000 14:33:07 (data: acquisition in progress)

014 WUD/02 00220 12/20/2000 16:53:07 (data: acquisition completed)

022 WUD/02 00220 12/20/2000 16:55:22 (data: matrix defined)

056 GOT/03 00220 12/21/2000 08:00:57 (image: dynam. range verified)

052 GOT/03 00220 12/21/2000 08:01:46 (image: fluoresc. intens. calib.)

041 GOT/03 00220 12/21/2000 08:16:31 (bio: quantitation calib.)

061 GOT/03 00220 12/21/2000 08:18:58 (image: origin calib.)

062 GOT/03 00220 12/21/2000 08:20:25 (image: size x calib.)

063 GOT/03 00220 12/21/2000 08:23:19 (image: size y calib.)

101 GOT/03 00220 12/21/2000 08:25:44 (std/norm: detection threshold)

164 GOT/03 00220 12/21/2000 08:41:12 (std/norm: measurement x)

165 GOT/03 00220 12/21/2000 08:45:30 (std/norm: measurement y)

901 KRE/05 00080 12/21/2000 08:45:31 (access denied)

911 AAH/02 04092 12/21/2000 08:45:44 (user: access to object granted)

071 AAH/02 04092 12/21/2000 08:45:50 (anno: descript. text)

024 GOT/03 00220 12/21/2000 08:52:12 (data: vector defined)

911 BLD/03 00693 12/21/2000 09:02:36 (user: access to object granted)

073 BLD/03 00693 12/21/2000 09:02:39 (anno: AA protein sequence)

045 GOT/03 00220 12/21/2000 09:14:08 (bio: immunol. activity)

046 GOT/03 00220 12/21/2000 09:39:41 (bio: other bio-activity)

410 GOT/03 00220 12/21/2000 09:42:31 (output: numerical output)

411 GOT/03 00220 12/21/2000 09:44:07 (output: graphical output)

430 GOT/03 00220 12/21/2000 09:42:31 (output: printed)

The object state engine 208 (OSE) comprises methods including bi-directional information interchange with components and access interfaces including the Status Management Components comprised by Intelligent Objects (EVIO) 200; master query component (MQC) 2012; Intelligent Object generator (EVIO-G) 2002; Intelligent Object standardization component; object and image normalization components; object translation engine (OTE) 214 component; data type franslator (DTT) 2008 component; direct instrument acquisition and confrol (DIAC) 2006 interface; and legacy synchronization interface (LSI) 2018. The object state engine (OSE) 208 provides continuously-running (always-on) sets of processes, or activity listening mode (ALM) which enable creation and identification, monitoring, recordation, governing, synchronization, validation and alerting activities for Intelligent Objects (EVIO) 200 in real-time and/or within latency environments.

The object state engine (OSE) 208 comprises methods for active listening (activity listening mode - ALM) 2028; state processing (State Processing) 2030; query processing

(Query Processing) 2032; and access processing (Access Processing) 2034.

Initially, the object state engine (OSE) 208 comprises methods for triggering the creation (Object Creation) 2024 of a new Intelligent Object (EVIO) 200 via the Intelligent Object generator (EVIO-G) 2002 and assigning a unique identifier to it (UID Assignment) 2026.

The object state engine (OSE) 208 comprises state processing (State Processing) 2030 methods such as recording Intelligent Object (EVIO) 200 activity or transaction to provide activity history (State Memory) 2036; assigning a defined state to the Intelligent Object (EVIO) 200 to synchronize the current action (Update History) 2038; and in advantageous embodiments, relating the activity history to GLP/GMP-compliant data states (G*P

Assignment) 2040; and providing a validation state-based information ranking component (G*P Ranking) 2042. Additionally, the object state engine (OSE) 208 may provide status memory over state-less networks by transmitting action consequences back to the backend system. The object state engine (OSE) 208 also comprises query processing (Query

Processing) 2032 methods such as handling of network requests (Network Request) 2050 and external query submissions (External Submission) 2046 to the Intelligent Object (EVIO) 200; governing query access (User Access Privilege) 2048 and output generation (Output Generation) 2054 according to provided user access privileges; providing query status updating (Query Status Update) 2044; and providing query result synchronization (Result

Synchronization) 2052.

The object state engine (OSE) 208 also comprises access processing (Access Processing) 2034 methods such as Intelligent Object root and data content addressing and routing (Object Routing) 2056; Intelligent Object-to-Intelligent Object linking and synchronization (Object: Object) 2058; state-related vector definition of object data subsets for dynamic information interchange (DII Definition) 2060; and synchronized accessing to raw data matrix vectors (RDM Vectors) 2062.

An object standardization technique (EVIO-S) 2004 comprises methods including bidirectional information interchange with components and access interfaces including the object state engine (OSE) 208; object normalization engine (ONE) 210 component; global image normalization component; and object translation engine (OTE) 214. The object standardization technique (EVIO-S) 2004 activates and interacts with these components to provide automated standardization; and normalization of data; by methods including calibration by standardized empirical criteria; calibration functions including but not limited to linear; non-linear; polynomial; exponential; logarithmic; cubic spline; adaptive; weighted point-to-point fit; and a variety of multi-parametric functions.

An object normalization engine (ONE) 210 component comprises methods including bi-directional information interchange with components and access interfaces including the object state engine (OSE) 208 and the object standardization technique (EVIO-S) 2004 component. The object normalization engine (ONE) 210 component provides methods, protocols and processing components which normalize scientific data contained in objects for comparison independent of procedural errors. These methods allow for accurate and precise comparison by eliminating the variability due to multiple sources of errors in the process of performing experiments and inherent in multiple datasets of different origins. These methods, protocols and processing components comprise automated and/or event-driven processes and algorithms which generate a normalized global standard to provide algorithms to which all similar data can be referenced to in regard to their field parameters contained within the raw data matrix; apply these algorithms to user-defined workspaces addressed by dynamically generated vector subsets to minimize data exchange and increase processing speed significantly, allowing for use of these algorithm even in network environments with limited data exchange capabilities; utilize a workspace cache area for this processing to maintain data content integrity at all times; provide algorithms for processing a variety of scientific data configurations such as timeline-related; spectra or wavelength-related; kinetics-related; migration- or separation-related data content matrices in single and multidimensional variations; locational deviations within arrays, bioassay-related and gene and/or protein sequence-related raw data matrices; multi-parameter normalization in respect to color, intensity, dynamic range and x/y/z distortions in 2D and 3D scientific images; x/y/z-alignment and component distance adjustments in molecular structures; and acoustic wave pattern and/or video signals. Another aspect of the object normalization engine (ONE) 210 provides a component comprised of one or several algorithms which detect non-obvious data redundancies in diverse data resources, databases, data marts or data warehouses; and eliminate or otherwise retire such multiple records. In another aspect of the object normalization engine (ONE) 210, algorithms are applied to subsets of decompressed workspaces within loss-free compressed raw data providing normalization to compressed data without the need for decompression of the entity of such data sets. In yet another aspect of the object normalization engine (ONE)

210, algorithms are used to track deviations from an established global standard; and to correct them in real-time for use in calibrated on-the-fly analysis applications. The object normalization engine (ONE) 210 also provides means for saving or transferring workspace cache area data converted by these algorithms between applications. A direct instrument acquisition and confrol (DIAC) 2006 comprises methods including bi-directional information interchange with components and access interfaces including but not limited to the Master Query; Intelligent Object generator (EVIO-G) 2002; object state engine (OSE) 208 component and external instruments and devices. The direct instrument acquisition and control (DIAC) 2006 interface comprises methods including automated detection and/or user definition of instrument and device dependencies, parameters, and/or operational method definitions; definition and functional integration of dependencies, parameters, and/or operational method definitions for interactive remote and/or local user interactivity and instrument control; an Instrument Control comprised by the unified presentation layer (UPL) 206, which presents information including but not limited to Connection status; such as presence or absence of connection; connection type information; instrument activity information such as run-time - hours, minutes, seconds; experiment status information such as validation status; instrument status information such as various operating parameters; and user interactivity such as start, pause, resume, stop; and which enables the acquisition of data content via instrumentation; and the generation of Intelligent Objects (EVIO) 200 corresponding to data content.

EXAMPLE 3

Example 3 shows a specific instantiation of enabling code, providing instructions utilized in the direct instrument acquisition and control (DIAC) 2006 interface to remotely operate and/or monitor connected instrumentation in real-time. Functions such as status of the instrumentation, parameter queries, start-stop or pause-resume and the like are provided. A remote-control styled dialog and message handler are implemented.

// RemoteDlg dialog

RemoteDlg::RemoteDlg(CWnd* pParent /*=NULL */) : CDialog(RemoteDlg::IDD, pParent) {

//{{AFXJDATAJNIT(RemoteDlg) //}}AFX__DATAJNIT

}

void RemoteDlg::DoDataExchange(CDataExchange * pDX)

{

CDialog: :DoDataExchange(pDX); //{{AFXJ ATAjvlAP(RemoteDlg)

//jjAFX DA TAJvIAP }

BEGIN __MESSAGEJvIAP(RemoteDlg, CDialog)

//{{AFXJvISGJvIAP(RemoteDlg)

ON_COMMAND(ID_SELECTjiNALYZEINTEG_REMOTE, OnSelectAnalyzelntegRemote)

//jjAFXJΛSGjVlAP END MESSAGEJMAPQ

// RemoteDlg message handlers void RemoteDlg:: OnSelectAnalyzelntegRemoteQ {

....

The direct instrument acquisition and control (DIAC) 2006 interface provides linking of user-defined and/or automatically detected instrument and/or device dependencies with the instrument control user interface; real-time, pre-programmed and/or latent viewing and interactivity from local and/or remote locations; and recordation of experimental and instrument running parameters via the object state engine (OSE) 208.

A data type translator (DTT) 2008 component is comprised within the Intelligent Object Handler (IOH) 202, comprising methods including bi-directional information interchange with components and access interfaces including the Intelligent Object generator (EVIO-G) 2002; object translation engine (OTE) 214 component and application framework component. The data type translator (DTT) 2008 provides methods to field applications and database environment definitions provided by an application / database definition generator (ADG) 2010 interface; and define data type dependencies as required for components and access interfaces including the Intelligent Object generator (EVIO-G) 2002, application framework and object translation engine (OTE) 214.

With respect to FIG. 20, there is shown an embodiment of object translation engine (OTE) showing its relationships to external databases and to certain required and optional components and access interfaces comprised within the Intelligent Object Handler. The object translation engine interacts with an application / database generator (ADG) 2010 and master query component (MQC) 2012 to provide Intelligent Object translation and functional integration with heterogeneous applications and data resource back-ends. An alternative embodiment of OTE is illustrated in FIG. 21. The object translation engine (OTE) 214 component comprises methods including bidirectional information interchange with components and access interfaces including the master query component (MQC) 2012; object state engine (OSE) 208 component; data type translator (DTT) 2008 component; application / database definition generator (ADG) 2010 and master query interface (MQI) 218. The object translation engine (OTE) 214 component also provides methods, protocols and processing components required to enable dynamic, automated franslation of previously heterogeneous and/or incompatible data into data types; structures formats; matrices; and various data content access and routing protocols required for functional integration including but not limited to heterogeneous and/or dynamically defined query, viewing or analysis protocols; processing components; access interfaces; data resources; and/or applications environments. Additionally, the object translation engine

(OTE) 214 comprises automated and/or event-driven processes, protocols and algorithms including but not limited to data object, data field and raw data matrix structure definition tables; data structure information for non-object data; data type, access and structure definition tables; database type, access and structure definition tables; application type, access and structure definition tables; table lookup to provide real-time franslation of the Intelligent

Object (EVIO) 200 within heterogeneous database and application environments; and linking of structure information and definition tables to dynamically direct Intelligent Object property pane activation and presentation (Property Panes) 1000; data object activation and presentation; data content activation and presentation; application activation and presentation; component activation and presentation; and interface activation and presentation; in real-time, according to defined data structure; database; and application requirements.

An application / database definition generator (ADG) 2010 component comprises methods including bi-directional information interchange with components and access interfaces including the object translation engine (OTE) 214; Intelligent Object application framework (EvIO-A) 2016; application translation interface (ATI) 216; external data content; databases and data resources; external applications and components. The application / database definition generator (ADG) 2010 enables the detection of structural and functional information necessary for standardization of non-object data; and for the presentation of standardized Intelligent Object (EVIO) 200 data for analysis within dynamically defined analytical environments. The application / database definition generator (ADG) 2010 also comprises and provides methods including the: extraction interface to diverse data object, data field and raw data matrix definitions and activation of external components for meta-data exfraction; extraction interface to diverse data type, access, structure and functional dependencies; extraction interface to diverse database type, access and structure dependencies; exfraction interface to diverse application type, access and structure dependencies; Additionally, the application / database definition generator (ADG) 2010 automates the query of all application and database requirements according to automated and/or user-defined requirements utilizing methods including data table extraction to determine data object, data field and raw data matrix definitions; data type extraction to determine data access and structure dependencies for Intelligent Objects (EVIO) 200; database type extraction to determine database access and structure dependencies; application type exfraction to determine application type, access and structure; Finally, the application / database definition generator (ADG) 2010 provides table definitions for look-up to provide real-time franslation of Intelligent Object (EVIO) 200 meta-data and data content between and within heterogeneous computing environments and defines the computing environment for components and access interfaces including the data type franslator (DTT) 2008, the application framework and the application translation interface (ATI) 216.

A master query interface (MQI) 218 comprises methods including bi-directional information interchange with components and access interfaces including the master query component (MQC) 2012; object franslation; Intelligent Object handle (EVIO-H) 2014 component; external object query interfaces comprised by Intelligent Objects ( O) 200; components and/or access interfaces comprised by an external Intelligent Object Pool (IOP) 204; an external result aggregation engine; and various data resources. Additionally, the master query interface (MQI) 218 comprises methods including linking of Intelligent Object (EVIO) 200 root routing information comprised within external unique object identifier interfaces; linking of components and access interfaces to direct interactive content routing provided by components comprised within external unique object identifier interfaces; linking of components and access interfaces to aggregated query result output provided by external result aggregation engines; linking components and access interfaces to other external components and access interfaces for query processing, such as but not limited to distributed learning engines; and knowledge exfraction engines.

An Intelligent Object handle (EVIO-H) 2014 component comprises methods including bi-directional information interchange with components and access interfaces including the master query component (MQC) 2012 ; master query interface (MQD 218; Intelligent Object application framework (EVIO-A) 2016 component; and a report generation interface (RGI) 220. The Intelligent Object handle (EVIO-H) 2014 component enables management of

Intelligent Object (EVIO) 200 data by activating information linking and directing information provided by components and access interfaces, including but not limited to data content attribute definitions; meta-data tags; and address vector pointers; comprised by Intelligent Objects (EVIO) 200, according to query and/or command parameters fielded by automated; and/or user-based methods. A report generation interface (RGI) 220 comprises methods including bi-directional information interchange with components and access interfaces including the Intelligent Object handle (EvIO-H) 2014 component; object translation engine (OTE) 214; distributed learning engines; knowledge extraction engines; and an external result aggregation engine component. The report generation interface (RGI) 220 comprising methods for assembly, tabulation, validation and ranking, according to information received from external processing engines and access interface components, of data content including data objects; specified meta-data indices of the intelligent Object (EVIO) 200 data and data content; and specified data content subsets; defined to levels of granularity as small as a single byte. Additionally, the report generation interface (RGI) 220 relays generated results to external processing engines, access interfaces and pane descriptor components in an automated, synchronized, real-time manner.

An Intelligent Object application framework (EVIO-A) 2016 comprises methods including bi-directional information interchange with components and access interfaces including the master query component (MQC) 2012; data type translator (DTT) 2008 component; Application/Database Definition Generator; Intelligent Object handle (EVIO-H)

2014; application franslation interface (ATI) 216; Intelligent Objects (EVIO) 200 and their content; and the Intelligent Object Pool (IOP) 204; applications comprised within the Intelligent Object Handler (IOH) 202 via modules and/or plug-ins, access interfaces, and processing components. The application framework provides methods including but not limited to fielding of automated and/or user-directed queries; applications assembly commands; processing requests; viewing requests; and other dynamic applications needs, and provides methods including but not limited to; detection; assembly; activation; synchronization and functional integration of required components, interfaces and protocols to enable assembly of unified applications; and activation of a comprised component for automated applications assembly within homogeneous and/or heterogeneous data resources; applications; access interfaces; and processing components environments.

The component for automated applications assembly comprised by the Intelligent Object application framework (EVIO-A) 2016 enables automated assembly of new applications during run-time ("just-in-time") from sets of components according to specific needs and best suited for complex processing requirements in heterogeneous data and applications environments. The automated applications assembly component comprises methods for selection and combination of required I/O components, such as components required to transfer data into and results out of individual analytical and/or descriptive and or annotative components; selection of algorithms best suited for processing of specifically defined data types or data type descriptors; dynamic combination of these components and algorithms towards automated and/or user-defined analytical performance goals, utilizing distributed subcomponent integration under best-fit conditions; activation of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications; synchronization of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications; assembly of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications memory ranking of performance-optimized component selection; memory ranking of information- optimized component selection; and best choice adjustment according to user-defined functional requirements.

In addition to its embodiment as comprised by the Intelligent Object application framework (EVIO-A) 2016, the automated applications assembly component may be contained in a stand-alone application or module for non-object data; in a stand-alone application or module for object data; or as a plug-in or module for an information technology platform containing Intelligent Object data. The automated applications assembly component may comprise further methods for selection of components based on their functional consistency and accuracy within all components assembled, such as, but not limited to functions for governing raw data precision; handling of mathematical errors; provision of data pointer referencing; matrix operation synchronization in regard to internal or external transformations and dimension descriptions; output rounding; determination of logical processing pathways; accounting for Boolean inheritances; iterative step frace-ing; and controlling and logging of rollback behavior; selection of components based on their immediate availability for real-time use; selection of components is based on the ranking among available components in regard to overall performance, such as, but not limited to: network traffic; local processing; remote processing; process sharing; distributed processing; direct "on-object"-processing; result clustering; and graphics element preprocessing and charting; selection of components based on the ranking among available components in regard to validation required for decisive answers (output knowledge assessment). Additionally, the automated applications assembly component may comprise further methods for provision of a vectorized "Application Archive Table" for quick referencing of previously assembled applications with similar processing needs; provision of "on-the-fly" temporary applications memory management for Just-in-Time (JIT) component linking, loading and unloading from the active caching area. The automated applications assembly component may also comprise further methods for provision of an intuitive interactive graphical user interface for drag-&-drop selection of components for process modeling and analytical simulations based on user output requests. The automated applications assembly component may also comprise further methods for provision of active communication with learning engines, such as for example, a distributed learning engine or knowledge extraction engine to optimize iterative processes or loop algorithms based on condition feedback. An application franslation interface (ATI) 216 comprises methods including bidirectional information interchange with components and access interfaces including the application / database definition generator (ADG) 2010; application framework; external result aggregation engine; and including but not limited to external data resources; applications; access interfaces; and processing components. The application translation interface (ATI) 216 comprises and provides methods including the; interface layer to present defined data object, data field and raw data matrix structure definitions utilizing provided definition look-up tables; interface layer to present defined data type, access, structure and function definitions, via provided look-up tables; interface layer to present defined database type, access, structure and function definitions provided via look-up tables; interface layer to present defined application type, access and structure definitions provided via look-up tables; transferring of requests such as read/write processes within or in-between external applications; Intelligent Object (EVIO) 200 and data content property presentation in real-time, according to defined requirements.

A legacy synchronization interface (LSI) 2018 comprises methods including bi- directional information interchange with components and access interfaces including the object state engine (OSE) 208; and external data content, databases, and data resources. Additionally, the legacy synchronization interface (LSI) 2018 provides comprised components, and interfaces to synchronize object data of various types with other data contained in off-line and/or batch processing legacy databases or external applications; synchronize Intelligent Object (EVIO) 200 data with other data contained in off-line and/or batch processing legacy databases or external applications in regard to their integrity, content and state; and to synchronize Intelligent Object (EVIO) 200 data content with external, off-line or temporarily unavailable data sets, including but not limited to raw data vector matrices linking; and property pane updating . hi another aspect, the legacy synchronization interface (LSD 2018 reports to the object state engine (OSE) 208 to update state history records for changes during times where activity-listening-mode is temporarily unavailable under conditions, such as, but not restricted to off-line; connection time-out; transaction acknowledgement errors; and/or record locking conflicts on the legacy end. In another aspect, the legacy synchronization interface (LSI) 2018 comprises methods for metadata index updating in batch mode; and for Intelligent Object (EVIO) 200 object pane descriptor (OPD) 1024 updating whenever object property panes are added or descriptors need to be modified; by relaying required information to the object state engine (OSE) 208 component. This may for example, be any OPD interface, such as an external OPD interface described with greater particularity relative to exemplary EVIO. In another aspect, the legacy synchronization interface (LSD 2018 provides link functions between "local state machines" and the object state engine (OSE) 208 component to enable real-time synchronous handshaking during connect and disconnect of heterogeneous legacy data and/or applications; transaction management and accounting for such as "once-and-only-once" transactions; linking between "local state machines" and components within the unified presentation layer (UPL) 206 of the Intelligent Object Handler (IOH) 202; to enable real-time platform- integration of external applications, which modify data properties during their execution, for synchronization and update. The described legacy synchronization interface (LSI) 2018 also contains a component which provides feedback on synchronization conditions including but not limited to frequency; updates; and timing preferences towards a variety of internally and/or externally comprised components and interfaces, such as knowledge exfraction engines; and distributed learning engines; and for automated synchronization and optimization based on event histories. The legacy synchronization interface (LSI) 2018 also contains a component, which provides logging and reporting of synchronization events to methods comprised within such as Intelligent Objects (EVIO) 200; processing components; access interfaces; applications; data resources and/or databases; and which provides the interface to integrate required methods to automatically request synchronization and/or metadata index updates based on provided instructions including protocols and definitions such as user preferences; user profiles; administrative; and/or maintenance actions.

In an optional embodiment, an information technology platform architecture advantageously enabled in software comprises a unified presentation layer (UPL) 206 graphical user interface, processing components and access interfaces to enable functionally integrated user interactivity. The presentation layer, interfaces and components comprising sets of instructions for methods, processes and/or protocols not limited to user interaction; data content definition, accessing, unified viewing, processing and routing; environment definition, accessing, unified viewing, processing and routing; for homogeneous and/or heterogeneous data and applications environments. The information technology platform allows for fast, efficient, functionally integrated, multidimensional accessing, routing; viewing; querying; analyzing; and other data-enabling operations via the utilization of comprised methods and/or processes including data-enabled parallel processing; via vectorized data content accessing and routing; direct information interchange between data objects; organization, ranking and comparison of data according to Boolean and other statistical analyses of the information interchanged; nested vector table translation; and nondestructive cache "overlay" processing. The architecture utilizes a variety of data objects as core accessing; routing; and processing elements; and providing a set of components and access interfaces including but not limited to definition of the data object and data content according to methods including but not limited to data object and content definition; data mafrix structure definition; application requirements definition; data resource (database, data storage) definition; and preparation of the data object and data content according to methods including but not limited to data content and activity synchronization; standardization; franslation; validation; ranking; automated and/or interactive data organization; cache-based non-destructive processing; analysis and presentation of the data object and data content according to methods including but not limited to direct data-to-data information interchange; vectorized accessing and routing of data content; meta-data learning and optimization; to enable fast, efficient, functionally integrated interaction of data objects within homogeneous and/or heterogeneous data and applications environments.

In an optional embodiment, a data object Handler comprises a unified presentation layer (UPL) 206 graphical interface advantageously enabled in software, utilizing processing components and access interfaces to enable functionally integrated user interactivity. The unified presentation layer (UPL) 206, components and interfaces comprising methods not limited to Intelligent Object (EVIO) 200 data as core elements, which provide methods advantageous for data object handling, including but not limited to automated and/or interactive data and data resource access, routing, processing, franslation, analytical integration, viewing, analysis and management. A multi-platform graphical user interface, which functionally integrates plug-ins; components; modules; applications; interfaces; from sources not limited to diverse scientific; business; manufacturing; academic; manufacturing; and laboratory systems environments. The unified presentation layer (UPL) 206 provides methods advantageous for data object handling and analysis of data content, dynamically presented within the handler to enable user interactivity, including but not limited to sets of customizable toolbars; user menus; and various analytical interfaces; such as File New; Open; Open All (in directory); Close; Close All; Print preview; Print; (...); Edit Undo; Redo; Cut; Copy; Paste; Select; Select All; (...); (...); These components and access interfaces comprise methods for automated and/or interactive applications access, routing, translation, integration, viewing and management; automated and/or interactive data and data resource access, routing, processing, translation, integration, viewing, analysis and management.

Having described many aspects of the invention, it will be apparent to those workers having ordinary skill in the art that various modification may be made to the various structures, organizations, methods, procedures, algorithms, organizations, interfaces, and the like provided by aspects of the invention. For example, other structures and methods may be utilized for the intelligent object handler. FIG. IB, shows one of many alternative embodiments of the Intelligent Object Handler, providing an overview for a more general understanding ofthe Intelligent Object Handler's functions. Through provision of these components and modules, real-time data flow to and from

Intelligent Object (EVIO) 200 data is described, governed, controlled, secured, and monitored and the data stream is minimized to provide means for highly efficient, non-redundant, global and selective real-time querying and reporting.

Methods defined and described include but are not limited to: cache-based non- destructive processing; information interchange of defined vector data subsets directly between data objects, applications, components and interfaces; directed meta-data and data content information interchange between data objects, applications, components and interfaces. Additionally, methods are defined and described which enable detection, exfraction, definition and functional interaction of and between comprised and/or external applications, components, interfaces and data. The representation definitions create state- relevant data presentation formats in accordance with data type conventions required by detected and/or user defined applications, databases, and analytical environments. The methods comprised within these Intelligent Object Handler (IOH) 202 and Sentient Platform information technology system (See FIG. 1A) enable actions including highly secure user interactivity over a variety of connection protocols; automated and/or user-defined data translation; automated and/or user-directed functional integration of data, applications and instrumentation over a variety of network protocols; direct data-to-data interaction; dynamic data content presentation within different Intelligent Object property pane (Property Panes) 1000 layers; and automated applications assembly. It is evident from the above description, that this object management architecture allows for efficient real-time processing of complex, multidimensional, interdependent queries by providing the applications and data handling framework and infrastructure on both the user-interface level and object-interaction level, to allow for a comprehensive analysis of otherwise inaccessible, inconsistent data sets. OPERATING AND BUSINESS MODEL PROVTOING INFORMATION SERVICES

Among its inventive aspects, the invention provides a revolutionary new information technology platform that places the power (in terms of response time to complex queries and analytical requests utilizing current tools, such as a common query in bioinformatics for detection of spots in a 2-D Elecfrophoresis gel) of an entire floor of clustered servers or 'massively parallel mainframe' computers (e.g. IBM, COMPAQ, or the like) at the hands of any scientist or consumer, for that matter, with a computer and a connection to the web. As a result, information processing, management and storage in every field imaginable (Life

Sciences, Agribusiness, Large Scale Manufacturing, Physics Imaging, and many more) are dramatically and revolutionarily more efficient and cost effective.

The inventive system, method, and business model is projected toward an initial market in the Life Sciences industries as a result of internal expertise and a tremendous and growing need for the kind of time efficiency and cost effectiveness that our IT Platform will provide.

To further facilitate the need of Life Science and Life Scientist, the invention provides developments and advances toward a number of product modules (typically implemented as computer program software for execution on computer systems) ranging from Drug Discovery, Genomics, Proteomics to Metabolism product modules, that will reside upon the platform and thereby enable the dramatic shortening of timelines for new drug development and gene therapies (while also providing for rapidly, validated diagnosis and treatment) in a Real-Time and cost effective manner. The abbreviated timelines will, in turn, provide cost savings for each new drug to the tune of at least $200 million dollars, while facilitating sales, based on earlier than expected market entry, upwards of $2 billion, for each new drug.

These IT platforms will become a standard, particularly as purveyors of solutions for substantially improved drug discovery, via its various Drug Discovery, Genomic and Proteomic product modules. The motivation for the platform architecture and its associated methods and procedures has arisen largely because, as a result of the human genome project and other related activities (genomics and proteomics), Biotech and Pharmaceutical companies are drowning in a flood of information, information which may hold the key to powerful and valuable new drug discoveries and gene therapies. Currently, Biotechnology and Pharmaceutical companies are spending upwards of $40 billion each year to sift through this information in order to uncover new drug candidates and potential gene therapies. Despite the vast sums of money being spent, the task of finding new drug candidates and gene therapies remains daunting, costly and highly inefficient. Some reasons for this can be traced to a number of factors, several of which include: a variety of different types and kinds of databases; applications and systems that cannot communicate with one another; the enormous cost to retool a company's existing information technology platform; the scarcity of bioinformatics specialist; and, the lack of appropriate analysis tools. As a result, Biotechnology and Pharmaceutical companies are facing three critical issues. The pressure to reduce cost, to speed up the entire process for new drug development and to recover R&D cost more quickly via the sales of new drugs. To date, this remains a wholly unrealized goal.

As a part of the solution, the inventive EVIO IT platform provides Biotech and pharmaceutical companies with the ability to quickly and cost effectively sort through the growing mass of information to discover and produce drugs in vastly reduced time periods and at greatly reduced cost. It will be possible as a result of the EVIO™ IT platform and drug discovery, proteomics and genomics modules for Biotech and Pharmaceutical companies to shorten the drug discovery process by 2 to 4 years and save upwards of $200 million. Additionally, the various Biotech and Pharmaceutical companies will benefit from earlier than expected revenues (several billion dollars), as a result of reduced development time and thus earlier than anticipated market entry for each new drug.

The inventive system and methods therefore also provide or support a number of new and novel business model and operating model innovations that satisfy the needs of the information community as well as provide revenue. Forming coφorate strategic relationships are part of this overall concept.

Business development efforts related to the inventive technology include marketing the inventive products and services to Biotech and Pharmaceutical research companies initially, and to Life Science companies, in general. Heretofore, the major participants in the field of Biotechnology software for data analysis have comprised the following three categories: Legacy Data Warehouses, data marts, ERP data mining tool companies, which provide proprietary applications and databases; Applications Service Providers (ASPs), Portals and other web-enabled service providers; and Network Integration Providers, which provide network integration of public databases, proprietary data and applications as well as support for local/remote collaboration and decision-making. These established companies, have been, in general, committed to legacy software, narrowly useful web-based technology, or piecemeal component-based integration solutions, which have depended and continue to depend on expensive mainframe, server cluster, and hardware-enabled "parallel processing" computing to provide their analytical product. As of yet, no clear leader has emerged to meet the demand for innovative software solutions within this rapidly expanding field, and therefore there remains a need for a more innovative and satisfactory solution.

Embodiments of the inventive system, method, and business model will generate revenue from, for example, at least one or more of the following areas; (1) the sale and licensing of its IT Platform, (2) the sale of its various Drug Development, Genomics,

Cheminformatics and Proteomics modules, (3) the sale and licensing of its data-pool assets, (4) royalties from strategic collaborations, and (5) internal use of the IT Platform for production of valued information such as for internal drug discovery or monitoring of such as public health data. Other revenue streams are also contemplated. Several exemplary application areas are now described by way of example. While the above referenced related patent applications have described innovations in information technology, especially for processing of high numbers of heterogeneous high-density data in heterogeneous computing environments, and more particularly in biotechnology, pharmaceutical, chemical, and life science environments, the invention is not so limited. The systems, methods, interfaces, engines, procedures, functions, algorithms, and other aspects of the invention as described here and in the related applications that are incoφorated by reference may advantageously be applied to and/or used in conjunction with information systems generally, physics imaging and analysis, intelligence integration and analysis, large scale manufacturing, agriculture and agribusiness, geographic information systems (GIS), the food industry, epidemiology, large scale forensics, economics and financial systems, health and human services, medical systems, as well as many other fields in which large amounts of data are involved. hi the field of Information Systems, applications of the inventive structure and method include but are not limited to Information Technology (IT) Platform(s), B2A infrastructure, database technology, and platform back-ends, among others. Some of the value in this area includes but is not limited to Flexible, Efficient, and Scalable Systems Integration; Data-enabling for Fast and Secure Data Access and Management; and Scalable and Efficient Applications Development Environment. Computer, network, and information systems providers may benefit from aspects ofthe invention. In the field of Physics Imaging and Analysis, applications of the inventive structure and method include but are not limited to Groundwater, Oil, Mineral Exploration, Mining, Mapping, and Real-time Analysis. Some of the value in this area includes but is not limited to Added Efficiency and Functionality for Remote, Magnetic and Sonic Imaging and Analysis, Reduced Exploration Costs, and Increased Predictive Accuracy for Reduced Exfraction Footprint. Organizations such as NASA, the Department of Energy, an mineral and resource exploration organizations may benefit from aspects ofthe invention.

In the field of Large Scale Manufacturing, applications of the inventive structure and method include but are not limited to Just-in-time (JIT) Inventory Management, Process Management, Robotics, and CAD/CAM. Some of the value in this area includes but is not limited to Improved Market, Acquisition and Inventory based on Global Data Access, Flexible and Scalable Process and Infrastructure Management, Real-time, and Integrated

Process Optimization. Automobile manufacturers, chemical manufacturers, semiconductor manufacturers, and other large scale material and manufacturing organizations may benefit from the inventive technology.

In the field of Agribusiness, applications of the inventive structure and method include but are not limited to GMO's, Crop Engineering, Seed Banks and Animal Breeding.

Some of the value in this area includes but is not limited to Enhanced Bioengineering Applications, Automated QA/QC, Integrated GLP/GMP, Inventory and Process Flow Automation, and Real-time Supply Chain Management. Chemical, textile, and other food research and production organizations may benefit from the inventive technology in this area. In the Food Industry, applications of the inventive structure and method include but are not limited to Modified Additives, Food fristantization, Food and Foodstuffs processing, Manufacturing Process Design and Automation, and Inventory and Product Distribution. Some of the value in this area includes but is not limited to Enhanced Bioengineering Applications, Automated QA/QC, Integrated GLP/GMP, Inventory and Process Flow Automation, and Real-time Supply Chain Management, among others. Consumer food producers, processors, and packagers will benefit from such technology. h the field of Epidemiology, applications of the inventive structure and method include but are not limited to Disease Studies, toxicology studies and analysis, and disease Outbreak Prevention. Some ofthe value in this area includes but is not limited to its Real-time capabilities, and its ability to provide Predictive Modules for Multidimensional Disease

Studies and Diagnostics. For example, the Center for Disease control (CDC), the Department of Health and Human Services (DHHS), and various governmental and environmental laboratories may benefit from such technology.

In the field of forensics, particularly Large Scale Forensics, applications of the inventive structure and method include but are not limited to Fingeφrint, DNA, and Materials

Analysis, and Real-time Data Integration and Access. Some of the value in this area includes but is not limited to Real-time Access to Global Data Records, On-site Fingeφrint, Photo Searching, and DNA matching. Law enforcement agencies such as the FBI, Pnteφol, and other investigative and law enforcement agencies will benefit from the technology, and in addition such organizations such as insurance companies and health maintenance organizations will benefit.

Therefore it will be appreciated that the invention is not limited to any particular field or application; rather, aspects of the invention may be applied to information technology generally where large amounts of heterogeneous data or information are involved.

Although the foregoing invention has been described in some detail by way of illustration and example for puφoses of clarity of understanding, it will be readily apparent to those of ordinary skill in the art in light of the teachings of this invention that certain changes and modifications may be made thereto without departing from the spirit or scope of the appended claims .

Claims

WE 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.

2. An Intelligent Object Pool as in Claim 1, comprising further methods, such as for a. provision of automated; event-driven; interactive; and/or user-directed methods for activation and implementation of comprised methods for; i. management and processing of Intelligent Object subsets (iPools); ii. assessment, ranking, alerting and validating data integrity; ii. management and processing of data exchange; iii. management and processing of data definition; iv. management and processing of process optimization; v. processing of queries; vi. processing of analyses; vii. processing of significance generation; iix. provision of data relationship viewing; ix. provision of data relationship analysis; x. provision of data relationship learning and knowledge extraction; and b. storage, processing and management of data subset Infra-Pools (iPools) comprising defined subsets of Intelligent Object data within said data Pool.

3. An Intelligent Object Pool as in Claim 1, comprising further methods for a. provision of pool boundary protocols, definitions and methods for data security; data integrity assessment; and data exchange via comprised components and access interfaces; b. provision of meta-data indices and query protocols, definitions and methods for

Intelligent Object meta-data definition and annotation; meta-data linking; access optimization, routing optimization and processing optimization via comprised components and interfaces; c. provision of pool content access protocols, definitions and methods for aggregate metadata definition; provision of meta-data definitions via table lookup for interactive content routing; d. provision of meta-data definitions via table lookup for direct information interchange between Intelligent Objects; aggregation of processing or query results; report generation; and data relationship viewing via comprised sets of components and interfaces.

4. An Intelligent Object Pool as in Claim 1, comprising further pool content access protocols including modules for distributed learning and knowledge exfraction; such as distributed learning engines (DLE/DLEi); and/or knowledge exfraction engines (KEE/KEEi).

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 of

2. data pool contents, comprising the entity of potentially accessible data objects and their data content.

6. An object pool as in Claim 5, comprising further methods, such as for a. provision of automated; event-driven; interactive; and/or user-directed methods for activation and implementation of comprised methods for; i. management and processing of subsets of data objects; ii. assessment, ranking, alerting and validating data integrity; iii. management and processing of data exchange; iv. management and processing of data definition; v. management and processing of process optimization; vi. processing of queries; vii. processing of analyses; viii. processing of significance generation; ix. provision of data relationship viewing; x. provision of data relationship analysis; xi. provision of data relationship learning and knowledge extraction; b. storage, processing and management of i. data subset Infra-Pools (subsets of data objects) comprising defined subsets of data object data within said data Pool.

7. An object pool as in Claim 5, comprising further methods for a. provision of pool boundary protocols, definitions and methods for data security; data integrity assessment; and data exchange via comprised components and access interfaces. b. provision of meta-data indices and related meta-data query protocols, definitions and methods for data object meta-data definition and annotation; meta-data linking; access optimization, routing optimization and processing optimization via comprised components and interfaces; c. provision of pool content access protocols, definitions and methods for aggregate meta-data definition; provision of meta-data definitions via table lookup for interactive content routing; provision of meta-data definitions via table lookup for direct information interchange between data objects; aggregation of processing or query results; report generation; and data relationship viewing via comprised sets of components and interfaces.

8. An object pool as in Claim 5, comprising further pool content access protocols including modules for distributed learning and knowledge exfraction; such as distributed learning engines (DLE/DLEi); and/or knowledge extraction engines (KEE/KEEi).

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.

10. A set of pool boundary protocol definitions as in Claim 9, comprising components and access interfaces providing further methods for a. generation and management of data availability and accessing information; b. management and processing of data subscribed to or otherwise exchanged; c. maintenance of access histories for auditing of exchange and ownership activities; and d. verification of data integrity states for quality assurance.

11. A set of pool boundary protocol definitions as in Claim 9, comprising components and access interfaces providing further methods for utilization of Intelligent Objects.

12. A set of pool boundary protocol definitions as in Claim 9, comprising components and access interfaces providing further methods for utilization of object-oriented data structures other than Intelligent Objects.

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.

14. A set of meta-data index definitions and methods as in Claim 13, comprising components and access interfaces providing further methods for a. generating meta-data index definitions for sets of data; b. provision of meta-data information required for definition, translation and integration of Intelligent Objects; c. integration of analytical processes with Intelligent Objects and iPools; and d. providing meta-data index-based optimization of Intelligent Object-to-

Intelligent Object and iPool-to-iPool intercommunication.

15. A set of meta-data index definitions and methods as in Claim 13, comprising components and access interfaces providing further methods for a. utilizing meta-data information to activate methods and algorithms such as nested vector lookup tables; interactive presorting and exclusion algorithms and object clustering algorithms.

16. A set of meta-data index definitions and methods as in Claim 13, comprising components and access interfaces providing further methods for utilization of Intelligent Objects.

17. A set of meta-data index definitions and methods as in Claim 13, comprising components and access interfaces providing further methods for utilization of object-oriented data structures other than Intelligent Objects.

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.

19. A set of pool content access definitions and methods as in Claim 18, comprising components and access interfaces providing further methods for a. data relationship viewing; b. application of custom-defined methods to data sets; c. real-time significance detection; d. real-time significant answer generation; and e. report generation.

20. A set of pool content access definitions and methods as in Claim 18, comprising components and access interfaces providing further methods for a. enabling object-to-analysis tools interactions; b. provision of result merging algorithms; and c. provision of clustering algorithms; including i. calculation methods not limited to 1. Jacquard coefficient; 2. Dice coefficient;

3. Jeffrey coefficient;

4. Pearson coefficient

5. simple matching;

6. product moment correlation coefficient; 7. mean square difference; and;

8. absolute difference; and ii. clustering methods: not limited to

1. minimum variance;

2. single, complete, average and weighted average linking;

3. median method; 4. cenfroid method;

5. neighbor joining method;

6. Fitch-Margoliash least square method; and

7. Fitch-Margoliash evolutionary clock method.

21. A set of pool content access definitions and methods as in Claim 18, comprising components and access interfaces providing further methods for provision of learning and knowledge exfraction algorithms.

22. A set of pool content access definitions as in Claim 18, comprising components and access interfaces providing further methods for utilization of Intelligent Objects.

23. A set of pool content access definitions as in Claim 18, comprising components and access interfaces providing further methods for utilization of object-oriented data structures other than Intelligent Objects.

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 adminisfration permissions provided by such as an external Intelligent Object Handler; iPool access permissions; and Intelligent Object access permissions.

25. An iPool security authentication component as in Claim 24, comprising further methods for

a. implementation of criteria for permission or denial to access and/or route subsets of data content defined to the level of single bytes by activation of vectorized pointers to said data content.

26. An iPool security authentication component as in Claim 24, comprising further methods for a. implementation of criteria for permission or denial to access and/or route subsets iPool meta-data information and definitions; including at least one or some combination of iPool content overviews; and iPool relationship information.

28. An iPool security authentication component as in Claim 24, which comprises further methods for definition and implementation of data according to conditions of ownership.

29. An iPool security authentication component as in Claim 24, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

31. An iPool security authentication interface as in Claim 30, comprising further methods for detection and extraction of information required for iPool security authentication.

32. An iPool security authentication interface as in Claim 30, comprising further methods for interchange of information required for and/or provided by iPool security authentication including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data- enabling information.

33. An iPool security authentication interface as in Claim 30, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by iPool security authentication.

34. An iPool security authentication interface as in Claim 30, comprised within an information technology platform using Intelligent Objects.

35. An iPool security authentication interface as in Claim 30, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

37. An iPool availability monitoring component (iPAM) as in Claim 36, comprising further methods for a. access management for iPool data content according to availability; b. generation of meta-data definitions regarding data availability; and c. provision of data and data subset cacheing for flagged data including at least one or some combination of specified Intelligent Object data; Intelligent Object data content workspace subsets; offline Intelligent Object data; and for data including at least one or some combination of user defined; often used; and recently used data.

38. An iPool availability monitoring component (iPAM) as in Claim 36, comprising further methods for a. provision of data content backup functionality for specified data; b. provision of multiple content addressing for specified or often used data; b. data nomenclature alias detection and linking; and c. multiple address ranking and management.

39. An iPool availability monitoring component as in Claim 36, comprised as a module within an information technology platform for Intelligent Objects.

40. An iPool availability monitoring component as in Claim 36, comprised as a module within an information technology platform using object-oriented data structures.

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.

42. An iPool availability monitoring interface as in Claim 41, comprising further methods for detection and extraction of information required for iPool availability monitoring.

43. An iPool availability monitoring interface as in Claim 41, comprising further methods for interchange of information required for and/or provided by iPool availability monitoring including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data- enabling information.

44. An iPool availability monitoring interface as in Claim 41, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by iPool availability monitoring.

45. An iPool availability monitoring interface as in Claim 41, comprised within an information technology platform using Intelligent Objects.

46. An iPool availability monitoring interface as in Claim 41, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

48. An iPool exchange protocol component as in Claim 47, comprising further methods for a. definition regarding criteria for exchange, including i. protocols and/or algorithms for Intelligent Object data attribute access; ii. protocols and/or algorithms for such as ownership, licensing, and subscriptions; iii. protocols and/or algorithms for such as exchange charges, and royalties; iv. protocols and/or algorithms for exchange accounting; and v. account definitions; b. provision of user ownership management; c. provision of user ownership recordation; d. provision of authentication and permission or denial of iPool access requests; according to correspondence of i. user ownership verification to comprised definitions such as for access, routing and processing;

49. An iPool exchange protocol component as in Claim 47, comprising further methods for a. provision of user exchange activity history provided by an interface to an external Intelligent Object Handler; b. provision of data attribute access and linking activities; c. provision of ownership, licensing, and subscription status; d. provision of fees, charges and royalty status information; including i. previewing of fees, charges and/or royalty terms and conditions according to proposed queries and/or user commands defined but not yet requested.

50. An iPool exchange protocol component as in Claim 47, comprised as a module within an information technology platform for Intelligent Objects.

51. An iPool exchange protocol component as in Claim 47, comprised as a module within an information technology platform using object-oriented data structures.

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.

53. An iPool exchange protocol interface as in Claim 52, comprising further methods for detection and extraction of information required for iPool exchange protocol.

54. An iPool exchange protocol interface as in Claim 52, comprising further methods for interchange of information required for and or provided by iPool exchange protocol including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

55. An iPool exchange protocol interface as in Claim 52, comprising further methods for bidirectional interchange of data content accessed via vector pointers as required for and/or provided by iPool exchange protocol.

56. An iPool exchange protocol interface as in Claim 52, comprised within an information technology platform using Intelligent Objects.

57. An iPool exchange protocol interface as in Claim 52, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

59. An object integrity assessment component as in Claim 58, comprising further methods for

a. review of Intelligent Object state histories for alerts or integrity violations; and b. provision of various authentication and integrity verification procedures as required for quality assurance/quality control.

60. An object integrity assessment component as in Claim 58, comprising further methods for

a. provision of alerts regarding Intelligent Object integrity violation status; and b. provision of alerts regarding processes that may or will violate Intelligent Object integrity.

61. An object integrity assessment component as in Claim 58, comprising further methods for activation of an interactive user interface providing a description of said alert and providing optional processing methods and/or cancellation of said processes.

62. An object integrity assessment component as in Claim 58, comprised as a module within an information technology platform for Intelligent Objects.

63. An object integrity assessment component as in Claim 58, comprised as a module within an information technology platform using object-oriented data structures.

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.

65. An object integrity assessment interface as in Claim 64, comprising further methods for detection and extraction of information required for object integrity assessment.

66. An object integrity assessment interface as in Claim 64, comprising further methods for interchange of information required for and/or provided by object integrity assessment including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data- enabling information.

67. An object integrity assessment interface as in Claim 64, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by object integrity assessment.

68. An object integrity assessment interface as in Claim 64, comprised within an information technology platform using Intelligent Objects.

69. An object integrity assessment interface as in Claim 64, further comprised within an information technology platform using object-oriented data structures other than Intelligent

Objects.

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.

71. An iPool integrity assessment component as in Claim 70, comprising further methods for a. review of iPool histories for alerts or integrity violations; and b. provision of various authentication and integrity verification procedures as required for quality assurance/quality control.

72. An iPool integrity assessment component as in Claim 70, comprising further methods for a. provision of alerts regarding iPool integrity violation status; and b. provision of alerts regarding processes that may or will violate iPool integrity.

73. An iPool integrity assessment component as in Claim 70, comprising further methods for a. activation of an interactive user interface providing a description of said alert and providing optional processing methods and/or cancellation of said processes.

74. An iPool integrity assessment component as in Claim 70, comprised as a module within an information technology platform for Intelligent Objects.

75. An iPool integrity assessment component as in Claim 70, comprised as a module within an information technology platform using object-oriented data structures.

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.

77. An iPool integrity assessment interface as in Claim 76, comprising further methods for detection and exfraction of information required for iPool integrity assessment.

78. An iPool integrity assessment interface as in Claim 76, comprising further methods for interchange of information required for and/or provided by iPool integrity assessment including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data- enabling information.

79. An iPool integrity assessment interface as in Claim 76, comprising further methods for bidirectional interchange of data content accessed via vector pointers as required for and/or provided by iPool integrity assessment.

80. An iPool integrity assessment interface as in Claim 76, comprised within an information technology platform using Intelligent Objects.

81. An iPool integrity assessment interface as in Claim 76, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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 as 1. 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.

83. An iPool meta-data index component as in Claim 82, further comprising methods for a. exclusion of irrelevant object data layers; b. provision of result aggregation optimization based on linking of result aggregation requirements to iPool Meta-data index content; and c. provision of query optimization based on linking of query parameters to iPool Meta-data index content.

84. An iPool meta-data index component as in Claim 82, further comprising methods for provision of iPool meta-data information required for methods and processes including at least one or some combination of iPool activation; iPool sorting; iPool-to-iPool queries; iPool data presentation; and result generation.

85. An iPool integrity assessment component as in Claim 82, comprised as a module within an information technology platform for Intelligent Objects.

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.

88. An iPool meta-data index interface as in Claim 87, comprising further methods for detection and exfraction of information required for iPool meta-data indexing.

89. Pool meta-data index interface as in Claim 87, comprising further methods for interchange of information required for and/or provided by iPool meta-data indexing actions including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

90. Pool meta-data index interface as in Claim 87, comprising further methods for bidirectional interchange of data content accessed via vector pointers as required for and/or provided by iPool meta-data indexing.

91. Pool meta-data index interface as in Claim 87, comprised within an information technology platform using Intelligent Objects.

92. Pool meta-data index interface as in Claim 87, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

94. A real-time meta-data linking component as in Claim 93, comprising further methods for linking of meta-data detected corresponding to meta-data comprised within linked meta-data indices said meta-data comprising at least one or some combination of attributes; annotations; properties, values, definitions; tables; lists; addressing protocols; access and routing protocols; processing protocols; and/or query parameters.

95. A real-time meta-data linking component as in Claim 93, comprising further methods for a. activation of methods and processes corresponding to linked meta-data; b. provision of relevant data access based on correspondence of said query and/or processing request meta-data parameters to provided meta-data indices.

96. A real-time meta-data linking component as in Claim 93, comprised as a module within an information technology platform for Intelligent Objects.

97. A real-time meta-data linking component as in Claim 93, comprised as a module within an information technology platform using object-oriented data structures.

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.

99. A real-time meta-data linking interface as in Claim 98, comprising further methods for detection and extraction of information required for real-time meta-data linking.

100. A real-time meta-data linking interface as in Claim 98, comprising further methods for interchange of information required for and/or provided by real-time meta-data linking including meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data- enabling information.

101. A real-time meta-data linking interface as in Claim 98, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by real-time meta-data linking.

102. A real-time meta-data linking interface as in Claim 98, comprised within an information technology platform using Intelligent Objects.

103. A real-time meta-data linking interface as in Claim 98, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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 of i. Intelligent Object state information; structure; function; type; and content; further comprising ii. meta-data information such as content addressing; content association; weighting; sorting; and ranking; of such as attributes; annotations; and definitions.

105. An Intelligent Object-to-Intelligent Object query component as in Claim 104, comprising further methods for a. provision of definitions for Intelligent Object-to-Intelligent Object information interchange; comprising meta-data definitions; lists; tables; indices; for b. activation of direct meta-data to meta-data information linking; accessing; routing; and information interchange corresponding to automated and/or user- directed queries.

106. An Intelligent Object-to-Intelligent Object query component as in Claim 104, comprising further methods for a. organization of said Intelligent Object content and meta-data linking according to information including at least one or some combination of content attributes; validation state; ranking; relationships; associations; and the like for b. provision of query optimization; based on dynamic updating of said Intelligent

Object organization and linking for information interchange; according to correspondence between said information and queries; query histories; commands; command histories; and/or other access, routing and processing actions.

107. An Intelligent Object-to-Intelligent Object query in Claim 104, comprised as a module within an information technology platform for Intelligent Objects.

108. An Intelligent Object-to-Intelligent Object query component as in Claim 104, comprised as a module within an information technology platform using object-oriented data structures.

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.

110. An Intelligent Object-to-Intelligent Object meta-data query interface as in Claim 109, comprising further methods for detection and exfraction of information required for customization and/or optimization of Intelligent Object-to-Intelligent Object queries.

111. An Intelligent Object-to-Intelligent Object meta-data query interface as in Claim 109, comprising further methods for interchange of information required for and/or provided by Intelligent Object-to-Intelligent Object query processes, said information comprising metadata index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

112. An Intelligent Object-to-Intelligent Object query interface as in Claim 109, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by intelligent Object-to-Intelligent Object meta-data queries.

113. An intelligent Object-to-Intelligent Object query interface as in Claim 109, comprised within an information technology platform using Intelligent Objects.

114. An Intelligent Object-to-Intelligent Object query interface as in Claim 109, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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 of i. Intelligent Object state information; structure; function; type; and content; further comprising ii.' meta-data information such as content addressing; content association; weighting; sorting; and ranking; of such as attributes; annotations; and definitions.

116. An iPool-to-iPool query component as in Claim 115, comprising further methods for a. provision of definitions for iPool-to-iPool information interchange; comprising meta-data definitions; lists; tables; indices; for b. activation of direct meta-data to meta-data information linking; accessing; routing; and information interchange corresponding to automated and/or user- directed queries.

117. An iPool-to-iPool query component as in Claim 115, comprising further methods for organization of said iPool content and meta-data linking according to information including at least one or some combination of content attributes; validation state; ranking; relationships; associations; and the like for provision of query optimization; based on dynamic updating of said iPool organization and linking for information interchange; according to correspondence between said information and queries; query histories; commands; command histories; and/or other access, routing and processing actions.

118. An iPool-to-iPool query in Claim 115, comprised as a module within an information technology platform for Intelligent Objects.

119. An iPool-to-iPool query component as in Claim 115, comprised as a module within an information technology platform using object-oriented data structures.

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.

121. An iPool-to-iPool meta-data query interface as in Claim 120, comprising further methods for detection and extraction of information required for customization and/or optimization of iPool-to-iPool queries.

122. An iPool-to-iPool meta-data query interface as in Claim 120, comprising further methods for interchange of information required for and/or provided by iPool-to-iPool query processes, said information comprising meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

123. An iPool-to-iPool query interface as in Claim 120, comprising further methods for bidirectional interchange of data content accessed via vector pointers as required for and/or provided by iPool-to-iPool meta-data queries.

124. An iPool-to-iPool query interface as in Claim 120, comprised within an information technology platform using Intelligent Objects.

125. An iPool-to-iPool query interface as in Claim 120, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

126. An aggregate meta-data index generator component (aMDX), for generating metadata 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.

127. An aggregate meta-data index generator as in Claim 126, comprising further methods for a. 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 i. including meta-data for such as iPool subset attributes; annotations; protocols; ontologies; content attributes; data type, structure, and access dependencies; ownership and access information; relationship information; activity ranking histories; significance ranking histories; and validation ranking histories.

128. An aggregate meta-data index generator as in Claim 126, comprising further methods for a. organization; sorting and ranking of said information according to available algorithms for assessment of relationships such as at least one of the following similarity; association; contiguity; proximity; dependency; functionality; for b. query optimization requirements, based on correspondence of submitted query parameters; and query histories; to contents of meta-data indices.

129. An aggregate meta-data index generator as in Claim 126, comprising further methods for a. generation of meta-data information required for methods and processes including at least one or some combination of iPool activation; iPool sorting; iPool-to-iPool queries; iPool data presentation; and result generation.

130. An aggregate meta-data index generator as in Claim 126, comprised as a module within an information technology platform for Intelligent Objects.

131. An aggregate meta-data index generator as in Claim 126, comprised as a module within an information technology platform using object-oriented data structures.

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.

133. An aggregate meta-data index generator interface as in Claim 132, comprising further methods for detection and extraction of information required for customization and/or optimization of meta-data index generation.

134. An aggregate meta-data index generator interface as in Claim 132, comprising further methods for interchange of information required for and/or provided by meta-data index generation, said information comprising meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

135. An aggregate meta-data index generator interface as in Claim 132, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by meta-data index generation methods and processes.

136. An aggregate meta-data index generator interface as in Claim 132, comprised within an information technology platform using Intelligent Objects.

137. An aggregate meta-data index generator interface as in Claim 132, further comprised within an information technology platform using object-oriented data structures other than

Intelligent Objects.

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 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 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.

139. An aggregate real-time significance generator as in Claim 138, comprising further methods for organization of data utilizing methods and processes including assembly; ranking; classification; and/or tabulation of Intelligent Objects; based on the significance of results generated by external applications; components; access interfaces; and activated by query submissions, user preference rules and/or viewing instructions.

140. An aggregate real-time significance generator as in Claim 138, comprising further methods for a. comparison of normalized parameters such as data content values; and metadata index properties provided by direct Intelligent Object-to-Intelligent Object; and iPool-to-iPool information interchange provided via addressing including at least one or some combination of vector subset pointing; meta-data index addressing; and activated by such as query submissions, user preference rules and/or viewing instructions; for b. organization of Intelligent Object and iPools, utilizing methods and processes including assembly; ranking; classification; and or tabulation of Intelligent Objects.

141. An aggregate real-time significance generator as in Claim 138, comprised as a module within an information technology platform for Intelligent Objects.

142. An aggregate real-time significance generator as in Claim 138, comprised as a module within an information technology platform using object-oriented data structures.

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.

144. An aggregate real-time significance generator interface as in Claim 143, comprising further methods for detection and extraction of information required for customization and/or optimization of processes for significance detection and generation.

145. An aggregate real-time significance generator interface as in Claim 143, comprising further methods for interchange of information required for and/or provided by significance generation, said information comprising nested vector lookup tables and meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

146. An aggregate real-time significance generator interface as in Claim 143, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by meta-data index generation methods and processes.

147. An aggregate real-time significance generator interface as in Claim 143, comprised within an information technology platform using Intelligent Objects.

148. An aggregate real-time significance generator interface as in Claim 143, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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.

150. A result aggregation engine component as in Claim 149, further comprising methods for a. generation of aggregated, customized, assembled, ranked, validated, and/or otherwise classified meta-data profiles; and b. generation of aggregated, customized, assembled, ranked, validated, and/or otherwise classified meta-data outputs and updates such as for iPool definition updates; iPool relationship definitions; Intelligent Object definition updates; and

Intelligent Object relationship definitions pertaining to Intelligent Object and iPool properties, values and relationships

151. A result aggregation engine component as in Claim 149, further comprising methods for generation of aggregated and otherwise organized results for presentation and reporting via an external Intelligent Object Handler.

152. A result aggregation engine component as in Claim 149, comprised as a module within an information technology platform for Intelligent Objects.

153. A result aggregation engine component as in Claim 149, comprised as a module within an information technology platform using object-oriented data structures.

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.

155. A result aggregation engine interface as in Claim 154, comprising further methods for detection and exfraction of information required for customization and/or optimization of processes for result detection and aggregation.

156. A result aggregation engine interface as in Claim 154, comprising further methods for interchange of information required for and/or provided by result aggregation, said information comprising nested vector lookup tables and meta-data index information such as

, data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

157. A result aggregation engine interface as in Claim 154, comprising further methods for bidirectional interchange of data content accessed via vector pointers as required for and/or provided by result aggregation methods and processes.

158. A result aggregation engine interface as in Claim 154, comprised within an information technology platform using Intelligent Objects.

159. A result aggregation engine interface as in Claim 154, further comprised within an information technology platform using object-oriented data structures other than Intelligent

Objects.

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.

161. An EVIO Zoom component as in Claim 160, further comprising methods for a. exfraction of graphical viewing information; b. processing of graphical viewing information; and c. addressing of graphical viewing information; i. said graphical viewing information comprising at least one or some combination of thumbnail views, expanded or "zoomed" views, data relationship overviews; self-organizing maps; similarity clustering; dendrograms; charts; tables; and/or additional graphical representations.

162. An EVIO Zoom component as in Claim 160, further comprising methods for a. activation of thumbnail viewing of such as Intelligent Object data content; iPool data contents; according to correspondence of meta-data or data content attributes to automated and/or user-directed queries and/or commands.

163. An EVIO Zoom component as in Claim 160, further comprising methods for a. provision of user-directed and/or automated graphical pre-sorting and sorting of such as said Intelligent Objects according to correspondence of data content attributes to automated and/or user-directed queries and/or commands.

164. An EVIO Zoom component as in Claim 160, comprised as a module within an information technology platform for Intelligent Objects.

165. An EVIO Zoom component as in Claim 160, comprised as a module within an information technology platform using object-oriented data structures.

166. An EVIO Zoom interface (EVIO-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 EVIO 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 EVIO Zoom viewing processes; and provision of access confrol for information interchange to and from said Intelligent Objects, Intelligent Object Pool, iPools, components and interfaces.

167. An EVIO Zoom interface as in Claim 166, further comprising automated and/or interactive methods for a. synchronization of said viewing information interchange and activity b. recordation of said viewing information interchange and activity; c. auditing of said viewing information interchange and activity; d. validation of said viewing information interchange and activity.

168. An IMO Zoom interface as in Claim 166, comprised within an information technology platform using Intelligent Objects.

169. An EVIO Zoom interface as in Claim 166, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

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/or iv. optimization of accessing, routing and processing protocols for user workspaces; Intelligent Objects; Intelligent Object Pools; and iPools.

171. A distributed learning engine component as in Claim 170, comprising further methods for interactive application of protocols, functions and algorithms for learning utilizing including at least one or some combination of user queries; automated queries; customized sets of queries; data objects such as the Intelligent Object; data handlers such as the Intelligent Object Handler; data pools such as the Intelligent Object Pool; iPools; the global data entity; and or data subsets therein as a data resource.

172. A distributed learning engine component as in Claim 170, comprising further methods for a. application of a comprised set of pool content access definitions, which may include but are not limited to the following cross-reference clustering; Boolean network algorithms; Bayesian network algorithms; neural network algorithms; iterative learning algorithms; time series analysis algorithms; pattern matching algorithms; structure matching algorithms; and rule induction algorithms; to enable b. at least one or more of the following automated, dynamic and/or interactive processes for iterative refinement; significance detection; tabulation; validation; ranking; assembly; and/or other forms of distributed learning.

173. A distributed learning engine component as in Claim 170, comprising further methods for provision of said learning processes within a local environment, such as on a single computer containing meaningfully related data and analytical applications.

174. A distributed learning engine component as in Claim 170, comprised as a module within an information technology platform for Intelligent Objects.

175. A distributed learning engine component as in Claim 170, comprised as a module within an information technology platform using object-oriented data structures.

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.

177. A distributed learning engine interface as in Claim 176, comprising further methods for detection and exfraction of information required for customization and/or optimization of processes for distributed learning.

178. A disfributed learning engine interface as in Claim 176, comprising further methods for interchange of information required for and/or provided by distributed learning, said information comprising nested data content vector lookup tables and meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

179. A disfributed learning engine interface as in Claim 176, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by distributed learning methods and processes.

180. A disfributed learning engine interface as in Claim 176, comprised within an information technology platform using Intelligent Objects.

181. A distributed learning engine interface as in Claim 176, further comprised within an information technology platform using object-oriented data structures other than Intelligent

Objects.

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 exfraction 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.

183. A knowledge extraction engine component as in Claim 182, further comprising methods for a. application of a comprised set of pool content access definitions, which may include but are not limited to the following cross-reference clustering; Boolean network algorithms; Bayesian network algorithms; neural network algorithms; iterative learning algorithms; time series analysis algorithms; pattern matching algorithms; structure matching algorithms; and rule induction algorithms; to enable b. at least one or more of the following automated, dynamic and/or interactive processes for iterative refinement; significance detection; tabulation; validation; ranking; assembly; and/or other forms of knowledge extraction.

184. A knowledge exfraction engine component as in Claim 182, further comprising methods for interactive application of protocols, functions and algorithms for knowledge exfraction utilizing including at least one or some combination of user queries; automated queries; customized sets of queries; data objects such as the Intelligent Object; data handlers such as the Intelligent Object Handler; data pools such as the Intelligent Object Pool; iPools; the global data entity; and/or data subsets therein as a data resource.

185. A knowledge extraction engine component as in Claim 182, comprised as a module within an information technology platform for Intelligent Objects.

186. A knowledge extraction engine component as in Claim 182, comprised as a module within an information technology platform using object-oriented data structures.

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 exfraction 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.

188. A knowledge extraction engine interface as in Claim 187, comprising further methods for detection and exfraction of information required for customization and/or optimization of processes for knowledge extraction.

189. A knowledge extraction engine interface as in Claim 187, comprising further methods for interchange of information required for and/or provided by knowledge extraction, said information comprising nested data content vector lookup tables and meta-data index information such as data content information; data attribute information; data relationship information; protocols; ontologies; annotations; and other data-enabling information.

190. A knowledge exfraction engine interface as in Claim 187, comprising further methods for bi-directional interchange of data content accessed via vector pointers as required for and/or provided by knowledge extraction methods and processes.

191. A knowledge exfraction engine interface as in Claim 187, comprised within an information technology platform using Intelligent Objects.

192. A knowledge extraction engine interface as in Claim 187, further comprised within an information technology platform using object-oriented data structures other than Intelligent Objects.

193. A system comprising

1. 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 metadata;

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 metadata 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 metadata 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 EVIO Zoom component (EVIO-Z) for interactive user viewing;

30. an EVIO Zoom interface (BVIO-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.

194. A data structure ("Intelligent Molecular Object, hereinafter "Intelligent

Object") providing methods for unified, functional integration and unified data content access and management, wherein the methods comprise: a. at least one component comprising procedures for persistent data content and activity status management; and b. at least one interface comprising procedures for functional integration and information interchange between the data, associated data and applications, components and interfaces.

195. An Intelligent Object as in Claim 1, wherein the procedures for persistent data content and activity status management further comprise a. at least one component comprising procedures for persistent data content and activity status management across diverse data types, content and computing environments; and b. at least one interface comprising procedures for direct data content addressing, definition and presentation of data content properties for information interchange between said data, associated data and applications, components and interfaces across diverse data types, content and computing environments.

196. An Intelligent Object as in Claim 1, wherein said procedures for persistent data content and activity status management across diverse data types, content and computing environments further comprise a. at least one set of procedural steps for data content access and processing synchronization; b. at least one set of procedural steps for persistent data content access and processing logging and auditing; c. at least one set of procedural steps for monitoring and verification of data integrity, command history, and regulatory validation states.

197. An Intelligent Object as in Claim 1, wherein said interface procedures for direct data content addressing, definition, presentation and functional integration further comprise methods for: a. vectorized access, routing, franslation, linking and comparison of data content information such as data content and data content subsets ("workspaces") defined to granularity from entire data content files to data content subsets as small as single byte workspaces; b. and direct interchange of information not limited to said not limited to processing information, commands, queries, meta-data, data content and said defined workspace subsets; i. between said data objects; and ii. between said data objects, heterogeneous applications and a variety of components, access interfaces, and presentation layers.

198. An Intelligent Object as in Claim 1, further comprising: a. a set of unified presentation layers ("property panes") comprising methods for user viewing and interactivity; b. a set of unique components (and / or "processing components") comprising methods for raw data matrix mapping, status management, data access and routing, data content franslation and / or activation of external processing components for data processing; and c. a set of functional interface layers ("access interfaces") comprising methods for direct data content comparison and information interchange between addressed data content, meta-data, applications and components.

199. A data structure as in Claim 1, further comprised as a core element within an information technology platform architecture ("Sentient Platform") advantageously enabled in software, comprising methods for: a. functional data integration, multidimensional data accessing and routing, viewing, querying, analyzing and other data-enabling operations i. utilizing single data content files and / or high numbers of complex, heterogeneous and / or interdependent data content files which are functionally unified, although utilizing diverse and / or distributed data content resources; and ii. capable of simultaneously utilizing data content stored in diverse and distributed database and / or data storage resources, diverse computational hardware and network environments with diverse and dynamic application needs.

200. The creation method of said data structure, which comprises methods and processes not limited to a. automated detection of data content newly available locally and / or over networks that correspond to actions including user initiated and / or automated queries, user initiated and / or automated data acquisition activities and / or data import requests b. invocation of a new unique object identifier property pane via a component comprised within an external object handler, c. assignation of a globally unique identifier, d. generation of functionally integrated property panes within the Intelligent Object; e. identification of all user-defined and content attribute based connections to the data structure; and f. listing within the unique object identifier property pane of information comprising the Intelligent Object's creator, network and / or local routing information, content attribute information, information on connected users, access permissions, authentication information such as globally unique identification and public key encryption status, and current session information; and g. state history recordation of all Intelligent Object activity over networks and / or within local computing environments.

201. A unique object identifier property pane (UID), for interactive user, data, session and machine authentication, comprising methods for a. bi-directional information interchange with an external application for data handling and applications integration ("IOH") and a comprised unique object identifier access interface; and b. provision of globally unique identification of said Intelligent Object utilizing globally unique identifiers comprising an 128-bit alphanumeric string.

202. A unique object identifier property pane as in Claim 8, wherein the procedures for identification further comprise methods for: a. provision of additional identification information including; i. data creation information, comprising time, date and machine identification information; ii. ownership information, comprising unique identification information for the object creator; iii. security setting information, comprising access permissions, readonly permission, write permission; iv. routing information, comprising raw data content addressing information and Intelligent Object data addressing information; and v. real-time information about locally or remotely connected users, comprising user's unique identification information; computer name; login time; network address or location information; and session identification information; and b. at least one rule or policy for object data security which either permits or denies access for information interchange between data objects, data content, users and applications, based on comprised criteria for session, user and data authentication.

203. An interactive content router component (ICR), for addressing of data content access and routing, comprising methods for a. bi-directional information interchange with components and access interfaces including said object root router component, a status management component, an object pane descriptor component, and a unique object identifier Access Interface; and b. utilization of information provided by said object pane descriptor component and comprised meta-data index information to optimize linking, organization and direction of vectorized access and routing requests, processing commands, and information interchange between such as Intelligent Objects, heterogeneous and / or homogeneous data objects and data content, applications, data resources and / or databases.

204. An interactive content router component as in Claim 10, further comprising methods for a. implementation of read-only access to data content, and routing of said vectorized data to an external application for data handling, for cache-based processing according to non-destructive overlay methods; b. addressing to multiple data content locations according to provided criteria; c. direction of said vectorized data content access and routing within any local computing environment, local network, wide area network and / or global network; d. direction of meta-data, data content and / or processing results routing within said computing environments; e. Additionally, said comprised methods and processes report data content origination and routing information to a unique object identifier access interface.

205. An object root router component (ORR), for addressing, accessing and routing ofthe Intelligent Object, comprising methods for a. bi-directional information interchange with components and access interfaces such as a unique object identifier access interface, an interactive content router component, and a status management component; b. definition ofthe origin ofthe Intelligent Object; and c. addressing for access and routing ofthe Intelligent Object.

206. An object root router component as in Claim 12, further comprising methods for a. definition of the origin of the Intelligent Object and for multiple addresses to said Intelligent Object, locally and / or over any local network and / or global network; b. definition of the origin of associated data objects according to object description and relationship definitions; and c. addressing for data management, accessing and routing of the Intelligent Object within local, distributed and / or remote database and data storage technology.

207. A unique object identifier access interface (UEDi), for authentication, validation, and gating permission or denial of access to said Intelligent Object and comprised data content, comprising methods for a. bi-directional information interchange with components and access interfaces including an object root router component, interactive content routing component, status management component and said unique object identifier property pane; and b. permission or denial of access to said elements, components and access interfaces.

208. A unique object identifier access interface as in Claim 14, further comprising methods for a. fielding of electronic signatures for validated identification and authentication.

209. An object state engine property pane (OSE), for viewing and interactivity regarding Intelligent Object state information, comprising methods for a. bi-directional information interchange with components and access interfaces including an external object handler user interface and a status management component; and b. interactive, real-time Intelligent Object activity viewing, activity alerting, auditing and manual activity synchronization.

210. An object state engine property pane as in Claim 16, further comprising methods for a. detailed activity logging via a linked status management component of state attributes including: globally unique user identification; computer, instrument or device identification; login date and time; logout date and time; user;

Intelligent Object and data content addressing information; unique session identification; data authentication information; data integrity information; user access authentication and / or denial of access; session activity records; data ranking status; and / or validation states.

211. An always-on status management component (SMC), for persistent data object state history and status management, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object root routing component, said interactive content routing component, said unique object identification access interface, said object state engine property pane, an object graph preview component, an object pane descriptor component, and an external object state engine; and b. launching of and interaction with said external object state engine component.

212. An always-on status management component as in Claim 18, further comprising methods for a. communication with an external object state engine to enable monitoring of data integrity, command history and regulatory validation states; b. communication with an external object state engine to enable viewing of instrument parameters related to acquisition of data content and / or other instrument activities c. communication with said object state engine to provide automated validation status verification according industry-specific validation requirements not limited to Good Practice (G*P)-compliance including GLP Laboratory Information Management Systems (LEVIS); U. S. Food and Drug Adminisfration Center for Drug Evaluation and Research (FDA CDER ); Codebook for Forensic Investigation Requirements (CFIR); and International Organization for Standardization (ISO 9000); and d. provision of ₍information including data acquisition state; calibration information; applied transformation or analysis processes; and validation state (Object State List - Table 1) to the object state engine property pane; e. utilization of comprised state history information and non-destructive overlay processing techniques for data integrity protection and verification; auditing; logging; and detailed rollback to previous Intelligent Object data states; and f. functional integration of data and applications via interactive information exchange with external components that provide processes including data type franslation and applications integration.

. An object query interface access interface (OQI), for massively parallel and direct Intelligent Object-to-Intelligent Object information interchange, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an object pane descriptor component, a meta-data index access interface, and said status management component; b. reception of query requests from the status management component and an external object state engine component; c. implementation of queries across data subsets comprised within homogeneous and / or heterogeneous data content storage resources, based on query information provided by the object pane descriptor component, metadata index interface and status management component; d. initiation of direct object-to-object information interchange in parallel with corresponding Intelligent Objects via their comprised object query interfaces, by directing the interactive content routing of specified data vectors and / or meta-data index information directly between object query interfaces and of other Intelligent Objects for linking, comparison and relationship definition; e. relaying said data content information to an external result aggregation engine for further processing and presentation to the user via the unified presentation layer user interface; routing of results of Boolean comparisons and other algorithms applied to linked data content and/or meta-data compared back to the object pane descriptor- property pane for presentation to the user; and f. routing of results of said direct object-to-object information interchange to i. update an object pane descriptor component and ii. update a meta-data index access interface.

214. An object query interface access interface as in Claim 20, further comprising methods for a. implementation of queries across data subsets comprised within an external object data storage resources, based on query information provided by the object pane descriptor component, meta-data index interface and status management component;

215. A meta-data index property pane (MDX), for unified user viewing and interactivity with data object meta-data, comprising methods for: a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration and a meta-data index access interface; b. viewing of meta-data index information relating to said Intelligent Object and its data content and activity, said information comprising automatically generated and / or user-defined meta-descriptions and query relationship frees regarding information comprising specific data functionality and / or relationships to other data and / or data inter-dependencies.

216. A meta-data index property pane as in Claim 22, further comprising methods for: a. interactive user definition and updating of said meta-data index information relating to said Intelligent Object and its data content and activity.

217. A meta-data index access interface (MDXi), for functional integration of data object meta-data according to user activities, data properties and analytical requirements, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object query interface, said meta-data index property pane, and an object pane descriptor component; b. dynamic integration of meta-data information resulting from such as user- based and / or automated query histories, various applied analytical command and result histories, user-defined meta-data entries, and / or a combination thereof; and aggregation and integration of results of multi-parametric clustering and/or other data analyses; and c. provision of sets of rules to optimize access and routing and by said Intelligent Object.

218. A meta-data index access interface as in Claim 24, further comprising methods for a. extraction, integration and implementation of a variety of result aggregation, distributed learning and knowledge extraction algorithms, such as but not limited to external result aggregation engines; distributed learning engines; and knowledge extraction engines.

219. An object pane descriptor property pane (OPD), for unified user viewing and interactivity with data object properties presented within the entity of property panes, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration and an object pane descriptor component; and b. provision of an overview of properties presented within said Intelligent Object's property panes such as, but not limited to data content attributes, data state, data location and / or locations, data environment definitions, data structure and / or structures, meta-data, locally available and / or remotely linked applications, processing components and access interfaces, linked databases and / or data resources; and c. provision of graphical data content and information views of linked data and applications.

220. An object pane descriptor property pane as in Claim 26, further comprising methods for a. viewing of information highlighting functional relationships between Intelligent Object data properties, and related applications and data; and b. interactive "drag and drop" functionality to enable user definition of custom and / or automated analytical requirements.

221. An object pane descriptor component (OPD), for functional integration of data object properties presented within the entity of property panes, comprising methods for a. bi-directional information interchange with components and access interfaces including said interactive content routing component, said status management component, said object query interface, said meta-data index access interface, said object pane descriptor property pane, an object graph preview property pane, an object graph preview access interface, an object access manager component, an applications / database definition router access interface, and a mafrix structure descriptor component; to provide b. dynamic detection, updating, routing and presentation of information required for functionality defined by the entity of object property panes comprised by said Intelligent Object; and c. direct linking of data with functionally related Intelligent Objects, data content and related applications; to enable d. unified analysis of data from homogeneous and /or heterogeneous data types from homogeneous and / or heterogeneous sources.

222. An object pane descriptor component as in Claim 28, further comprising methods for a. provision of an overview of properties presented within said Intelligent Object's property panes, such as data content attributes, data state, data location and / or locations, data environment definitions, data structure and / or structures, meta-data, locally available and / or remotely linked applications, processing components and access interfaces, linked databases and / or data resources b. provision of information regarding functional relationships of data objects, data content and meta-data.

223. An object pane descriptor component as in Claim 28, further comprising methods for a. provision of functionally related data object, data content and meta-data information comprising: data content attributes; data content interrelationships; data state; data location and / or locations; data environment definitions; data structure and / or structures; b. provision of said information for functional linking, vectorized accessing and routing of data content, meta-data and processing results; c. functional integration of said data within a computing environment comprising locally available and / or remotely linked applications; processing components; access interfaces; databases and / or data resources located within local computing environments, local networks, wide area networks and / or global networks; and d. viewing and interactive user definition and updating of said information to provide integrated functionality of properties defined by the entity of object property panes .

224. An applications / database definition router interface (ADDR), for definition and provision of application and database dependencies, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object pane descriptor component and a matrix structure descriptor interface; b. addressing and functional linking of data content for interactivity with heterogeneous applications, databases and / or data resources.

225. An applications / database definition router interface as in Claim 31, further comprising methods for a. detection, exfraction and definition of required and / or available data content attributes, data state, data locations, data environment definitions, data structures required for interactivity with locally available and / or remotely linked applications, databases and / or data resources.

226. An object graph preview property pane (OGP), for unified user viewing of data content, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration user interface, said status management component, said object pane descriptor component and an object graph preview interface; b. user reviewing of data content such as low-resolution graphical "thumbnail" data previews.

227. An object graph preview property pane as in Claim 33, further comprising methods for a. interactive user identification of data content subsets for accessing and user reviewing.

228. An object graph preview property pane as in Claim 33, further comprising methods for a. Interactive user identification of data content for access according to metadata and vectorized data access protocols; and b. user reviewing of heterogeneous data content within a unified presentation environment comprising methods for detailed audio, graphic, digital video, review.

229. An object graph preview property pane as in Claim 33, further comprising methods for a. definition and selection of workspace subsets, which may include an entire data content file or a subset of said data content as small as a single byte, to applications such as pattern detection, normalization, comparison, 2D and

3D viewing and / or analysis; b. interactive linking to external methods provided for detailed data relationship viewing, such as a data pool viewer; and c. viewing of subsets of data content and / or linked data with corresponding content attributes.

230. An object graph preview interface (OGPi), for accessing and directing graphical data content, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object pane descriptor component, said object graph preview property pane, and an object access manager component; b. routing and linking of data content between applications windows; and c. linking of limited resolution image/graphics ("thumbnail") views of data content to the object graph preview property pane.

231. An object graph preview interface as in Claim 37, further comprising methods for a. launching of functionally integrated applications according to correspondence of data content, queries and applications functionality via a comprised module launch component (MLC); b. routing and linking of data content including content attribute information, data annotations, limited resolution graphic views of any selected data file content, and c. linking of limited resolution image/graphics ("thumbnail") views of data content from external applications and / or software systems such as operating systems, for passing said view to the object graph preview property pane.

232. An application franslator link property pane (ATL), for interactive user modeling, linking, assembly, and integration of applications, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration and an object access manager component; b. provision of a list of available and applicable applications, application components and related data resources; and c. manual launching of external modules for cached non-destructive analysis and / or processing of data.

233. An application translator link property pane as in Claim 39, further comprising methods for a. provision of a list of available and applicable applications, analytical components and related data resources; b. manual linking of data content to related software modules and / or processing devices such as preferred analytical applications, processing devices and other interactive devices for actions not limited to viewing, analyzing and / or listening; and c. manual launching of external components for analysis and / or processing of data.

234. An application translator link property pane as in Claim 39, further comprising methods for a. provision of a user interface for unified application and application component relationship definition, functional access, organization, franslation, and integration; and b. interactive, unified user viewing of and interactivity with applications components and their required and / or available relationships; i. depending on data content, functional data relationships, analytical requirements, available applications, available applications components, franslation requirements and specific user queries; c. provision of an interactive user interface for automated, instantaneous applications functionality integration via linking to an external component for automated applications assembly, to provide the assembly functionality for dynamic development of new and customized applications.

235. An object access manager component (OAM) for functional analytical application, component, interface and data integration, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object pane descriptor component, said object graph preview property pane and an object access manager component; and b. defining parameters required for functional access, routing and presentation of data content within a given application or database environment.

236. An object access manager component, as in Claim 42, further comprising methods for a. provision of a messaging queue; which i. defines the applications window content required for data content transfer between the Intelligent Object and heterogeneous applications; ii. governs functional presentation within homogeneous and / or heterogeneous application and database environments; and iii. functionally integrates data content with a variety of applications; b. direction of access and routing requests for specific data content to linked applications; c. direction of information interchange between the Intelligent Object and external processing components and / or various applications such as text editors to allow for analysis, customization, formatting, processing, reviewing and unified presentation of said data content in a non-destructive manner, through said external components and applications; d. interaction with external object translation engines to provide i. data content franslation for functional integration with a variety of applications; and ii. data content and attribute-based algorithms for applications franslation, integration and inter-application communication; e. direct linking of data content and meta-data to external components comprising methods including data content franslation and presentation according to requirements of heterogeneous software modules or plug-ins; f. direct linking of data content and meta-data to external applications including applications running on hand-held electronic devices such as those used for data text entry; and g. direct linking of data content and meta-data to external applications including laboratory instrument plug-ins for real-time viewing of instrument and / or data parameters related to acquisition of data content.

237. A raw data mafrix property pane (RDM), for provision of detailed data storage and access information, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration user interface and a data link insertion component; b. provision of information regarding originating data content matrices.

238. A raw data mafrix property pane as in Claim 44, further comprising methods for a. user reviewing of data content information such as data source location, data source type, data storage information, data access; data content path and vectorized data matrix structure information; b. provision of information regarding originating data content matrices, across heterogeneous originating data and data resource type and / or structure.

239. A data link insertion component (DLI), for synchronization of data content access and routing with required transport protocols, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said raw data matrix property pane; and matrix structure descriptor access interface; b. data content distinction by type membership such as file, database record, application, and live data acquisition; and c. detection and activation of transport protocols required for specified data type accessing and routing requests.

240. A data link insertion component as in Claim 46, further comprising methods for a. detection and definition of data type, transport and routing protocols for the required communication mechanism to data content such as PPP over TC/TP, peer-to-peer, client/server, server/server, http and / or ftp.

241. A mafrix structure descriptor component (MSD), for provision of vectorized data content mapping, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said status management component, said object pane descriptor component; said Application / Database Definition Router interface; and said data link insertion component; b. matrix structure description of data content according to comprised vector mapping definitions; and c. mapping of data according to data field, data format and / or data structure.

242. A mafrix structure descriptor component as in Claim 48, further comprising methods for a. linking of said data matrix structure information to meta-data and data description information; b. linking of addressing definitions required to enable functional integration data content accessing; and c. accessing of data content ("workspaces") to levels of granularity including data subset overviews, data files, fields, rows, cells, pixels or bytes;

243. A text annotation property pane (TAN), for unified, interactive user text entry and linking of textual and other references, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to an external application for data handling and applications integration user interface and a text annotation access interface; b. manual entry, viewing and linking of information such as text annotation; c. activation of external components or applications such as text editors to allow for customization, formatting, reviewing and processing of said information through external editors; and d. provision of functionality for linking of customized text annotations, external text resources, references, related data and information.

A text annotation access interface (TANi), for direct linking of external applications for text editing and for linking of textual and other reference files, comprising methods for a. bi-directional information interchange with components and access interfaces not limited to said object access manager; and said text annotation property pane; b. linking of external components or applications such as text editors to allow for customization, formatting, reviewing and processing of said information through external editors; and which allow for: c. passing of said information back to the text annotation property pane.

245. An applications handling framework is provided to enable functionally integrated user interactivity, comprising structures and methods for one or more of a. bi-directional information interchange with components and access interfaces comprising such as a data object with a comprised status management component agent; an object pool database structure with a comprised result aggregation engine; an object normalization engine; an object state engine; an object translation engine; and application translation interface, a master query interface; and a report generation interface; b. utilizing unique data structures as core accessing; routing; and processing elements for i. unified analysis of homogeneous and/or heterogeneous data content, contained within homogeneous and/or heterogeneous data formats, types and structures; ii. by homogeneous and/or heterogeneous analytical applications, modules, and plug-ins; iii. in homogeneous and/or heterogeneous network computing environments; to enable c. provision of user interactivity utilizing said Intelligent Object data,

Intelligent Object Handler, and Intelligent Object Pool applications within a unified, globally accessible graphical user environment, via an interactive unified presentation layer (UPL) graphical user interface.

. An applications handling framework as in Claim 1 , wherein said methods for one or more of utilization, accessing, routing and processing of data structures further comprise a. definition of said data object and data content according to methods comprising data matrix structure definition; application requirements definition; data resource definition; and b. preparation of said data object and data content according to methods for one or more of data content and activity synchronization; standardization; franslation; validation; ranking; and automated and/or interactive data organization; c. nested vector table translation of data content presentation! via extraction of required information, generation and provision of look up tables for applications integration; and

• d. non-destructive cache-based "overlay" analytical processing of data content; e. analysis and presentation of said data object and data content according to methods required for analysis by potentially heterogeneous applications; to enable f. unified analysis of homogeneous and/or heterogeneous data by heterogeneous analytical applications in heterogeneous network environments.

247. An applications handling framework as in Claim 1, wherein said methods for one or more of utilization, accessing, routing and processing of data structures further comprise a. applications environment detection, exfraction and definition for accessing, unified viewing, processing and routing; and b. data content detection, exfraction and definition for accessing, unified viewing, processing and routing.

248. An applications handling framework as in Claim 1, wherein said methods for utilization, accessing, routing and processing of functionally integrated data structures further comprise one or more of a. direction of vectorized data content accessing, linking and routing between data objects for direct parallel information interchange; b. direction of meta-data accessing, linking and routing between data objects for direct parallel information interchange; c. direction of vectorized data content accessing, linking and routing between data objects and applications for direct parallel information interchange; d. direction of meta-data accessing, linking and routing between data objects and applications; for direct parallel information interchange; and e. comparison, ranking and organization of said data according to Boolean analysis, structural matching and/or other statistical analyses of said information interchanged.

249. An applications handling framework as in Claim 1, wherein said methods for user interaction further comprise one or more of a. direct vectorized accessing to all relevant data content and meta-data properties of said potentially heterogeneous and distributed data content; b. direct accessing to analytical functionality of integrated applications and/or analytical components; and c. functional integration of data content according to data inter-relationships and analytical functionality required for interactive accessing; routing; viewing; querying; and analyzing of data content.

250. Within information technology platform architecture advantageously enabled in software as the "Sentient IT Platform", comprising Intelligent Object data structures and the Intelligent Object Pool database structure, an Intelligent Object Handler data and applications handling framework is provided to enable functionally integrated user interactivity, said Intelligent Object Handler comprising structures and methods for one or more of a. bi-directional information interchange with components and access interfaces comprising such as a data object with a comprised status management component agent; an object pool database structure with a comprised result aggregation engine; an object normalization engine; an object state engine; an object translation engine; and application franslation interface, a master query interface; and a report generation interface; b. utilizing unique Intelligent Object data structures and comprised processing components and access interfaces as accessing; routing; and processing elements; for i. unified analysis of homogeneous and/or heterogeneous data content, contained within homogeneous and/or heterogeneous data formats, types and structures; ii. by homogeneous and/or heterogeneous analytical applications, modules, and plug-ins; iii. in homogeneous and/or heterogeneous network computing environments; to enable c. provision of user interactivity utilizing said Intelligent Object data, Intelligent Object Handler, and Intelligent Object Pool applications within a unified, globally accessible graphical user environment, via an interactive unified presentation layer (UPL) graphical user interface.

. An Intelligent Object Handler data and applications handling framework as in Claim 6, wherein said methods for utilization, accessing, routing and processing of intelligent Object data structures and applications further comprise a. Intelligent Object ("EVIO", hereinafter "Intelligent Object") data as core elements, which provide methods advantageous for data handling, for i. automated and/or interactive data and data resource access, routing, processing, translation, analytical integration, viewing, analysis and management; b. definition of said Intelligent Object data structures and data content according to methods comprising data matrix structure definition; application requirements definition; data resource definition; and c. preparation of said Intelligent Object data structures and data content according to methods for data content and activity synchronization; standardization; translation; validation; ranking; and automated and/or interactive data organization; d. nested vector table translation of data content presentation via exfraction of required information, generation and provision of look up tables for applications integration; and e. non-destructive cache-based "overlay" analytical processing of data content; f. analysis and presentation of said Intelligent Object data structures and data content according to methods required for analysis by potentially heterogeneous applications; to enable: g. unified analysis of homogeneous and/or heterogeneous data by heterogeneous analytical applications in heterogeneous network environments.

252. An Intelligent Object Handler data and applications handling as in Claim 6, wherein said methods for unified utilization, accessing, routing and processing of Intelligent Object data structures further comprise one or more of a. applications environment detection, extraction and definition for accessing, unified viewing, processing and routing; and b. data content detection, exfraction and definition for accessing, unified viewing, processing and routing.

253. An Intelligent Object Handler data and applications handling framework as in Claim 6, wherein said methods for utilization, accessing, routing and processing of functionally integrated Intelligent Object data structures further comprise one or more of a. direction of vectorized data content accessing, linking and routing between intelligent Object data structures for direct parallel information interchange; b. direction of meta-data accessing, linking and routing between Intelligent

Object data structures for direct parallel information interchange; c. direction of vectorized data content accessing, linking and routing between Intelligent Object data structures and applications for direct parallel information interchange; d. direction of meta-data accessing, linking and routing between Intelligent Object data structures and applications; for direct parallel information interchange; and e. comparison, ranking and organization of said Intelligent Object data structures and their data content according to Boolean analysis, structural matching and/or other statistical analyses of said information interchanged.

254. An intelligent Object Handler data and applications handling framework as in Claim 6, wherein said methods for user interaction further comprise one or more of a. direct vectorized accessing to all relevant data content and meta-data properties of said potentially heterogeneous and distributed data content; and b. direct accessing to analytical functionality of integrated applications and/or analytical components; and c. functional integration of data content according to data inter-relationships and analytical functionality required for interactive accessing; routing; viewing; querying; and analyzing of data content utilizing said applications and applications components.

255. An Intelligent Object Handler data and applications handling framework as in

Claim 6, providing a graphical user interface comprising further methods for a. User-directed functional integration of plug-ins; components; modules; applications; interfaces; from sources not limited to diverse scientific; business; manufacturing; academic; manufacturing; and laboratory systems environments; including i. multi-platform installation; including for such as Unix, Linux, Win32, Mac OS 9 and 10, and other computer operating systems; and ii. automated and/or interactive applications franslation, integration, access, viewing and management; automated and/or interactive data and data resource access, routing, processing, translation, integration, viewing, analysis and management.

256. An Intelligent Object Handler data and applications handling framework as in

Claim 6, providing a graphical user interface comprising further methods for one or more of a. interactive data object handling and analysis of data content, dynamically presented to enable user interactivity, via sets of customizable toolbars such as; user menus; and various analytical interfaces; such as File; New;

Open; Open All (in directory); Close; Close All; Print preview; Print; Edit Undo; Redo; Cut; Copy; Paste; Select; Select All; and other customizable toolbars and menus.

257. A user definition and administration (UDA) component for user, access, authentication and privilege definition and processing, comprising methods for one or more of a. bi-directional information interchange with components and access interfaces including the said User menu, Intelligent Object generator component; object state engine component; master query component; and b. definition and integration of requirements for user, access, authentication and privilege definitions such as Laboratory Information Management Systems (LEVIS) for local and/or remote data sources; applications; and other user activities within heterogeneous and/or homogeneous computing and/or network information environments.

258. A user definition and adminisfration (UDA) component as in Claim 13, functionally linked to a "User" menu comprised by said unified presentation layer within said Intelligent Object handler, said component comprising further methods for one or more of a. provision of a user interface and functionality to set up and govern user preferences and privileges, for such as password settings; look preference; color preference; local cache size; local cache clear; import settings; auto setup; connectivity profile; database access preference; applications list; personal data storage; and for b. provision of a user interface and functionality for global user adminisfration; comprising such as a dynamically updated list of user names; a dynamically updated list of user levels; Add User; Edit User;

Export User; Import User; Lock/Unlock User; Retire User; and Clear User Password.

259. An Intelligent Object generator (EVIO-G) component, to generate new Intelligent Objects, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the data type franslator component; b. fielding of data object and content import requests; c. generation of Intelligent Object data structures; d. utilization of data content and information provided by a data type translator; for one or more of: e. provision of run-time translation of heterogeneous data types and their data content into Intelligent Object data; and f. assignation of a unique object identifier to the Intelligent Object, such as a 128 bit alphanumeric identifier.

260. An Intelligent Object generator (EVIO-G) component as in Claim 15, which comprises further methods for one or more of a. bi-directional information interchange with components and access interfaces including the user definition and adminisfration component; direct instrument acquisition and control component; and object state engine component; and b. activation of object state history via the object state engine.

261. An object state engine (OSE) component for Intelligent Object state management, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including an object handler, status management component agents comprised by said Intelligent Objects; and master query interface; b. monitoring and governing any activities of Intelligent Objects in realtime via a comprised active listening mode (ALM) 2028; c. provision of continuously-running sets of processes updated by synchronization with any system clock, such as atomic clock synchronization over a network; d. provision of a state processing method for recording Intelligent activity or transactions, to provide activity history; e. provision of a state processing method assigning a defined state to the Intelligent Object to synchronize the current action; f. provision of a query processing method for handling of external query submissions to Intelligent Objects; g. provision of a query processing method for Intelligent Object-to-

Intelligent Object query result synchronization; h. provision of a query processing method for governing user access to Intelligent Objects and Intelligent Object-to-Intelligent Object intercommunication between Intelligent Objects, between said Intelligent Objects and applications, and between analytical and processing components; based on definitions such as security protocols and privilege definitions; i. provision of a query processing method for governing user access to output generation of said Intelligent Objects and analyses; j. provision of a query processing method for query status updating; k. provision of a query processing method for query result synchronization; 1. provision of a query processing method for output generation; m. provision of an access processing method for Intelligent Object root addressing and routing; n. provision of an access processing method for data content addressing and routing; o. provision of an access processing method for Intelligent Object-to- Intelligent Object linking and synchronization.

262. An object state engine (OSE) component as in Claim 15, which comprises further methods for a. bi-directional information interchange with components and access interfaces including the master query component; and legacy synchronization interface.

263. An object state engine (OSE) component as in Claim 15, which comprises further methods for one or more of a. Intelligent Object generator; Intelligent Object standardization component; Object and Image Normalization components; object franslation engine component; data type translator component; direct instrument acquisition and confrol interface; triggering of the Intelligent Object generator to create a new Intelligent Object if an available Intelligent Object pertaining to queried data content does not exist; b. assigning a unique identifier to newly generated Intelligent Objects; c. provision of a state processing method for comparison of said activity history to GLP/GMP laboratory information management system (LEVIS)-style experiment data states and validating any action by assigning a defined state to the object; d. provision of a state processing method for validation state-based alerting and information ranking; e. provision of a state processing method which queries existing data and application resources to detect and update data content status; f. provision of a state processing method for accepting status updates received or "pushed" from external data and applications sources; g. provision of a state processing method for maintaining status memory over state-less networks by transmitting action consequences back to the backend system; h. provision of a query processing method for handling of network requests to Intelligent Objects; i. provision of an access processing method comprising procedural ranking of requests for information exchange based on annotation or validation state ofthe addressed Intelligent Object; j . provision of an access processing method for activating vectorized access to subsets of object data ("the workspace") within provided data content matrices for dynamic information interchange; and k. provision of an access processing method for access ordering and ranking; and synchronized accessing to raw data matrix vectors; 1. enabling other customized functionality for monitoring, governing, updating, synchronization, recordation and alerting activities of Intelligent Objects in real-time and/or within latency environments.

264. An object standardization technique (EVIO-S) component for standardization of data content queried or processed, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the object state engine; object translation engine; and b. provision of calibration to data content via utilization of linear; nonlinear; polynomial; exponential; logarithmic; cubic spline; adaptive; weighted point-to-point fit; and a variety of multi-parametric functions.

265. An object standardization technique (EVIO-S) component as in Claim 20, which comprises further methods for one or more of a. bi-directional information interchange with components and access interfaces including the object normalization engine component; and global image normalization component; and b. activation and interaction with said components to provide automated standardization; and normalization of data; by methods for calibration by standardized empirical criteria.

266. An object normalization engine (ONE) component, for normalization of data to be compared, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including an object state engine; b. normalization of scientific data contained in Intelligent Objects for comparison independent of procedural errors and multiple sources of errors inherent in multiple datasets of different origins; via comprised methods for i. generation of a normalized global standard to provide algorithms to which all similar data can be referenced to in regard to their field parameters contained within the raw data mafrix; ii. application of said algorithms to user-defined workspaces addressed by dynamically generated vector subsets to minimize data exchange and increase processing speed, allowing for use of said algorithm even in network environments with limited data exchange capabilities; iii. utilization of a workspace cache area for said processing to maintain data content integrity at all times; and iv. provision of standard algorithms for processing a variety of scientific data configurations such as timeline-related; spectra or wavelength-related; kinetics-related; migration- or separation- related data content matrices in single and multidimensional variations; locational deviations within arrays, bioassay-related and gene and/or protein sequence-related raw data matrices.

267. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for a. an object standardization technique component; an object translation engine; and application translation interface, a master query interface; and a report generation interface.

268. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for one or more of a. provision of multi-parameter normalization in respect to color, intensity, dynamic range and x/y/z distortions in 2D and 3D scientific images; b. provision of x/y/z-alignment and component distance adjustments in molecular structures; and acoustic wave pattern and/or video signals.

269. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for one or more of a. detection of non-obvious data redundancies in diverse data resources, databases, data marts or data warehouses; b. validation and accessibility ranking of such multiple records; c. multiple addressing of such multiple records; and or d. elimination or retirement of such multiple records.

270. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for one or more of a. application of said algorithms to subsets of decompressed workspaces within loss-free compressed raw data providing normalization to compressed data without the need for decompression ofthe entity of such data sets.

271. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for one or more of i. tracking of deviations from an established global standard; and to ii. correction of detected deviations in real-time for use in calibrated on-the-fly analysis applications.

272. An object normalization engine (ONE) component as in Claim 22, which comprises further methods for a. saving or transferring workspace cache area data converted by said algorithms between applications.

273. A direct instrument acquisition and confrol (DIAC) interface, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the master query component; Intelligent Object generator component; object state engine component; and external instruments and devices; b. acquisition of data content via instrumentation; c. recordation of experimental and instrument running parameters; and d. activation of a component for generation of Intelligent Objects corresponding to said data content.

274. A direct instrument acquisition and control (DIAC) interface as in Claim 29, which comprises further methods for one or more of a. automated detection and/or user definition of instrument and device dependencies, parameters, and/or operational method definitions; b. definition and functional integration of said dependencies, parameters, and/or operational method definitions for interactive remote and/or local user interactivity and instrument confrol; c. linking of said user-defined and or automatically detected instrument and/or device dependencies with said Instrument Confrol user interface; to enable d. real-time, pre-programmed and/or latent viewing and interactivity from local and/or remote locations; and e. provision of an Instrument Confrol interface comprised by the unified presentation layer, which presents information for Connection status, such as presence or absence of connection and connection type information; instrument activity information such as run-time - hours, minutes, seconds; experiment status information such as validation status; instrument status information such as various operating parameters; and user interactivity such as start, pause, resume, stop.

275. A data type translator (DTT), which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the Intelligent Object generator; object franslation engine component; and application framework component; b. fielding of applications and database environment definitions provided by an application / database definition generator interface; and c. definition of data type dependencies to define the Intelligent Object;

276. A data type franslator (DTT) as in Claim 31, which comprises further methods for a. provision of data type dependencies as required for linked components and access interfaces.

277. An object translation engine (OTE) component, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the master query component; object state engine component; data type franslator component; application / database definition generator; and master query interface; b. activation of data object, data field and raw data matrix structure definition tables for franslation of Intelligent Object presentation according to applications requirements; c. activation of table lookup to provide real-time translation of the Intelligent Object within heterogeneous database and application environments; d. activation of data structure information for non-object data for translation of Intelligent Object presentation according to applications requirements; e. activation of data type, access and structure definition tables for franslation of Intelligent Object presentation according to applications requirements; f. activation of database type, access and structure definition tables for franslation of Intelligent Object presentation according to applications requirements; g. activation of application type, access and structure definition tables for franslation of Intelligent Object presentation according to applications requirements; and h. automated franslation of said previously heterogeneous and/or incompatible data object into a variety of required data types; structures formats; and matrices.

278. An object franslation engine (OTE) component as in Claim 33, which comprises further methods for one or more of a. activation of data content access and routing protocols required for functional integration for heterogeneous and/or dynamically defined query, viewing or analysis protocols; processing components; access interfaces; data resources; and/or applications environments; and b. linking of said structure information and definition tables to dynamically direct Intelligent Object property pane activation and presentation; data object activation and presentation; data content activation and presentation; application activation and presentation; component activation and presentation; and interface activation and presentation; in real-time, according to defined data structure; database; and application requirements.

279. An application / database definition generator (ADG) component, for detection, extraction and generation of structural and functional information necessary for standardized unified access, presentation and utilization of heterogeneous data; comprising methods for one or more of a. bi-directional information interchange with components and access interfaces including the object translation engine; Intelligent Object application framework; application franslation interface; external data content; databases and data resources; and external applications and components; b. provision of an interface for detection and exfraction of diverse data object, data field and raw data matrix definitions c. provision of an interface for detection and exfraction of diverse data type, access, structure and functional dependencies; d. provision of an interface for detection and exfraction of diverse database type, access and structure dependencies; e. provision of an interface for detection and exfraction of diverse application type, access and structure dependencies; f. provision of an automated query interface to define application and database dependencies according to automated and/or user-defined requirements utilizing said provided methods for i. data table extraction to determine data object, data field and raw data matrix definitions; ii. data type extraction to determine data access and structure dependencies for Intelligent Objects; iii. database type extraction to determine database access and structure dependencies; and iv. application type exfraction to determine application type, access and structure; g. dynamic updating of applications and database resource availability information based on presence, absence or other characteristics such as performance response time, for previously detected application and database functionality; h. dynamic updating of applications and database resource availability information based on presence, absence or other characteristics such as performance response time, for application and database functionality requested at run-time; i. generation of table definitions for look-up to provide real-time translation of Intelligent Object data content between and within heterogeneous computing environments; and j. definition of the computing environment as required for linked components and access interfaces including the data type translator, the application framework and the application franslation interface.

An application / database definition generator (ADG) component as in Claim , comprising further methods for one or more of a. provision of an interface for activation of external components for metadata exfraction; b. generation of table definitions for look-up to provide real-time franslation of Intelligent Object meta-data.

281. A master query component (MQC), which comprises methods for a. bi-directional information interchange with components and access interfaces including an object state engine component; an Intelligent Object handle component; an Intelligent Object application framework component; and a master query interface; b. fielding and direction of automated queries and commands for data acquisition; access, retrieval, franslation, viewing, processing and/or analysis; and c. provision of state-related vector definition of object data subsets for dynamic information interchange.

282. A master query component (MQC) as in Claim 37, comprising further methods for one or more of a. bi-directional information interchange with components and access interfaces including unified presentation layer toolbars and query interfaces; a direct instrument acquisition and confrol interface; an object franslation engine; and b. presentation of security, access and interactivity protocols to menus, toolbars and/or other tools for user interactivity according to said unified presentation layer; and c. fielding and direction of user-directed queries and commands for data acquisition; access, retrieval, franslation, viewing, processing and/or analysis.

283. A master query interface (MQI) for direct linking of vectorized data content and meta-data between Intelligent Objects, applications, analytical components and interfaces, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the object state engine; external object query interfaces comprised by Intelligent Objects; components and/or access interfaces comprised by external Intelligent Object Pool and/or Intelligent Object Pools ("IOP"; hereinafter "Pool(s)"); external result aggregation engine; and depending on the system configuration, to varied components, interfaces and data content resources; b. linking to Intelligent Object root routing information; c. linking to direct interactive Intelligent Object content routing vector addresses; and d. linking to aggregated query result output provided by external result aggregation engines.

284. A master query interface (MQI) as in Claim 39, which comprises further methods for one or more of a. bi-directional information interchange with components and access interfaces including the master query component; object franslation engine; Intelligent Object handle component; b. linking to Intelligent Object meta-data content information; c. linking to other external components and access interfaces for query processing, such as a distributed learning engine, or knowledge extraction engine.

285. An Intelligent Object handle component (EVIO-H) for activation and direction of Intelligent Object information interchange, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the master query component; master query interface; Intelligent Object application framework component; and report generation interface; b. management of Intelligent Object data by activating and directing information linking provided by said components and access interfaces to comprised meta-data tags; data content atfribute definitions; vector address pointers; comprised by said Intelligent Objects, c. fielding of queries and/or command parameters provided by automated; and/or user-based methods.

286. A report generation interface (RGI), for generation of reports based on data information and aggregated processing results, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the Intelligent Object handle component; object franslation engine; distributed learning engines; knowledge extraction engines; and an external result aggregation engine component; b. assembly of information comprised by such as data objects; specified meta-data indices of said data; specified data content subsets defined to levels of granularity as small as a single byte; and aggregated processing results; c. tabulation of information comprised by such as data objects; specified meta-data indices of said data; specified data content subsets defined to levels of granularity as small as a single byte; and aggregated processing results; i. according to information and requests received from external processing engines and access interface components; and d. relaying generated results to external processing engines, access interfaces and pane descriptor components in an automated, synchronized, real-time manner.

287. A report generation interface (RGI) as in Claim 42, which comprises further methods for one or more of a. validation reporting regarding information comprised by such as data objects; specified meta-data indices of said data; specified data content subsets defined to levels of granularity as small as a single byte; and aggregated processing results; and b. ranked reporting of information comprised by such as data objects; specified meta-data indices of said data; specified data content subsets defined to levels of granularity as small as a single byte; and aggregated processing results; i. according to information and requests received from external processing engines and access interface components.

288. An Intelligent Object application framework (EVIO-A) for functional integration of intelligent Object data with applications components, plug-ins and modules, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the Intelligent Objects and their content; master query component; data type franslator component; Application / Database Definition Generator; Intelligent Object handle component; application translation interface; applications comprised within said Intelligent Object handler as components, modules and/or plug-ins; b. fielding of automated and/or user-directed queries; applications assembly commands; processing requests; viewing requests; other dynamic applications needs; c. detection of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and or heterogeneous data content and applications; and d. activation and enabling of a comprised automated applications assembly component to enable dynamic assembly of applications utilizing Intelligent Objects for unified, functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications.

. An automated applications assembly component (AAA), to enable automated assembly of new applications during run-time ("just-in-time") from sets of components according to specific needs and best suited for complex processing requirements in heterogeneous data and applications environments, comprising methods for one or more of a. selection and combination of required I/O components, such as components required to transfer data into and results out of individual analytical and/or descriptive and/or annotative components; b. selection of algorithms best suited for processing of specifically defined data types or data type descriptors; c. dynamic combination of said components and algorithms towards automated and/or user-defined analytical performance goals, utilizing distributed subcomponent integration under best-fit conditions; d. activation of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications; e. synchronization of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications; f. assembly of required components, interfaces and protocols to enable functionally integrated analysis utilizing homogeneous and/or heterogeneous data content and applications memory ranking of performance-optimized component selection; g. memory ranking of information-optimized component selection; and h. best choice adjustment according to user-defined functional requirements.

290. An automated applications assembly (AAA) component according to Claim 45, further contained in a stand-alone application or module for non-object data.

291. An automated applications assembly (AAA) component according to Claim

45, further contained in a stand-alone application or module for object data.

292. An automated applications assembly (AAA) component according to Claim 45, further contained as a plug-in or module for an information technology platform containing Intelligent Object data.

293. An automated applications assembly according to Claim 45, in which selection of components is based on their immediate availability for real-time use.

294. An automated applications assembly according to Claim 45, comprising further methods for one or more of: a. selection of components based on their functional consistency and accuracy within all components assembled, such as, but not limited to functions for governing raw data precision; handling of mathematical errors; provision of data pointer referencing; mafrix operation synchronization in regard to internal or external transformations and dimension descriptions; output rounding; determination of logical processing pathways; accounting for Boolean inheritances; iterative step tracing; and controlling and logging of rollback behavior.

295. An automated applications assembly according to Claim 45, comprising further methods for one or more of: a. selection of components is based on the ranking among available components in regard to overall performance, such as, but not limited to one or more of: network traffic; local processing; remote processing; process sharing; distributed processing; direct "on-object"-processing; result clustering; and graphics element preprocessing and charting.

296. An automated applications assembly according to Claim 45, comprising further methods for one or more of: a. selection of components based on the ranking among available components in regard to validation required for decisive answers (output knowledge assessment).

297. An automated applications assembly according to Claim 45, comprising further methods for a. provision of a vectorized "Application Archive Table" for quick referencing of previously assembled applications with similar processing needs.

298. An automated applications assembly according to Claim 45, comprising further methods for a. provision of "on-the-fly" temporary applications memory management for Just-in-Time (JIT) component linking, loading and unloading from the active caching area.

299. An automated applications assembly according to Claim 45, comprising further methods for a. provision of an intuitive interactive graphical user interface for drag-&- drop selection of components for process modeling and analytical simulations based on user output requests.

300. An automated applications assembly according to Claim 45, comprising further methods for a. provision of active communication with learning engines, such as for example, a distributed learning engine or knowledge extraction engine to optimize iterative processes or loop algorithms based on condition feedback.

301. An application translation interface (ATI), for presentation of Intelligent Object data according to heterogeneous applications requirements, which comprises methods for a. bi-directional information interchange with components and access interfaces such as the Intelligent Object Handler; master query interface, provision of an interface layer to present defined data object, data field and raw data matrix structure definitions to required external data resources; applications; access interfaces; and processing components utilizing provided definition look-up tables; b. provision of an interface layer to present defined data type, access, structure and function definitions to required external data resources; applications; access interfaces; and processing components via provided look-up tables; c. provision of an interface layer to present defined database type, access, structure and function definitions to required external data resources; applications; access interfaces; and processing components via provided look-up tables; d. provision of an interface layer to present defined application type, access and structure definitions to required external data resources; applications; access interfaces; and processing components via provided look-up tables; and e. transferring of requests such as read/write processes within or in-between external applications; Intelligent Object and data content property presentation in real-time, according to defined requirements.

302. An application translation interface (ATI), for presentation of Intelligent Object data according to heterogeneous applications requirements, which comprises methods for a. bi-directional information interchange with components and access interfaces such as the result aggregation engine; application / database definition generator; application handling framework; external result aggregation engine; as well as with external data resources; applications; access interfaces; and processing components.

303. A legacy synchronization interface (LSD, for updating and synchronization of batch processed or temporarily offline Intelligent Object data and data content, which comprises methods for one or more of a. bi-directional information interchange with components and access interfaces including the object state engine; and external data content, databases, and data resources; b. synchronization of object data of various types with data content contained in off-line and/or batch processing legacy databases or external applications, in regard to data integrity, content and state for updating of such as raw data vector matrices linking; and property pane content definition; c. synchronization of Intelligent Object data with data content contained in off-line and/or batch processing legacy databases or external applications in regard to data integrity, content and state for updating of such as raw data vector matrices linking; and property pane content definition; d. synchronization of Intelligent Object data content with external, off-line or temporarily unavailable data sets in regard to data integrity, content and state for updating of such as raw data vector matrices linking; and property pane content definition.

304. A legacy synchronization interface (LSD as in Claim 59, comprising further methods for a. reporting to the object state engine to update state history records for changes during times where activity-listening-mode is temporarily unavailable under conditions, such as, but not restricted to off-line; connection time-out; transaction acknowledgement errors; or record locking conflicts on the legacy end.

305. A legacy synchronization interface (LSI) as in Claim 60, comprising further methods for one or more of a. metadata index updating in batch mode; and for b. object pane descriptor updating whenever object panes are added or descriptors need to be modified; by c relaying required information to said object state engine component.

306. A legacy synchronization interface (LSI) as in Claim 60, comprising further methods for one or more of a. provision of link functions between "local state machines" or agents, such as for "pushed" updating and said object state engine component; to enable b. synchronous handshaking during connect and disconnect of heterogeneous legacy data and/or applications; c. transaction management and accounting for such as "once-and-only- once" transactions; d. linking between "local state machines" or agents and components within the unified presentation layer of said Intelligent Object handler; to enable e. platform-integration of external applications, which modify data properties during their execution, for synchronization and update.

307. A legacy synchronization interface (LSD as in Claim 60, comprising further methods for one or more of: a. provision of feedback on synchronization conditions for frequency; updates; and timing preferences towards a variety of internally and/or externally comprised components and interfaces, such as knowledge exfraction engines; and distributed learning engines; and for b. "best-fit" optimization of synchronization and timing based on said event history feedback.

308. A legacy synchronization interface as in Claim 60, comprising further methods for a. logging and reporting of synchronization events to methods comprised within such as Intelligent Objects; processing components; access interfaces; applications; data resources and/or databases; and b. provision of the interface to integrate required methods for synchronization requests or "pulls" and/or metadata index updates utilizing provided protocols and/or definitions such as user preferences; user profiles; administrative protocols; and/or maintenance action definitions.