background preloader

HTML Microdata

HTML Microdata
Abstract This specification defines the HTML microdata mechanism. This mechanism allows machine-readable data to be embedded in HTML documents in an easy-to-write manner, with an unambiguous parsing model. It is compatible with numerous other data formats including RDF and JSON. Status of This document This section describes the status of this document at the time of its publication. This document was edited in place on 23 June 2014 to fix a wrong "Previous Version" link. If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them via using our public bug database. The bulk of the text of this specification is also available in the WHATWG HTML Living Standard, under a license that permits reuse of the specification text. Publication as a Working Group Note does not imply endorsement by the W3C Membership. The latest stable version of the editor's draft of this specification is always available on the W3C HTML git repository. 1 Dependencies

Related:  NeWeb ModulesMicrodata

About microdata - Webmaster Tools Help The HTML5 microdata specification is a way to label content to describe a specific type of information—for example, reviews, person information, or events. Each information type describes a specific type of item, such as a person, and event, or a review. For example, an event has the properties venue, starting time, name, and category. Microdata uses simple attributes in HTML tags (often <span> or <div>) to assign brief and descriptive names to items and properties. Here's an example of a short HTML block showing basic contact information for Bob Smith. <div> My name is Bob Smith but people call me Smithy.

RDF 1.1 Lite Issue # 2: property vs rel from Guha on 2011-10-22 ( from October 2011) RDF 1.1 Lite Issue # 2: property vs rel Jason Douglas brings up one of the main points that lead us at to support Microdata in favor RDFa, namely the distinction between rel and property. Google announced supported RDFa in 2009. One of the startling discoveries we made was that the error rate (i.e., webmasters marking up their pages to say X when the really meant to say Y) was about 3 times as much as it was for other formats (which include microformats, sitemaps, Google shopping feeds, etc.). The error rate is/was so bad that we had resort to highly non-scalable techniques like having humans look at the markup on each site to make sure it said what the page said.

5 Microdata — HTML5 (including next generation additions still i Microdata 5.1 Introduction 5.1.1 Overview HTML5 This Version: Latest Published Version: Latest Version of HTML: Latest Editor's Draft of HTML: Previous Version: Microdata You are here: Home Dive Into HTML5 Diving In There are over 100 elements in HTML5. Some are purely semantic, others are just containers for scripted APIs. Throughout the history of HTML, standards wonks have argued about which elements should be included in the language.

Search engine optimization As an Internet marketing strategy, SEO considers how search engines work, what people search for, the actual search terms or keywords typed into search engines and which search engines are preferred by their targeted audience. Optimizing a website may involve editing its content, HTML and associated coding to both increase its relevance to specific keywords and to remove barriers to the indexing activities of search engines. Promoting a site to increase the number of backlinks, or inbound links, is another SEO tactic. The plural of the abbreviation SEO can also refer to "search engine optimizers", those who provide SEO services. History

Microdata support for Rich Snippets Webmaster Level: All HTML5 is the fifth major revision of HTML, the core language of the World Wide Web. The HTML5 specification includes a description of microdata, a new markup standard for specifying structured information within web pages. Today, we’re happy to announce support for microdata for use in rich snippets in addition to our existing support for microformats and RDFa. By using microdata markup in your web pages, you can specify reviews, people profiles, or events information on your web pages that Google may use to improve the presentation of your pages in Google search results. Here is a simple HTML block showing a section of a review of “L’Amourita Pizza”: HTML5/RDFa Arguments When I came back from holiday, I caught up with the recent discussions around RDFa and HTML5. It’s exhausting reading so many posts repetitively reiterating the positions of people who all have the best of intentions but fundamentally different priorities. And such a shame that so much energy is spent on fruitless discussion when it could be spent at the very least improving specifications, if not testing, implementing, experimenting or otherwise in some very minor way changing the world. The particular thread’s subject was the use of prefixes, which are used to provide a shorthand for URIs, which are used to name properties such as It’s unquestionable, really, that prefixes are a source of problems: But underlying the arguments about the costs of prefixes are arguments about whether these disadvantages are important enough to stop giving people shorthands for URIs and/orusing URIs when naming properties and/orusing RDF as the data model for data on the web

Getting Started Most webmasters are familiar with HTML tags on their pages. Usually, HTML tags tell the browser how to display the information included in the tag. For example, <h1>Avatar</h1> tells the browser to display the text string "Avatar" in a heading 1 format. However, the HTML tag doesn't give any information about what that text string means—"Avatar" could refer to the hugely successful 3D movie, or it could refer to a type of profile picture—and this can make it more difficult for search engines to intelligently display relevant content to a user. provides a collection of shared vocabularies webmasters can use to mark up their pages in ways that can be understood by the major search engines: Google, Microsoft, Yandex and Yahoo!