<?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">SASA-a Semi-Automatic Semantic Annotator for Personal Knowledge Management</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Kim</forename><surname>Tighe</surname></persName>
							<email>ktighe@hp.com</email>
							<affiliation key="aff0">
								<orgName type="department">Semantic Infrastructure Research Group</orgName>
								<orgName type="institution">Hewlett-Packard</orgName>
								<address>
									<settlement>Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sean</forename><surname>O'riain</surname></persName>
							<email>sean.oriain@hp.com</email>
							<affiliation key="aff0">
								<orgName type="department">Semantic Infrastructure Research Group</orgName>
								<orgName type="institution">Hewlett-Packard</orgName>
								<address>
									<settlement>Galway</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">SASA-a Semi-Automatic Semantic Annotator for Personal Knowledge Management</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">F87FD3855715E903428A104ABBBD466E</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>
			<textClass>
				<keywords>
					<term>I.I.7 [Computing Methodologies]: Document and Text Processing -General. J.0 [Computer Applications]: General Management</term>
					<term>Economics</term>
					<term>Experimentation Semantic Annotation</term>
					<term>Personal Knowledge Management</term>
					<term>PDF</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Best practice organisations have realised that people and their knowledge remain their greatest assets and will continue to be the largest contributory factor in obtaining future competitive advantage. Knowledge fundamentally derived from people in the absence of their understanding, personal context and application remains largely as obscure information. Current personal knowledge management (PKM) activities do not adequately support the finding, reminding, reuse and collaboration of information. In this paper we propose a novel PKM tool called SASA, a semi-automatic semantic annotator of PDF documents, which will enable collecting, connecting and collaborating of discovered information to facilitate knowledge sharing and personal content management within a business setting. SASA, a plug-in for Adobe Acrobat Professional, utilises Semantic Web technologies to enable building, augmenting and sharing of ontologies amongst knowledge workers. Within an ontology named entities are connected to additional information such as Web pages, documents, mail messages, personal notes, and wikis. SASA automatically derives the context of the document, highlights named entities and applies the relevant additional information. The business case for such a tool is outlined and user scenario development used to illustrate how SASA will assist Business Client Account Managers in the laborious process of reviewing, annotating and gathering information from customer documentation by enhancing their PKM.</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>In a rapidly changing global economy unified by improved communication and transportation, people and their knowledge are an organisation's greatest assets <ref type="bibr" target="#b0">[1]</ref>. The constant emergence of new products and competitors combined with an increasing global marketplace are challenges facing an organisation's ability to survive in an increasingly unpredictable and competitive environment. An enterprise's continued existence will increasingly depend upon their ability to becoming a knowledgerich knowledge managing organisation <ref type="bibr" target="#b1">[2]</ref>. Organisations that focus solely on the application of their collective intellectual capital to achieve objectives run the risk of neglecting the fundamental truth that knowledge is derived from people <ref type="bibr" target="#b2">[3]</ref>. Lacking the human element of understanding, personal context and application, knowledge within an organisation remains largely as obscure information. Supporting individuals in their PKM is therefore vital and will be the single largest contributory factor in gaining future competitive advantage over the next 25 years <ref type="bibr" target="#b3">[4]</ref>.</p><p>Enabling technologies for the WWW have provided knowledge workers with rich information sources but have also resulted in adding to the existing considerable volume of information that can be searched and queried. The classical Information Retrieval (IR) problem of identification and retrieval of current information for activities such as informed decision making remains problematic. The core focus of PKM is directed at improving individual efficiency. Current activities however remain limited lacking adequate support for the finding, reminding, reuse and collaboration of information <ref type="bibr" target="#b4">[5]</ref>. There remains a growing need for intuitive processes and PKM based tools to assist the worker in evaluating not only their own knowledge but also a means to augment it by exploration and learning from additional information sources. Maximising human capital on a personal level leads to enhancing individual effectiveness in a manner that improves productivity for both the individual and enterprise <ref type="bibr" target="#b5">[6]</ref>. It is our contention that PKM enhanced with Semantic Web technologies can be used to assist in achieving this productivity gain.</p><p>The Semantic Web <ref type="bibr" target="#b6">[7]</ref> envisages annotating document content by assigning to entites in the text links to their semantic descriptions from domain ontologies to make it easier for machines to assist humans in finding, sharing, combining, and reusing information. Current semantic annotation tools (e.g. KIM <ref type="bibr" target="#b7">[8]</ref>, Trailblazer <ref type="bibr" target="#b15">[16]</ref> <ref type="foot" target="#foot_0">1</ref> and tools based on Annotea<ref type="foot" target="#foot_1">2</ref> or CREAM <ref type="bibr" target="#b8">[9]</ref>) cater for document annotation of Web-native formats such as HTML and XML. None however cater for the Portable Document Format (PDF <ref type="bibr" target="#b9">[10]</ref> <ref type="foot" target="#foot_2">3</ref> ), a format prevalent in virtually all market segments and used extensively for document interchange and publishing.</p><p>With the advent of the Semantic Web this paper examines how Semantic Web enabling technologies, namely semantic annotation can be applied to the area of PKM to enhance knowledge worker productivity and efficiency. This paper proposes a novel tool, SASA for semi-automatic semantic annotation of PDF documents, which will enable collecting, connecting and collaborating amongst knowledge workers to facilitate knowledge sharing and personal content management within a business setting.</p><p>The remainder of this paper is structured as follows: Section 2 outlines the business case. Section 3 illustrates the scenario development. Section 4 presents our proposed solution. Section 5 compares related work. Section 6 concludes this paper and outlines future work.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">BUSINESS CASE</head><p>HP 4 Services' Managed Services (MS) provides customers 5 with strategic outsourcing services and solutions to manage their IT infrastructures. The MS business unit itself is structured into a number of areas of expertise known as towers. Each tower specializes in a particular area such as the End User Workplace Management (EUWM) which focuses on the end users desktop environment. The EUWM Pre-Sales &amp; Implementation Team is assigned Customer Relationship Management and Project Management activities during the pre-sales and transition/transformation stages of any customer engagement.</p><p>In each of the above activities, the EUWM consultant's task of understanding, interpreting and producing all relevant support documentation is crucial for the successful proposal, implementation and delivery of any service. Failing to adequately capture all customer requirements, service limitations and any assumptions made will impact customer satisfaction level, the delivery organisations ability to succeed, HP's profitability, and ultimately, HP's ability to win further contracts. Underpinning all activities is the consultant whom has to ensure that services scoped in the solution are delivered efficiently and implemented in adherence to contractual obligations. For that reason, their resulted outputs from reviewing customer documentation such as Project Definition Document or Project Requirements Document are essential for the project to initially commence and to continue on-going successfully.</p><p>New EUWM customer undertaking will require the consultant to begin the laborious process of reviewing, annotating and gathering information from on average 50 or more substantial documents which typically are received in either Microsoft Word or Adobe PDF format. At present, each document is manually reviewed and annotated by the consultant. Central document repository systems such as SharePoint 6 are occasionally used for information sharing in addition to documentation notes capture in an associated mail or Word documents. However, it is not a standard practice and can lead to problems of omitting key 4 Hewlett-Packard Ltd. <ref type="bibr" target="#b4">5</ref> Telecom/NSP, financial services, manufacturing and government or public sector markets. 6 SharePoint is Microsoft collaborative management tool for document and information sharing.</p><p>comments that are difficult to identify and retrieve particularly for new document versions. Increasing the customer base, scope expansion, EUWM organisational expansion and having to comply with standards such as ISO <ref type="foot" target="#foot_3">7</ref> frameworks has led to a considerable increase in documentation volume and the level of manual effort required.</p><p>There is a clear opportunity for an intuitive tool that would assist the consultants in performing documentation review and in information gathering process in order to improve both collaboration and traceability of document findings. Currently under active development SASA is such a tool that offers the semi-automatic semantic annotation of PDF documents. Its usage will contribute towards a reduction in the level of effort required in each new project stage, cost reduction and increased team productivity. The assigned account manager firstly accesses the transition\transformation and delivery documentation, begins the analysis process in an attempt to identify what is of relevance to the EUWM tower and what contractually HP are obliged to deliver. The Overall HP-Customer Contract is opened with Adobe Acrobat Professional and using our plug-in SASA creates the category <ref type="foot" target="#foot_4">8</ref> "Customer X" for the customer and begins reviewing the documentation. With reference to Figure <ref type="figure">1</ref>, when the account manager identifies an item of interest such as 'Application Packaging' it is added to the category as a named entity. A note of "Due to ITAR 9 U.S. government regulations all Customer X transmissions must be manufactured within North America" is associated with that named entity. As the account managers' analysis progresses, another document, which is part of the Associated Schedules documentation, is found to contain a key stipulation regarding where UNIX application packaging must be performed. Another note is then added to the named entity 'Application Packaging' along with a bookmark to document Schedule B, which was found to have the associated information.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">SCENARIO DEVELOPMENT</head><p>In this manner peripheral information obtained from sources such as emails, phones calls and HP-Customer group discussions can be used to filter information and associate it with suitable named entities. Once the document review stage has concluded the Project Definition Document write up commences. Resulting from the review the accounts manager now has in effect a semantically annotated information source.</p><p>Figure <ref type="figure" target="#fig_0">2</ref> shows that to retrieve the information the manager need only click 'Find Entities' to have all named entities such as 'Application Packaging' belonging to the category highlighted.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 1. Adding a note to named entity 'Application Packaging'</head><p>Selection of the named entity 'Application Packaging' will provide visibility of all additional information and annotations from previous documentation reviews. The client account manager also has the ability to view a summary of all the named entites and their associated information (see Figure <ref type="figure" target="#fig_0">2</ref>). This assists the accounts manager in ensuring that issues regarding the like of UNIX application packaging and ITAR regulations are factored in and captured in the Project Definition Document. Otherwise the potential knock on effects of overlooking this information could adversely affect the project timeline, project scope, level of effort required, and delivery model with ultimately negative commercial impact. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">PROPOSED SOLUTION</head><p>SASA is implemented as a plug-in 10 for Adobe Acrobat Professional. SASA adds a toolbar to the standard interface (see 10 A dynamically-linked extension to Acrobat, which hooks into the user interface and adds functionality to Acrobat Professional, Acrobat Standard, or Adobe Reader.</p><p>Figure <ref type="figure">1</ref>). The toolbar provides functionality allowing the user to apply or create ontologies and link associated information as semantic annotations to named entities within the PDF document's text content. Dialog windows created using the Adobe Dialog Manager (ADM) <ref type="foot" target="#foot_5">11</ref> are used to facilitate the addition of the named entities and their associated information. SASA stores the ontologies on the users' local machine in Resource Description Format (RDF) <ref type="bibr" target="#b10">[11]</ref>, which makes them portable amongst groups.</p><p>Referring to Figure <ref type="figure" target="#fig_2">3</ref>, the SASA application architecture will contain: 1) A Trainer component to train SASA using the text and the users' selected ontology about the context of the currently viewed PDF document. SASA will extract the text from the document and use a Vector Space Model (VSM) <ref type="bibr" target="#b11">[12]</ref> <ref type="foot" target="#foot_6">12</ref> to represent the collected training information by using the words from the document and their frequency of occurrence to augment the existing training data. 2) A Categorisation component to derive the context of the currently viewed document using the Cosine Similarity Measure <ref type="bibr" target="#b12">[13]</ref> to compare the text of the document with the training data and calculate from the vectors the most likely match to the current ontologies.  ontology of the user's choice to highlight and add links to named entities on a Web page. Table <ref type="table" target="#tab_1">1</ref> shows an extract from a recent survey of semantic annotation tools. It was found that they cater primarily for Web native formats such as HTML and XML. SASA caters for PDF and can be integrated with HPs Mozilla Firefox extension Trailblazer <ref type="bibr" target="#b15">[16]</ref> to allow for HTML also. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">CONCLUSIONS AND FUTURE WORK</head><p>In this paper we have proposed a plug-in for Adobe Acrobat Professional called SASA, a novel PKM tool for semi-automatic semantic annotation of PDF documents utilising Semantic Web enabling technologies. SASA allows the user to build, augment and share ontologies amongst knowledge workers. Within an ontology named entities are connected to additional information such as Web pages, documents, mail messages, personal notes, and wikis. SASA automatically derives the context of the document, highlights named entities and applies the relevant additional information. The business case for such a tool is outlined and user scenario development used to illustrate how SASA will enhance PKM. Our future work plans, aside from continued implementation of our SASA plug-in, include detailed definition of the case study. We also plan to carry out a systematic user evaluation -with the help of Client Account Managers at HP Galway. Lastly, we are also working on semantically annotating a number of PDF documents at the one time and researching sub section document training.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 2 .</head><label>2</label><figDesc>Figure 2. Document annotated showing summary of all named entities and their associated information</figDesc><graphic coords="3,60.00,432.54,228.28,165.12" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>3) A NEIO component to add and delete named entities and their associated information to and from the ontology. 4) An Annotator component to semantically annotate the text of the PDF document by finding and highlighting named entities of interest and applying their relevant additional information. 5) An Import/Export component to share ontologies amongst users. 6) A Viewer component to view an entire trail of annotations for a selected ontology.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 .</head><label>3</label><figDesc>Figure 3. Overview of SASA Architecture 5. RELATED WORK SemanticWord [14], a Microsoft Word-based environment, adds several toolbars to the interface which support the creation of semantic annotations in documents and templates according to selected ontologies. Magpie [15] is a Web browser extension which uses Named Entity Recognition (NER) based on a supplied</figDesc><graphic coords="3,317.94,387.36,225.85,170.46" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Take for example the situation where a EUWM client account manager has to prepare and deliver a Project Definition Document based on the requirements of the U.S. car manufacturing customer "Customer X", and the capabilities of the delivery organisation and support structure. Material used in drawing this information together is contained in a large number of key business documents such as Statement of Work (SOW), HP Overall Scope</figDesc><table /><note>document, Technical Solution Document (TSD), RCM Model, Overall HP-Customer Contract and Associated Schedules, Requests For Information (RFI), Requests For Proposals (RFP), etc.</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1 . Extract from comparison of annotation tools for requirements 1-7 [17].</head><label>1</label><figDesc></figDesc><table><row><cell>Annotation Tool</cell><cell>Semantic Word</cell><cell>Magpie</cell><cell>Amaya</cell></row><row><cell>Standard formats</cell><cell>DAML+OIL</cell><cell>HTML OCML</cell><cell>RDF(S) XLink, XPointer</cell></row><row><cell>User-centered design</cell><cell>Microsoft Word GUIs</cell><cell>Web browser plug-in</cell><cell>Web browser &amp; editor</cell></row><row><cell>Ontology support</cell><cell>-</cell><cell>-</cell><cell>Annotation server</cell></row><row><cell>Document formats</cell><cell>Word</cell><cell>HTML</cell><cell>HTML, XHTML and XML</cell></row><row><cell>Document evolution</cell><cell>Mark-up tied to text regions</cell><cell>-</cell><cell>XPointer</cell></row><row><cell>Annotation storage</cell><cell>-</cell><cell>None, real time</cell><cell>Local or annotation server</cell></row><row><cell>Automation</cell><cell>Yes</cell><cell>Yes</cell><cell>No</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://www.hp.com/ie/galway/sirg/trailblazer/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">http://www.annotae.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">A de facto standard on the Web alongside HTML.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_3">International Standards Organisation</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_4">'Category' is used to represent an ontology.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_5">A cross-platform API for implementing dialog interfaces for Adobe applications such as Acrobat, etc.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_6">An algebraic model used for information filtering and information retrieval.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">ACKNOWLEDGMENTS</head><p>We would like to thank Robert Connolly and Richard Joyce from the EUWM Pre-Sales &amp; Implementation Team, Dara Keogh, and Colman O'Dywer from the Solutions Management Services Team at HP Galway for their time and expertise in framing the business case.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">The Knowledge Creating Company</title>
		<author>
			<persName><forename type="first">I</forename><surname>Nonaka</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1991">1991</date>
			<publisher>Harvard Business Review</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Working Knowledge, How Organisations Manage What They Know</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">H</forename><surname>Davenport</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Prusak</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1997">1997</date>
			<publisher>Harvard Business School Press</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">The Knowledge Creating Company -How Japanese Companies Create the Dynamics of Innovation</title>
		<author>
			<persName><forename type="first">I</forename><surname>Nonaka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Takeuchi</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1995">1995</date>
			<publisher>The Oxford University Press</publisher>
			<pubPlace>Oxford</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Managing Knowledge Means Managing Oneself</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">F</forename><surname>Drucker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Leader to Leader</title>
		<imprint>
			<biblScope unit="volume">16</biblScope>
			<biblScope unit="page" from="8" to="10" />
			<date type="published" when="2000">Spring 2000</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Personal Knowledge Management with Semantic Wikis Technical Report</title>
		<author>
			<persName><forename type="first">M</forename><surname>Volkel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Oren</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2005-12">December 2005</date>
		</imprint>
		<respStmt>
			<orgName>AIFB Karlsruhe</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m">The Financial and Non-Financial Returns to Innovative Work Practices</title>
				<meeting><address><addrLine>New York</addrLine></address></meeting>
		<imprint>
			<publisher>Ernst &amp; Young</publisher>
			<date type="published" when="1995-03">1995. March</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">The Semantic Web</title>
		<author>
			<persName><forename type="first">T</forename><surname>Berners-Lee</surname></persName>
		</author>
		<author>
			<persName><surname>Hendler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Lassils</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2001-05">May 2001</date>
			<publisher>Scientific American</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">KIM-a semantic platform for information extraction and retrieval</title>
		<author>
			<persName><forename type="first">B</forename><surname>Popov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kirayakov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Ognyanoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Manov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kirilov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nat. Lang. Eng</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">3/4</biblScope>
			<biblScope unit="page" from="375" to="392" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Leveraging metadata creation for the Semantic web with CREAM, KI &apos;2003-advances in artificial intelligence</title>
		<author>
			<persName><forename type="first">S</forename><surname>Handschuh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Studer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Annual German Conference on AI</title>
				<meeting>the Annual German Conference on AI</meeting>
		<imprint>
			<date type="published" when="2003-09">September 2003, 2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<ptr target="http://partners.adobe.com/public/developer/pdf/index_reference.html" />
		<title level="m">Portable Document Reference Manual, Fifth Edition, Adobe Systems Incorporated</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">RDF Vocabulary Description Language 1.0: RDF Schema</title>
		<author>
			<persName><forename type="first">D</forename><surname>Brickley</surname></persName>
		</author>
		<author>
			<persName><forename type="middle">R V</forename><surname>Guha</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2004-02">2004. February 2004</date>
		</imprint>
	</monogr>
	<note>W3C Recommendation 10</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Introduction to Modern Information Retrieval</title>
		<author>
			<persName><forename type="first">G</forename><surname>Salton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mcgill</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1983">1983</date>
			<publisher>McGraw-Hill</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Information Retrieval</title>
		<author>
			<persName><forename type="middle">C J</forename><surname>Van Rijsbergen</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1979">1979</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">SemanticWord processing for content authors</title>
		<author>
			<persName><forename type="first">M</forename><surname>Tallis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Knowledge Markup and Semantic Annotation Workshop (SEMANNOT 2003) at 2 nd International Conference on Knowledge Capture (K-CAP 2003)</title>
				<meeting>the Knowledge Markup and Semantic Annotation Workshop (SEMANNOT 2003) at 2 nd International Conference on Knowledge Capture (K-CAP 2003)<address><addrLine>Sanibel, Florida, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003-10-26">October 26, 2003. 2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Collaborative Semantic Web Browsing with Magpie</title>
		<author>
			<persName><forename type="first">J</forename><surname>Domingue</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dzbor</surname></persName>
		</author>
		<author>
			<persName><forename type="middle">E</forename><surname>Motta</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the 1st European Semantic Web Symposium (ESWS)</title>
				<meeting>of the 1st European Semantic Web Symposium (ESWS)</meeting>
		<imprint>
			<date type="published" when="2004-05">May 2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Using Named Entities as a basis for sharing associative trails between Semantic Desktops</title>
		<author>
			<persName><forename type="first">K</forename><surname>Tighe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Johnston</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">1st International Semantic Desktop Workshop (ISWC)</title>
				<imprint>
			<date type="published" when="2005-11">November 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Semantic Annotation for Knowledge Management: Requirements and a Survey of the State of the Art Journal of Web Semantics</title>
		<author>
			<persName><forename type="first">V</forename><surname>Uren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Cimiano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Iria</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Handschuh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Vargas-Vera</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Motta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Ciravegna</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Science, Services and Agents on the World Wide Web</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="page" from="14" to="28" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

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