<!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>
      <title-group>
        <article-title>COOL-WD: A Completeness Tool for Wikidata</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fariz Darari</string-name>
          <email>fariz@cs.ui.ac.id</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Radityo Eko Prasojo</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Simon Razniewski</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Werner Nutt</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Computer Science</institution>
          ,
          <addr-line>Universitas Indonesia, Depok</addr-line>
          ,
          <country country="ID">Indonesia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>KRDB, Free University of Bozen-Bolzano</institution>
          ,
          <addr-line>39100</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Wikidata as a collaborative Semantic Web data source has enjoyed increasing prominence, storing over 150 million facts about more than 26 million entities. Yet it is missing a way to assess its completeness. In this demo we present COOL-WD, a tool for supporting the completeness lifecycle of Wikidata, that is, the creation, view, update, and consumption of metadata about Wikidata completeness. COOL-WD is available at http://cool-wd.inf.unibz.it/ and has so far collected more than 10,000 completeness statements.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Completeness Lifecycle. When
talking about completeness statements of
RDF data sources, we conceive that
the statements go through a lifecycle
consisting of four phases as shown in
Fig. 1:</p>
      <p>1. Creation: Completeness
statements about RDF data sources are
created, where provenance (e.g.,
author, reference, timestamp) of the
statements can also be added.</p>
      <p>2. View : Completeness statements
(and their provenance), as well as
parts of data captured by the statements, are available for viewing.
3. Update: Completeness statements can be updated (i.e., edited or deleted),
if, for example, they are no longer valid or incorrectly given.</p>
      <p>4. Consumption: Various consumption tasks such as query completeness
checking and completeness analytics are performed.</p>
      <p>The stages are collectively referred to as cycle because the consumption stage
might reveal (in-)completeness problems of the data source, thus triggering the
further creation of completeness statements.</p>
      <p>Outcome. The intended outcome of the demo session is three-fold, that
visitors shall become aware of: (i) how natural completeness information is for KBs
(e.g., Wikidata); (ii) how the completeness lifecycle models a process of
creating, viewing, updating, and consuming completeness information; and (iii) how
COOL-WD realizes support for the completeness lifecycle of Wikidata.</p>
      <p>
        While the present demonstration focuses on Wikidata, the need for expressing
and storing completeness information is not limited to this KB. Our goal is to
increase awareness of the completeness issue on the Semantic Web, and the need
for considering it in the design of future methodologies, standards, and KBs.
Related Work. Data completeness relates to the breadth, depth, and scope of
information in the data [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Techniques to measure completeness of RDF data
sources, as surveyed by Zaveri et al. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], are commonly done via comparison with
the gold-standard data source. The surveyed techniques did not concern how to
express that a source is of gold-standard completeness quality. Formal approaches
that deal with the representation and reasoning of completeness statements have
been proposed both for relational DBs [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and RDF KBs [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Such approaches,
however, lack a practical methodology of working with completeness statements.
Recoin [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], a relative completeness tool for Wikidata, looks at the extent of
information about Wikidata entities as a whole, for instance, whether or not
information about Donald Trump is more abundant than about other, similar
entities.
COOL-WD is a completeness tool for Wikidata, enabling collaborative
annotations of complete parts of Wikidata. COOL-WD maintains real time
communication with Wikidata, and is implemented as client-server architecture. Two
in-sync clients are available: the COOL-WD Web interface, and direct editing
from wikidata.org. The direct editing script can be activated by adding the line
importScript( `User:Fadirra/coolwd.js' ); to the Wikidata user's common.js
le. The server side is responsible for controlling the application logic and
storing completeness information. The UI is developed using GWT.3 The server is
Apache Tomcat-based, and the completeness DB relies on PostgreSQL.
      </p>
      <p>COOL-WD is in active use by the Wikidata community and contains so far
around 10,000 completeness statements, available for bulk download at http:
//completeness.inf.unibz.it/rdf-export/.
3</p>
    </sec>
    <sec id="sec-2">
      <title>Demonstration Experience</title>
      <p>On the Wikidata page of Austria4, the user is left clueless whether all the
states of Austria are present. Moreover, it is unknown which of the states
are already complete for their districts, hindering where to put focus on
data collection about Austria.
1. Creation. By comparing information in Wikidata with the o cial website of
Austria,5 users can observe that Wikidata is complete for the states. Thus the
user can add the corresponding completeness statement, as well as the reference
URL. Using the direct editing, the adding is as simple as clicking the
respective property to the Wikidata page about Austria. The Wikidata username and
timestamp are added accordingly.
2. View. As illustrated in Fig. 2 (a), the user can view completeness statements
about Austria, as well as the provenance, by clicking the \(i)" icon.
Greenhiglighted properties indicate completeness, while yellow indicates unknown. For
instance, the user can see that the completeness of short names is unknown.
We also provide a Linked Data API for COOL-WD completeness statements.
For example, the dereferenceable URI for the statement (Q40,P150) as above
is http://cool-wd.inf.unibz.it/resource/statement-Q40-P150. There, the user
can view an RDF description of the completeness statement, modeled using our
completeness vocabulary (http://completeness.inf.unibz.it/sp-vocab) and the
W3C PROV vocabulary (http://www.w3.org/ns/prov).
3. Update. The user may notice a completeness statement for \diplomatic
relation", which is not valid anymore, as Austria in the meantime has also
established diplomatic relations with Kyrgyzstan6. The user can therefore remove the
3 http://www.gwtproject.org/
4 https://www.wikidata.org/wiki/Q40
5 https://www.parlament.gv.at/ENGL/PERK/BOE/
6 https://www.embassypages.com/missions/embassy11893
statement simply by clicking the green box. To update the URL of an existing
statement, the user can edit the reference eld after clicking \(i)".
4. Consumption. So far, COOL-WD supports three consumption tasks: data
completeness tracking, completeness analytics, and query completeness
diagnostics. The tracking shows the progress of completing the data of a single entity in
terms of the fraction of the (known) non-functional properties that are complete.
The completeness analytics summarizes in a tabular view the completeness of a
class of entities. For example, for the class of Austrian states, the user might be
interested in the completeness percentage of their districts and borders (i.e., how
complete is the class for these properties?). The percentage is computed based on
whether completeness statements exist or not for the properties of interest wrt.
all entities of the class. Finally, query completeness diagnostics enables the
completeness assessment of SPARQL basic graph pattern queries (as in Fig. 2 (b)).
Additionally, statements used to guarantee query completeness can be shown.
Acknowledgements This work was partially funded by the Free University of
Bolzano under the TaDaQua project.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>A.</given-names>
            <surname>Ahmeti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          .
          <article-title>Assessing the completeness of entities in knowledge bases</article-title>
          .
          <source>In ESWC Posters &amp; Demos</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>F.</given-names>
            <surname>Darari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Nutt</surname>
          </string-name>
          , G. Pirro, and
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          .
          <article-title>Completeness statements about RDF data sources and their use for query answering</article-title>
          .
          <source>In ISWC</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          and
          <string-name>
            <given-names>W.</given-names>
            <surname>Nutt</surname>
          </string-name>
          .
          <article-title>Completeness of queries over incomplete databases</article-title>
          .
          <source>PVLDB</source>
          ,
          <volume>4</volume>
          (
          <issue>11</issue>
          ):
          <volume>749</volume>
          {
          <fpage>760</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>R. Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          and
          <string-name>
            <given-names>D. M.</given-names>
            <surname>Strong</surname>
          </string-name>
          .
          <article-title>Beyond accuracy: What data quality means to data consumers</article-title>
          .
          <source>J. of Management Information Systems</source>
          ,
          <volume>12</volume>
          (
          <issue>4</issue>
          ):5{
          <fpage>33</fpage>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>A.</given-names>
            <surname>Zaveri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rula</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maurino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pietrobon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          .
          <article-title>Quality assessment for Linked Data: A survey</article-title>
          .
          <source>Semantic Web</source>
          ,
          <volume>7</volume>
          (
          <issue>1</issue>
          ):
          <volume>63</volume>
          {
          <fpage>93</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>