Difference between revisions of "microdata"

From Microformats Wiki
Jump to navigation Jump to search
m (→‎summary: fixed typo)
Line 15: Line 15:
 
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)
 
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)
  
For common semantics on the web (e.g. [[hcard|people+organizations]], [[hcalendar|events]], [[hreview|reviews]], [[hatom|syndicated content]]), [[microformats]] are still simpler and easier than [[microdata]], as well already well implemented across numerous tools and services.
+
For common semantics on the web (e.g. [[hcard|people+organizations]], [[hcalendar|events]], [[hreview|reviews]], [[hatom|syndicated content]]), [[microformats]] are still simpler and easier than [[microdata]], and are already well implemented across numerous tools and services.
  
 
For uncommon, rare, experimental, or one-off semantics, [[microdata]] offers a simpler and easier to understand solution than alternatives that use [[namespaces]] like XML/RDF/RDFa.  Developers should consider [[microdata]] as another way of expressing semantics that they may otherwise use [[poshformats]] for.
 
For uncommon, rare, experimental, or one-off semantics, [[microdata]] offers a simpler and easier to understand solution than alternatives that use [[namespaces]] like XML/RDF/RDFa.  Developers should consider [[microdata]] as another way of expressing semantics that they may otherwise use [[poshformats]] for.

Revision as of 13:30, 19 July 2010

<entry-title>microdata</entry-title>

microdata is an extension to Microformats in HTML5 that provides another way to embed microformats and poshformats vocabularies.

Specification: http://www.w3.org/TR/microdata/

summary

microdata consists of a set of attribute extensions to Microformats in HTML5:

  • itemprop attribute is a more specific version of class, for field names
  • subject attribute allows semantically linking within the page. Conceptually similar to the include-pattern.
  • itemref attribute allows including properties elsewhere on the page that are not descendants of itemscope. Takes space-separated ids (for example itemref="address phone" would include the elements with id="address" and id="phone"). Conceptually similar to the include-pattern.
  • content attribute on the meta element can be used to include invisible data that is not part of the content. As current browsers move meta inside <head>, make sure to include via itemref. Conceptually similar to the 'value-title' feature of the Value Class Pattern.
  • itemscope attribute identifies blocks to be marked as structured data. Conceptually similar to the mfo-examples brainstorming.
  • itemtype attribute to specify the type for an item (for example: itemtype="http://microformats.org/profile/hcard")

For common semantics on the web (e.g. people+organizations, events, reviews, syndicated content), microformats are still simpler and easier than microdata, and are already well implemented across numerous tools and services.

For uncommon, rare, experimental, or one-off semantics, microdata offers a simpler and easier to understand solution than alternatives that use namespaces considered harmful like XML/RDF/RDFa. Developers should consider microdata as another way of expressing semantics that they may otherwise use poshformats for.

history

microdata didn't happen overnight. Much of the design and simplicity of microdata is based on years of work on microformats principles deliberately designed to help guide and create simpler, more usable and accessible solutions. It happened so quickly because Ian Hickson designed microdata based upon years of work by both the microformats community, and the concept of using reverse-domain-names as unique qualifiers (popularized perhaps by Java programming language naming conventions).

potential

I think there are some very clever ideas in general purpose microdata, it has a lot of potential, and despite being a bit more abstract than microformats, still much simpler/easier to explain to web designers/developers/programmers than any form of RDF.

General microdata may be the right solution to the general purpose data representation problem that microformats specifically chose not to work on.

- Tantek 17:42, 22 August 2009 (UTC)

microdata vocabularies

Separate from the microdata specification, there are a number of microdata vocabularies, based on microformats and previous formats like vCard and iCalendar.

microdata vCard vocabulary

Formerly documented as a separate specification at http://dev.w3.org/html5/mdvcard/, the microdata vCard vocabulary is currently available as part of WHATWG additions to HTML5.

hCard 1.0.1 (under development) is incorporating these errata.

Using hCard will produce Google Rich Snippets, as well as work with Yahoo Search, and Firefox Extensions Operator Firefox plugin and other tools.

Note:

  • Avoid the "microdata vCard vocabulary" as in many ways it is an out-of-date fork/snapshot of hCard, even though portions of it appear to based directly on the vCard RFC. as well.
  • Avoid Google’s Rich Snippets vocabularies (Person and Organization), which are also forks of hCard/vCard, and are only implemented by Google currently.

microdata vEvent vocabulary

Formerly documented as a separate specification at http://dev.w3.org/html5/mdvevent/, the microdata vEvent vocabulary is currently available as part of WHATWG additions to HTML5.

hCalendar 1.0.1 (under development) is incorporating these errata.

Using hCalendar will produce Google Rich Snippets, as well as work with Yahoo Search, and Firefox Extensions Operator Firefox plugin and other tools.

Note:

  • Avoid the "microdata vEvent vocabulary" as in many ways it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties, even though portions of it appear to based directly on the iCalendar RFC.
  • Avoid Google’s Rich Snippets vocabulary (Event), which is also a fork of hCalendar/iCalendar, and are only implemented by Google currently.

microdata Licensing Works vocabulary

Formerly documented as a separate specification at http://dev.w3.org/html5/mdwork/, the microdata Licensing Works vocabulary is currently available as part of WHATWG additions to HTML5.

The Licensing microformat work provides a potential microformat alternative to the microdata Licensing Works vocabulary.

Please see: Licensing Brainstorming and provide feedback.

microformats in microdata

For those that are ok with going with an Microformats in HTML5 only solution, it may be interesting to consider and document a consistent way to use microformats and microformats vocabulary in microdata.

(needs expansion with examples) ...

alternatives

Since the introduction of XMDP, web authors have been able to define their specific uses of rel attribute values and class names.

(needs expansion with examples) ...

see also