Edit Paper: Updating Relational Data via SPARQL/Update

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.

Updating Relational Data via SPARQL/Update

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

Retrieved from "https://www.openresearch.org/wiki/Updating_Relational_Data_via_SPARQL/Update"
Facts about "Updating Relational Data via SPARQL/Update"
RDF feed
Access APINo data available now. +
Event in seriesEDBT +
Has BenchmarkHttp://wifo5-03.informatik.uni-mannheim.de/bizer/BerlinSPARQLBenchmark/ +
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://www.ifi.uzh.ch/en/seal/research/projects/ontoAccess.html +
Has EvaluationNo data available now. +
Has EvaluationMethodNo data available now. +
Has ExperimentSetupNo data available now. +
Has GUINo +
Has HypothesisNo data available now. +
Has ImplementationOntoAccess +
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 Version0.3.2 +
Has abstractRelational Databases are used in most curr …
Relational Databases are used in most current enterprise environments to store and manage data. The semantics of the data is not explicitly encoded in the relational model, but implicitly on the application level. Ontologies and Semantic Web technologies provide explicit semantics that allows data to be shared and reused across application, enterprise, and community boundaries. Converting all relational data to RDF is often not feasible, therefore we adopt an ontology-based access to relational databases. While existing approaches focus on read-only access, we present our approach OntoAccess that adds ontology-based write access to relational data. OntoAccess consists of the update-aware RDB to RDF mapping language R3M and algorithms for translating SPARQL/Update operations to SQL. This paper presents the mapping language, the translation algorithms, and a prototype implementation of OntoAccess.
 a prototype implementation of OntoAccess. +
Has approachAdding ontology-based write access to relational data +
Has authorsMatthias Hert +, Gerald Reif + and Harald C. Gall +
Has conclusionIn this paper, we presented our approach O …
In this paper, we presented our approach OntoAccess that enables the manipulation of relational data via SPARQL/Update. We introduced the update-aware RDB to RDF mapping language R3M that captures additional information about the database schema, in particular about integrity constraints. This information enables the detection of update requests that are invalid from the RDB perspective. Such requests cannot be executed by the database engine as they would violate integrity constraints of the database schema. The information can also be exploited to provide semantically rich feedback to the client. Therefore, the causes for the rejection of a request and possible directions for improvement can be reported in an appropriate format.
 can be reported in an appropriate format. +
Has future workFuture work is planned for various aspects …
Future work is planned for various aspects of OntoAccess. Further research needs to be done on bridging the conceptual gap between RDBs and the Semantic Web. Ontology-

based write access to the relational data creates completely new challenges on this topic with respect to read-only approaches. The presence of schema constraints in the database can lead to the rejection of update requests that would otherwise be accepted by a native triple store. A feedback protocol that provides semantically rich information about the cause of a rejection and possible directions for improvement plays a major role in bridging the gap. Other database constraints such as assertions have to be evaluated as well to see

if they can reasonably be supported in the mapping. Also, a more formal definition of the mapping language will be provided. Furthermore, we will extend our prototype implementation to support the SPARQL/Update MODIFY operation, SPARQL queries, and the just mentioned feedback protocol.
 and the just mentioned feedback protocol. +
Has motivationNo data available now. +
Has platformNo data available now. +
Has problemTransforming Relational Databases into Semantic Web +
Has relatedProblemNo data available now. +
Has vendorfree +
Has year2010 +
ImplementedIn ProgLangNo data available now. +
Proposes AlgorithmNo data available now. +
RunsOn OSNo data available now. +
TitleUpdating Relational Data via SPARQL/Update +
Uses FrameworkJena +
Uses MethodologyNo data available now. +
Uses ToolboxNo data available now. +