Apparatus and method for managing and inferencing contextural relationships accessed by the context engine to answer queries received from the application program interface, wherein ontology manager is operationally coupled with a working memory
View Patent ↗Standardized support for management of contextual relationships, which includes specification of the context hierarchy, association of relationships with a particular context, and derivation of transitive dependencies, is provided with a Context Manager service. The Context Manager provides a programmatic interface for defining contexts and the relationships therein. The Context Manager saves the relationship facts in one or more context stores, which are organized by contexts. The Context Manager interfaces with the Ontology Manager that processes queries on relationships with respect to a given set of contexts. The Context Manager provides a high-level abstraction for relationship management in a context. Developers of business solutions can then focus on the core business logic, without worrying about the details of storing and inferencing relationships.
1. An apparatus for managing and inferencing contexts and contextual relationships between resources comprising:
an application program interface (API), the API receiving queries about contextual relationships including creating or removing context, link context and ontology definitions, add or remove resources and interrelationships in and from context, and retrieve resource relationships;
a context engine, coupled to receive and process requests from the API;
an ontology manager accessible by the context engine and adapted to interpret ontology semantics and answer queries about contextual relationships; and
one or more context stores accessible by the context engine, the context engine using ontology semantics derived from the ontology manager to describe contextual relationships and storing the contextual relationships in one or more of the plurality of context stores, contextual relationship data stored in the context stores being accessed by the context engine to answer queries received from the API, wherein said ontology manager is operationally coupled with a working memory that holds at least part of relationship facts from said one or more context stores and said contexts provide one or more mechanisms for recording a current status of one or more resources by representing relationships among objects, roles, and processes explicitly or implicitly used in said resources.
2. The apparatus recited in claim 1 , wherein said said resources comprise one or more computer programs.
3. The apparatus recited in claim 1 , wherein said contexts have one or more relationships with one or more of other contexts, including inclusion, exclusion, sharing, and nesting.
4. The apparatus recited in claim 1 , wherein said contextual relationships represent one or more relationships among objects, roles, and processes which are defined in one or more said contexts and explicitly or implicitly used in one or more computer programs.
5. The apparatus recited in claim 4 , wherein said contextual relationships include generalization, specialization, transitive dependency, inversion, symmetry, and arbitrary user-defined relationships.
6. The apparatus recited in claim 1 , wherein said API includes operations for creating contexts, optionally as children of other contexts.
7. The apparatus recited in claim 1 , wherein said API includes operations for asserting relationships within a specific context.
8. The apparatus recited in claim 1 , wherein each of said one or more context stores is operationally coupled with an adapter that operates on a corresponding context store.
9. The apparatus recited in claim 1 , further comprising one or more ontology directories for recording meta-level information about which of said one or more context stores are available to the ontology manager.
10. The apparatus recited in claim 1 , further comprising one or more ontology source connectors for providing mechanisms for importing context stores recorded in one or more persistent storage media including local file system, remote servers, database systems, and Web servers.
11. The apparatus recited in claim 10 , further comprising one or more cache memories for storing context relationship information from remote context stores for improving performance and reliability.
12. The apparatus recited in claim 1 , further comprising a query optimizer accessed by the context engine to optimize queries from said interface.
13. A method for managing and inferencing contexts and contextual relationships, comprising the steps of:
receiving definitions and queries about contextual relationships through an application program interface (API), the API receiving queries about contextual relationships including creating or removing context, link context and ontology definitions, add or remove resources and interrelationships in and from context, and retrieve resource relationships;
accessing an ontology manager which interprets ontology semantics and answers queries about relationships;
recording contextual relationships in one or more context stores;
accessing data stored in said one or more context stores in response to queries received by the API; and
answering queries received through said API about contextual relationships wherein said contexts provide one or more mechanisms for recording a current status of one or more resources by representing relationships among objects, roles, and processes explicitly or implicitly used in said resources.
14. The method recited in claim 13 , wherein prior to said answering step, the further step of optimizing said queries.
15. The method recited in claim 13 , wherein said answering step further comprises the steps of:
copying relationship facts from said one or more context stores to a working memory; and
inferencing using the relationship facts stored in said working memory.
16. The method recited in clam 13 , wherein said resources comprise one or more computer programs.
17. The method recited in claim 13 , wherein said contexts have one or more relationship with one or more of other contexts, including, but not limited to, inclusion, exclusion, sharing, and nesting.
18. The method recited in claim 13 , wherein said contextual relationships represent one or more relationships among objects, roles, and processes which are defined in one or more said contexts and explicitly or implicitly used in one or more computer programs.
19. The method recited in claim 18 , wherein said contextual relationships include, but not are limited to, generalization, specialization, transitive dependency, inversion, symmetry, and arbitrary user-defined relationships.