Knowledge Base Coordinator Ontology Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current tools for integrating disparate ontologies lack adequate safeguards for semantics, security, integrity, and accessibility, making it difficult to manage and merge multiple ontologies effectively in a secure and traceable manner.

Innovation Solution

A Knowledge-Base Coordinator (KBC) is introduced, which uses a meta-ontology to classify and control access to multiple ontologies, providing a secure, traceable, and location-transparent design for seamless inclusion of multiple ontologies, including support for hierarchical systems, access control, and ontology versioning, while allowing runtime merging of independently designed ontologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If multiple ontologies are integrated using current tools, then the quantity of knowledge resources increases, but semantic integrity and security are compromised

Engineering Contradiction:
Improvequantity of ontologiesVSAvoidsemantic integrity
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent introduces a Knowledge Base Coordinator (KBC) as an intermediary system that manages the integration of multiple ontologies. The KBC uses a meta-ontology to classify source ontologies, control their inclusion, and enforce access policies, thereby maintaining semantic integrity while enabling multi-ontology systems. This mediator coordinates between disparate ontology sources and the merged knowledge base, ensuring security and traceability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If ontologies are merged without coordination, then the versatility of knowledge applications increases, but system security and accessibility control deteriorate

Engineering Contradiction:
Improveversatility of knowledge applicationsVSAvoidsystem security risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary classification and authorization mechanisms through the meta-ontology before ontologies are merged. The system pre-defines access control policies, classifies source ontologies into types, and establishes security rules in advance. This preliminary structuring enables versatile multi-ontology applications while maintaining security control through pre-established authorization frameworks.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If a meta-ontology framework is implemented to control access, then semantic security improves, but system complexity increases

Engineering Contradiction:
Improvesemantic securityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the knowledge base system into distinct layers: source ontologies, a meta-ontology for classification and control, and a merged ontology. The KBC is divided into separate modules including an ontology inclusion manager, access control enforcer, and versioning controller. This segmentation manages complexity by organizing functions into discrete, manageable components while maintaining comprehensive security control.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If runtime merging of ontologies is enabled, then the dynamic evolvability of applications improves, but traceability and version control become more difficult

Engineering Contradiction:
Improvedynamic evolvabilityVSAvoidtraceability of ontology sources
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms through the KBC that track ontology inclusions, modifications, and versions in real-time. The system maintains provenance information about source ontologies and their contributions to the merged ontology. This feedback loop enables runtime merging while preserving traceability, as the KBC continuously monitors and records changes to maintain an audit trail of ontology evolution.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7734557B2Methods, software, and systems for knowledge base coordination
Publication Date: 2010.06.08 THE BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UNIV
  • US7734557B2 patent drawing
  • US7734557B2 patent drawing
  • US7734557B2 patent drawing

AI summary

The present invention provides computer program products, systems, and related methods of coordinating a knowledge base.