<!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>The BAsAS Architecture For Semantic Web Annotations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Valentin Zacharias ontoprise GmbH Amalienabdstr.</string-name>
          <email>zach@ontoprise.de</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>(Raumfabrik</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Karlsruhe</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>GERMANY</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>We describe a generic architecture for the (semi-automatic) creation, storage and querying for annotations of web resources. Our BAsAS architecture uses recent advances from the Semantic Web and Web 2.0 communities to make Semantic Web annotations a reality. The BAsAS architecture makes it easy for users to start to annotate and easy for developer to use the annotations that get created. Besides describing the general architecture we will also detail an implementation of this architecture build for a Semantic Web community portal.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>2. ARCHITECTURE</title>
      <p>The BAsAS architecture is so named for its main
characteristics: Browser, Annotation server, AJAX and SPARQL.
These parts and their interaction are shown in Figure 1. At
the core of the architecture is a Semantic Web data store
that holds the annotations and that offers a SPARQL
interface to access them. It should also offer an HTML interface
for browser based access.</p>
      <p>Annotations are done by the user with the help of an AJAX
interface to an annotation server. This annotation server
helps to keep the client side of the annotation as lighweight
as possible, in particular any complex algorithms for
automatic annotation are run on this server. The annotation
server is also responsible for receiving the information from
the annotation interface and translating it into update
requests for the data store. Only with the help of such a server
component is it possible to build an extrem lightweight
annotation component.</p>
      <p>The annotation component needs some way to establish the
context it is called in for this gives the information on what
the user wants to annotate. This context can be
established by a lighweight browser “plugin”. As we will see this
needs not be an actual browser plugin. A short snippet of
JavaScript that browsers treat like a bookmark is sufficient
in many cases. We will also show that sometimes not even
that is necessary.</p>
    </sec>
    <sec id="sec-2">
      <title>3. UNITRACC COMMUNITY PORTAL</title>
      <p>We are currently implementing the architecture described in
the preceeding chapter for the use in the system unitracc.
Unitracc(“Underground Infrastructure Training and
Competence Center”) is an internet based e-learning system for
the area of canalization. Unitracc also contains a collection
of web based tools that help public authorities manage and
monitor underground infrastructure. The system already
contains a large number of information units, especially
enhanced digital versions of two standard textbooks about
canalization. Unitracc is developed by the company Prof.
Dr. Ing. Stein &amp; Partner GmbH, a leading engineering firm
whose founder is also the author of many standard works
of technical literature. The development has been funded
in part by the German Federal Ministry of Education and
Research. Access to unitracc is available on a subscription
basis, the target audience ranges from beginning trainees
and their teachers to architects.</p>
      <p>We are currently in the process of extending this platform in
the direction of a community portal. In addition to the core
content supplied by the creators of unitracc there should be
an outer layer of user created content, such as comments,
technical manuals uploaded by tool vendors or annotations
of web sites. We expect this layer of content to be less
reliable but also to be more current and diverse. We chose
to build the this part of the platform as open as possible: we
believe that the openness increases the motivation of people
to contribute. We hope that people will be less reluctant to
put effort into a commercial site when they know that this
content can be used by everyone.</p>
    </sec>
    <sec id="sec-3">
      <title>3.1 Annotation</title>
      <p>Users of the site will be encouraged to annotate the web
resources relavant to unitracc using a simple annotation tool.
For the time beeing we have settled on a very simple
annotation format: the annotation is always for the whole web
page and it only consists of “has topic” relations to the
topics from the unitracc topic hierarchy. The integration of
the annotation tool with the browser is done with a
bookmarklet. The annotation interface is realized with AJAX,
it supports the user mainly by offering auto complete for
the topics. It also receives the proposals from the automatic
categorization performed by the annotation servlet and
displays them to the user. A screenshot of the annotation
interface is shown in Figure 2. The topic hierarchy that forms
that basis for the annotations can also be edited using an
AJAX interface. This interface also allows many people to
change the topic hierarchy simultanously. Changes to the
topic hierarchy are currently meant to be done only by the
administrators of unitracc.</p>
      <p>The annotation interface, like the topic hierarchy editor, is
created using the Google Web Toolkit[1].</p>
    </sec>
    <sec id="sec-4">
      <title>4. ACKNOWLEDGMENTS</title>
      <p>This work was supported in part by the German Federal
Minsitry of Education and Resarch under the ksi
underground project.
5. REFERENCES
[1] Google web toolkit,</p>
      <p>http://code.google.com/webtoolkit/.
[2] J. Kahan and M.-R. Koivunen. Annotea: an open rdf
infrastructure for shared web annotations. In WWW,
pages 623–632, 2001.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [3]
          <string-name>
            <surname>M.-R. Koivunena</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Swick</surname>
            , and
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Prud</surname>
          </string-name>
          <article-title>'hommeaux. Annotea shared bookmarks</article-title>
          .
          <source>In Proceedings of the KCAP03 workshop</source>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>