Information Retrieval and the Semantic Web

Total Page:16

File Type:pdf, Size:1020Kb

Information Retrieval and the Semantic Web Information Retrieval and the Semantic Web Tim Finin1, James Mayfield2, Anupam Joshi1, R. Scott Cost2 and Clay Fink2 University of Maryland,1 The Johns Hopkins University2 Baltimore County Applied Physics Laboratory Baltimore MD 21250 USA Laurel MD 20723 USA Abstract ments as opposed to conventional ones. We describe Swoogle, a prototype crawler-based search engines for Information retrieval technology has been central to the RDF documents. This system allows users to retrieve success of the Web. For semantic web documents or indexed RDF documents based on the RDF classes and annotations to have an impact, they will have to be com- properties they use and also uses the Haircut information patible with Web based indexing and retrieval technol- retrieval engine to retrieve documents using character- ogy. We discuss some of the underlying problems and based n-grams. issues central to extending information retrieval systems The next section will motivate the ability to index and to handle annotations in semantic web languages. We search for documents consisting of or annotated with also describe three prototype systems that we have im- semantic web content. Section Three will lay out the plemented to explore these ideas. landscape of possible ways to adapt information retrieval 1. Introduction systems to the Semantic Web and Section Four will de- scribe three different prototype systems we have built to Information retrieval technology has been central to the explore the problem. The fifth section summarizes this success of the Web. Web based indexing and search work and speculates on what the future may bring. systems such as Google and Yahoo have profoundly changed the way we access information. For the seman- 2. Motivation tic web technologies [4][5] to have an impact, they will have to be compatible with Web search engines and in- The Semantic Web has lived its infancy as a clearly de- formation retrieval technology in general. We discuss lineated body of Web documents. That is, by and large several approaches to using information retrieval systems researchers working on aspects of the Semantic Web with both semantic web documents and with text docu- knew where the appropriate ontologies resided and ments that have semantic web annotations. tracked them using explicit URLs. When the desired Se- One vision of the Semantic Web is that it will be mantic Web document was not at hand, one was more much like the Web we know today, except that docu- likely to use a telephone to find it than a search engine. ments will be enriched by annotations in machine under- This closed world assumption was natural when a hand- standable markup. These annotations will provide meta- ful of researchers were developing DAML 0.5 ontolo- data about the documents as well as machine interpret- gies, but is untenable if the Semantic Web is to live up to able statements capturing some of the meaning of the its name. Yet simple support for search over Semantic documents’ content. We describe initial experiments that Web documents, while valuable, represents only a small demonstrate how existing IR systems can be coaxed into piece of the benefits that will accrue if search and infer- supporting this scenario using a technique we call swan- ence are considered together. We believe that Semantic gling to encode RDF triples as word-like terms. Web inference can improve traditional text search, and In an alternate vision, semantic web content will exist that text search can be used to facilitate or augment Se- in separate documents that reference and describe the mantic Web inference. Several difficulties, listed below, content of conventional web documents. Here too it may stand in the way of this vision. be desirable to use conventional systems such as Google Current Web search techniques are not directly suited to index and retrieve these documents. We discuss how to indexing and retrieval of semantic markup. Most the swangling technique can also be used to add asser- search engines use words or word variants as indexing tions to RDF documents in a way that is compatible with terms. When a document written using some flavor of many standard search engines. SGML is indexed, the markup is simply ignored by many A final approach to using IR engines for SWD docu- search engines. Because the Semantic Web is expressed ments is to build custom indexing and retrieval engines entirely as markup, it is thus invisible to them. Even specifically designed to work with semantic web docu- when search engines detect and index embedded markup, they do not process the markup in a way that allows the other containing the corresponding semantic markup. markup to be used during the search, or even in a way The two files are bound by placing in each a pointer to that can distinguish between markup and other text. the URI of the other, either by URI naming convention, Current Web search techniques cannot use semantic or by concurrent retrieval (i.e., as part of a single transac- markup to improve text retrieval. Web search engines tion). While this method makes it difficult to associate typically rely on simple term statistics to identify docu- semantic markup with specific components of the HTML ments that are most relevant to a query. One might con- page, it is possible to implement using today’s standards. sider techniques such as thesaurus expansion or blind Whichever approach is taken to binding semantic markup relevance feedback to be integration of inference into the to HTML, the current lack of a standard has made it dif- retrieval process, but such inference is simple compared ficult to exploit the relationship between the two. with what is possible using semantic markup. One would One of the stated objectives of the semantic web is to like the presence of semantic markup in either the query enhance the ability of both people and software agents to or the documents retrieved to be exploitable during find documents, information and answers to queries on search to improve that search. the Web. While there has been some research on infor- Likewise, text is not useful during inference. To the mation retrieval techniques applied to documents with extent that it is possible to automatically convert text to a markup [1][2][3][7][13], combining retrieval with ontol- semantic representation, such resulting representations ogy browsing [9], the role of explicit ontologies in in- can be used during inference. However, semantic inter- formation retrieval tasks [19], and on question answering pretation is difficult at best, and unsolved in the general as a retrieval task [18], much of it can be seen as incre- case. We would like a way to exploit relevant text during mental extensions to familiar paradigms. Our goal is inference, without needing to analyze the semantics of more ambitious and offers, we think, a new paradigm for that text. information retrieval that mixes and interleaves search, There is no current standard for creating or manipulat- retrieval and understanding. ing documents that contain both HTML text and semantic To explore the tight integration of search and infer- markup. There are two prime candidates for such hybrid ence, we propose a framework designed to meet the fol- documents. First, semantic markup might be embedded lowing desiderata: directly in an HTML page. Unfortunately, while we call • The framework must support both retrieval-driven approaches like RDF and OWL semantic markup, they and inference-driven processing. are typically used not as markup but rather as stand-alone • Retrieval must be able to use words, semantic knowledge representation languages that are not directly markup, or both as indexing terms. tied to text. Furthermore, embedding RDF-based markup • Web search must rely on today’s broad coverage, in HTML is non-compliant with HTML standards up to text-based retrieval engines. and including HTML 4.0. This issue is currently under • Inference and retrieval should be tightly coupled; study by a W3C task force [23]. improvements in retrieval should lead to improve- The second way to bind HTML to semantic markup is ments in inference, while improvements in inference to create a pair of documents, one containing HTML, the Local KB Semantic Inference Semantic Encoded Encoder Web Query Engine Markup Markup Web Search Engine Semantic Semantic Ranked Filters Extractor Markup Markup Pages Figure 1. Integration of inference and retrieval over semantic markup. Arrows represent data flow. should lead to improvements in retrieval. Only some of the semantic markup retrieved through In the following subsections, we first describe the por- this process will be useful for the task at hand. Some will tions of the framework that use semantic markup, then not come from an appropriate trusted authority. Some show how text processing can be mixed in to increase will be redundant. Some will be irrelevant. Thus, before system capabilities and improve performance. it is asserted into the inference engine’s knowledge store, the semantic markup gleaned from each page must be 2.1 Processing of Semantic Markup filtered. The result will be a collection of facts and rules, which are likely to further the inferences being pursued, Imagine we are concerned only with retrieval and infer- or serve as valuable relevance feedback terms. These ence over semantic markup. We would like the ability to facts and rules are passed to the inference engine, which operate some sort of inference engine, to identify facts may then iterate the entire process. and rules needed by the inference engine to reach its de- sired conclusions, to search the Semantic Web for such 2.2 Using Text facts and rules, and to incorporate the results of the search into the inference process. Figure 1 shows the The process described in the previous subsection basic architecture of such a system.
Recommended publications
  • Semantics Developer's Guide
    MarkLogic Server Semantic Graph Developer’s Guide 2 MarkLogic 10 May, 2019 Last Revised: 10.0-8, October, 2021 Copyright © 2021 MarkLogic Corporation. All rights reserved. MarkLogic Server MarkLogic 10—May, 2019 Semantic Graph Developer’s Guide—Page 2 MarkLogic Server Table of Contents Table of Contents Semantic Graph Developer’s Guide 1.0 Introduction to Semantic Graphs in MarkLogic ..........................................11 1.1 Terminology ..........................................................................................................12 1.2 Linked Open Data .................................................................................................13 1.3 RDF Implementation in MarkLogic .....................................................................14 1.3.1 Using RDF in MarkLogic .........................................................................15 1.3.1.1 Storing RDF Triples in MarkLogic ...........................................17 1.3.1.2 Querying Triples .......................................................................18 1.3.2 RDF Data Model .......................................................................................20 1.3.3 Blank Node Identifiers ..............................................................................21 1.3.4 RDF Datatypes ..........................................................................................21 1.3.5 IRIs and Prefixes .......................................................................................22 1.3.5.1 IRIs ............................................................................................22
    [Show full text]
  • Where Is the Semantic Web? – an Overview of the Use of Embeddable Semantics in Austria
    Where Is The Semantic Web? – An Overview of the Use of Embeddable Semantics in Austria Wilhelm Loibl Institute for Service Marketing and Tourism Vienna University of Economics and Business, Austria [email protected] Abstract Improving the results of search engines and enabling new online applications are two of the main aims of the Semantic Web. For a machine to be able to read and interpret semantic information, this content has to be offered online first. With several technologies available the question arises which one to use. Those who want to build the software necessary to interpret the offered data have to know what information is available and in which format. In order to answer these questions, the author analysed the business websites of different Austrian industry sectors as to what semantic information is embedded. Preliminary results show that, although overall usage numbers are still small, certain differences between individual sectors exist. Keywords: semantic web, RDFa, microformats, Austria, industry sectors 1 Introduction As tourism is a very information-intense industry (Werthner & Klein, 1999), especially novel users resort to well-known generic search engines like Google to find travel related information (Mitsche, 2005). Often, these machines do not provide satisfactory search results as their algorithms match a user’s query against the (weighted) terms found in online documents (Berry and Browne, 1999). One solution to this problem lies in “Semantic Searches” (Maedche & Staab, 2002). In order for them to work, web resources must first be annotated with additional metadata describing the content (Davies, Studer & Warren., 2006). Therefore, anyone who wants to provide data online must decide on which technology to use.
    [Show full text]
  • Mathematical Model of Semantic Look-An Efficient Context Driven Search
    Mathematical Model of Semantic Look - An Efficient Context Driven Search Engine Leena Giri Ga, Srikanth P La, Manjula S Ha, K R Venugopal a, L M Patnaikb aDepartment of Computer Science and Engineering, University Visvesvaraya College of Engineering, Bangalore University, Bangalore 560 001 India, Contact: [email protected]. bHonorary Professor, IISc., Bangalore. The World Wide Web (WWW) is a huge conservatory of web pages. Search Engines are key applications that fetch web pages for the user query. In the current generation web architecture, search engines treat keywords provided by the user as isolated keywords without considering the context of the user query. This results in a lot of unrelated pages or links being displayed to the user. Semantic Web is based on the current web with a revised framework to display a more precise result set as response to a user query. The current web pages need to be annotated by finding relevant meta data to be added to each of them, so that they become useful to Semantic Web search engines. Semantic Look explores the context of user query by processing the Semantic information recorded in the web pages. It is compared with an existing algorithm called OntoLook and it is shown that Semantic Look is a better optimized search engine by being more than twice as fast as OntoLook. Keywords : Ontology, RDF, Semantic Web. 1. INTRODUCTION the web page playing multiple roles. Both Ontolo- gies and RDF are embedded in web pages forming Semantic Web (Web 3.0) is the proliferation of the semantic annotation of a web page.
    [Show full text]
  • Ech-0205 V1.0 Linked Open Data
    E-Government Standards Page 1 of 49 eCH-0205 Linked Open Data Name Linked Open Data eCH-number eCH-0205 Category Accessory Document Quality stage Defined Version 1.0 Status Approved Decision on 2018-03-06 Date of issue 2018-03-13 Replaces version - Requirements - Annexes - Languages English (original) Authors Members of the eCH Specialized Group “Open Government Data” Main Author: Beat Estermann, Berner Fachhochschule [email protected] For a list of further contributors, see Annex B. Editor / Distribution eCH registered association, Mainaustrasse 30, Postfach [P.O. Box], 8034 Zürich T 044 388 74 64, F 044 388 71 80 www.ech.ch / [email protected] eCH registered association www.ech.ch / [email protected] eCH-0205 Linked Open Data / 1.0 / Approved / 2018-03-13 E-Government Standards Page 2 of 49 Summary This document provides the Swiss Linked Data community with a shared vision of the state of linked open data publication in the public and heritage sectors in Switzerland and gives people who are new to the community a first overview of previous and ongoing activities in the area of data publication, data use, and know-how exchange. The document contains a short introduction to linked (open) data, gives a detailed account of what linked data publica- tion is about, provides an overview of the present state of linked data publication by Swiss public and heritage sector organizations, and presents a series of exemplary use cases that serve as test and study cases to tackle current challenges and demonstrate the usefulness of linked (open) data in practice.
    [Show full text]
  • FHIR RDF in Action
    FHIR RDF in Action Harold Solbrig, Mayo Clinic Amsterdam, 15-17 November | @fhir_furore | #fhirdevdays17 | www.fhirdevdays.com FHIR® is the registered trademark of HL7 and is used with the permission of HL7. The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7. About Me – Harold Solbrig • Began in 1972 doing nuclear reactor safety software • Began medical computing 1975-78 – Berkeley Scientific Labs • First commercial Unix sysop • Hardware - disc controllers / television newsrooms • Worked on ASN.1, ISO 11179 (X3/L8) (metadata), ISO TC 215 (healthcare), OMG, HL7, WHO, IHTSDO / SNOMED International, ISO TC 37 (terminology) • BS in Maths and Computer Science, MsC in Software Engineering • With Mayo Clinic 1999-today (more or less) About Me – Harold Solbrig FHIR RDF in Action - Outline • FHIR RDF with SNOMED and OWL • FHIR RDF and i2b2 • fhir.schema.org (if time allows) FHIR Resource Instance in RDF http://www.hl7.org/fhir/diagnosticreport-example-f201-brainct.ttl RDF Turtle Syntax RDF Rendering Extensions – Concept URIs <http://snomed.info/id/394914008> JSON RDF Rendering Extensions – Resource Types Construct the actual URI Resource Type Ontology Header Stay tuned: • Looking at http://hl7.org/fhir/owl/DiagnosticRepor Requirement: import FHIR URI Catalog t/f201 (or variant thereof) as an • No ‘import in RDF’ – have to use OWL alternative • owl:imports requires owl:Ontology • ‘f201.ttl’ vs. ‘f201’ – reasoners don’t cope well with something that is both a fhir:DiagnosticReport and an owl:Ontology
    [Show full text]
  • Ccrel: the Creative Commons Rights Expression Language
    ccREL: The Creative Commons Rights Expression Language Hal Abelson, Ben Adida, Mike Linksvayer, Nathan Yergler [hal,ben,ml,nathan]@creativecommons.org Version 1.0 { March 3rd, 2008 1 Introduction This paper introduces the Creative Commons Rights Expression Language (ccREL), the standard recommended by Creative Commons (CC) for machine-readable expression of copyright licensing terms and related information.1 ccREL and its description in this paper supersede all previous Creative Commons recommendations for expressing licensing metadata. Like CC's previous rec- ommendation, ccREL is based on the World-Wide Web Consortium's Resource Description Frame- work (RDF).2 Compared to the previous recommendation, ccREL is intended to be both easier for content creators and publishers to provide, and more convenient for user communities and tool builders to consume, extend, and redistribute.3 Formally, ccREL is specified in an abstract syntax-free way, as an extensible set of properties to be associated with a licensed documents. Publishers have wide discretion in their choice of syntax, so long as the process for extracting the properties is discoverable and tool builders can retrieve the properties of ccREL-compliant Web pages or embedded documents. We also recommend specific concrete \default" syntaxes and embedding schemes for content creators and publishers who want to use CC licenses without needing to be concerned about extraction mechanisms. The default schemes are RDFa for HTML Web pages and resources referenced therein, and XMP for stand- alone media.4 An Example. Using this new recommendation, an author can express Creative Commons struc- tured data in an HTML page using the following simple markup: 1Information about Creative Commons is available on the web at http://creativecommons.org.
    [Show full text]
  • Specification of the Legal Knowledge Interchange Format
    IST-2004-027655 ESTRELLA European project for Standardised Transparent Representations in order to Extend Legal Accessibility Specific Targeted Research Project Information Society Technologies Deliverable 1.1 Specification of the Legal Knowledge Interchange Format Due date of deliverable: 31 December 2006 Actual submission date: 22 January 2007 Start date of project: 1 January 2006 Duration: 30 months University of Amsterdam FINAL Project co-funded by the European Commission within the Sixth Framework Programme (2002-2006) Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Executive Summary This deliverable reports on the specification of syntax and semantics of the LKIF language, and should be read in conjunction with deliverable D1.4 on the LKIF ontologies. The proposed LKIF adds a terminology for deontic statements, and a special LKIF rule language to existing fragments of OWL and the rule language SWRL. The Technical Annex states about this work package: The main technical objectives of this work package are to develop a first version of a Legal Knowledge Interchange Format (LKIF), building upon emerging XML-based standards of the Semantic Web, including RDF and OWL, and Application Program Interfaces (APIs) for interacting with legal knowledge systems. The LKIF will apply the state of the art in the field of Artificial Intelligence and Law, taking into account business and application requirements. Existing Semantic Web initiatives are aimed at modelling concepts (OWL ”ontologies”) and rules (RuleML and SWRL).
    [Show full text]
  • Resource Description Framework (RDF) Schema Specification
    Resource Description Framework (RDF) Schema Specification W3C Proposed Recommendation 03 March 1999 This Version: http://www.w3.org/TR/1999/PR-rdf-schema-19990303 Newest Version: http://www.w3.org/TR/PR-rdf-schema Editors: Dan Brickley, University of Bristol R.V. Guha, Netscape Document Status and errata Acknowledgments Copyright ©1998,1999 W3C (MIT, INRIA, Keio) , All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Status of this document This document is a Proposed Recommendation of the World Wide Web Consortium. Review comments on this specification should be sent by 2359Z April 06, 1999 to <www-rdf- [email protected]>. The archive of public comments is available at http://w3.org/Archives/Public/www-rdf-comments. W3C Members may send their formal comments, visible only to W3C staff, to <[email protected]>. This specification is a revision of the last-call working draft dated 1998-10-30 incorporating suggestions received in review comments and further deliberations of the W3C RDF Schema Working Group. The detailed differences are available for reviewers to compare. The Working Group anticipates no further substantial changes to this specification. We encourage active implementation to test this specification during the Proposed Recommendation review period. Publication as a Proposed Recommendation does not imply endorsement by the W3C membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite W3C Drafts as other than "work in progress". The Resource Description Framework is part of the W3C Metadata Activity. The goal of this activity, 4/26/99 and of RDF specifically, is to produce a language for the exchange of machine-understandable descriptions of resources on the Web.
    [Show full text]
  • Downloading Only the Most Relevant Data for Analysis
    Stuart_Practical ontologies_TEXT PROOF_04 28/07/2016 09:14 Page i Practical Ontologies for Information Professionals Stuart_Practical ontologies_TEXT PROOF_04 28/07/2016 09:14 Page ii Every purchase of a Facet book helps to fund CILIP’s advocacy, awareness and accreditation programmes for information professionals. Stuart_Practical ontologies_TEXT PROOF_04 28/07/2016 09:14 Page iii Practical Ontologies for Information Professionals David Stuart Stuart_Practical ontologies_TEXT PROOF_04 28/07/2016 09:14 Page iv © David Stuart 2016 Published by Facet Publishing 7 Ridgmount Street, London WC1E 7AE www.facetpublishing.co.uk Facet Publishing is wholly owned by CILIP: the Chartered Institute of Library and Information Professionals. David Stuart has asserted his right under the Copyright, Designs and Patents Act 1988 to be identified as author of this work. Except as otherwise permitted under the Copyright, Designs and Patents Act 1988 this publication may only be reproduced, stored or transmitted in any form or by any means, with the prior permission of the publisher, or, in the case of reprographic reproduction, in accordance with the terms of a licence issued by e Copyright Licensing Agency. Enquiries concerning reproduction outside those terms should be sent to Facet Publishing, 7 Ridgmount Street, London WC1E 7AE. Every effort has been made to contact the holders of copyright material reproduced in this text, and thanks are due to them for permission to reproduce the material indicated. If there are any queries please contact the publisher. British Library Cataloguing in Publication Data A catalogue record for this book is available from the British Library. ISBN 978-1-78330-062-4 (paperback) ISBN 978-1-78330-104-1 (hardback) ISBN 978-1-78330-152-2 (e-book) First published 2016 Text printed on FSC accredited material.
    [Show full text]
  • Reconciliation of RDF⋆ and Property Graphs
    Reconciliation of RDF⋆ and Property Graphs Olaf Hartig University of Waterloo http://olafhartig.de November 14, 2014 Abstract Both the notion of Property Graphs (PG) and the Resource Description Framework (RDF) are commonly used models for representing graph-shaped data. While there exist some system- specific solutions to convert data from one model to the other, these solutions are not entirely compatible with one another and none of them appears to be based on a formal foundation. In fact, for the PG model, there does not even exist a commonly agreed-upon formal definition. The aim of this document is to reconcile both models formally. To this end, the document proposes a formalization of the PG model and introduces well-defined transformations between PGs and RDF. As a result, the document provides a basis for the following two innovations: On one hand, by implementing the RDF-to-PG transformations defined in this document, PG-based systems can enable their users to load RDF data and make it accessible in a compatible, system- independent manner using, e.g., the graph traversal language Gremlin or the declarative graph query language Cypher. On the other hand, the PG-to-RDF transformation in this document enables RDF data management systems to support compatible, system-independent queries over the content of Property Graphs by using the standard RDF query language SPARQL. Addi- tionally, this document represents a foundation for systematic research on relationships between the two models and between their query languages. If you have comments or suggestions about this proposal, as well as implementations or applications thereof, do not hesitate to let the author know about them.
    [Show full text]
  • Rdfa and Microdata Bethany Wetherill San Jose State University, [email protected]
    University of Nebraska - Lincoln DigitalCommons@University of Nebraska - Lincoln Library Philosophy and Practice (e-journal) Libraries at University of Nebraska-Lincoln 2014 RDFa and Microdata Bethany Wetherill San Jose State University, [email protected] Follow this and additional works at: http://digitalcommons.unl.edu/libphilprac Part of the Library and Information Science Commons Wetherill, Bethany, "RDFa and Microdata" (2014). Library Philosophy and Practice (e-journal). 1151. http://digitalcommons.unl.edu/libphilprac/1151 RDFa and Microdata 1 Running head: RDFa and Microdata RDFa and Microdata: Is One Better Than The Other? Bethany Wetherill A Research Proposal Submitted in Partial Fulfillment of the Requirements for LIBR 281 - Metadata San Jose State University 2014 RDFa and Microdata 2 Abstract This project seeks to explore and observe differences in RDFa and microdata and their ability to retain proper schematization and syntax when converted back to RDF/XML. Online conversion tools were used to transpose existing RDF/XML files from online data dumps to RDFa and microdata, and then back to RDF/XML, offering some insights into RDFa and microdata’s capabilities, as well as a taste of what may happen in the future if major search engines decide to move away from microdata and developers need to convert to a different semantic markup language. Multiple online converters were employed in the conversion process in an attempt to identify and isolate the effects of potential programming errors. Ultimately, there was no major difference in data integrity between RDFa to RDF/XML and microdata to RDF/XML. Larger differences can be ascribed to the conversion tools being used rather than the formats themselves, as well as the quality the original RDF document.
    [Show full text]
  • Web Engineering for Semantic Web Applications
    DISSERTATION WEESA - Web Engineering for Semantic Web Applications ausgefuhrt¨ zum Zwecke der Erlangung des akademischen Grades eines Doktors der technischen Wissenschaften unter der Leitung von Univ.-Prof. Dipl.-Ing. Dr.techn. Harald Gall Institut fur¨ Informatik Universitat¨ Zurich¨ und o.Univ.-Prof. Dipl.-Ing. Dr.techn. Mehdi Jazayeri Institut fur¨ Informationssysteme Technische Universitat¨ Wien eingereicht an der Technischen Universitat¨ Wien Fakultat¨ fur¨ Informatik von Univ.-Ass. Dipl.-Ing. Gerald Reif [email protected] Matrikelnummer: 9130640 Wien, im Mai 2005 Kurzfassung Die wachsende Popularitat¨ des World Wide Webs hat zu einer exponentiellen Steigerung der Zahl der Webseiten gefuhrt.¨ Die große Anzahl der verfugbaren¨ Webseiten macht es Benutzern immer schwerer benotigte¨ Informationen zu finden. Sucht man im Web nach einer spezifischen Information, lauft¨ man Gefahr, die relevanten Daten in der großen Anzahl von irrelevanten Su- chergebnissen zu ubersehen.¨ Web-Applikationen stellen derzeit Webseiten in HTML Format zur Verfugung,¨ in denen der Inhalt in naturlicher¨ Sprache ausgedruckt¨ ist. Daher ist die Semantik des Inhalts fur¨ Computer nicht zugangig.¨ Um es Computern zu ermoglichen¨ dem Benutzer bei Informationsproblemen zu unterstutzen,¨ schlagt¨ das Semantik Web eine Erweiterung des exi- stierenden Webs vor, welche die Semantik der Webseiten fur¨ Computer verarbeitbar macht. Die Semantik des Inhalts einer Webseite wird dabei mit RDF Meta-Daten beschrieben. Diese Meta- Daten beschreiben den Inhalt der Webseite in einer maschinen-verarbeitbaren Form. Die Existenz von semantisch annotierten Webseiten ist daher die Voraussetzung fur¨ das Semantik Web. Semantische Annotation beschaftigt¨ sich mit diesem Problem und zielt darauf ab, semanti- sche Meta-Daten zu naturlichsprachigen¨ Dokumenten hinzuzufugen,¨ um den Inhalt maschinen- verarbeitbar zu machen.
    [Show full text]