Semantic Resource Integration via Intermediary Adapter Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing applications, including those based on the semantic web, are limited in their ability to dynamically integrate and utilize additional semantic data links and properties from other applications without modifying their code, leading to static use cases and underutilization of semantic databases.
Innovation Solution
An integrating application that receives requests for semantic resources, determines their properties, identifies associated applications, and presents them on demand, allowing for dynamic integration and utilization of new data without modifying existing application code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications are statically linked to use cases through code modifications, then the main application can access semantic data from other applications, but the system lacks flexibility and requires code changes to integrate new applications or data links
Solution Approach 1:
The patent introduces an intermediary component (integration service or adapter layer) that mediates between the main application and other applications. This intermediary handles the discovery, linking, and data access operations, allowing the main application to access semantic data without direct code modifications. The intermediary translates and coordinates communications between different applications, enabling dynamic integration while maintaining application independence.
Solution Approach 2:
The system is segmented into independent functional components: the main application, intermediary integration service, and other applications. Each component operates independently with well-defined interfaces. The integration logic is separated from the main application code and placed in the intermediary layer, allowing new applications to be integrated by configuring the intermediary rather than modifying the main application code.
2Productivity
If the main application designer identifies each use case and resolves dependencies manually, then specific use cases can be implemented, but the process is time-consuming and cannot adapt to new use cases dynamically
Solution Approach 1:
The system performs preliminary actions by pre-configuring the intermediary service with metadata about available applications, their data models, and potential integration points. This preliminary setup enables automatic discovery and integration when new use cases arise, eliminating the need for manual use case identification and dependency resolution for each new scenario.
Solution Approach 2:
The main application and other applications are equipped with self-service capabilities through metadata annotations and automatic discovery mechanisms. The intermediary service automatically discovers available applications, identifies compatible data links, and configures integrations without requiring manual intervention from the application designer. This self-service approach enables rapid adaptation to new use cases.
3Adaptability or versatility
If applications are modified to access semantic data links from other applications, then data integration is achieved, but existing applications cannot leverage new data links without code updates
Solution Approach 1:
The intermediary layer acts as a buffer between applications and semantic data links. When new data links or applications are added to the system, only the intermediary needs to be updated with new configuration information. The main application continues to operate without modifications, accessing new data links through the intermediary's updated interface. This decouples the update requirement from the main application code.
Solution Approach 2:
The intermediary service provides universal access functionality to multiple applications and data sources through a standardized interface. A single intermediary component serves multiple purposes: discovering applications, resolving dependencies, managing data links, and facilitating access. This multi-functional design allows the system to accommodate new applications and data links through a single universal access point without requiring individual application modifications.
Data Source
AI summary
An approach is provided for integrating applications on demand to display and manipulate a semantic resource. An integrating application causes, at least in part, reception of a request for a semantic resource, and determines whether the semantic resource is known to a first application. The integrating application discovers one or more properties of the semantic resource based, at least in part, on the determination. The integrating application identifies a second application associated with the semantic resource based, at least in part, on the one or more properties. The integrating application causes, at least in part, presentation of the semantic resource through the second application.