978-3-642-23300-5 6 Chapter.Pd

Total Page:16

File Type:pdf, Size:1020Kb

978-3-642-23300-5 6 Chapter.Pd The Problem of Conceptual Incompatibility Simon Mcginnes To cite this version: Simon Mcginnes. The Problem of Conceptual Incompatibility. 1st Availability, Reliability and Security (CD-ARES), Aug 2011, Vienna, Austria. pp.69-81, 10.1007/978-3-642-23300-5_6. hal-01590394 HAL Id: hal-01590394 https://hal.inria.fr/hal-01590394 Submitted on 19 Sep 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Problem of Conceptual Incompatibility Exploring the Potential of Conceptual Data Independence to Ease Data Integration Simon McGinnes Trinity College Dublin, Dublin 2, Ireland [email protected] Abstract. Application interoperability and data exchange are desirable goals, but conventional system design practices make these goals difficult to achieve, since they create heterogeneous, incompatible conceptual structures. This conceptual incompatibility increases system development, maintenance and integration workloads unacceptably. Conceptual data independence (CDI) is proposed as a way of overcoming these problems. Under CDI, data is stored and exchanged in a form which is invariant with respect to conceptual structures; data corresponding to multiple schemas can co-exist within the same application without loss of integrity. The use of CDI to create domain- independent applications could reduce development and maintenance workloads and has potential implications for data exchange. Datasets can be merged without effort if stored in a conceptually-independent manner, provided that each implements common concepts. A suitable set of shared basic-level archetypal categories is outlined which can be implemented in domain- independent applications, avoiding the need for agreement about, and implementation of, complex ontologies. Keywords. Data integration, domain-independent design, conceptual data independence, archetypal categories. 1 Introduction: The Problem of Conceptual Incompatibility The present massive proliferation of databases, web pages and other information resources presents a data integration problem. There is a need to use data in a joined- up way, but mechanisms are lacking that allow easy data integration in the general case; it is often hard to combine data resources. A prime reason for this is that different datasets typically have incompatible conceptual structures. Common practice in information systems (IS) design leads each organisation or software vendor to create its own idiosyncratic data structures that are incompatible with those created by others; commercial pressures can have the same effect. Standard conceptual structures are normally used only in limited circumstances, when imposed by enterprise software platforms, legislative requirements or other external constraints. In the rush 2 Simon McGinnes to create ever-more comprehensive and powerful IS, the increasing problem of heterogeneous, incompatible conceptual structures has been left for future technology to solve. 1.1 Why Do Current Methods of Integration Not Solve the Problem? Developers have historically faced two issues with regard to integration of systems that have distinct conceptual data structures: physical incompatibility and conceptual incompatibility. Thankfully, many technologies now exist to resolve the first issue, by physically interconnecting heterogeneous platforms; these include RPC, CORBA and web services. Programs can also be linked simply by exchanging files using a common format such as XML. However, progress on physical compatibility has exposed the deeper second issue of conceptual or semantic compatibility: the problem of reconciling implicit conceptual models. If we wish to use several data resources in an integrated way, they must share both a common vocabulary and a common conceptual framework. This fundamental and unavoidable principle of semiotics [1] may be understood by analogy to human communication: if two people wish to exchange information effectively they must speak the same language, but they must also possess shared concepts. Conceptual compatibility thus runs deeper than mere language; for people to communicate they must interpret words identically, or nearly so, and there is no guarantee that this will be the case. Meaning is essentially personal and subjective, affected by context, culture, and so on. Getting two programs to exchange data involves a similar problem. A common, recognisable vocabulary must be used by both sides, and the two programs must also have been programmed with common concepts, so that they can act on the data appropriately. Computers cannot yet understand data in the sense that a human does, but they can be programmed to deal sensibly with specific items of data provided that the data is of a known type; this is what we mean when we say that a program ―understands‖ a particular concept. In practice, however, most IS share neither vocabulary nor concepts. It would be surprising if they did, given they ways they are developed and the rarity with which standard conceptual structures are applied. For this reason, linking real-world IS that have heterogeneous conceptual schemas is rarely a simple matter. In trivial cases it can seem straightforward to map the conceptual models of distinct systems to one another. For example, two programs which manage data about customers might well use similar data structures and common terms such as name, address and phone number. But semantic complexity lurks even in apparently straightforward situations. Is a customer a person or an organisation? Are business prospects regarded as customers, or must we already be trading with someone for them to be considered a customer? What about ex-customers? Many such questions can be asked, highlighting the inconvenient truth that most concepts are more complex than they seem, when one scratches the surface, and certainly far more complicated and esoteric than the trivial example quoted above. Uniting separately- developed conceptual structures can be challenging even for expert developers The Problem of Conceptual Incompatibility 3 working with systems in closely-related domains [2]; it can be difficult to discern what data structures are intended to signify and what unstated assumptions have been made. Another approach to data integration involves the use of automated schema matching, and tools for this purpose have been developed with some success [3]. But there is an inherent limit to the ability of automated matching strategies to operate reliably in the general case. Software cannot easily call upon context, domain expertise and general knowledge to understand and disambiguate the meaning of conceptual structures [4]. Again, the analogy of human understanding is relevant. When conversing with others, we draw upon our prior knowledge to understand what is meant. A person without prior knowledge has no hope of understanding what somebody else says. This analogy suggests that automated schema matching strategies must first overcome the grand challenge of accumulating and applying general knowledge before they can be expected to extract the semantics in arbitrary schemas with sufficient reliability [5]. In summary, semantic issues make it difficult, as a rule, to match conceptual models between IS—especially since most IS have idiosyncratic designs and complex conceptual structures that are based on unstated assumptions [6]. Conceptual incompatibility therefore presents a major barrier when we attempt to link IS. And this ignores the scalability problem, that integrating systems typically requires a good deal of interface code which must be crafted, onerously, by hand. Conceptual incompatibility is also a problem for end users [7]. It means that we must adopt a different mental model of reality each time we use a different program. For example, consider how the concept person is treated in different software products from the same vendor. In Microsoft Word, people are represented merely as ―users‖. In Microsoft Project, people are considered from a management perspective as ―resources‖. In Microsoft Outlook people are considered as ―contacts‖. Although these different treatments refer to the same underlying entity (a person), they are in fact three quite distinct mental concepts, each with its own meaning and implications. The same applies to most software applications: each application takes a unique perspective on reality to suit its own purpose. The user is left to mentally reconcile the various perspectives. This is at best confusing, since the concepts may be overlapping or orthogonal, and applications rarely spell out precisely what they mean by any given term. It can also be a problem for developers, who often lack understanding of the domain concepts in applications [8]. 2 Standardisation of Conceptual Structures The reliance on post-hoc system integration implicitly facilitates the trend towards growth in conceptual incompatibility. By allowing heterogeneous applications to proliferate, we are effectively supporting the development
Recommended publications
  • 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]
  • Tantek Çelik HTML5 Now a Step-By-Step Tutorial for Getting Started Today Tantek Çelik
    <!DOCTYPE html> <meta charset= "utf-8"><title>HTML5 Now</title> <hgroup> <h1> HTML5 </h1> N <h2> OW A STEP-BY-STEP TUtoRIAL FOR GETTING STARTED TODAY </h2> </hgroup> <div class= "vcard"> <a href= "http://tantek.com" class= "url fn"> TANTEK ÇELIK </a> <div> EXTENDED REFERENCE GUIDE HTML5 NOW A STEP-BY-STEP TUtoRIAL FOR GETTING STARTED TODAY TANTEK ÇELIK HTML5 Now A Step-by-Step Tutorial for Getting Started Today Tantek Çelik New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 Fax: 510/524-2221 Find us on the web at www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2011 by Pearson Education, Inc. Senior Editor: Karyn Johnson Production Editor: Hilal Sala Copy Editor: Kelly Anton Technical Editor: Ben Ward Interior Design and Composition: Andreas deDanaan Presentation Graphics and Design: Coley Wopperer Author Photo: Matt Nuzzaco Cover Design: Mimi Heft Cover Production: Andreas deDanaan Video Production and Direction: Mary Sweeney Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For information on getting permission for reprints and excerpts, contact [email protected]. Notice of Liability The information in this book is distributed on an “As Is” basis without warranty. While every precaution has been taken in the preparation of the book, neither the author nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the computer software and hardware products described in it.
    [Show full text]
  • REST in Practice
    REST in Practice Jim Webber, Savas Parastatidis, and Ian Robinson Beijing · Cambridge · Farnham · Köln · Sebastopol · Tokyo REST in Practice by Jim Webber, Savas Parastatidis, and Ian Robinson Copyright © 2010 Jim Webber, Savas Parastatidis, and Ian Robinson. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Simon St.Laurent Indexer: Lucie Haskins Production Editor: Rachel Monaghan Cover Designer: Karen Montgomery Copyeditor: Audrey Doyle Interior Designer: Ron Bilodeau Proofreader: Rachel Monaghan Illustrator: Robert Romano Production Services: Newgen North America Printing History: September 2010: First Edition. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc., REST in Practice, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and au- thors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-0-596-80582-1 [M] C o n t e n t s Foreword .
    [Show full text]
  • Foundations of Semantic Web Technologies
    FOUNDATIONS OF SEMANTIC WEB TECHNOLOGIES Linked Data and Applications Sebastian Rudolph Agenda 1 Linked (Open) Data 2 Semantic Web and HTML RDFa Microformats Google Knowledge Graph 3 OWL Applications OWL DL Application EDF Energy OWL Profile Application BBC World Cup Semantic Technologies in the Pharmaceutical Industry 4 Summary TU Dresden Foundations of Semantic Web Technologies slide 2 of 51 Agenda 1 Linked (Open) Data 2 Semantic Web and HTML RDFa Microformats Google Knowledge Graph 3 OWL Applications OWL DL Application EDF Energy OWL Profile Application BBC World Cup Semantic Technologies in the Pharmaceutical Industry 4 Summary TU Dresden Foundations of Semantic Web Technologies slide 3 of 51 Data in the Web • more and more data is available in the Web for programmatic access • often specified using Semantic Web Standards, e.g., the following Linking Open Data (LOD) Initiative http://www.w3.org/wiki/SweoIG/TaskForces/ CommunityProjects/LinkingOpenData • using APIs, e.g. via JSON/REST • Semantic Web technologies simplify the integration of data from different sources • combination of data leads to deeper insights TU Dresden Foundations of Semantic Web Technologies slide 4 of 51 Linked Data in the Web 01.05.2007 Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch. http://lod-cloud.net/ TU Dresden Foundations of Semantic Web Technologies slide 5 of 51 Linked Data in the Web 31.03.2008 ECS Sem- South- Web- ampton Central updated Music- Doap- Audio- brainz space Flickr Scrobbler QDOS exporter SIOC profiles BBC BBC Magna- SW Later + John Onto- tune Conference Jamendo Peel world TOTP FOAF Corpus profiles Open- Guides Geo- names Revyu DBpedia US RDF Book Census Mashup World Data NEW! Fact- DBLP book lingvoj riese Berlin NEW! RKB Euro- Explorer stat flickr Gov- Wiki- Open wrappr Track company Cyc DBLP Hannover W3C Project WordNet Guten- berg Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch.
    [Show full text]
  • Starting to Cook a Coaching Dialogue System in the Olympus Framework
    Starting to Cook a Coaching Dialogue System in the Olympus framework Joana Paulo Pardal and Nuno J. Mamede Abstract This paper presents the COOKCOACH, a system that guides the user while cooking a recipe during a spoken dialogue coaching session. We describe our expe- rience creating the first version of our coaching dialogue system that helps the user cook a selected dish. We use the CMU dialogue systems framework OLYMPUS. The main challenge we faced was the change of paradigm: instead of the system being driven by the user, the user is guided by the system. The result is a system capable of dictating generic tasks to the user. The methodology allows us to create different systems in diverse domains for similar guidance tasks that support the user while s/he performs some procedural task. The use of ontologies to facilitate the creation of new systems is briefly explored. Key words: Coaching, Ontologies, Cooking, Knowledge Acquisition, Interface Design, Human-Human Dialogue Corpora 1 Introduction Everyone needs to eat. Most of us need to cook. Once in a while, or daily. Whether we like it or not. However, most cooking books scatter the related knowledge across different sections assuming a common level of expertise. This means that an unex- perienced cook needs to navigate the cooking book to find all s/he needs, to cook what s/he has in mind. It also means that an experienced cook will read superfluous information s/he might already know. It is also a scenario where the person needs to stop what s/he is doing to read and handle the book, shifting focus from the task and Joana P.
    [Show full text]
  • Web Standards.Pdf
    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Sikos, Ph.D. RELATED Web Standards Web Standards: Mastering HTML5, CSS3, and XML gives you a deep understand- ing of how web standards can be applied to improve your website. You will also find solutions to some of the most common website problems. You will learn how to create fully standards-compliant websites and provide search engine-optimized Web documents with faster download times, accurate rendering, lower development costs, and easy maintenance. Web Standards: Mastering HTML5, CSS3, and XML describes how you can make the most of web standards, through technology discussions as well as practical sam- ple code. As a web developer, you’ll have seen problems with inconsistent appearance and behavior of the same site in different browsers. Web standards can and should be used to completely eliminate these problems. With Web Standards, you’ll learn how to: • Hand code valid markup, styles, and news feeds • Provide meaningful semantics and machine-readable metadata • Restrict markup to semantics and provide reliable layout • Achieve full standards compliance Web standardization is not a sacrifice! By using this book, we can create and maintain a better, well-formed Web for everyone. CSS3, and XML CSS3, Mastering HTML5, US $49.99 Shelve in Web Development/General User level: Intermediate–Advanced SOURCE CODE ONLINE www.apress.com www.it-ebooks.info For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. www.it-ebooks.info Contents at a Glance About the Author................................................................................................
    [Show full text]
  • D2.4 Weblog Spider Prototype and Associated Methodology
    SEVENTH FRAMEWORK PROGRAMME FP7-ICT-2009-6 BlogForever Grant agreement no.: 269963 BlogForever: D2.4 Weblog spider prototype and associated methodology Editor: M. Rynning Revision: First version Dissemination Level: Public Author(s): M. Rynning, V. Banos, K. Stepanyan, M. Joy, M. Gulliksen Due date of deliverable: 30th November 2011 Actual submission date: 30th November 2011 Start date of project: 01 March 2011 Duration: 30 months Lead Beneficiary name: CyberWatcher Abstract: This document presents potential solutions and technologies for monitoring, capturing and extracting data from weblogs. Additionally, the selected weblog spider prototype and associated methodologies are analysed. D2.2 Report: Weblog Spider Prototype and Associated Methodology 30 November 2011 Project co-funded by the European Commission within the Seventh Framework Programme (2007-2013) The BlogForever Consortium consists of: Aristotle University of Thessaloniki (AUTH) Greece European Organization for Nuclear Research (CERN) Switzerland University of Glasgow (UG) UK The University of Warwick (UW) UK University of London (UL) UK Technische Universitat Berlin (TUB) Germany Cyberwatcher Norway SRDC Yazilim Arastrirma ve Gelistrirme ve Danismanlik Ticaret Limited Sirketi (SRDC) Turkey Tero Ltd (Tero) Greece Mokono GMBH Germany Phaistos SA (Phaistos) Greece Altec Software Development S.A. (Altec) Greece BlogForever Consortium Page 2 of 71 D2.2 Report: Weblog Spider Prototype and Associated Methodology 30 November 2011 History Version Date Modification reason Modified
    [Show full text]
  • Smart Kitchen Final
    Supporting Cooking Tasks by a Smart Formulation Table Wolfgang Maass1,2 Andreas Filler 1Research Center for Intelligent Media Research Center for Intelligent Media Furtwangen University, Germany Furtwangen University, Germany 2Institute of Technology Management, University of St. Gallen, Switzerland Abstract—Kitchen environments are target of many In this article, we focus on the formulation area and how Ubiquitous Computing prototypes that investigate the it can be enhanced by non-intrusive information services that application of technologies in real-world situations. In this support weighing and mixing tasks. On technological level, paper, we present a design-driven approach that carefully we investigate whether Ubiquitous Computing technologies, analyzes domain theories, identifies requirements for human Semantic Technologies, and Internet of Things (IoT) task support, derives services accordingly, and uses these technologies can be used to positively support preparation descriptions for guiding implementations. We focus on how and concocting situations in a way that does not interfere preparation and concocting tasks can be supported by a with traditional cooking behaviors. formulation table with integrated scaling mechanism and a set of dedicated information services. We present how requirements are translated into system architectures and a prototype. Empirical studies are current tangible user interfaces, intelligent environment, design work. method II. REQUIREMENTS I. INTRODUCTION In our project, we have selected several functional and A kitchen is an environment equipped with different non-functional user requirements related to preparation and tools and services that assist individuals and groups in concocting situations. These requirements represent a different situations, such as cooking, washing the dishes, selection for complete cooking processes encompassing all breakfast preparation, and also communications.
    [Show full text]
  • Microformats and Microdata and SEO
    Microformats and Microdata and SEO Making the Web a Better Place with Rich Snippets Microformats are a way of marking up content with “meta” information. Other means include Microdata and RDFa. In essence, this involves adding some additional HTML around existing content so that the content can be identified by automated web services. These services include search engines and news aggregators. Of the three existing formats, I recommend looking at either Microdata or Microformats. Microformats Microformats is a grass-roots effort and has been around for quite a while now. It is based on tagging items with specific classes. There are many “patterns” for Microformats. Each pattern is intended for a specific type of content and has its own set of classes for marking things up. Some examples of Microformats patterns include: hCard - for people and organizations hCalendar - for events hProduct - for products hReview - for reviews of items hRecipe - for recipes Microdata The Microdata format was proposed by several major search engines within the last year. This is a similar idea to Microformats but the content is marked up in a different way - with new attributes on HTML tags. Since Microdata uses new attributes, it is a bit more technical than simply adding classes to markup. There are similar examples of Microdata patterns: Person - a person (alive, dead, undead, or fictional) Organization - an organization such as a school, NGO, corporation, club, etc. Event - an event happening at a certain time at a certain location Place - entities that have a somewhat fixed, physical extension LocalBusiness - particular physical business or branch of an organization Product - anything that is made available for sale Review - a review of an item What are they Good for? When Google (for example) presents the results of a search, sometimes you get more than just a few lines of text.
    [Show full text]
  • The Webdatacommons Microdata, Rdfa and Microformat Dataset Series
    The WebDataCommons Microdata, RDFa and Microformat Dataset Series Robert Meusel, Petar Petrovski, and Christian Bizer University of Mannheim, Germany Research Group Data and Web Science frobert,petar,[email protected] Abstract. In order to support web applications to understand the con- tent of HTML pages an increasing number of websites have started to annotate structured data within their pages using markup formats such as Microdata, RDFa, Microformats. The annotations are used by Google, Yahoo!, Yandex, Bing and Facebook to enrich search results and to display entity descriptions within their applications. In this paper, we present a series of publicly accessible Microdata, RDFa, Microformats datasets that we have extracted from three large web corpora dating from 2010, 2012 and 2013. Altogether, the datasets consist of almost 30 billion RDF quads. The most recent of the datasets contains amongst other data over 211 million product descriptions, 54 million reviews and 125 million postal addresses originating from thousands of websites. The availability of the datasets lays the foundation for further research on in- tegrating and cleansing the data as well as for exploring its utility within different application contexts. As the dataset series covers four years, it can also be used to analyze the evolution of the adoption of the markup formats. Keywords: Microdata, RDFa, Microformats, Dataset, Web Science 1 Introduction A large number of websites have started to use markup standards to annotate information about products, reviews, blog posts, people, organizations, events, and cooking recipes within their HTML pages. The most prevalent of these standards are Microformats,1 which use style definitions to annotate HTML text with terms from a fixed set of vocabularies; RDFa [1], which is used to embed any kind of RDF data into HTML pages, and Microdata [7], a recent format developed in the context of HTML5.
    [Show full text]
  • Restful Web Apis
    CHAPTER 10 The Hypermedia Zoo There are a lot of hypermedia document formats in active use. Some are designed for very specialized purposes—the people who use them may not even think of them as hypermedia formats. Other hypermedia formats are in such common usage that people don’t really think about them at all. In this chapter, I’ll take you on an educational tour of a “zoo” containing the most popular and most interesting hypermedia formats. I won’t be going into a lot of technical detail. Any one of these formats probably isn’t the one you want to use, and I’ve covered many of them earlier in the book. Many of the formats are still under active development, and their details might change. If you’re interested in one of the zoo’s specimens, the next step is to read its formal specification. My goal is to give you a sense of the many forms hypermedia can take, and to show how many times we’ve tackled the basic problems of representing it. The hypermedia zoo is so full that you probably don’t need to define a brand new media type for your API. You should be able to pick an existing media type and write a profile for it. I’ve organized the hypermedia zoo along the lines of my introduction to hypermedia. There’s a section for domain-specific formats (a la Chapter 5), a section for formats whose primary purpose is to implement the collection pattern (a la Chapter 6), and a section for general hypermedia formats (a la Chapter 7).
    [Show full text]
  • Tagging Techniques for Search Engine Optimization
    Facoltà di Ingegneria Corso di Studi in Ingegneria Informatica Tesi di laurea Tagging techniques for Search Engine Optimization Anno Accademico 2012/2013 relatore Ch.mo prof. Porfirio Tramontana candidato Russo Gianluca matr. M63/90 Facoltà di Ingegneria - Corso di Studi in Ingegneria Informatica Tagging techniques for Search Engine Optimization Contents Introduction 7 Objectives . .9 Chapter organization . 10 1 Context and background 12 1.1 From a Web of documents to a Web of Knowledge . 12 1.1.1 The Internet . 12 1.1.2 World Wide Web . 13 1.1.3 Hyper Text Markup Language - HTML . 15 1.1.4 Extensible Markup Language - XML . 17 1.2 Introduction to Semantic Web . 20 1.3 Semantic Web Architecture . 22 1.4 The principles of the Semantic Web . 26 1.5 Semantic Web Languages . 31 1.5.1 Markup concept . 31 1.5.2 Metadata concept . 32 1.5.3 Resource Description Framework - RDF . 33 1.5.4 Ontology . 35 1.6 Search Engine Optimization - SEO . 36 1 Facoltà di Ingegneria - Corso di Studi in Ingegneria Informatica Tagging techniques for Search Engine Optimization 2 Semantic annotation of Web pages 40 2.1 The basic concepts and related problem . 40 2.1.1 Internal-Embedded annotation . 42 2.1.2 External-Linked annotation . 43 2.1.3 Direct or Manual annotation . 44 2.1.4 Automated annotation . 44 2.2 Technological solutions . 45 2.2.1 Microformats . 46 2.2.2 RDFa . 49 2.2.3 Microdata . 52 2.2.4 Schema.org . 54 2.3 Technological choices . 56 3 MicrodataSemantic tool 60 3.1 Motivation and Overview .
    [Show full text]