<!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>Towards Trust for Semantic Web Annotations</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>General Terms Design</institution>
          ,
          <addr-line>Security, Human Factors</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Wolfgang Woerndl TU Muenchen Boltzmannstr.</institution>
          <addr-line>3 85748 Garching</addr-line>
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In the Semantic Web, users can attach (semantic) meta data to Web resources. One problem is the trustworthiness of these annotations. This paper identifies two main steps towards a Semantic Web trust framework and provides possible solutions. The first step is to authenticate users and annotations. This is done in our approach by introducing Liberty Alliance identity management into Semantic Web annotations. Users have to login using Liberty Alliance accounts to create or modify annotations and their credentials are stored with the annotations. The author of an annotation can also define optional access rights to her annotations, for example to restrict access to the participants of a lecture course. We present our implementation which is an extension of the Annozilla plugin for the Mozilla Web browser. One advantage of using the Liberty Alliance specification for authentication is possible interoperability with other Web applications. Users can thereby reuse accounts for different services under their control (identity management). The second step is a framework for expressing trust in a (Web) resource. Users can rate resources (or other trust ratings) using a trust ontology. The rating is always done with regard to a distinct facet or aspect. For example, a user can express high trust in the w3c.org Web site regarding the aspect “Web technology”. Our trust ontology also integrates (optional) references to domainspecific text representations of trust values.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;trust</kwd>
        <kwd>identity management</kwd>
        <kwd>annotation</kwd>
        <kwd>annotea</kwd>
        <kwd>liberty alliance</kwd>
        <kwd>authentication</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Categories and Subject Descriptors</title>
      <p>H.5.3 [Group and Organization Interfaces] and K.6.5 [Security
and Protection] - Authentication
Permission to make digital or hard copies of all or part of this work for
personal or classroom use is granted without fee provided that copies are
not made or distributed for profit or commercial advantage and that
copies bear this notice and the full citation on the first page. To copy
otherwise, or republish, to post on servers or to redistribute to lists,
requires prior specific permission and/or a fee.</p>
      <p>Conference’04, Month 1–2, 2004, City, State, Country.</p>
      <p>Copyright 2004 ACM 1-58113-000-0/00/0004…$5.00.</p>
    </sec>
    <sec id="sec-2">
      <title>1. INTRODUCTION</title>
      <p>In the Semantic Web, users can attach (semantic) meta data to
Web resources. These annotations can then be displayed to other
users or used by computer programs to improve the understanding
of content. For example, in an E-Learning scenario, users could
annotate (Web) resources with meta data such as “difficult” or
“important”, or rate resources with regard to a certain topic or
course.</p>
      <p>One problem is the trustworthiness of annotations. In the
traditional WWW, users have to manually decide whether a Web
page is trustworthy or not. For example, an annotation by the
lecturer of a course would constitute high trust to her students. In
a Semantic Web, we need a framework for representing trust in
Web resources which can be used by programs to enhance search
results or information personalization, for example.</p>
      <p>
        Annotea provides a standardized framework for the creation and
management of annotations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Usually, Web server functionality
provides user authentication for annotations. Often, the standard
HTTP authentication mechanism is used. In this case, users have
to provide credentials to access annotations but the identity
information is not associated with the annotation itself. Existing
approaches for secure authentication in open networks, such as
the Liberty Alliance project, are not integrated into annotation
infrastructures.
      </p>
      <p>In this paper, we identity two main steps towards a trust
framework for (Semantic Web) annotations. First of all, we want
to motivate the goal of our research by explaining an example
scenario in section 2. In section 3, we describe how to
authenticate users applying the Liberty Alliance standard for
distributed and federated identity management (section 3). In
section 4, we then explain the expression of trust in resources
using a trust ontology. The paper finishes with a short discussion
of related work and conclusion.</p>
    </sec>
    <sec id="sec-3">
      <title>2. MOTIVATION AND REQUIREMENTS</title>
      <p>Consider an E-Learning scenario, where a lecturer provides
content in form of various Web pages. Users (e.g. lecturer,
students, anonymous guests) could annotate and rate these
ELearning Web resources. For example, a user wants to annotate a
Web page (or part of it) as “difficult” or “important” (using a
Semantic Web ontology, for instance), or express her trust in the
Web page. These annotations could then be used to adapt content
to a learner’s needs or preferences, or used by other users to
evaluate resources. If annotations are written by the lecturer of the
course, students certainly would have higher confidence in the
reliability of the information.</p>
      <p>Students can also make annotations but other users might find all
information as completely trustworthy. In this case, it is useful to
be able to express trust not only in resources such as Web pages
but also in other annotations itself. If a student annotation is rated
as trustworthy by several other users, this would constitute a
higher level of trust.</p>
      <p>Furthermore, when annotations are linked to user accounts, users
might want to control access to their annotations. For example, a
lecturer might want to restrict access to some annotations to the
registered students of her course.</p>
      <p>Requirements for trust for Semantic Web annotations can be
summarized as follows:</p>
      <p>Securely authenticating users who want to create or
manage annotations
Associating identity information with annotations so
that other users can be certain who created an
annotation</p>
      <sec id="sec-3-1">
        <title>Providing means to control access to annotations</title>
        <p>Rating resources using trust expressions in annotations</p>
      </sec>
      <sec id="sec-3-2">
        <title>Expressing trust or distrust in other ratings</title>
        <p>Using the existing protocols such as Annotea and
Liberty Alliance without much modification, if possible
These requirements roughly fall into these two categories:
1.Identity management: mechanism for securely authenticating
users without necessarily relinquishing privacy considerations
2.Trust framework: an ontology and a framework for trust
expressions and rating of resources
In the following two sections we will outline our ideas for a
solution regarding these requirements.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>3. INTRODUCING LIBERTY ALLIANCE</title>
    </sec>
    <sec id="sec-5">
      <title>IDENTITY MANAGEMENT INTO</title>
    </sec>
    <sec id="sec-6">
      <title>ANNOTATIONS</title>
      <p>Our approach for identity management and user authentication is
to use the standards of the Liberty Alliance project.</p>
    </sec>
    <sec id="sec-7">
      <title>3.1 The Liberty Alliance Project</title>
      <p>
        The Liberty Alliance project is an initiative by more than 150
companies and organization to provide standards for secure Web
authentication (www.projectliberty.org). The Liberty Alliance
specification offers a scheme to single sign on, authentication and
controlled sharing of user identities among services. It uses the
standard Security Assertion Markup Language (SAML)
(xml.coverpages.org/saml.html) for the secure exchange of
authentication information [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Liberty Alliance distinguishes
three entities:
principal: user, whose identity has to be verified
service provider: the actual service the user wants to
access (e.g. the annotation service)
identity provider: a service that manages user accounts
and authenticates users
A certain degree of anonymity remains: users do not
have to provide information about their real identity, but
can use a pseudonym. On the other hand, when several
annotations can be securely linked to one pseudonym, a
sense of trust can be achieved nevertheless
In the Liberty Alliance framework, users can manage different
accounts and link them under their own control. In addition,
Liberty Alliance features other privacy mechanisms, for examples
regarding user consent [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
    </sec>
    <sec id="sec-8">
      <title>3.2 Liberty Alliance and Annotea</title>
      <p>The integration of Liberty Alliance identity management in
Annotea in our approach can be outlined according to the
following procedure:
In the Liberty Alliance approach, identity providers take care of
the authentication of users, not the service providers. Advantages
of using Liberty Alliance for Semantic Web annotations are as
follows:
(www.sourceid.org). We also use SourceID to provide the identity
provider system.</p>
    </sec>
    <sec id="sec-9">
      <title>3.3 User Interface</title>
      <p>Fig. 1 displays our user interface for creating an annotation. In the
top part, the user can enter the text of her annotation. Then she
has to select an annotation service. Depending on the service, one
or more identity providers are available. In step 3 the user can
select one identity provider and login using a Liberty Alliance
account (as explained above). When creating several annotations
within one session, the user has to login only once. Note that
users cannot fill in a “author“ field, because the author
information is provided through the Liberty Alliance account. In
step 4, the user can choose from several (facultative) options. She
can select a type of the annotation, the language and a privacy
attribute for the annotation.
The privacy option is used to define access rights to the
annotations. Because users might not want to specify detailed
access rights themselves, profiles with predefined options can be
provided in our framework. A simple profile might include the
following options:
public: (read) access for everybody
private: read access only for the author of the annotation
anonymous: everybody can read the content of the
annotation, but the author information is not shown
The third option is interesting, because users have to login to
create annotations in our framework and cannot make anonymous
annotations by omitting author information or entering fake data.</p>
    </sec>
    <sec id="sec-10">
      <title>4. EXPRESSING TRUST IN WEB</title>
    </sec>
    <sec id="sec-11">
      <title>RESOURCES</title>
    </sec>
    <sec id="sec-12">
      <title>4.1 Overview</title>
      <p>In chapter 3, we explained how to integrate identity management
into Semantic Web annotations to securely authenticating users.
The second part now is to provide a framework for expressing
trust in Web resources. The idea is that users can rate Web
resources. Rating thereby means assigning a trust value to a
resource. These ratings (or trust statements) are stored and
managed using the Annotea protocol. Our approach is not only
designed to rate Web resources but also other trust expressions
themselves.</p>
      <p>All trust statements are made with regard to a distinct facet or
aspect. For example, a user might find the Web site of the World
Wide Web Consortium trustworthy regarding “Web technology”.
Since users have to login (as explained in section 3) to create trust
statements, the ratings are associated with the user identity. Other
examples for aspects are “design” or “function” when rating a
product.</p>
    </sec>
    <sec id="sec-13">
      <title>4.2 Trust Ontology</title>
      <p>
        The core of the approach is a trust ontology that formalizes the
mentioned trust statements. Fig. 2 shows an example of an
instance of the ontology.
&lt;rdf:RDF
... namespace definitions omitted ..&gt;
&lt;tr:TrustStatement
rdf:about="http://annotest.w3.org/annotations/anno
tation/5930134703.359235"
a:context="http://www.dgk.org/#xpointer(/html[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ])"
a:created="2005-10-19T10:10:00"&gt;
&lt;dc:creator&gt;Werner Jansen&lt;/dc:creator&gt;
&lt;dc:date&gt;2005-10-19T10:10:00&lt;/dc:date&gt;
&lt;a:annotates rdf:resource="http://www.dgk.org/"/&gt;
&lt;tr:trustRegarding&gt;cardiology&lt;/tr:trustRegarding&gt;
&lt;tr:trustValue&gt;1.0&lt;/tr:trustValue&gt;
&lt;tr:trustOntology
rdf:resource="http://www11.in.tum.de/sw/trust/trus
tOnt#"/&gt;
&lt;tr:trustRepresentation
rdf:resource="http:www11.in.tum.de/sw/trust/trustO
nt#AbsoluteTrust"/&gt;
&lt;/tr:TrustStatement&gt;
&lt;/rdf:RDF&gt;
The ontology consists of trust statements, with the following parts
(tags highlighted in bold in Fig. 2):
trustRegarding: this is the facet on which the trust
statement is based on
trustValue: a numerical value ranging from -1.0
(absolute distrust) to 1.0 (complete trust). 0 is neutral,
i.e. “don’t know whether resource is trustworthy or not”
(optional) trustOntology: reference to domain-specific
ontology that explains the meaning of trustValues in
natural language
(optional) trustRepresentation: a specific trust value in
the trustOntology
The trustOntology and trustRepresentation can be used to specify
what a certain trust value really means in a given domain. This
information can then be used to adapt the user interface. In this
case, different values of trustRepresentation can be defined in the
trustOntology, in different languages, and shown to the user when
displaying annotations.
      </p>
      <p>As an example in the E-Learning scenario from section 2,
trustRegarding might be “relevance for exam”, the trustOntology
could be various degrees of relevance, such as “very relevant” or
“not really relevant, but might help”. The lecturer can then
annotate material with trust statements, and, since the identity of
users is securely authenticated, students can take these
annotations for granted. On the other hand, students can create
annotations themselves which might then be rated by other
students.</p>
      <p>
        The trust statements are integrated into Annotea using a distinct
annotation type. Annotea uses sub classes of a class “Annotation”
to describe the type of an annotation [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], for example “Comment”
or “See Also”. The idea is to define a new annotation type “Trust”
to represent the trust statements. These statements can then be
displayed to users like normal Annotea annotations, or used to
personalize information access. For example, important
ELearning material can be highlighted or Web searches of
annotated pages could be ranked according to available trust
statements.
      </p>
    </sec>
    <sec id="sec-14">
      <title>4.3 Related Work</title>
      <p>
        A lot of work is done in the field of trust for the Semantic Web.
An overview gives the (slightly outdated) Semantic Web
Trust and Security Resource Guide:
www.wiwiss.fuberlin.de/suhl/bizer/SWTSGuide/
Our trust ontology is similar to the one used by Golbeck, Parsia
and Hendler in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This approach uses FOAF (friend-of-a-friend,
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]) to identify users and built social networks. One extension is
the reference to an external, domain-specific trust ontology in our
model.
      </p>
      <p>
        C.Görn recently proposed an ontology for trust models [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The
ontology includes attributes for start and end dates of trust
statements. The approach – and some other trust formalizations,
including [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] – is more geared towards expressing trust in
persons, not Web pages or annotations.
      </p>
    </sec>
    <sec id="sec-15">
      <title>5. CONCLUSION</title>
      <p>In this paper, we have presented an approach to improve trust for
(Semantic Web) annotations. First, we have applied Liberty
Alliance identity management to authenticate users. Then, we
have shown how users can make trust expression by using a trust
ontology.</p>
      <p>The rating of Web resources is already done by online shops such
as amazon.com, for example. With a general Web trust
framework, users could rate products or other resources across
different sites. Such an approach would be susceptible to spam or
fake ratings. In this case, secure authentication of users is
especially important. This raises privacy issues. One solution is to
disallow anonymous annotations but optionally leaving out author
information when displaying annotations. In our framework, this
is possible by associating access rights to annotations. Trust
ratings could also be used to compute similarities between users
and recommend item based on this user similarity (collaborative
filtering). Thereby, the explicit representation of distrust in our
model is beneficial.</p>
      <p>An idea for improvement in our approach is the introduction of
aging of trust annotations. Old ratings might constitute a lesser
meaning than new ratings. Another (related) problem is how to
handle changes in Web resources. If a Web page is modified, the
associated trust statements have to be modified as well. Future
work also includes the refinement of our implementation, which
include the integration in current Annozilla versions, and the
application and evaluation of the approach in the E-Learning
scenario.</p>
    </sec>
    <sec id="sec-16">
      <title>6. ACKNOWLEDGMENTS</title>
      <p>The author would like to thank his diploma/master students
Markus Geiger and Werner Jansen, who worked out the details
and designed and partly implemented the two parts of the system,
and also Manuel Giuliani, who worked on the demo application.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Kahan</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koivunen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prud'Hommeaux</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Swick</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Annotea</surname>
          </string-name>
          :
          <article-title>An Open RDF Infrastructure for Shared Web Annotations</article-title>
          .
          <source>In Proc. of the WWW10 International Conference</source>
          , Hong Kong, May
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Liberty</given-names>
            <surname>Alliance Project Whitepaper</surname>
          </string-name>
          : Personal Identity. http://www.projectliberty.org/resources/whitepapers/Persona l_Identity.pdf,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Watson</surname>
            ,
            <given-names>T</given-names>
          </string-name>
          . (ed.)
          <article-title>Liberty ID-FF Architecture Overview</article-title>
          . http://www.projectliberty.org/specs/draft-liberty
          <article-title>-idff-archoverview-1.2-errata-v1.0</article-title>
          .pdf
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Golbeck</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Trust networks on the semantic web</article-title>
          .
          <source>In Proceedings of Cooperative Intelligent Agents (CIA)</source>
          , Helsinki, Finland,
          <year>2003</year>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Dumbill</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>XML Watch: Finding friends with XML and RDF</article-title>
          . IBM Developer Works, http://www106.ibm.com/developerworks/xml/library/xfoaf, 2002
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Görn</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>An extended Ontology for Trust Models</article-title>
          . http://b4mad.net/
          <year>2006</year>
          /01/10/trust.html
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>