DOCSLIB.ORG

Semantic Web

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Semantic Web Web of Data © Copyright 2010 Dieter Fensel and Tobias Buerger www.sti-innsbruck.at 1 Where are we? # Title 1 Introduction 2 Semantic Web Architecture 3 Resource Description Framework (RDF) 4 Web of data 5 Generating Semantic Annotations 6 Storage and Querying 7 Web Ontology Language (OWL) 8 Rule Interchange Format (RIF) 9 Reasoning on the Web 10 Ontologies 11 Social Semantic Web 12 Semantic Web Services 13 Tools 14 Applications www.sti-innsbruck.at 2 Agenda 1. Motivation 2. “Building” the Web of Data by publishing structured data on the Web 2.1 Embedding structured information in Web pages • Technical solution – Microformats – RDFa – GRDDL • Example: Yahoo SearchMonkey • Extensions and current developments: Microdata in HTML5 2.2 Linked Data • Technical solution – Principles – Publishing and consuming Linked Data – Adding legacy data to the Web of Data • Examples: Linked Data applications • Extensions and current developments: Multimedia Interlinking 3. Summary 4. References www.sti-innsbruck.at 3 3 MOTIVATION www.sti-innsbruck.at 4 4 Evolution of the Web: The Origins Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 5 5 Evolution of the Web: The Origins Web of Data As We May Think (1945): •Introduc@on of the Memex. •Memex was envisioned to provide access to Semantic Web huge collec@ons of text in which people could Picture from [4] follow trails of links and notes. ? •Memex is widely known as the pre-cursor of Web SocialSemantic Web the Hypertext movement. (WebAnnotations 2.0) Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 6 6 Evolution of the Web WebHypertext: of Data •Term coined 1965 by Ted Nelson •Defini@on: A hypertext is an organisa@on of objects in a highly connected fashion Semantic Web •Characteris@c elements: Nodes (e.g., text Picture from [4] parts) and hyperlinks (logical connec@ons ? between nodes) Web Semantic •Further people: John Lickleder, Douglas Annotations HypermediaEnglbart Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 7 7 Evolution of Hypertext: Hypermedia Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 8 Evolution of the Web Hypermedia: Web of Data •Evolu@on of the hypertext idea •Novelty: Mul@media aspects; i.e., mul@media resources might be part of interlinked structure Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 9 9 Evolution of Hypermedia: the Web Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 10 10 Evolution of the Web Web of Data Web: •Exemplary hypermedia system Semantic Web •Proposed by Tim-Berners-Lee in 1990 Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 11 11 Evolution of the Web: The Semantic Web Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 12 12 Evolution of the Web Web of Data Seman>c Web: •Vision advocated by Tim Berners Lee. Semantic Web •Contents have well-defined meaning. Picture from [4] •Backbone: formal ontologies allowing agents ? to draw automa@c conclusions. Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 13 13 Evolution of the Web: Web 2.0 Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 14 Evolution of the Web: Semantic Annotations Web of Data Seman>c Annota>ons: •Annota@ons are generated for the exis@ng Web Semantic Web Picture from [4]• Genera@on automa@c, semi-automa@c, or ? manually based on human input •See following lecture. Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 15 15 Evolution of the Web: Web of Data Web of Data Semantic Web Picture from [4] ? Web Semantic Annotations Hypermedia Hypertext “As We May Think”, 1945 Picture from [3] www.sti-innsbruck.at 16 16 Motivation: From a Web of Documents to a Web of Data • Web of Documents • Fundamental elements: 1. Names (URIs) 2. Documents (Resources) described by HTML, XML, etc. 3. Interactions via HTTP Hyperlinks 4. (Hyper)Links between documents or anchors in these documents • Shortcomings: – Untyped links “Documents” – Web search engines fail on complex queries www.sti-innsbruck.at 17 17 Motivation: From a Web of Documents to a Web of Data • Web of Documents • Web of Data Typed Links Hyperlinks “Documents” “Things” www.sti-innsbruck.at 18 18 Motivation: From a Web of Documents to a Web of Data • Characteristics: • Web of Data – Links between arbitrary things (e.g., persons, locations, Typed Links events, buildings) – Structure of data on Web pages is made explicit – Things described on Web pages are named and get URIs – Links between things are made explicit and are typed “Things” www.sti-innsbruck.at 19 19 Vision of the Web of Data • The Web today • The Web of Data is envisioned as – Consists of data silos which can be a global database accessed via specialized search egines in an isoltated fashion. – consisting of objects and their – One site (data silo) has movies, the descriptions other reviews, again another actors. – in which objects are linked with – Many common things are represented each other in multiple data sets – Linking identifiers link these data sets – with a high degree of object structure – with explicit semantics for links and content – which is designed for humans and machines Content on this slide by Chris Bizer, Tom Heath and Tim Berners-Lee www.sti-innsbruck.at 20 20 BUILDING THE WEB OF DATA BY PUBLISHING STRUCTURED DATA ON THE WEB www.sti-innsbruck.at 21 21 How to “Build” the Web of Data? • Publish structured data by 1. using Web (2.0) APIs [5] (will be discussed in the Lecture on “Service Web”) 2. embedding structured information (Microformats, RDFa, GRDDL) 3. linking data [6] [2] [7] [4] www.sti-innsbruck.at 22 22 2.1 EMBEDDING STRUCTURED INFORMATION IN WEB PAGES www.sti-innsbruck.at 23 23 Microformats Recommended literature: [6], [8] www.sti-innsbruck.at 24 24 What are Microformats? • An approach to add meaning to HTML elements and to make data structures in HTML pages explicit. • “Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviours and usage patterns (e.g. XHTML, blogging).” [6] www.sti-innsbruck.at 25 25 What are Microformats? /2 • Are highly correlated with semantic (X)HTML / “Real world semantics” / “Lowercase Semantic Web” [9]. • Real world semantics (or the Lowercase Semantic Web) is based on three notions: – Adding of simple semantics with microformats (small pieces) – Adding semantics to the today’s Web instead of creating a new one (evolutionary not revolutionary) – Design for humans first and machines second (user centric design) • A way to combine human with machine-readable information. • Provide means to embed structured data in HTML pages. • Build upon existing standards. • Solve a single, specific problem (e.g. representation of geographical information, calendaring information, etc.). • Provide an “API” for your website. • Build on existing (X)HTML and reuse existing elements. • Work in current browsers. • Follow the DRY principle (“Don’t Repeat Yourself”). • Compatible with the idea of the Web as a single information space. www.sti-innsbruck.at 26 26 Microformats Illustrated Example adapted from Chris Griego www.sti-innsbruck.at 27 27 Design Patterns • Microformats can be seen as design patterns that make structure and semantics of data explicit. • Elemental microformats (consist of just one tag) – Rel-home links to homepage <link href="http://technorati.com" rel="home" /> – Rel-License links to content license <a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by2.0</a> – Others: rel-tag, rel-encluse, xfn-tags • Compound microformats (more complex structures) – Often based on existing standard – E.g. hCard, hCalendar, hEvent, hReview Picture from [6] www.sti-innsbruck.at 28 28 Syntax • Microformats use existing HTML attributes to embed structured data types in an HTML document and to indicate the presence of metadata • Rel/rev-attribute is used for elemental microformts, e.g., <a href=“http://technorati.com/tag/semantics” rel=“tag”>semantics</a> expresses that the current page is “tagged” with “semantics” • Class-attribute is used for compound microformats, e.g. <span class=“geo”><span class=“latitude”>23.44</span><span class=“longitude”>44.33</span><span> expresses that a given data block contains geo-coordinates (longitude/ latitude) www.sti-innsbruck.at 29 29 Expressive Power • Microformats extends the expressive power of HTML. • Expressive power is limited as microformats are only designed to use pre-defined vocabularies to mark up content in Web pages using different HTML attributes. www.sti-innsbruck.at 30 30 Usage: Compound Microformat hCard • hCard is a simple format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard (RFC2426). BEGIN: VCARD VERSION: 3 FN: Dieter Fensel ORG: STI Innsbruck … URL: http://www.sti-innsbruck.at TEL: +43 512 507 9872 END: VCARD Example on this slide by Alexander Graf www.sti-innsbruck.at 31 31 Usage: Compound Microformat hCard: hCard /2 • hCard is a simple format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard (RFC2426).
Recommended publications
  • Privacy Protection for Smartphones: an Ontology-Based Firewall Johanne Vincent, Christine Porquet, Maroua Borsali, Harold Leboulanger

    Privacy Protection for Smartphones: an Ontology-Based Firewall Johanne Vincent, Christine Porquet, Maroua Borsali, Harold Leboulanger

    Privacy Protection for Smartphones: An Ontology-Based Firewall Johanne Vincent, Christine Porquet, Maroua Borsali, Harold Leboulanger To cite this version: Johanne Vincent, Christine Porquet, Maroua Borsali, Harold Leboulanger. Privacy Protection for Smartphones: An Ontology-Based Firewall. 5th Workshop on Information Security Theory and Prac- tices (WISTP), Jun 2011, Heraklion, Crete, Greece. pp.371-380, 10.1007/978-3-642-21040-2_27. hal-00801738 HAL Id: hal-00801738 https://hal.archives-ouvertes.fr/hal-00801738 Submitted on 18 Mar 2013 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 Privacy Protection for Smartphones: An Ontology-Based Firewall Johann Vincent, Christine Porquet, Maroua Borsali, and Harold Leboulanger GREYC Laboratory, ENSICAEN - CNRS University of Caen-Basse-Normandie, 14000 Caen, France {johann.vincent,christine.porquet}@greyc.ensicaen.fr, {maroua.borsali,harold.leboulanger}@ecole.ensicaen.fr Abstract. With the outbreak of applications for smartphones, attempts to collect personal data without their user’s consent are multiplying and the protection of users privacy has become a major issue. In this paper, an approach based on semantic web languages (OWL and SWRL) and tools (DL reasoners and ontology APIs) is described.
  • Interaction Between Web Browsers and Script Engines

    Interaction Between Web Browsers and Script Engines

    IT 12 058 Examensarbete 45 hp November 2012 Interaction between web browsers and script engines Xiaoyu Zhuang Institutionen för informationsteknologi Department of Information Technology Abstract Interaction between web browser and the script engine Xiaoyu Zhuang Teknisk- naturvetenskaplig fakultet UTH-enheten Web browser plays an important part of internet experience and JavaScript is the most popular programming language as a client side script to build an active and Besöksadress: advance end user experience. The script engine which executes JavaScript needs to Ångströmlaboratoriet Lägerhyddsvägen 1 interact with web browser to get access to its DOM elements and other host objects. Hus 4, Plan 0 Browser from host side needs to initialize the script engine and dispatch script source code to the engine side. Postadress: This thesis studies the interaction between the script engine and its host browser. Box 536 751 21 Uppsala The shell where the engine address to make calls towards outside is called hosting layer. This report mainly discussed what operations could appear in this layer and Telefon: designed testing cases to validate if the browser is robust and reliable regarding 018 – 471 30 03 hosting operations. Telefax: 018 – 471 30 00 Hemsida: http://www.teknat.uu.se/student Handledare: Elena Boris Ämnesgranskare: Justin Pearson Examinator: Lisa Kaati IT 12 058 Tryckt av: Reprocentralen ITC Contents 1. Introduction................................................................................................................................
  • Semantics Developer's Guide

    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
  • Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing

    Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing

    RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing A collection of attributes and processing rules for extending XHTML to support RDF W3C Recommendation 14 October 2008 This version: http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014 Latest version: http://www.w3.org/TR/rdfa-syntax Previous version: http://www.w3.org/TR/2008/PR-rdfa-syntax-20080904 Diff from previous version: rdfa-syntax-diff.html Editors: Ben Adida, Creative Commons [email protected] Mark Birbeck, webBackplane [email protected] Shane McCarron, Applied Testing and Technology, Inc. [email protected] Steven Pemberton, CWI Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported - 1 - How to Read this Document RDFa in XHTML: Syntax and Processing into a user’s desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo’s creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.
  • Using Rule-Based Reasoning for RDF Validation

    Using Rule-Based Reasoning for RDF Validation

    Using Rule-Based Reasoning for RDF Validation Dörthe Arndt, Ben De Meester, Anastasia Dimou, Ruben Verborgh, and Erik Mannens Ghent University - imec - IDLab Sint-Pietersnieuwstraat 41, B-9000 Ghent, Belgium [email protected] Abstract. The success of the Semantic Web highly depends on its in- gredients. If we want to fully realize the vision of a machine-readable Web, it is crucial that Linked Data are actually useful for machines con- suming them. On this background it is not surprising that (Linked) Data validation is an ongoing research topic in the community. However, most approaches so far either do not consider reasoning, and thereby miss the chance of detecting implicit constraint violations, or they base them- selves on a combination of dierent formalisms, eg Description Logics combined with SPARQL. In this paper, we propose using Rule-Based Web Logics for RDF validation focusing on the concepts needed to sup- port the most common validation constraints, such as Scoped Negation As Failure (SNAF), and the predicates dened in the Rule Interchange Format (RIF). We prove the feasibility of the approach by providing an implementation in Notation3 Logic. As such, we show that rule logic can cover both validation and reasoning if it is expressive enough. Keywords: N3, RDF Validation, Rule-Based Reasoning 1 Introduction The amount of publicly available Linked Open Data (LOD) sets is constantly growing1, however, the diversity of the data employed in applications is mostly very limited: only a handful of RDF data is used frequently [27]. One of the reasons for this is that the datasets' quality and consistency varies signicantly, ranging from expensively curated to relatively low quality data [33], and thus need to be validated carefully before use.
  • Semantic Web and Services

    Semantic Web and Services

    Where are we? Artificial Intelligence # Title 1 Introduction 2 Propositional Logic 3 Predicate Logic 4 Reasoning 5 Search Methods Semantic Web and 6 CommonKADS 7 Problem-Solving Methods 8 Planning Services 9 Software Agents 10 Rule Learning 11 Inductive Logic Programming 12 Formal Concept Analysis 13 Neural Networks 14 Semantic Web and Services © Copyright 2010 Dieter Fensel, Mick Kerrigan and Ioan Toma 1 2 Agenda • Semantic Web - Data • Motivation • Development of the Web • Internet • Web 1.0 • Web 2.0 • Limitations of the current Web • Technical Solution: URI, RDF, RDFS, OWL, SPARQL • Illustration by Larger Examples: KIM Browser Plugin, Disco Hyperdata Browser • Extensions: Linked Open Data • Semantic Web – Processes • Motivation • Technical Solution: Semantic Web Services, WSMO, WSML, SEE, WSMX SEMANTIC WEB - DATA • Illustration by Larger Examples: SWS Challenge, Virtual Travel Agency, WSMX at work • Extensions: Mobile Services, Intelligent Cars, Intelligent Electricity Meters • Summary • References 3 3 4 4 1 MOTIVATION DEVELOPMENT OF THE WEB 5 5 6 Development of the Web 1. Internet 2. Web 1.0 3. Web 2.0 INTERNET 7 8 2 Internet A brief summary of Internet evolution Age of eCommerce Mosaic Begins WWW • “The Internet is a global system of interconnected Internet Created 1995 Created 1993 Named 1989 computer networks that use the standard Internet and Goes Protocol Suite (TCP/IP) to serve billions of users TCP/IP TCP/IP Created 1984 ARPANET 1972 worldwide. It is a network of networks that consists of 1969 Hypertext millions of private
  • Mapping Between Digital Identity Ontologies Through SISM

    Mapping Between Digital Identity Ontologies Through SISM

    Mapping between Digital Identity Ontologies through SISM Matthew Rowe The OAK Group, Department of Computer Science, University of Sheffield, Regent Court, 211 Portobello Street, Sheffield S1 4DP, UK [email protected] Abstract. Various ontologies are available defining the semantics of dig- ital identity information. Due to the rise in use of lowercase semantics, such ontologies are now used to add metadata to digital identity informa- tion within web pages. However concepts exist in these ontologies which are related and must be mapped together in order to enhance machine- readability of identity information on the web. This paper presents the Social identity Schema Mapping (SISM) vocabulary which contains a set of mappings between related concepts in distinct digital identity ontolo- gies using OWL and SKOS mapping constructs. Key words: Semantic Web, Social Web, SKOS, OWL, FOAF, SIOC, PIMO, NCO, Microformats 1 Introduction The semantic web provides a web of machine-readable data. Ontologies form a vital component of the semantic web by providing conceptualisations of domains of knowledge which can then be used to provide a common understanding of some domain. A basic ontology contains a vocabulary of concepts and definitions of the relationships between those concepts. An agent reading a concept from an ontology can look up the concept and discover its properties and characteristics, therefore interpreting how it fits into that particular domain. Due to the great number of ontologies it is common for related concepts to be defined in separate ontologies, these concepts must be identified and mapped together. Web technologies such as Microformats, eRDF and RDFa have allowed web developers to encode lowercase semantics within XHTML pages.
  • INPUT CONTRIBUTION Group Name:* MAS WG Title:* Semantic Web Best Practices

    INPUT CONTRIBUTION Group Name:* MAS WG Title:* Semantic Web Best Practices

    Semantic Web best practices INPUT CONTRIBUTION Group Name:* MAS WG Title:* Semantic Web best practices. Semantic Web Guidelines for domain knowledge interoperability to build the Semantic Web of Things Source:* Eurecom, Amelie Gyrard, Christian Bonnet Contact: Amelie Gyrard, [email protected], Christian Bonnet, [email protected] Date:* 2014-04-07 Abstract:* This contribution proposes to describe the semantic web best practices, semantic web tools, and existing domain ontologies for uses cases (smart home and health). Agenda Item:* Tbd Work item(s): MAS Document(s) Study of Existing Abstraction & Semantic Capability Enablement Impacted* Technologies for consideration by oneM2M. Intended purpose of Decision document:* Discussion Information Other <specify> Decision requested or This is an informative paper proposed by the French Eurecom institute as a recommendation:* guideline to MAS contributors on Semantic web best practices, as it was suggested during MAS#9.3 call. Amélie Gyrard is a new member in oneM2M (via ETSI PT1). oneM2M IPR STATEMENT Participation in, or attendance at, any activity of oneM2M, constitutes acceptance of and agreement to be bound by all provisions of IPR policy of the admitting Partner Type 1 and permission that all communications and statements, oral or written, or other information disclosed or presented, and any translation or derivative thereof, may without compensation, and to the extent such participant or attendee may legally and freely grant such copyright rights, be distributed, published, and posted on oneM2M’s web site, in whole or in part, on a non- exclusive basis by oneM2M or oneM2M Partners Type 1 or their licensees or assignees, or as oneM2M SC directs.
  • Wiki Semantics Via Wiki Templating

    Wiki Semantics Via Wiki Templating

    Chapter XXXIV Wiki Semantics via Wiki Templating Angelo Di Iorio Department of Computer Science, University of Bologna, Italy Fabio Vitali Department of Computer Science, University of Bologna, Italy Stefano Zacchiroli Universitè Paris Diderot, PPS, UMR 7126, Paris, France ABSTRACT A foreseeable incarnation of Web 3.0 could inherit machine understandability from the Semantic Web, and collaborative editing from Web 2.0 applications. We review the research and development trends which are getting today Web nearer to such an incarnation. We present semantic wikis, microformats, and the so-called “lowercase semantic web”: they are the main approaches at closing the technological gap between content authors and Semantic Web technologies. We discuss a too often neglected aspect of the associated technologies, namely how much they adhere to the wiki philosophy of open editing: is there an intrinsic incompatibility between semantic rich content and unconstrained editing? We argue that the answer to this question can be “no”, provided that a few yet relevant shortcomings of current Web technologies will be fixed soon. INTRODUCTION Web 3.0 can turn out to be many things, it is hard to state what will be the most relevant while still debating on what Web 2.0 [O’Reilly (2007)] has been. We postulate that a large slice of Web 3.0 will be about the synergies between Web 2.0 and the Semantic Web [Berners-Lee et al. (2001)], synergies that only very recently have begun to be discovered and exploited. We base our foresight on the observation that Web 2.0 and the Semantic Web are converging to a common point in their initially split evolution lines.
  • Hidden Meaning

    Hidden Meaning

    FEATURES Microdata and Microformats Kit Sen Chin, 123RF.com Chin, Sen Kit Working with microformats and microdata Hidden Meaning Programs aren’t as smart as humans when it comes to interpreting the meaning of web information. If you want to maximize your search rank, you might want to dress up your HTML documents with microformats and microdata. By Andreas Möller TML lets you mark up sections formats and microdata into your own source code for the website shown in of text as headings, body text, programs. Figure 1 – an HTML5 document with a hyperlinks, and other web page business card. The Heading text block is H elements. However, these defi- Microformats marked up with the element h1. The text nitions have nothing to do with the HTML was originally designed for hu- for the business card is surrounded by meaning of the data: Does the text refer mans to read, but with the explosive the div container element, and <br/> in- to a person, an organization, a product, growth of the web, programs such as troduces a line break. or an event? Microformats [1] and their search engines also process HTML data. It is easy for a human reader to see successor, microdata [2] make the mean- What do programs that read HTML data that the data shown in Figure 1 repre- ing a bit more clear by pointing to busi- typically find? Listing 1 shows the HTML sents a business card – even if the text is ness cards, product descriptions, offers, and event data in a machine-readable LISTING 1: HTML5 Document with Business Card way.
  • Le Microformat Hproduct C'est Quoi ? Pourquoi Utiliser Le Microformat

    Le Microformat Hproduct C'est Quoi ? Pourquoi Utiliser Le Microformat

    Apprendre à utiliser les microformats : hProduct 2017-02-21 23:02:01 Nicolaseo Le microformat hProduct c’est quoi ? hProduct est un microformat approprié pour publier et embarquer les données de vos produits. C’est une sorte de méta tags qui permet de structurer vos données pour permettre aux robots des moteurs de recherche de mieux référencer votre contenu. Pourquoi utiliser le microformat hProduct Le microformat hProduct est basé sur un ensemble de champs très important pour communiquer avec les robots des moteurs de recherche comme Google. Utiliser les {meta- tags|richsnippets|microformats} (et tout ce qui peut permettre aux moteurs de recherche de mieux classer votre contenu) vous apportera plus de visibilité sur internet grâce à un meilleur référencement de votre site et de son contenu. Comment utiliser le microformat hProduct Le schéma hProduct se compose de ce qui suit : hproduct brand. optionnel. texte. peut aussi utiliser hCard pour les fabricants. category. optionnel. texte. peut aussi utiliser rel-tag. ré-utilisé à partir de hCard. price. optionnel. floating point number. peut utiliser un format de devise. description. optionnel. texte. peut aussi inclure un marquage HTML valide. réutilisé à partir de hReview. fn. requis. texte. nom du produit ou titre. réutilisé de hCard. photo. optionnel. élément image ou lien. réutilisé de hCard. url. optionnel. href. peut contenir rel-tag rel=’product’. ré-utilisé de hCard. review. optionnel. hReview, ou hReview-aggregate. listing. optionnel. hListing, ou hListing-aggregate. identifier. optionnel. type. requis. – exemples : model mpn upc isbn issn ean jan sn vin sku value. requis. – l’étiquette peut être implicite. Détails des champs du microformat hProduct Les noms de classe category, fn, photo, url sont réutilisés à partir de hCard.
  • 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

    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.