From Relational Data to RDFS Models

From Relational Data to RDFS Models
From Relational Data to RDFS Models
Bibliographical Metadata
Year:	2004
Authors:	Maksym Korotkiy, Jan L. Top
Venue	ICWE
Content Metadata
Problem:	Transforming Relational Databases into Semantic Web
Approach:	integration of relational-like information resources with RDFS-aware systems
Implementation:	FDR2
Evaluation:	No data available now.

Abstract

A vast amount of information resources is stored as relational-like data and inaccessible to RDFS-based systems. We describe FDR2 – an approach to integration of relational-like information resources with RDFS-aware systems. The proposed solution is purely RDFS-based. We use RDF/S as a mechanism to specify and perform linking of relational data to a predefined domain ontology. The approach is transformation-free, this ensures that all the data is accessible and usable in consistence with the original data model.Property "Has abstract" (as page type) with input value "A vast amount of information resources is stored as relational-like data and inaccessible to RDFS-based systems. We describe FDR2 – an approach to integration of relational-like information resources with RDFS-aware systems. The proposed solution is purely RDFS-based. We use RDF/S as a mechanism to specify and perform linking of relational data to a predefined domain ontology. The approach is transformation-free, this ensures that all the data is accessible and usable in consistence with the original data model." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Conclusion

In this paper we have introduced FDR2 – a technique that enables us to link relational and RDF/S data models. According to FDR2 a relational schema is automatically created to explicate the structure and internal relationships between elements of a relational collection of data. Explication of virtual relations allows the user to construct a relational schema specific RDMap by defining relationships between concepts from the relational schema and a domain ontology. The actual relational data are automatically expressed in RDF according to the generated relational schema. Run-time integration is achieved by applying an RDFS reasoner to merge the above-mentioned components into a single RDFS model and to deduct necessary entailments. A resulting run-time model allows to access the relational data with queries termed according to the domain ontology. FDR2 is purely RDF/S-based and does not require any additional software components except an RDFS reasoner.Property "Has conclusion" (as page type) with input value "In this paper we have introduced FDR2 – a technique that enables us to link relational and RDF/S data models. According to FDR2 a relational schema is automatically created to explicate the structure and internal relationships between elements of a relational collection of data. Explication of virtual relations allows the user to construct a relational schema specific RDMap by defining relationships between concepts from the relational schema and a domain ontology. The actual relational data are automatically expressed in RDF according to the generated relational schema.</br>Run-time integration is achieved by applying an RDFS reasoner to merge the above-mentioned components into a single RDFS model and to deduct necessary entailments. A resulting run-time model allows to access the relational data with queries termed according to the domain ontology. FDR2 is purely RDF/S-based and does not require any additional software components except an RDFS reasoner." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Future work

No data available now.

Approach

Positive Aspects: No data available now.

Negative Aspects: No data available now.

Limitations: No data available now.

Challenges: No data available now.

Proposes Algorithm: No data available now.

Methodology: No data available now.

Requirements: No data available now.

Limitations: No data available now.

Implementations

Download-page: No data available now.

Access API: No data available now.

Information Representation: No data available now.

Data Catalogue: {{{Catalogue}}}Property "Has DataCatalouge" (as page type) with input value "{{{Catalogue}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Runs on OS: No data available now.

Vendor: No data available now.

Uses Framework: No data available now.

Has Documentation URL: No data available now.

Programming Language: No data available now.

Version: No data available now.

Platform: No data available now.

Toolbox: No data available now.

GUI: No