Edit Paper: Accessing and Documenting Relational Databases through OWL Ontologies

Jump to: navigation, search

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

Accessing and Documenting Relational Databases through OWL Ontologies
title

Abstract[edit]

{{{Abstract}}}

Conclusion[edit]

{{{Conclusion}}}

Future work[edit]

{{{Future work}}}

Approach[edit]

Positive Aspects: {{{PositiveAspects}}}

Negative Aspects: {{{NegativeAspects}}}

Limitations: {{{Limitations}}}

Challenges: {{{Challenges}}}

Proposes Algorithm: {{{ProposesAlgorithm}}}

Methodology: {{{Methodology}}}

Requirements: {{{Requirements}}}

Limitations: {{{Limitations}}}

Implementations[edit]

Download-page: {{{Download-page}}}

Access API: {{{API}}}

Information Representation: {{{InfoRepresentation}}}

Data Catalogue: {{{Catalogue}}}

Runs on OS: {{{OS}}}

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

Vendor: {{{vendor}}}

Uses Framework: {{{Framework}}}

Has Documentation URL: {{{DocumentationURL}}}

Programming Language: {{{ProgLang}}}

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

Version: {{{Version}}}

Platform: {{{Platform}}}

Toolbox: {{{Toolbox}}}

GUI: No

Research Problem[edit]

Subproblem of: {{{Subproblem}}}

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

RelatedProblem: {{{RelatedProblem}}}

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

Motivation: {{{Motivation}}}

Evaluation[edit]

Experiment Setup: {{{ExperimentSetup}}}

Evaluation Method : {{{EvaluationMethod}}}

Hypothesis: {{{Hypothesis}}}

Description: {{{Description}}}

Dimensions: {{{Dimensions}}}

Benchmark used: {{{Benchmark}}}

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

Results: {{{Results}}}


[edit]
Paper Title*: Full title of the given paper
Subject: Primary subject or topic of research of the paper.
Author(s):
Publication venue: Publication venue of the paper.
Year: The year in which the paper is published.
Keywords:
Abstract: Abstract of the paper.
Conclusion:
Future work: Future ideas of the paper.
Problem: The research problem.
Approach: Approach used to achieve the goal.
Implementation: The implementation/framework that is invoked when running.
Evaluation: Proposed work Evaluation.
Positive Aspects:
Negative Aspects:
Limitations:
Challenges:
Proposes Algorithm:
Proposes Model:
Methodology:
Requirements:
Download-page:
Access API:
Information Representation:
Data Catalogue:
OS:
Vendor: Organization: commercial, free or otherwise
Uses Framework: Framework name
Documentation URL: Link to Documentation webpage.
Programming Language:
Version:
Platform:
Toolbox:
GUI: whether the implementation has a GUI?
Subproblem of: A broader research problem.
Related Problem: A another research problem.
Motivation: The motivation to solve the problem.


Experiment setup:
Evaluation method : A broader research problem.
Hypothesis: A another research problem.
Description: The motivation to solve the problem.
Dimensions:
Select evaluation dimension.
Benchmark: Benchmark used for evaluation.
Results:



Paper description:

Cancel

Retrieved from "https://www.openresearch.org/wiki/Accessing_and_Documenting_Relational_Databases_through_OWL_Ontologies"
Facts about "Accessing and Documenting Relational Databases through OWL Ontologies"
RDF feed
Access APINo data available now. +
Event in seriesFQAS +
Has BenchmarkNo data available now. +
Has ChallengesNo data available now. +
Has DataCatalouge{{{Catalogue}}} +
Has DescriptionNo data available now. +
Has DimensionsNo data available now. +
Has DocumentationURLhttp://No data available now. +
Has Downloadpagehttp://No data available now. +
Has EvaluationNo data available now. +
Has EvaluationMethodNo data available now. +
Has ExperimentSetupNo data available now. +
Has GUINo +
Has HypothesisNo data available now. +
Has ImplementationROSEX-SPARREW +
Has InfoRepresentationNo data available now. +
Has LimitationsNo data available now. +
Has NegativeAspectsNo data available now. +
Has PositiveAspectsNo data available now. +
Has RequirementsNo data available now. +
Has ResultsNo data available now. +
Has SubproblemNo data available now. +
Has VersionNo data available now. +
Has abstractRelational databases have been designed to …
Relational databases have been designed to store high volumes of data and to provide an efficient query interface. Ontologies are geared towards capturing domain knowledge, annotations, and to offer high-level, machine-processable views of data and metadata. The complementary strengths and weaknesses of

these data models motivate the research effort we present in this paper. The goal of this work is to bridge the relational and ontological worlds, in order to leverage the efficiency and scalability of relational technologies and the high-level view of data and metadata proper of ontologies. The system we designed and developed

achieves: (i) automatic ontology extraction from relational data sources and (ii) automatic query translation from SPARQL to SQL. Among the others, we focus on two main applications of this novel technology: (i) ontological publishing of relational data, and (ii) automatic relational schema annotation and documentation. The system has been designed and tested against real-life scenarios from Big Science projects, which are used as running examples throughout the paper.
 as running examples throughout the paper. +
Has approachNo data available now. +
Has authorsCarlo Curino +, Giorgio Orsi +, Emanuele Panigati + and Letizia Tanca +
Has conclusionIn this paper, we presented a completely a …
In this paper, we presented a completely automated approach to map relational databases and ontologies. The system proposed is capable of extracting an ontological view of the relational schema, and to enable SPARQL access to the relational data source by means of a query rewriting mechanism. The same approach can be used to efficiently store relational ontologies on a RDBMS; moreover, the mapping we devised is completely based on OWL with no need to resort to a new formalism. The impact of this system has been discussed considering three main applications: (i) publishing of relational data in an ontological format, (ii) documentation of relational schemas by means of ontological annotations, and (iii) efficient relational storage for data-intensive ontologies.
nal storage for data-intensive ontologies. +
Has future workNo data available now. +
Has motivationNo data available now. +
Has platformNo data available now. +
Has problemTransforming Relational Databases into Semantic Web +
Has relatedProblemNo data available now. +
Has vendorNo data available now. +
Has year2009 +
ImplementedIn ProgLangNo data available now. +
Proposes AlgorithmNo data available now. +
RunsOn OSNo data available now. +
TitleAccessing and Documenting Relational Databases through OWL Ontologies +
Uses FrameworkNo data available now. +
Uses MethodologyNo data available now. +
Uses ToolboxNo data available now. +