DOCSLIB.ORG

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

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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. description est réutilisé à partir de hReview. Les champs du schéma hProduct représentent ce qui suit : hproduct:: Nom de classe racine brand:: Le nom de classe brand est utilisé pour identifier la marque du produit. DEVRAIT utiliser hCard pour le nom du fabricant. DOIT être singulier. category:: le nom de classe identifie la catégorie produit. PEUT utiliser le microformat rel-tag. PEUT être pluriel pour représenter plusieurs catégories. price:: le nom de classe price est utilisé pour indiquer le prix du produit. DOIT être singulier. description:: le nom de classe description est utilisé pour décrire le produit. DOIT être singulier. fn:: nom du produit en texte. DOIT être singulier. photo:: le nom de classe photo PEUT être appliqué à un élément <img> ou <a>. PEUT être pluriel. url:: le nom de classe url DEVRAIT faire référence à la page web associée avec les détails produits. PEUT utiliser rel-tag, rel=’product’. DOIT être singulier. review:: le nom de classe review identifie les avis pour le produit. DEVRAIT utiliser hReview. PEUT être pluriel. listing:: le nom de classe listing identifie les listings de produits. DEVRAIT utiliser hListing. PEUT être pluriel. identifier:: la structure identifier est utilisée pour décrire les identifiants produits comme Model, UPC ou SKU, et elle est conçue pour s’adapter aux nouveaux identifiants ou non-identifiés-à-cette-heure. DEVRAIT être singulier. type:: le nom de classe type identifie le type d’identifiant. value:: label PEUT être implicite Ce que dit Google à propos du balisage de produit L’utilisation de balisage permet à Google de créer des résultats de recherche plus riche et vous permet d’attirer les acheteurs potentiels lorsqu’ils sont à la recherche d’objets à acheter sur Google ou des images qui comprennent des produits que vous vendez. Maintenir l’exactitude et la fraîcheur de vos informations de produit, de sorte que vos clients vont trouver les articles pertinents qu’ils recherchent. Il existe deux types de pages où vous souhaitez généralement utiliser ce balisage: une page de produit qui décrit un seul produit une page shopping aggrégateur qui répertorie un seul produit , ainsi que des informations sur les différents vendeurs offrant ce produit Des lignes directrices Les résultats riches des produits fournissent aux utilisateurs des informations sur un produit spécifique, comme ses notes, son prix, sa disponibilité etc…. Les directives suivantes sont applicables au balisage de produit : Utilisez des marqueurs pour un produit spécifique, pas une catégorie ou d’une liste de produits. Par exemple, “chaussures dans notre boutique” est pas un produit spécifique. Voir aussi nos politiques de données structurées pour plusieurs entités sur la même page. Produits liés adultes-ne sont pas pris en charge . Le nom de l’ évaluateur doit être un nom valide pour une personne ou de l’ équipe , par exemple, «James Smith» ou «CNET examinateurs.” En revanche, “50% de rabais sur Black Friday” est invalide. Pour inclure des informations de produit Recherche d’images, suivez ces instructions pour le balisage nécessaire: Pour afficher vos informations de produit dans la riche visionneuse d’ image: Inclure les name, image, priceet priceCurrencypropriétés. Sinon, au lieu de priceet priceCurrency, vous pouvez inclure les quatre propriétés et d’ exclure price. Pour afficher vos informations de produit dans les Articles connexes en vedette: Inclure les name, image, price, priceCurrency, et availabilitypropriétés. Les définitions de type propriétés de l’information sur le produit Lorsque vous marquez votre contenu pour des informations, utilisez les propriétés suivantes du schema.org produitType: Propriétés Texte , nécessaire name Le nom du produit. URL , nécessaire pour Recherche, recommandé pour la recherche image L’URL d’une photo du produit. Photos montrant clairement le produit, par exemple sur un fond blanc, sont préférés. Texte , recommandé description Description du produit. Texte , recommandé brand La marque du produit. Review , recommandé review Un examen imbriquée du produit. AggregateRating , recommandé aggregateRating Un aggregateRating imbriquée du produit. Offre , recommandée offers Une offre de vendre le produit. Comprend une offre imbriquée ou AggregateOffer. Texte , recommandé sku | gtin8 | Diverses propriétésP dro’idperniétitféicsation; ceux – ci sont décrites au gtin13 |gtin14 schema.org/Product . Google recommande d’ inclure la marque et au | mpn moins un identifiant pour chaque produit. Propriétés de l’offre Lors du marquage des offres dans un produit, utilisez les propriétés suivantes du schema.org Offre Type: Propriétés Nombre , nécessaire price Le prix du produit. Suivez les directives d’utilisation schema.org . Texte , nécessaire priceCurrency La monnaie utilisée pour décrire le prix du produit, en trois lettres ISO 4217 le format. Date de recommandé La date ( ISO 8601 format de date) , après quoi le prix ne sera plus priceValidUntil disponible. (Votre extrait de produit ne peut pas afficher si la priceValidUtilpropriété indique une date antérieure.) ItemAvailability , nécessaire pour Articles connexes disposent en Recherche d’ images, recommandé pour la recherche La valeur est prise à partir d’ une liste restreinte d’options, exprimée availability dans le balisage en utilisant les liens URL. Google comprend aussi leurs noms courts (par exemple InStockou OutOfStock, sans le champ d’adresse URL complète.) URL , recommandée url Une URL de la page Web du produit (qui inclut l’offre). Chose , recommandée L’ordre du jour étant épuisé. Typiquement, cela inclut un produit itemOffered imbriqué, mais elle peut aussi contenir d’autres types de texte libre ou élément. Aggregate propriétés offrent Un AggregateOfferest une sorte d’offre qui représente une agrégation d’autres offres. Lors du marquage des offres globales dans un produit, utilisez les propriétés suivantes du schema.org AggregateOffer Type: Propriétés Nombre , nécessaire lowPrice Le prix le plus bas de toutes les offres disponibles. Nombre à virgule flottante. Nombre recommandé Le prix le plus élevé deP rtouptreisé tlées offres disponibles. Nombre à virgule highPrice flottante. Texte , nécessaire priceCurrency La monnaie utilisée pour décrire le prix du produit, en trois lettres ISO 4217 le format. Nombre recommandé offerCount Le nombre d’offres pour le produit. Ajouter un balisage à vos pages produits afin que Google peut fournir des informations détaillées sur les produits dans les Résultats de la recherche – y compris Recherche d’images. Les utilisateurs peuvent voir les prix, la disponibilité, et examiner les notes à droite sur les résultats de la recherche. Vous l’aurez donc compris utiliser les microformats est très important pour votre succès ;).
Load more

Recommended publications
  • Requirements, Design and Applications to Semantic Integration and Knowledge Discovery
    Practical Ontologies: Requirements, Design and Applications to Semantic Integration and Knowledge Discovery by Daniela Rosu A thesis submitted in conformity with the requirements for the degree of Doctor of Philosophy Graduate Department of Computer Science University of Toronto © Copyright by Daniela Rosu 2013 Practical Ontologies: Requirements, Design and Applications to Semantic Integration and Knowledge Discovery Daniela Rosu Doctor of Philosophy Graduate Department of Computer Science University of Toronto 2013 Abstract Due to their role in describing the semantics of information, knowledge representations, from formal ontologies to informal representations such as folksonomies, are becoming increasingly important in facilitating the exchange of information, as well as the semantic integration of information systems and knowledge discovery in a large number of areas, from e-commerce to bioinformatics. In this thesis we present several studies related to the development and application of knowledge representations, in the form of practical ontologies. In Chapter 2, we examine representational challenges and requirements for describing practical domain knowledge. We present representational requirements we collected by surveying current and potential ontology users, discuss current approaches to codifying knowledge and give formal representation solutions to some of the issues we identified. In Chapter 3 we introduce a practical ontology for representing data exchanges, discuss its relationship with existing standards and its role in facilitating the interoperability between information producing and consuming services. ii We also consider the problem of assessing similarity between ontological concepts and propose three novel measures of similarity, detailed in Chapter 4. Two of our proposals estimate semantic similarity between concepts in the same ontology, while the third measures similarity between concepts belonging to different ontologies.
    [Show full text]
  • 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.
    [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]
  • Microformats the Next (Small) Thing on the Semantic Web?
    Standards Editor: Jim Whitehead • [email protected] Microformats The Next (Small) Thing on the Semantic Web? Rohit Khare • CommerceNet “Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.” — Microformats.org hen we speak of the “evolution of the is precisely encoding the great variety of person- Web,” it might actually be more appropri- al, professional, and genealogical relationships W ate to speak of “intelligent design” — we between people and organizations. By contrast, can actually point to a living, breathing, and an accidental challenge is that any blogger with actively involved Creator of the Web. We can even some knowledge of HTML can add microformat consult Tim Berners-Lee’s stated goals for the markup to a text-input form, but uploading an “promised land,” dubbed the Semantic Web. Few external file dedicated to machine-readable use presume we could reach those objectives by ran- remains forbiddingly complex with most blog- domly hacking existing Web standards and hop- ging tools. ing that “natural selection” by authors, software So, although any intelligent designer ought to developers, and readers would ensure powerful be able to rely on the long-established facility of enough abstractions for it. file transfer to publish the “right” model of a social Indeed, the elegant and painstakingly inter- network, the path of least resistance might favor locked edifice of technologies, including RDF, adding one of a handful of fixed tags to an exist- XML, and query languages is now growing pow- ing indirect form — the “blogroll” of hyperlinks to erful enough to attack massive information chal- other people’s sites.
    [Show full text]
  • Data Models for Home Services
    __________________________________________PROCEEDING OF THE 13TH CONFERENCE OF FRUCT ASSOCIATION Data Models for Home Services Vadym Kramar, Markku Korhonen, Yury Sergeev Oulu University of Applied Sciences, School of Engineering Raahe, Finland {vadym.kramar, markku.korhonen, yury.sergeev}@oamk.fi Abstract An ultimate penetration of communication technologies allowing web access has enriched a conception of smart homes with new paradigms of home services. Modern home services range far beyond such notions as Home Automation or Use of Internet. The services expose their ubiquitous nature by being integrated into smart environments, and provisioned through a variety of end-user devices. Computational intelligence require a use of knowledge technologies, and within a given domain, such requirement as a compliance with modern web architecture is essential. This is where Semantic Web technologies excel. A given work presents an overview of important terms, vocabularies, and data models that may be utilised in data and knowledge engineering with respect to home services. Index Terms: Context, Data engineering, Data models, Knowledge engineering, Semantic Web, Smart homes, Ubiquitous computing. I. INTRODUCTION In recent years, a use of Semantic Web technologies to build a giant information space has shown certain benefits. Rapid development of Web 3.0 and a use of its principle in web applications is the best evidence of such benefits. A traditional database design in still and will be widely used in web applications. One of the most important reason for that is a vast number of databases developed over years and used in a variety of applications varying from simple web services to enterprise portals. In accordance to Forrester Research though a growing number of document, or knowledge bases, such as NoSQL is not a hype anymore [1].
    [Show full text]
  • Microformats Cheat Sheet
    Elemental Microformats Design Patterns tom eview Datetime Pattern esume XFN VoteLinks microformats.org hR hR hCard hCalendar rel="contact" rel="parent" rev="vote-for" <abbr hA rel="acquaintance" rel="spouse" class="foo" • adr rev="vote-against" + country-name title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ" rel="friend" rel="kin" rev="vote-abstain" • extended-address rel="met" rel="muse" >Human Date Time</abbr> + post-office-box rel="co-worker" rel="crush" Rel-Nofollow + postal-code rel="colleague" rel="date" rel="nofollow" Include Pattern • street-address + locality rel="co-resident" rel="sweetheart" <object Rel-Tag class="include" + region rel="neighbor" rel="me" rel="tag" • type rel="child" type="text/html" • affiliation Rel-Directory (Draft) data="#idref" ¤ author rel="directory" /> + best × + bookmark (rel) Rel-License + bday <a class="include" • • category rel="license" href="#idref">...</a> + + class × contact Compound Microformats + description + dtend + dtreviewed hCard hCalendar hResume (Draft) × dtstart class="vcard" class="vevent" class="hresume" × dtstamp class="adr" class="category" rel="tag" class="affiliation" (hcard) duration class="type" class="class" class="education" (hcalendar) • education [work|home|pref|postal|dom|intl] class="description" • email class="experience" (hcalendar) • type class="post-office-box" class="dtend" (ISO Date) class="publication" (citation) • value class="street-address" class="dtstamp" (ISO Date) class="skill" rel="tag" × entry-content class="extended-address" class="dtstart" (ISO Date) class="summary" • entry-summary
    [Show full text]
  • Microformats: Empowering Your Markup for Web 2.0
    Microformats: Empowering Your Markup for Web 2.0 John Allsopp Microformats: Empowering Your Markup for Web 2.0 Copyright © 2007 by John Allsopp All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-59059814-6 ISBN-10 (pbk): 1-59059-814-8 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013. Phone 1-800-SPRINGER, fax 201-348-4505, e-mail [email protected],or visit www.springeronline.com. For information on translations, please contact Apress directly at 2560 Ninth Street, Suite 219, Berkeley, CA 94710. Phone 510-549-5930, fax 510-549-5939, e-mail [email protected], or visit www.apress.com. The information in this book is distributed on an “as is” basis, without warranty. Although every precaution has been taken in the preparation of this work, neither the author(s) nor Apress 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 information contained in this work.
    [Show full text]
  • Rdfa Versus Microformats: Exploring the Potential for Semantic Interoperability of Mash-Up Personal Learning Environments
    RDFa versus Microformats: Exploring the Potential for Semantic Interoperability of Mash-up Personal Learning Environments Vladimir Tomberg, Mart Laanpere Tallinn University, Narva mnt. 25, 10120 Tallinn, Estonia [email protected], [email protected] Abstract. This paper addresses the possibilities for increasing semantic interoperability of mash-up learning environments through the use of automatically processed metadata associated with both learning resources and learning process. We analyze and compare potential of two competing technologies for this purpose: microformats and RDFa. 1 Introduction Mash-up Personal Learning Environments have become a fast developing trend in the world of technology-enhanced learning, partly because of their flexibility and lightweight integration features. Although it is quite easy to aggregate the RSS feeds from the blogs of learners, it is more difficult to get an overview of course and its learning activities. A course is not just a syllabus, it also involves various dynamic processes that can be described in many aspects. The course always has certain learning goals, a schedule that consists learning activities (assignments, discussions), registered participants like teachers and students, and different types of resources. It would be useful, if we would be able to extract such information also from mash-up personal learning environments (just like it can be done in traditional Learning Management Systems) and allow exchanging it between the course participants. Today for semantic tagging of Web content in general and learning content as special case various technologies are used. But there are no tools and ways exist for semantic annotation of learning process that takes place in a distributed network of mash-up personal learning environments.
    [Show full text]
  • From Atom's to OWL S: the New Ecology of The
    mindswap maryland information and network dynamics lab semantic web agents project From Atom's to OWL's: The new ecology of the WWW Jim Hendler [email protected] http://www.cs.umd.edu/~hendler mindswap maryland information and network dynamics lab semantic web agents project From Atom*s to OWL§s: The new ecology of the WWW Jim Hendler [email protected] http://www.cs.umd.edu/~hendler * syntax § semantics mindswap maryland information and network dynamics lab semantic web agents project Syntax to Semantics mindswap maryland information and network dynamics lab semantic web agents project Acknowledgements • In preparing this talk I have mostly ignored the advice of a great many people including Tim Berners-Lee, Dan Connolly, Wendy Hall, Eric Miller, Brand Nieman, Bijan Parsia, Guus Schreiber, Nigel Shadbolt, and Frank VanHarmelen • I owe much to my research group – Details at http://www.mindswap.org/ (Our Semantic Web Portal) XML 2005 mindswap maryland information and network dynamics lab semantic web agents project The Web used to be easy (ca. 1990) • Documents (HTML) – Emacs or vi via some cutting and pasting and it showed in your browser - woohoo! • And Links (HTTP) – Install LibWWW, customize parameters, and you were up and running - woohoo! XML 2005 mindswap maryland information and network dynamics lab semantic web agents project But that didn't last long… (ca 2000) © Commerce One and Addison-Wesley, 2001 XML 2005 mindswap maryland information and network dynamics lab semantic web agents project Excelsior … • Syndication – Atom, JSON,
    [Show full text]
  • Microformats, Metadata
    Microformats, Metadata April 29, 2013 1 Introduction 1.1 Content • What are microformats? • Why to use microformats? • How to replace microformats? • Advantages of microformats to own markup. • Disadvantages of microformats.. • Common used microformats • Microformats design patterns. • Resources on microformats. 1.2 What are microformats? • The way how to add simple markup into human readable information to allow computer processing. { acquiring data from documents { indexing { searching { storing { cross-referencing • Microformats are elements of a semantic markup using a plain old semantic (X)HTML (POSH) { Why has been the HTML designed at CERN (Conseil Europ´eenpour la Recherche Nucl´eaire(http://dg-rpc.web.cern.ch/dg-rpc/Scale. html)) v in the year 1991? 1 1.3 Example of Microformat <ol class='xoxo'> <li>Prvn´ıbod <ol> <li>Podbod a</li> <li>Podbod b</li> </ol> </li> <li>Druh´ybod <ol compact="compact"> <li>Podbod c</li> <li>Podbod d</li> </ol> </li> </ol> 1.4 Why to use microformats? Microformats combines some trends: • next logical step in web-design and information architecture progress • the manner how can people and organisations publish semantically rich content without dependency on centralized services • "agreement", that the traditional meta data either failed or their adoption took too long, so there has been a need of a different solution. { microformats use the meta data. :-) • Use of (X)HTML for data. 1.5 How can be microformats replaced? (1) • Including data in own formating in a different namespace { XHTML + Voice Profile (http://www.voicexml.org/specs/multimodal/ x+v/12/) { (X)HTML + SVG { XLink { XHTML+RDF { ... 1.6 How can be microformats replaced? (2) • Advantages: { easy visualisation (direct support in browsers, using CSS for exam- ple), { independent on centralized services.
    [Show full text]
  • Microformats a Pragmatic Path to the Semantic Web
    Microformats A Pragmatic Path to the Semantic Web Rohit Khare, Ph.D CommerceNet Labs Tantek Çelik Technorati, Inc. CommerceNet Labs Technical Report 06-01 January 2006 Abstract Microformats are a clever adaptation of semantic XHTML that makes it easier to publish, in- dex, and extract semi-structured information such as tags, calendar entries, contact informa- tion, and reviews on the Web. This makes it a pragmatic path towards achieving the vision set forth for the Semantic Web. Even though it sidesteps the existing “technology stack” of RDF, ontologies, and Artificial Intelligence-inspired processing tools, various microformats have emerged that parallel the goals of several well-known Semantic Web projects. This position paper introduces the ideas behind microformats and gives examples; compares to similar efforts in the Semantic Web; and compares their prospects according to Rogers’ Dif- fusion of Innovation model. Categories and Subject Descriptors I.7.2 [Document and Text Processing]: Document Preparation – markup languages, hypertext/hypermedia. H.3.5 [Information Storage and Retrieval]: Online Information Services – Web-based services. General Terms: Design, Standardization, Human Factors Keywords: Microformats, Semantic Web, Decentralization, HTML, CSS Authorship This report also draws upon the first author’s column for IEEE Internet Computing, “Microfor- mats: The Next (Small?) Thing on the Semantic Web?” Additional portions have been submit- ted to the 15th International World Wide Web Conference. Mr. Çelik is Chief Technologist for Technorati, Inc. He can be reached at 665 3rd Street, Suite 207, San Francisco, CA 94107, or as <[email protected]>. CN-TR 06-01: Microformats: A Pragmatic Path to the Semantic Web 1 1.
    [Show full text]
  • An Extensible Discovery Service for Smart Things
    An Extensible Discovery Service for Smart Things Simon Mayer Dominique Guinard Inst. for Pervasive Computing Inst. for Pervasive Computing ETH Zurich ETH Zurich Zurich, Switzerland Zurich, Switzerland [email protected] [email protected] ABSTRACT that, for these, we require a mechanism that allows machines We present DiscoWoT, a semantic discovery service for Web- to discover them and understand their capabilities in order enabled smart things. The service is based on the applica- to enable automatic usage by software applications. Possi- tion of multiple Discovery Strategies to a Web resource's bilities that would be enabled by machine-understandable representation, where arbitrary users can create and update semantic descriptions for smart things range from on-the- strategies at runtime using DiscoWoT's RESTful interface. fly user interface creation based on the specific capabilities Its goal is to provide a future-proof mechanism for enabling of the accessed device to enabling machines to discover re- both, human users and machines, to semantically discover quired services themselves or support users in finding ser- functionality provided by Web-enabled devices. Ultimately, vices within densely populated smart environments. The it aims to allow for the facilitated discovery, selection, and basis for such applications is a generic mechanism that al- utilization of smart things. DiscoWoT incorporates a trans- lows smart devices to provide semantic descriptions of the parent mechanism for deferring resource discovery to exter- services they offer. nal handlers and can thus interact with other services within The problem of describing resources on the Web is not discovery service federations. It may be accessed by arbi- inherent only to smart things, but rather is a general prob- trary users for ad hoc discovery of functionality offered by lem of providing service specifications that has been worked Web resources or incorporated into infrastructures for Web- on mainly in the Semantic Web domain.
    [Show full text]