Edit Paper: Relational.OWL - A Data and Schema Representation Format Based on OWL

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.


Relational.OWL - A Data and Schema Representation Format Based on OWL

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 seriesPAKDD +
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 Downloadpagehttps://github.com/berezovskyi/relational-owl +
Has EvaluationNo data available now. +
Has EvaluationMethodNo data available now. +
Has ExperimentSetupNo data available now. +
Has GUIYes +
Has HypothesisNo data available now. +
Has ImplementationRelational.OWL +
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 research fields which has recen
One of the research fields which has recently gained much scientific interest within the database community are Peer-to-Peer databases, where peers have the autonomy to decide whether to join or to leave an information sharing environment at any time. Such

volatile data nodes may appear shortly, collect or deliver some data, and disappear again. It even can not be assured that a peer joins the network ever again.

In this paper we introduce a representation format fort both, schema and data information based on the Web Ontology Language OWL. According to the advantages of the Semantic Web we are thus able to represent and to transfer every schema and data component of a database to any partner, without having to define a data and schema exchange format explicitly.
ata and schema exchange format explicitly. +
Has approachNo data available now. +
Has authorsCristian Pérez de Laborda + and Stefan Conrad +
Has conclusionIn this paper we have shown how to represe
In this paper we have shown how to represent schema and data items originally stored in relational database systems using our own OWL ontology. Relational.OWL enables us to semantically represent the schema of any relational database. This representation itself can be interpreted, due to the properties of OWL Full, as a novel ontology. Based on the latter

ontology, we can now semantically represent the data stored in this specific database.

The advantage of this representation technique is obvious: Both, schema and data changes can automatically be transferred to and processed by any remote database system, which is able to understand knowledge representation techniques used within OWL. Misunderstandings are impossible.Besides the refinement and completion of the concrete schema representation, we consider on how to adopt our technique to other types of database systems. Similar solutions can easily be found for Object-Oriented Databases, Hierarchical Databases like IMS, or its hybrid the modern and more common X.500 or LDAP Directory Systems
ore common X.500 or LDAP Directory Systems +
Has future workA further extension for Relational.OWL cou
A further extension for Relational.OWL could be a corresponding protocol extending the possibilities of Relational.OWL to particularly support data exchanges or replications. There we could employ the advantages of our knowledge representation technique for recurring problems occurring within such a data exchange process, e.g. identifying the same data items on remote databases. Although autonomously communicating databases in a metadata exchange are still more vision than reality, our model takes us one step further.
lity, our model takes us one step further. +
Has keywordsData Representation, Schema Representation, Semantic Web, Web Ontology Language (OWL), Resource Description Framework (RDF), Relational Databases, Ontologies +
Has motivationNo data available now. +
Has platformNo data available now. +
Has problemTransforming Relational Databases into Semantic Web +
Has relatedProblemNo data available now. +
Has vendorOpen Source +
Has year2005 +
ImplementedIn ProgLangJava +
Proposes AlgorithmNo data available now. +
RunsOn OSNo data available now. +
TitleRelational.OWL - A Data and Schema Representation Format Based on OWL +
Uses FrameworkNo data available now. +
Uses MethodologyNo data available now. +
Uses ToolboxNo data available now. +