Edit Paper: Cross: an OWL wrapper for teasoning on relational databases

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.


Cross: an OWL wrapper for teasoning on relational databases

Abstract[edit]

[[has abstract:={{{Abstract}}}]]

Conclusion[edit]

[[has conclusion:={{{Conclusion}}}]]

Future work[edit]

[[has future work:={{{Future work}}}]]

Approach[edit]

Positive Aspects: [[Has PositiveAspects::{{{PositiveAspects}}}]]

Negative Aspects: [[Has NegativeAspects::{{{NegativeAspects}}}]]

Limitations: [[Has Limitations::{{{Limitations}}}]]

Challenges: [[Has Challenges::{{{Challenges}}}]]

Proposes Algorithm: [[Proposes Algorithm::{{{ProposesAlgorithm}}}]]

Methodology: [[uses Methodology::{{{Methodology}}}]]

Requirements: [[Has Requirements::{{{Requirements}}}]]

Limitations: [[Has Limitations::{{{Limitations}}}]]

Implementations[edit]

Download-page: [[Has Downloadpage::{{{Download-page}}}]]

Access API: [[access API::{{{API}}}]]

Information Representation: [[Has InfoRepresentation::{{{InfoRepresentation}}}]]

Data Catalogue: [[Has DataCatalouge::{{{Catalogue}}}]]

Runs on OS: [[ runsOn OS::{{{OS}}}]]

Vendor: [[Has vendor::{{{vendor}}}]]

Uses Framework: [[Uses Framework::{{{Framework}}}]]

Has Documentation URL: [[Has DocumentationURL::{{{DocumentationURL}}}]]

Programming Language: [[implementedIn ProgLang::{{{ProgLang}}}]]

Version: [[has Version ::{{{Version}}}]]

Platform: [[has platform::{{{Platform}}}]]

Toolbox: [[uses Toolbox::{{{Toolbox}}}]]

GUI: has GUI::No

Research Problem[edit]

Subproblem of: [[Has Subproblem::{{{Subproblem}}}]]

RelatedProblem: [[Has relatedProblem::{{{RelatedProblem}}}]]

Motivation: [[Has motivation::{{{Motivation}}}]]

Evaluation[edit]

Experiment Setup: [[Has ExperimentSetup::{{{ExperimentSetup}}}]]

Evaluation Method : [[Has EvaluationMethod::{{{EvaluationMethod}}}]]

Hypothesis: [[Has Hypothesis::{{{Hypothesis}}}]]

Description: [[Has Description::{{{Description}}}]]

Dimensions: [[Has Dimensions::{{{Dimensions}}}]]

Benchmark used: [[has Benchmark::{{{Benchmark}}}]]

Results: [[Has 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

Access APINo data available now. +
Event in seriesER +
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://liris.cnrs.fr/∼pchampin/dev/cross +
Has EvaluationNo data available now. +
Has EvaluationMethodNo data available now. +
Has ExperimentSetupOn an Intel Core 2, 2.33GHz, with 2GB of memory +
Has GUINo +
Has HypothesisNo data available now. +
Has ImplementationCross +
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 abstractOne of the challenges of the Semantic Web
One of the challenges of the Semantic Web is to integrate the huge amount of information already available on the standard Web, usually stored in relational databases. In this paper, we propose a formalization of a logic model of relational databases, and a transformation of that model into an OWL, a Semantic Web language. This transformation is implemented in Cross, as an open-source prototype. We prove a relation between the notion of legal database state and the consistency of the corresponding OWL knowledge base. We then show how that transformation can prove useful to enhance databases, and integrate them in the Semantic Web.
s, and integrate them in the Semantic Web. +
Has approachNo data available now. +
Has authorsPierre-Antoine Champin +, Geert-Jan Houben + and Philippe Thiran +
Has conclusionIn this paper, we have proposed the ODBC m
In this paper, we have proposed the ODBC model, a formalization of relational databases focusing on their logic model. We have then presented a transformation of that model into OWL, a DL-based language designed for the Semantic Web. This transformation is implemented by the Cross open-source prototype, which effectively introduces the interesting notion of semantic values. We proved that the knowledge-based produced by this transformation is consistent if and only if the source database state is weakly legal (i.e. legal but regarding foreign key constraints). Taking advantage of that result, we have shown how that transformation can prove useful for the purpose of analysing legacy RDBs, enhancing existing RDBs with additional constraints, and integrating them in the SW.
nstraints, and integrating them in the SW. +
Has future workA first direction for further work would b
A first direction for further work would be to try and strengthen the theorem, to have an equivalence of OWL consistency with full legality, i.e. taking into account foreign keys. This could actually be done by using an expressive feature of OWL (the oneOf constructor, not mentioned in this paper), but would possibly make the reasoning intractable. Another solution would be to propose, in a similar way to finite model reasoning, an algorithm of closed world reasoning which would not be allowed to create individuals. We also want to get more experimental results for the Cross implementation. Preliminary results 7 are encouraging: the transformation of the schema of real database (127 tables, 869 columns, 132 unicity constraints, no foreign key) took around 1.5s; the resulting ontology was loaded in Pellet in about 9s, while reasoning took about 3s. Those results seem reasonable for a quite big schema. We now plan to experiment on the use cases presented in Section 6.3 with that database and a sample of other real databases.
base and a sample of other real databases. +
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 year2007 +
ImplementedIn ProgLangNo data available now. +
Proposes AlgorithmNo data available now. +
RunsOn OSNo data available now. +
TitleCross: an OWL wrapper for teasoning on relational databases +
Uses FrameworkNo data available now. +
Uses MethodologyNo data available now. +
Uses ToolboxNo data available now. +