<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <article-id pub-id-type="doi">10.1145/2814864.2814893</article-id>
      <title-group>
        <article-title>Updating SPARQL Results in Real-time with Client-side Fragment Patching</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ruben Verborgh ruben.verborgh@ugent.be</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rik Van de Walle rik.vandewalle@ugent.be</string-name>
          <email>erik.mannens@ugent.be</email>
          <email>miel.vandersande@ugent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Erik Mannens</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Ghent University - iMinds - Multimedia Lab Gaston Crommenlaan 8 bus 201 B-9050 Ledeberg-Ghent</institution>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Miel Vander Sande</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>A lot of Linked Data on the Web is dynamic. Despite the existing query solutions and implementations, crucial unresolved issues remain. This poster presents a novel approach to update sparql results client-side by exchanging fragment patches. We aim at a sustainable solution which balances the load and reduces bandwidth. Therefore, our approach bene ts 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.</p>
      </abstract>
    </article-meta>
  </front>
  <body />
  <back>
    <ref-list />
  </back>
</article>