<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">The BAsAS Architecture For Semantic Web Annotations</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<affiliation key="aff0">
								<orgName type="institution">Valentin Zacharias ontoprise GmbH</orgName>
								<address>
									<addrLine>Amalienabdstr. 36 (Raumfabrik 29</addrLine>
									<postCode>76227</postCode>
									<settlement>Karlsruhe</settlement>
									<country key="DE">GERMANY</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">The BAsAS Architecture For Semantic Web Annotations</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">D0BF699878857107F2173CA259D1F3D4</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T16:23+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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.</p><p>Besides describing the general architecture we will also detail an implementation of this architecture build for a Semantic Web community portal.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">INTRODUCTION</head><p>The Semantic Web is the vision of having data on the web defined and linked in such a way, that it can be used by machines not just for display purposes, but for integration, automation and reuse of data across various applications. An Annotation is a piece of information or knowledge entity that is associated with a document or part therof. In this paper we focus on Semantic Web Annotation, understood as annotations of web resources with the goal of lifting them into the semantic web. Unstructured content outside of the semantic web is annotated and these annotations become part of the Semantic Web. In this way (a part of) the content of the document becomes part of the Semantic Web, the document gets woven into the Semantic Web. Research that understands Semantic Web Annotations in this way must discuss the question of how the data created in the annotation process becomes part of the Semantic Web, how it is retrievable and usable for computer agents.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1">Contribution</head><p>What we are trying to do is similar to the Annotea <ref type="bibr" target="#b2">[2]</ref>[3] infrastructure: define an architecture that can form the backbone for Semantic Web annotations. We, however, improve * A full version of this paper is available at www.valentin-zacharias.de/papers/BAsAS.pdf on the well known Annotea idea in three crucial points: we show how the SPARQL language solves the problem of queries for annotations. We demonstrate how AJAX can be employed to build an annotation tool that is more lightweight and less browser dependent than anything that exists for Annotea. Finally we show a simple architecture that allows semi-automatic annotation while still retaining the extrem lighweight property of the annotation tools. To a large part this paper can be understood as an attempt to update the ideas pioneered by annotea using technology that was not available at the time it was initially conceived.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">ARCHITECTURE</head><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 <ref type="figure" target="#fig_0">1</ref>. 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. 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. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">UNITRACC COMMUNITY PORTAL</head><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 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Annotation</head><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 <ref type="figure" target="#fig_1">2</ref>. 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 The annotation interface, like the topic hierarchy editor, is created using the Google Web Toolkit <ref type="bibr" target="#b1">[1]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">ACKNOWLEDGMENTS</head></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: High level view of the BAsAS architecture</figDesc><graphic coords="2,179.33,53.80,251.05,187.87" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: The unitracc annotation interface</figDesc><graphic coords="2,361.05,282.27,150.64,160.48" type="bitmap" /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This work was supported in part by the German Federal Minsitry of Education and Resarch under the ksi underground project.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title/>
		<author>
			<persName><surname>References</surname></persName>
		</author>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<ptr target="http://code.google.com/webtoolkit/" />
		<title level="m">Google web toolkit</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Annotea: an open rdf infrastructure for shared web annotations</title>
		<author>
			<persName><forename type="first">J</forename><surname>Kahan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M.-R</forename><surname>Koivunen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WWW</title>
				<imprint>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page" from="623" to="632" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Annotea shared bookmarks</title>
		<author>
			<persName><forename type="first">M.-R</forename><surname>Koivunena</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Swick</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Prud</surname></persName>
		</author>
		<author>
			<persName><surname>Hommeaux</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the KCAP03 workshop</title>
				<meeting>the KCAP03 workshop</meeting>
		<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
