Wrapper Service for R2RML Data Transformation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current R2RML and RML mapping processors face challenges with rapid interoperability and compatibility issues due to varied tools and formats, leading to time-consuming and costly efforts in adapting to changing requirements and integrating diverse relational and RDF formats, especially when dealing with legacy systems.
Innovation Solution
A wrapper service that acts as a generic interface to consolidate various R2RML mapping processors, providing a unified platform-agnostic solution for transforming relational source data into RDF format, allowing for automatic adaptation to different input and output formats and systems, thereby simplifying the ETL process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple different R2RML and RML mapping processors are used to handle varied tools and formats, then the ability to support diverse formats and systems is improved, but the complexity of integration and interoperability increases
Solution Approach 1:
The patent introduces a wrapper service as an intermediary component that sits between the user and multiple R2RML/RML mapping processors. This wrapper provides a unified interface that abstracts the complexity of interacting with different processors, allowing users to work with a single standardized interface while the wrapper handles the complexity of routing requests to appropriate processors and managing format conversions.
Solution Approach 2:
The wrapper service is designed as a universal interface that can handle multiple R2RML and RML mapping processors through a single standardized API. It provides multi-functional capabilities by supporting various input formats (RDB, CSV, Excel, JSON, XML), multiple processor types, and different output formats, all through one unified service that adapts to different requirements without requiring users to learn multiple interfaces.
2Device complexity
If a single R2RML processor is used to simplify the system, then the complexity is reduced, but the adaptability to changing requirements and diverse formats deteriorates
Solution Approach 1:
The system implements dynamics by allowing the wrapper service to dynamically select and route requests to different R2RML/RML mapping processors based on the specific requirements of the task. The wrapper can adapt its behavior at runtime to handle different formats, processors, and configurations without requiring system reconfiguration, enabling the system to remain simple for users while being highly adaptable to changing requirements.
3Adaptability or versatility
If existing R2RML processor solutions are replaced to match new features and requirements, then the adaptability to new requirements is improved, but the time and cost required for replacement increases
Solution Approach 1:
The wrapper service performs preliminary actions by pre-configuring support for multiple R2RML and RML mapping processors and establishing a unified interface architecture in advance. This preliminary setup allows the system to adapt to new requirements by simply adding new processor support through the existing wrapper framework, rather than requiring complete system replacement. The wrapper can be extended to support new processors and formats by adding new components rather than replacing the entire system.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
- The present invention relates to data transformation from source data in RDB format to result data in RDF format, and more particularly relates to a system and method for efficient (R2)RML mapping-based data transformation. The invention helps to make source data from e.g., sensors and/or monitoring devices machine readable by transforming datasets in RDB format to datasets in graph dataset format as RDF datasets are. The latter graph RDF datasets may than be read out and used by machines, e.g., processor units. The proposed solution in form of a unified interface being a wrapper service serves as a simplistic interface that absorbs complexities arising from diverse tool implementations, accelerates registration of other tools, both existing and new, e.g., when new versions are released.