<!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>Discussion on Uncertainty Ontology for Annotation and Reasoning (a position paper)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>J. Dedek</string-name>
          <email>jan.dedek@mff.cuni.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>A. Eckhardt</string-name>
          <email>alan.eckhardt@mff.cuni.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>L. Galambos</string-name>
          <email>leo.galambos@mff.cuni.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>P. Vojtas</string-name>
          <email>peter.vojtas@mff.cuni.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Charles University in Prague, Department of Software Engineering</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this position paper we discuss the what, who, when, where, why and how of uncertain reasoning based on achievements of URW3XG [2], our experiments and some future plans. What and Why - improving semantic web practice through uncertain reasoning. This vision is described in the URW3XG charter (see [2]), especially the objective is “to identify and describe situations […] for which uncertainty reasoning would significantly increase the potential for extracting useful information; and to identify methodologies that can be applied to these situations and the fundamentals of a standardized representation that could serve as the basis for information exchange necessary for these methodologies to be effectively used.” A crucial point in this is uncertainty annotation of web (extending W3C standards [3]). Who and When - will create, maintain and use this annotation. Will this annotation be done by a human creator using an annotation supporting tool for web page creation? Or will it be done by a third party annotation? For this, we will discuss a refinement of URW3XG use cases. Possible use of this enriched web will be for humans and services. Where - will be this annotations stored. Our proposal is based on the web crawler Egothor repository [4] (we have crawled data in size of several TB from .cz domain) and an additional semantic repository build on the top using data pile technology [5]. How - to semantically enrich information and how to measure success and/or progress of such enrichment. This problem consists of two parts, namely, a data mining task and an ontology modeling task. Third party annotation of great size can be done only in an automated way and it should be done according to an ontology.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Our annotation ontology grows out of URW3XG uncertainty
ontology and extends some features needed for annotation. Below we
show a part of our annotation ontology in Fig. 1. We start here from an
assumption that a part of annotation will be done by a web information
extraction and that this is the main source of uncertainty.</p>
      <p>
        Web information extraction splits pages to dominantly tabular and/or
textual. Uncertainty issues connected with information extraction (and
annotation) from tabular pages were discussed in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Extraction of
textual pages will use techniques described in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Both approaches
(and any other approach) generate a level of (un)certainty they have
about their annotations. Also users, human or agents, can review these
uncertainties and provide feedback about them.
      </p>
      <p>Success of this approach can be measured primarily by the advance
of semantic web functionalities. This is easier to measure for software
agents. More difficult is to design metrics to measure human user
satisfaction. All these aspects will be discussed in this presentation.</p>
      <p>Acknowledgement. This work was partially supported by Czech projects
1ET100300517, 1ET100300419 and MSM-0021620838.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Eckhardt</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horváth</surname>
            <given-names>T.</given-names>
          </string-name>
          , Maruš!ák
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Novotný</surname>
          </string-name>
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Vojtáš</surname>
          </string-name>
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Uncertainty Issues in Automating Process Connecting Web and User, in URSW '07 Uncertainty Reasoning for the Semantic Web</article-title>
          .
          <source>CEUR-WS.org/</source>
          Vol-
          <volume>327</volume>
          /paper9.pdf
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>[2] Uncertainty Reasoning for the World Wide Web W3C Incubator Group Report 31 March</source>
          <year>2008</year>
          , http://www.w3.org/2005/Incubator/urw3/XGR-urw3/
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3] Search at http://www.w3.org/ for Ruby Annotation,
          <string-name>
            <surname>GRDDL</surname>
          </string-name>
          , RDFa
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>[4] Egothor search engine http://www.egothor.org/</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Bednárek</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Obdržálek</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yaghob</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zavoral</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Data Integration Using DataPile Structure</article-title>
          ,
          <source>In: Proceedings of the 9th East-European Conference on Advances in Databases and Information Systems, ADBIS</source>
          <year>2005</year>
          , Tallinn,
          <source>ISBN 9985-59-545-9</source>
          ,
          <year>2005</year>
          ,
          <fpage>178</fpage>
          -
          <lpage>188</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>J. D"</surname>
          </string-name>
          dek, P. Vojtáš.
          <article-title>Linguistic extraction for semantic annotation , accepted for IDC 2008, Catania</article-title>
          , Sicily, to appear
          <source>in the Symposium Proceedings</source>
          ,
          <article-title>which will be published by Springer as a part of their series Studies in Computational Intelligence</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>