Edit Paper: Updating Relational Data via SPARQL/Update

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
title

Abstract[edit]

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

Conclusion[edit]

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

Future work[edit]

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

Approach[edit]

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

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

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

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

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

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

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

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

Implementations[edit]

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

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

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

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: {{{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}}}Property "Has vendor" (as page type) with input value "{{{vendor}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

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

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

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}}}Property "Has Version" (as page type) with input value "{{{Version}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

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

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

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}}}Property "Has motivation" (as page type) with input value "{{{Motivation}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Evaluation[edit]

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

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

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

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

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

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}}}Property "Has Results" (as page type) with input value "{{{Results}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

[edit]

Bibliographical Metadata
Content Metadata
Approach
Implementations
Research Problem
Evaluation

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:	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.	Abstract of the paper.
Conclusion:	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.
Future work:	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.	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:	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.
Proposes Model:
Methodology:	No data available now.
Requirements:	No data available now.

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:	No data available now.
Evaluation method :		A broader research problem.
Hypothesis:	No data available now.	A another research problem.
Description:	No data available now.	The motivation to solve the problem.
Dimensions:		Select evaluation dimension.
Benchmark:		Benchmark used for evaluation.
Results:	No data available now.

Paper description:

Summary:

This is a minor edit

Watch this page

Cancel