• Aucun résultat trouvé

Updating SPARQL Results in Real-time with Client-side Fragment Patching

N/A
N/A
Protected

Academic year: 2022

Partager "Updating SPARQL Results in Real-time with Client-side Fragment Patching"

Copied!
1
0
0

Texte intégral

(1)

Updating SPARQL Results in Real-time with Client-side Fragment Patching

Miel Vander Sande

[email protected]

Ruben Verborgh

[email protected]

Erik Mannens

[email protected]

Rik Van de Walle

[email protected]

Ghent University – iMinds – Multimedia Lab Gaston Crommenlaan 8 bus 201 B-9050 Ledeberg-Ghent, Belgium

ABSTRACT

A lot of Linked Data on the Web is dynamic. Despite the existing query solutions and implementations, crucial unre- solved issues remain. This poster presents a novel approach to updatesparqlresults client-side by exchanging fragment patches. We aim at a sustainable solution which balances the load and reduces bandwidth. Therefore, our approach benefits from reusing unchanged data and minimizing data transfer size. By only working with patches, the load on the server is minimal. Also, the bandwidth usage is low, since only relevant changes are transferred to the client.

The full paper is included in the ACM Proceed- ings of the Research and Innovation Track of the SE- MANTICS2015 Conference (ACM 978-1-4503-3462- 4/15/09, DOI:http://dx.doi.org/10.1145/2814864.2814893).

.

45

Références

Documents relatifs

Design Requirements The requirements for our tool, SPARQL Faceter, are based on our earlier experience on tediously implementing server side faceted search over and over again

Table 1 shows an excerpt of the results of the following SPARQL query on DBpedia, which retrieves films directed by Danny Boyle, along with their music composers and actors, and

In this paper we proposed a novel method to predict potential side-effect profiles of drug candidate molecules based on their chemical structures using sparse canoni- cal

Although these SPARQL endpoints provide an opportunity to utilize the RDF datasets as integrative databases, using SPARQL language often requires cumbersome coding tasks, such as

1 https://code.org/about.. structure of the syntax of SPARQL, while at the same time trying to avoid excessive verbosity that would lead to cognitive overload for the user. Compared

We have defined a materialization and consistency preserving rewriting for SPARQL updates that essentially combines the ideas of [4] and our previous work on SPARQL updates under

This framework, called Lattice Based View Access (LBVA), allows the classi- fication of SPARQL query results into a concept lattice, referred to as a view, for data

OSGi specification releases some advises to use Ser- viceFactory Interface or Indirection mechanism in service object implementation in order to limit, "but not