EP1381972A4 - System, verfahren und softwarearchitektur und geschäftsmodell für eine intelligente, auf objekten basierende informations technologieplattform - Google Patents

System, verfahren und softwarearchitektur und geschäftsmodell für eine intelligente, auf objekten basierende informations technologieplattform

Info

Publication number
EP1381972A4
EP1381972A4 EP01991011A EP01991011A EP1381972A4 EP 1381972 A4 EP1381972 A4 EP 1381972A4 EP 01991011 A EP01991011 A EP 01991011A EP 01991011 A EP01991011 A EP 01991011A EP 1381972 A4 EP1381972 A4 EP 1381972A4
Authority
EP
European Patent Office
Prior art keywords
data
information
intelligent
methods
ipool
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01991011A
Other languages
English (en)
French (fr)
Other versions
EP1381972A2 (de
Inventor
Robert A Stanley
Erich A Gombocz
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
IO Informatics Inc
Original Assignee
IO Informatics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by IO Informatics Inc filed Critical IO Informatics Inc
Publication of EP1381972A2 publication Critical patent/EP1381972A2/de
Publication of EP1381972A4 publication Critical patent/EP1381972A4/de
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/248—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2453—Query optimisation
    • G06F16/24532—Query optimisation of parallel queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/26—Visual data mining; Browsing structured data

Definitions

  • 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.
  • COM Object Linking and Embedding
  • OLE Object Linking and Embedding
  • 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.
  • 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.
  • 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.
  • IMO intelligent object data structure
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • user interactivity at the front end is enabled by the unified presentation layer, which is linked to defined processing components and access interfaces.
  • 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.
  • aMDX Aggregate Meta-data Index
  • aRSG Aggregate Real-time Significance Generator
  • 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.
  • EVIO-Z EVIO Zoomer
  • 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.
  • 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.
  • object pane descriptors 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
  • OGP object graph preview
  • RDM raw data matrix
  • MSD matrix structure definitions
  • 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.
  • UDL unified presentation layer
  • GUI web-enabled graphical user interface
  • UDA user definition administration shell
  • 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.
  • MQC master query component
  • EVIO generator EVIO generator
  • 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.
  • ADG application definition generator
  • DTT data type translator
  • an integrity assessment interface 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.
  • iMDX iPool meta-data index
  • aMDX aggregate meta-data index
  • 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.
  • DII direct information interchange interface
  • an object query interface 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.
  • OQI object query interface
  • DII direct information interchange
  • EVIO data which initiates query analysis and results aggregation
  • RKI result generation interface
  • LSD legacy synchronization interface
  • 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.
  • 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.
  • 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. 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.
  • IOP Intelligent Object Pool
  • 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. 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
  • 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.
  • FIG. 10 represents a process model describing interactions of modules for an exemplary embodiment ofthe intelligent object pool (IOP) 204.
  • IOP intelligent object pool
  • 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.
  • FIG. 11 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.
  • 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 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.
  • the Intelligent Object Pool 204 may be activated and directed by the Intelligent Object Handler 202.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • EVIO Intelligent Object
  • 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.
  • OSE object state engine
  • IOH Intelligent Object Handler
  • SMC status management component
  • 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).
  • IOP Intelligent Object Pool
  • PPQ iPool-to-iPool queries
  • 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
  • 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.
  • IOH Intelligent Object Handler
  • UDA user definition and administration
  • OSE object state engine
  • EVIO Intelligent Object
  • IOP Intelligent Object Pool
  • 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.
  • 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.
  • the rules, policies, and procedures may be any one or more of automated, event-driven, interactive, and/or user- directed, secure, audited, and validated.
  • RAE result aggregation
  • RAEi Methods for result aggregation
  • 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.
  • 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.
  • PPQ meta-data indices methods
  • DLE pool content access methods
  • stand-alone functional modules constructed out of the defined components and access interfaces may be assembled to provide customized functionality.
  • 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.
  • PBP Pool boundary protocols
  • MDX Meta-Data Indices
  • PCA Pool Content Access
  • 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,
  • 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
  • Pool integrity protocols and procedures 408 that provide and maintain data integrity assessment for individual data objects as wells as data subset iPools 155.
  • the intelligent object data includes data content stored in global and/or local data resources of potentially heterogeneous type and/or structure.
  • the pool boundary protocols (PBP) 402 include a plurality of functional modules comprising components and access interfaces as described in greater detail elsewhere herein.
  • 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).
  • iPSAc iPool security authentication component
  • iPSAi iPool security authentication interface
  • the iPool Availability Monitor module 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).
  • iPAMc iPool Availability Monitor component
  • iPAMi iPool Availability Monitor interface
  • 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.
  • 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.
  • IPIAc iPool Integrity Assessment component
  • JJPIAi iPool Integrity Assessment interface
  • 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.
  • IOH Intelligent Object Handler 202
  • IOP Intelligent Object Pool
  • EVIO Intelligent Molecular Objects
  • 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.
  • the combination of iPSA and iPSAi comprise a Pool boundary protocol module for security.
  • pool boundary protocols 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.
  • Pool boundary protocols provide access control, tracking, recordation and management of data exchange, and data set integrity assessment required for iPool subset 156 boundaries and parameters .
  • 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
  • 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.
  • iPSAc iPool Security Authentication Component
  • 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.
  • iPSAc iPool Security Authentication component
  • 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.
  • 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.
  • 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.
  • 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.
  • Security Authentication module optionally but advantageously comprises a module within an information technology platform using object-oriented data structures.
  • 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.
  • Intelligent Object Pool access interfaces; an Intelligent Object Handler 202 (IOH); and Intelligent Molecular Objects 200 (IOM).
  • IOH Intelligent Object Handler 202
  • IOM Intelligent Molecular Objects 200
  • Intelligent Objects 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 Objects
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • iPAMc iPool Availability Monitoring component
  • 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.
  • 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.
  • 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.
  • the iPool Availability Monitoring interface (iPAMi) 434 comprised as a module within an information technology platform for Intelligent Objects.
  • the iPool Availability Monitoring interface comprised as a module within an information technology platform using object-oriented data structures.
  • 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.
  • 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
  • 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.
  • the iPool Exchange Protocol component (iPEPc) 435 comprises a module within an information technology platform for Intelligent Objects.
  • the iPool Exchange ProtocoJ component is optionally but advantageously comprised as a module within an information technology platform using object-oriented data structures.
  • iPEPi iPool Exchange Protocol Interface
  • 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
  • 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
  • the iPool Exchange Protocol interface (iPEPi) 436 comprises a module within an information technology platform for Intelligent Objects.
  • the iPool Exchange Protocol interface optionally comprises a module within an information technology platform using object-oriented data structures.
  • 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
  • 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.
  • 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.
  • 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
  • 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
  • iPIAc iPool Integrity Assessment Component
  • 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.
  • 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 Protocols 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.
  • 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.
  • the iPool Integrity Assessment component (iPIAc) 439 comprises a module within an information technology platform for Intelligent Objects.
  • the iPool Integrity Assessment component comprises a module within an information technology platform that optionally uses object-oriented data structures.
  • iPIAi iPool Integrity Assessment Interface
  • 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 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the iPool Meta-data Index component (iMDXc) 451 comprises a module within an information technology platform for Intelligent Objects.
  • the iPool Meta-data Index component optionally comprises a module within an information technology platform using object-oriented data structures.
  • 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.
  • 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.
  • 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
  • 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.
  • 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
  • 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.
  • 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.
  • other data access and/or applications definitions e.g. other meta-data
  • 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.
  • 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
  • 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.
  • 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.
  • OSE object state engine
  • SMC status management component
  • OQI object query interface
  • EVIO Intelligent Objects
  • the Real-time Meta-data Link component (RMLc) 453 comprises a module within an information technology platform for Intelligent Objects.
  • the Real-time Meta-data Link component (RMLc) 453 optionally comprises a module within an information technology platform using object-oriented data structures.
  • 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
  • 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.
  • RMLi Real-time Meta-data Link interface
  • the information required for organization of data and received by the real-time meta-data link interface 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.
  • 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.
  • 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 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.
  • RML real-time meta-data linking
  • 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 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.
  • 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.
  • the Intelligent Object-to-Intelligent Object Query meta-data interface 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.
  • the Intelligent Object-to-Intelligent Object Query component (OQMc) 455 comprises a module within an information technology platform for
  • 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 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.
  • modules including one or more of learning and knowledge extraction algorithms are provided.
  • the Pool Content Access definitions are provided within an information technology platform (ITP) 151 using object-oriented data structures 152.
  • 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
  • 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.
  • 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
  • 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.
  • 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
  • the Result Aggregation Engine component (RAEc) 475 comprised as a module within an information technology platform for Intelligent Objects.
  • the Result Aggregation Engine component (RAEc) 475 comprises a module within an information technology platform using object-oriented data structures.
  • 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
  • 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.
  • REEc Result Aggregation Engine component
  • 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.
  • RAEc Result Aggregation Engine component
  • REEi Result Aggregation Engine interface
  • 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.
  • 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.
  • 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.
  • Table I Exemplary computer program code for performing an embodiment of the procedure.
  • CClusterDlg: :CclusterDlg(CWnd* pParent /* NULL*/) : CDialog(CClusterDlg::IDD, pParent)
  • the EVIO Zoom component (IMO-Zc) 477 comprises a module within an information technology platform for Intelligent Objects.
  • the EVIO Zoom component (TMO-Zc) 477 optionally comprises a module within an information technology platform using object-oriented data structures.
  • 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
  • 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.
  • 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.
  • the EVIO Zoom interface (TMO-Zi) 478 comprises a module within an information technology platform 151 for intelligent Objects.
  • the EVIO Zoom interface (EVIO-Zi) 478 comprises a module within an information technology platform using object-oriented data structures.
  • 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.
  • 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
  • the Distributed Learning Engine component (DLEc) 479 comprised as a module within an information technology platform for Intelligent Objects.
  • the Distributed Learning Engine component (DLEc) 479 optionally comprises a module within an information technology platform using object-oriented data structures.
  • DLEi Distributed Learning Engine Interface
  • 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
  • iPools 155 components and access interfaces, and is optionally provided in the inventive system, method, and computer program.
  • 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.
  • DLEc Distributed Learning Engine component
  • the Distributed Learning Engine interface (DLEi) 480 comprised as a module within an information technology platform for Intelligent Objects.
  • the Distributed Learning Engine interface comprises a module within an information technology platform optionally using object-oriented data structures.
  • 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.
  • KEEc Knowledge Extraction Engine component
  • 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.
  • the Knowledge Extraction Engine component KEEc
  • KEEc Knowledge Extraction Engine component
  • 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
  • KEEc Extraction Engine component 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.
  • 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
  • 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.
  • the Knowledge Extraction Engine interface (KEEi) 482 comprises a module within an information technology platform for Intelligent Objects.
  • the Knowledge Extraction Engine interface (KEEi) 482 comprises a module within an information technology platform optionally using object-oriented data structures.
  • 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.
  • 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
  • Macintosh-based based platforms and/or environments or any Windows platform and/or Windows-based platforms such as Microsoft Windows 98, ME, 2000, NT
  • 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.
  • each property pane provides an overview of certain properties of the comprised data and its relationships.
  • 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.
  • 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.
  • 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.
  • 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.
  • ⁇ COLORREF cr RGB(rgb[(row * height) + colJ.rgbtRed, rgb [(row * height) + col] .rgbtGreen, rgb [(row * height) + colj.rgbtBlue); L_PutPixelColor(&mJitmapThumbnail, row, col, cr);
  • An object query interface (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.
  • 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.
  • RAE external result aggregation engine
  • RKI external report generation interface
  • 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.
  • CDialogView* view (CDialogView*)GetParentQ
  • CMainDoc* doc (CMainDoc*)view->GetDocwnent()
  • curr tate tr JT("None"); ⁇ ⁇
  • ⁇ parent mJreeObjectSate.Insertltem(str); mJreeObjectSate.SetItemData(parent,flag); continue;
  • HTREEITEM item mJreeObjectSate.Insertltem ⁇ nt, parent); mJreeObjectSate.SetItemData(item,flag); continue; ASSERT(FALSE);
  • 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.
  • ICR interactive content router component
  • SMC status management component
  • OQI object query interface
  • MDXi meta-data access interface
  • OAM object access manager component
  • ADDR application / database definition router
  • 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.
  • 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.
  • 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.
  • TCHAR extfjMAXJEXT] ⁇ NULL ⁇
  • TCHAR* icr new TCHAR[param.GetLengthQ + lj; memsetftcr, NULL, sizeof (TCHAR) * (param.GetLengthQ + 1));
  • 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.
  • a dynamic loading based on content is provided which allows to allocate and open all EVIO data of similar content attributes simultaneously.
  • BEGINJfESSA GEJ4AP (CFileExDlg, CFileDialog) // ⁇ AFXjMSGJMAP(CFileExDlg) ONJ ⁇ M_PAINTQ ON_BN_CLICKED(IDC_OPENALLCURRENTATTRIB, OnOpenAllSameAttrib)
  • m Curr Content Attr ⁇ b -1; m rrayFileName.RemoveAUQ; memset(&mJitmapThumbnail, NULL, sizeof (mJitmapTliumbnail));
  • HP ALETTE hp L_CreatePaintPalette(wnd_dc.GetSafeHdc(), &mJitmapThumbnail);
  • CPalette *oldjpal wndjlc.SelectPalette(CPalette::FromHandle ⁇ p), FALSE);
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Software Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)
EP01991011A 2000-12-06 2001-12-06 System, verfahren und softwarearchitektur und geschäftsmodell für eine intelligente, auf objekten basierende informations technologieplattform Withdrawn EP1381972A4 (de)

Applications Claiming Priority (33)

Application Number Priority Date Filing Date Title
US25406300P 2000-12-06 2000-12-06
US25406400P 2000-12-06 2000-12-06
US25406200P 2000-12-06 2000-12-06
US254062P 2000-12-06
US254063P 2000-12-06
US25905000P 2000-12-29 2000-12-29
US259050P 2000-12-29
US24623801P 2001-01-25 2001-01-25
US246238P 2001-01-25
US26695701P 2001-02-06 2001-02-06
US266957P 2001-02-06
US27671101P 2001-03-16 2001-03-16
US276711P 2001-03-16
US28265601P 2001-04-09 2001-04-09
US28265501P 2001-04-09 2001-04-09
US28265801P 2001-04-09 2001-04-09
US28265701P 2001-04-09 2001-04-09
US28265401P 2001-04-09 2001-04-09
US282655P 2001-04-09
US282656P 2001-04-09
US282654P 2001-04-09
US282658P 2001-04-09
US282657P 2001-04-09
US28299001P 2001-04-10 2001-04-10
US28299101P 2001-04-10 2001-04-10
US28298901P 2001-04-10 2001-04-10
US28297901P 2001-04-10 2001-04-10
US282979P 2001-04-10
US282989P 2001-04-10
US282991P 2001-04-10
US282990P 2001-04-10
PCT/US2001/047922 WO2002054171A2 (en) 2000-12-06 2001-12-06 System, method, software architecture and business model for an intelligent object based information technology platform
US254064P 2009-10-22

Publications (2)

Publication Number Publication Date
EP1381972A2 EP1381972A2 (de) 2004-01-21
EP1381972A4 true EP1381972A4 (de) 2007-03-14

Family

ID=27585833

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01991011A Withdrawn EP1381972A4 (de) 2000-12-06 2001-12-06 System, verfahren und softwarearchitektur und geschäftsmodell für eine intelligente, auf objekten basierende informations technologieplattform

Country Status (3)

Country Link
EP (1) EP1381972A4 (de)
AU (1) AU2002230765A1 (de)
WO (1) WO2002054171A2 (de)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060159325A1 (en) * 2005-01-18 2006-07-20 Trestle Corporation System and method for review in studies including toxicity and risk assessment studies
US8341536B2 (en) 2005-07-08 2012-12-25 International Business Machines Corporation Dynamic interface component control support
US7483757B2 (en) 2005-07-22 2009-01-27 Honeywell International, Inc. Control system migration
CN102918522B (zh) 2010-04-05 2016-05-04 昕易软件公司 用于生成统计研究信息的系统、方法以及设备
WO2012024450A2 (en) 2010-08-17 2012-02-23 Wisercare Llc Medical care treatment decision support system
US20140281019A1 (en) * 2013-03-15 2014-09-18 Microsoft Corporation Network Transmission Adjustment Based On Application-Provided Transmission Metadata
EP3052933B1 (de) * 2013-10-02 2019-09-04 Suri Technologies Ltd. Patientenspezifische immuntherapie zur behandlung heterogener tumore
BR112016005567B1 (pt) 2014-07-01 2022-08-16 Vf Worldwide Holdings Ltd Sistema de computador implementado e método para coletar e apresentar informação de multi-formato
CN107368753A (zh) * 2017-08-01 2017-11-21 浪潮软件集团有限公司 一种基于业务模型的可定制的数据权限模型及实现方法
CN110019176B (zh) * 2019-04-11 2023-08-18 普元信息技术股份有限公司 提高数据治理服务成功率的数据治理控制系统
CN110502762B (zh) * 2019-08-27 2023-07-28 北京金山数字娱乐科技有限公司 一种翻译平台及其管理方法
CN113095471B (zh) * 2020-01-09 2024-05-07 北京君正集成电路股份有限公司 一种提高检测模型效率的方法
CN112994846B (zh) * 2021-03-02 2023-01-31 广州汇通国信科技有限公司 一种应用于电力数据同步校验的治理方法
CN113218903B (zh) * 2021-05-19 2023-01-20 中国石油大学(华东) 一种基于微流控与人工智能的油液分析设备故障预测系统
CN113359642A (zh) * 2021-06-28 2021-09-07 上海致景信息科技有限公司 多品牌融合的染整控制方法、装置、系统及处理器
CN114968617B (zh) * 2022-04-28 2023-09-01 杭州未名信科科技有限公司 Api转换系统及其访问请求处理方法、电子设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0809198A2 (de) * 1996-05-22 1997-11-26 Wang Laboratories, Inc. Multidatenbankzugangsserver für Anwendungsprogramme
WO2000039709A1 (fr) * 1998-12-28 2000-07-06 Bull Procede de traitement d'une requete
WO2000065486A2 (en) * 1999-04-09 2000-11-02 Sandpiper Software, Inc. A method of mapping semantic context to enable interoperability among disparate sources

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5566330A (en) * 1991-08-20 1996-10-15 Powersoft Corporation Method for forming a reusable and modifiable database interface object
US6134559A (en) * 1998-04-27 2000-10-17 Oracle Corporation Uniform object model having methods and additional features for integrating objects defined by different foreign object type systems into a single type system
US6305007B1 (en) * 1998-07-24 2001-10-16 Computer Associates Think, Inc. Object property meta model emulator for legacy data structures
US6611844B1 (en) * 1999-02-19 2003-08-26 Sun Microsystems, Inc. Method and system for java program storing database object entries in an intermediate form between textual form and an object-oriented form

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0809198A2 (de) * 1996-05-22 1997-11-26 Wang Laboratories, Inc. Multidatenbankzugangsserver für Anwendungsprogramme
WO2000039709A1 (fr) * 1998-12-28 2000-07-06 Bull Procede de traitement d'une requete
WO2000065486A2 (en) * 1999-04-09 2000-11-02 Sandpiper Software, Inc. A method of mapping semantic context to enable interoperability among disparate sources

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PAPAKONSTANTINOU Y ET AL: "Object exchange across heterogeneous information sources", DATA ENGINEERING, 1995. PROCEEDINGS OF THE ELEVENTH INTERNATIONAL CONFERENCE ON TAIPEI, TAIWAN 6-10 MARCH 1995, LOS ALAMITOS, CA, USA,IEEE COMPUT. SOC, 6 March 1995 (1995-03-06), pages 251 - 260, XP000551569, ISBN: 0-8186-6910-1 *
SULL W ET AL: "Manufacturing information integration using an object-oriented knowledge framework", DECISION AIDING FOR COMPLEX SYSTEMS. CHARLOTTESVILLE, VA., OCT. 13 - 16, 1991, PROCEEDINGS OF THE INTERNATIONAL CONFERENCE ON SYSTEMS, MAN AND CYBERNETICS, NEW YORK, IEEE, US, vol. VOL. 1 _, 13 October 1991 (1991-10-13), pages 443 - 448, XP000238717, ISBN: 0-7803-0233-8 *

Also Published As

Publication number Publication date
EP1381972A2 (de) 2004-01-21
AU2002230765A1 (en) 2002-07-16
WO2002054171A2 (en) 2002-07-11
WO2002054171A3 (en) 2003-11-20

Similar Documents

Publication Publication Date Title
US20040003132A1 (en) Data pool architecture, system, and method for intelligent object data in heterogeneous data environments
WO2002054171A2 (en) System, method, software architecture and business model for an intelligent object based information technology platform
Swedlow et al. Bioimage informatics for experimental biology
Baumann The OGC web coverage processing service (WCPS) standard
US20030233365A1 (en) System and method for semantics driven data processing
Soibelman et al. Management and analysis of unstructured construction data types
US9069930B1 (en) Security information and event management system employing security business objects and workflows
US6799174B2 (en) Retrieving, organizing, and utilizing networked data using databases
US20040024720A1 (en) System and method for managing knowledge
WO1999013417A1 (en) A system, method, and medium for retrieving, organising, and utilizing networked data
Hilbig et al. MONA–Interactive manipulation of molecule collections
Do et al. On metadata interoperability in data warehouses
Butt et al. Towards Ontology Driven Provenance in Scientific Workflow Engine.
Hsu et al. Reconfigurable Web wrapper agents for biological information integration
Arafat et al. Quantum Theory and the Nature of Search.
Mosbah Information Retrieval Approach based on Recursive Query Shifting
Baklarz et al. DB2 Universal Database V8 for Linux, UNIX, and Windows Database Administration Certification Guide
Czajkowski et al. ERMrest: an entity-relationship data storage service for web-based, data-oriented collaboration
Oladele INTEGRATION OF BIOLOGICAL DATA SOURCES: A SURVEY
Candela et al. D4Science facilities for managing biodiversity databases
Hartstein Oracle Database New Features Guide, 10g Release 1 (10.1) Part No. B10750-01 Copyright© 2001, 2003 Oracle Corporation. All rights reserved. Contributors: Mateo Burtch, Paul Lane, Diana Lorentz, Mark Townsend, Sandra Cheevers, Michael
Sanyal et al. DB2 Universal Database V8 Application Development Certification Guide
Eckman et al. Data management in molecular and cell biology: vision and recommendations
Mirel et al. Integrating automated workflows, human intelligence and collaboration
Slezak et al. Design of the National Bioforensics Library Infrastructure

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030703

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: IO INFORMATICS, INC.

A4 Supplementary search report drawn up and despatched

Effective date: 20070213

17Q First examination report despatched

Effective date: 20070504

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20110701