Microformats Wiki - User contributions [en]

User:WebOrganics

2012-03-28T07:57:43Z

WebOrganics: removing note ... no longer relevant

Main Page

2010-12-24T21:15:27Z

WebOrganics: Undo revision 43401 by Jenniejames (Talk) Blatant Spam ...grrrrr

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
<span id="microformats_wiki_translations_in_other_languages">You may read and edit microformats articles in many other languages:</span>

* languages with over 100 articles
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span>
* languages with over 10 articles
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|<span lang="fa">پارسی</span> (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

faqs-for-rdf

2010-08-16T16:18:46Z

WebOrganics: /* Who else is looking at RDF and microformats? */ adding self

<entry-title>Microformat FAQs relating to RDF</entry-title>

== What are Microformats ==
'''What are Microformats?'''

Microformats are a set of simple, open data formats built upon existing and widely adopted standards, in particular [[semantic-html|semantic (X)HTML]]. The [[process|processes]], [[principles]], and practices of the microformats open standards community are what make microformats "microformats", but they center on using HTML and XHTML as designed, as a semantic language (though they can and have been implemented in other XML formats, e.g. RSS, Atom). See [[what-are-microformats]] for more.

One of the microformats principles is humans first, machines second. The more human friendly syntax of microformats can be converted to RDF via a number of mechanisms:
* microformats that have [[XMDP]] profiles can simply be directly used with RDF-compatible URIs for microformats terminology provided by those profiles. See [[profile-uris]].
* With the help of the [http://www.w3.org/2004/01/rdxh/spec GRDDL] mechanism, it is possible to view microformats as domain-specific [http://www.w3.org/RDF/ RDF] serializations.

See also: [http://microformats.org/about/ About Microformats]

== Why were microformats proposed when RDF already existed ==
'''Why were microformats proposed when RDF already existed to markup semantic information?'''

When Tantek first proposed microformats in 2004 with Kevin Marks ([http://tantek.com/presentations/2004etech/realworldsemanticspres.html] see [[history]] for more), it was in many ways a proof of concept that the neither the RDF data model nor (and especially) syntax(es) had significant advantages as a way of modeling (and especially ''authoring'') data over and above simple markup that perhaps mainstream to modern web designers were already broadly familiar with. And not just a lack of advantages, but that frankly, perhaps simpler, more real world solutions were possible.

== How real are microformats ==
'''But how real are microformats?'''

In just five years after that initial proposal, there is already solid support for several microformats in numerous sites from as large as AOL, Google, Yahoo, Yelp, to a very long tail of smaller sites - at last count Yahoo Searchmonkey reported over 1.3 billion [[hCards]] on the web. What started as a proof of concept has become the dominant form of representing semantics (over and above what's built into HTML) on the web.

== But I do RDF, why should I be interested? ==

Microformats lower the barrier to publishing data on the Web. This is entirely in line with the high level goals of the [http://www.w3.org/2001/sw/ Semantic Web].

Dan Connolly [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 rdf-interest, March 2000]:
<blockquote>
I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to manage the information in human-consumable form (XHTML) annotated with just enough info to extract the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. We all know that we have to produce a human-readable version of the thing… why not use that as the primary source?
</blockquote>

== I have an RDF vocabulary I would like to use as a microformat. How do I do it? ==

Before doing anything else, read the microformats [[process]].

In general the microformat process is empirical-data-driven. It starts with material already being published (and ''implied'' schema therein), rather than an existing format, model or explicit schema.

Check the list of what has already been covered and the work-in-progress on the Wiki [[Main_Page]].

It may be that there is already a microformat for the data you want to represent.

It may well be that what you have in mind isn't appropriate for use as a microformat, but it may still be a good idea to develop a (semantic) XHTML representation. Existing microformats demonstrate a standards-friendly Plain Old Semantic HTML ([[POSH]]) way of doing this.

== So, this is about using CSS class values to add semantics? ==

No. XHTML already expresses semantics, the '''HTML''' <code>class</code> attribute is just one of several mechanisms. From the [http://www.w3.org/TR/REC-html40/ HTML 4 spec]:

<blockquote>
The class attribute, on the other hand, assigns one or more class names to an element; the element may be said to belong to these classes.
</blockquote>

See also: [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling]

== What about namespaces for the attributes, should I use "xxx:term"? ==

In general, microformats rejects the use of explicit [[namespace]] prefixes in
documents as unnecessary for solving the 80/20 of problems that microformats
seeks to solve. The general approach taken is not to attempt to generalize to the extent of [http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml RDF-in-HTML], rather to define more domain-specific formats.

== But won't there be naming clashes? ==

The social aspect of the microformats [[process]] is such that conflicts ought to be prevented. The goal is to keep things as simple as possible by only focusing on '''existing''' well-defined problems, rather than trying to "boil the ocean" (solve the hypothetical general case).

In addition, [[XMDP]] profiles can be used to explicitly define terms used in microformats.

== So how do I get the data out? ==

See [http://www.w3.org/TeamSubmission/grddl/ GRDDL] ([http://www.w3.org/2004/01/rdxh/spec older version])

See also: [http://www.w3.org/2006/05/08-htmltf-minutes.html#item03 hGRDDL proposal], [http://www.w3.org/2006/07/SWD/wiki/hGRDDL_Example hGRDDL example]

== What is GRDDL? ==

See [[grddl]].

== Isn't there a clash between the semantics of XFN and FOAF? ==

The use of the page URI in XFN to identify a person appears to conflict with FOAF's by-reference approach, and to mask the potential for saying things about the page itself. However in practice this isn't a problem. It's possible to parse the document as XFN (using e.g. [http://www.w3.org/2003/12/rdf-in-xhtml-xslts/grokXFN.xsl grokXFN.xsl]) to extract the person-related statements, e.g.
<pre>
_:personA foaf:homepage <http://example.org/this-page> .
_:personA foaf:knows _:personB .
_:personB foaf:homepage <http://example.org/linked-page> .
</pre>
- and ''independently'' parse the document using other format mappings (e.g. [http://www.w3.org/2000/06/dc-extract/dc-extract.xsl dc-extract.xsl]) to obtain other statements, e.g.
<pre>
<http://example.org/this-page> dc:creator "The Creator" .
</pre>

See also: [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL], [http://www.oreillynet.com/pub/wlg/8281 XFN Delusions of Grandeur], [http://www.microformats.org/blog/2005/11/02/xfn-grandeur/ XFN Grandeur], [http://dannyayers.com/archives/2005/11/03/xfn-vs-foaf/ XFN vs. FOAF]

== What other work has been done with microformats and RDF? ==

* [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL]
* [http://people.w3.org/~dom/archives/2005/05/grddl-specification-updated/ GRDDL specification updated works with Microformats]

== Are there Schemas for Microformats? ==

Kind of. The primary specification is XHTML, but HTML4 provides a mechanism (the 'profile' attribute of the <head> element) to point to a meta data profile that defines properties and values. There is a (HTML-based) format specified for microformat profiles - [http://www.gmpg.org/xmdp/ XHTML Meta Data Profiles]. Note that XMDP's URLs for specifying terms is compatible with those used by RDF, with "#term" at the end.

See [[XMDP]] for more.

== What RDF vocabularies (and XSLT) corresponding to microformats is available? ==

See [http://esw.w3.org/topic/MicroModels MicroModels] (on ESW Wiki)

== Isn't this just scraping? ==

No. microformats specify parsing therefore do not require or suggest scraping.

microformats define parsing rules for well defined markup (e.g. [[hcard-parsing]] - applicable to most microformats).

"scraping", on the otherhand, is the use of site-specific regular expressions that ignore markup.

Also microformats can [[profile-uris|include URI(s) for every profile used]], and the profiles are clearly defined, the explicit data contained in a document can be extracted deterministically by parsing.

== Who else is looking at RDF and microformats? ==

* [http://www.w3.org/People/Connolly/ Dan Connolly]
* [http://internetalchemy.org/ Ian Davis]
* [http://sw.deri.org/~jbreslin/ John Breslin]
* [http://dannyayers.com Danny Ayers]
* [http://buzzword.org.uk/cognition/ Toby Inkster]
* [http://weborganics.co.uk/ Martin McEvoy]
* ... please add yourself if you are as well!

== How do I get involved? ==

If you're using the Web, you already *are* involved! Next place to go is the [http://microformats.org/ microformats.org] site, and maybe sign up to some of the [http://microformats.org/discuss/ mailing lists] (in particular [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss]). There's also an IRC channel [irc://irc.freenode.net#microformats #microformats on irc.freenode.net].

haudio

2010-08-10T20:38:14Z

WebOrganics: /* Implementations */ updated link to operator script

<entry-title>hAudio 0.9.1</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png

[[haudio|hAudio]] is a simple, open, distributed format, suitable for embedding information about audio recordings in (X)HTML, Atom, RSS, and arbitrary XML. hAudio is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hAudio Microformat Draft Specification ==

=== Editors ===
* [[User:ManuSporny | Manu Sporny]] ([http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.)
* [[ user:WebOrganics | Martin McEvoy ]]
=== Authors ===
* [[User:ManuSporny | Manu Sporny]]
* [[ user:WebOrganics | Martin McEvoy ]]

=== Contributors===
[[User:ManuSporny | Manu Sporny]], [[ user:WebOrganics | Martin McEvoy ]], [[ User:AlexandreVandeSande | Alexandre Van De Sande ]], Michael Johnson, Dave Longley, Brian Suda, Ben Wiley Sittler, Scott Reynen, Frances Berriman, James Craig, David Janes, [[User:AndyMabbett|Andy Mabbett]], Danny Ayers, Rudy Desjardins, Edward O'Connor, Ryan King, Chris Griego, Brad Hafichuk, Tantek Çelik, Colin Barrett, Joe Andrieu, Michael Smethurst, [[User:ChrisNewell | Chris Newell]], Julian Stahnke, Justin Maxwell, Paul Wilkins and David I. Lehn.

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

It is difficult for a browser to extract semantic information about an audio recording described on a web page. Metadata such as speaker, musician, publisher, label, title of the work, release date, acquisition link, related image artwork and tags provide relevant context for the audio recording.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a song performed by an artist, it can produce richer interactions. For example, specific searches may be performed for artists and songs via general search services such as Google and Wikipedia. Specific search services may also be queried such as MusicBrainz, The Internet Archive, FreeDB, or Bitmunk. Additionally, classification by crawlers can become more accurate. If there are 20 tracks found on a page done by the same artist, and that content consumes a significant portion of the page, it can be assumed that the page is not only about music, but also about a particular artist.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of audio content, the authors propose the hAudio microformat, an open standard for distributed audio metadata. The authors have researched both numerous [[audio-info-examples]] in the wild and earlier attempts at [[audio-info-formats]], and have designed hAudio around a simple minimal schema for audio content. Feedback is encouraged on the [[haudio-feedback|hAudio feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to media info and audio info in general. Among the many participants are [[RodBegbie]], Dean Hudson, [http://tantek.com/log/ Tantek Çelik], [http://napsterization.org/stories/ Mary Hodder], [http://joshkinberg.com/blog/ Joshua Kinberg], ChrisMessina, and [http://onlisareinsradar.com/ Lisa Rein].

=== Scope ===

Audio content consistently share several common fields. Where possible hAudio has been based on this minimal common subset.

=== Out of scope ===

Fields that are type-specific have been omitted from hAudio. It is important that hAudio be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a universal audio identifier, that is, how to identify the same audio album, song, speech, or podcast across different music and audio sites, though something very useful to have, is outside the scope of this format.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hAudio format is based on a set of fields common to numerous audio content sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] standards.

=== Schema ===

The hAudio schema consists of the following:

* hAudio ('''<code>haudio</code>''')
** '''fn''' or/and '''album''' required. text.
** '''contributor'''. optional. using text or [[hCard]].
** '''duration'''. optional. ISO-8601 time duration. (re-used from [[hcalendar]]).
** '''item''' optional. using text or multiple properties from [[hAudio]].
** '''position''' optional. text.
** '''category'''. optional. text.
** '''published'''. optional.
** '''photo'''. optional. using any element containing a URL, such as IMG.
** '''description''' optional. text.
** '''sample''' (rel). optional. sample file/stream using [[rel-design-pattern]] with <code>sample</code> as the <code>mf-rel-value</code>.
** '''enclosure''' (rel). optional. full download of file using [[rel-enclosure]].
** '''payment''' (rel). optional. link to purchase process using [[rel-payment]].
** '''price''' optional. Using the sub properties '''currency''' and '''amount'''.

=== Field details ===

The fields of the hAudio schema represent the following:

==== hAudio ====

An hAudio is used to identify and describe metadata associated with an audio recording.

* an hAudio element is identified by class name <code>haudio</code>

==== fn ====

The name of a single audio recording is a short textual description used to identify the work among interested parties. This can be the name of a speech, song name, or short description regarding a sound effect.

* The element is identified by the class name <code>fn</code>.
* hAudio {{must}} have <code>fn</code> or/and <code>album</code>.

==== Album ====

The title of a collection of audio recordings, such as those that are represented as a CD, album or LP. The text should be a short textual description used to identify the work among interested parties.

* The element is identified by the class name <code>album</code>.
* hAudio {{must}} have either <code>album</code> or <code>fn</code> or both.

==== Item ====

A container for another hAudio item, which MUST be considered a part of the parent audio recording. An example of an item that is part of an hAudio would be a track in an audio album, a aria in an Opera, or a section of a podcast.

* The element is identified by the class name <code>item</code>.
* hAudio {{may}} have one or more items.
* The element {{must}} be processed opaquely. No sub-elements should be read from any hAudio contained in a track element.
* The contents of the element {{must}} be marked up using properties in hAudio.

==== Position ====

The position is used to describe the position of the hAudio item in a list. Examples of hAudio lists can include album track listings, music top 10 lists, playlists, and podcast chapters.

* The element is identified by the class name <code>position</code>.
* hAudio {{may}} include one <code>position</code> element.
* The contents of the element {{must}} be a number or other sequential identifier.
* The sequential identifier {{may}} be specified out-of-sequence.

==== Contributor ====

A Contributor is any entity that takes part in the creation and distribution of an audio recording. Examples include: artist, composer, publisher, guitarist, vocalist, violinist, lead singer, backup singer, bassist, drummer, manager, and roadie.

* The element is identified by the class name <code>contributor</code>.
* hAudio {{may}} include one or more contributors.
* The contributor's name SHOULD also be marked up as a valid hCard Microformat. [[hcard]]
*# The <code>role</code> attribute {{should}} be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
* The contributor's name {{may}} be specified in plain-text without being enclosed in a hCard Microformat.

==== Published ====

The published date specifies the date that the audio recording was made available to the public. Examples include: The airing date of a radio broadcast, the day a speech was given, or the day a music album was made available for sale.

* The element is identified by the class name <code>published</code>.
* hAudio {{may}} include one or more <code>published</code> elements.
* The contents of the element {{may}} include a date format compliant with the [[datetime-design-pattern]].

==== Sample ====

A Sample URI specifies from where an excerpt of the audio recording may be retrieved.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>sample</code>.
* hAudio {{may}} include one or more URI <code>sample</code>s.
* The URI {{should}} point to a directly accessible stream or file.
* The type of the sample {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Full Download (Enclosure) ====

A Full Download URI specifies from where the full version of an audio recording may be retrieved. The URI {{must}} point to a direct link to a file retrieval process (FTP, HTTP, BitTorrent URI, etc).

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>enclosure</code>.
* hAudio {{may}} include one or more <code>enclosure</code> URIs.
* The type of the file {{should}} be specified by using the <code>type</code> specifier for a URI.

==== Purchase (Payment) ====

A Purchase URI specifies from where the full version of an audio recording may be purchased. The URI {{must}} point to the beginning of a purchase process for the hAudio.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>payment</code>.
* hAudio {{may}} include one or more <code>payment</code> URIs.
* The type of the file {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Photo ====

A photo specifies an image that should be used to summarize the audio recording. Examples include: the image of a speaker, an audio album cover image, or a picture from a concert.

* The element is identified by the class name <code>photo</code>.
* hAudio {{may}} include one or more <code>photo</code> elements.
* The element {{should}} use an <img> element.
* The element {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended.

==== Category ====

The Category specifies the genre or style used to classify the audio recording. Examples include: blues, rock, motivational, spoken word, or sound effect.

* The element is identified by the class name <code>category</code>.
* hAudio {{may}} include one or more <code>category</code> elements.
* This element {{may}} be expressed using the [[rel-tag]] elemental microformat. When a category is expressed using rel-tag, the content of the element is used as the text for the category. For example: <code><a class="category" rel="tag" href="/tags/symphony">Symphonic</a></code> would have "Symphonic" as the text for the category.

==== Duration ====

The Duration specifies the length in time of the audio recording. Examples include: 104 seconds, 3:23, and 4 minutes.

* The element is identified by the class name <code>duration</code>.
* hAudio {{may}} include one <code>duration</code> element.
* The contents of the element {{may}} use the [[abbr-design-pattern]] whose title attribute contains an ISO-8601 formatted duration. An example of 3:23 (i.e 3 minutes 23 seconds) would be "PT3M23S" in ISO 8601 format.
* The element {{may}} contain the following sub properties:
** '''h''' Hour.
** '''min''' Minute.
** '''s''' Second.
Example:
<pre><span class="duration">
<span class="h">1</span>:
<span class="min">3</span>:
<span class="s">23</span>
</span></pre>

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.

* The element is identified by the class name <code>price</code>.
* hAudio {{may}} include one or more <code>price</code> elements.
* The contents of the element {{may}} also use plain text with a currency symbol.
* The contents {{may}} contain the following sub properties:
** '''currency''' an [http://en.wikipedia.org/wiki/ISO_4217#Active_codes ISO 4217] currency name.
** '''amount''' a numerical value.
Example:
<pre><span class="price">
<abbr class="currency" title="GBP">£</abbr>
<span class="amount">4.99</span>
</span></pre>

==== Description ====

An explanation of the contents of the hAudio item. This could explain the significance of a speech, the full-text description of a sound effect, or the meaning of a song or album.

* The element is identified by the class name <code>description</code>.
* hAudio {{may}} include one or more <code>description</code> elements. If more than one description element is defined, the full description for the hAudio is the concatenation, in order, of all <code>description</code> elements.

=== Parser Processing Notes ===

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>
* If only 'album' is specified, then the hAudio is an album.
* If only 'fn' is specified, then the hAudio is a song, audio track, sound effect, speech, or other atomic/singular work.
* If both 'album' and 'fn' are specified, then the hAudio is a atomic/singular work that is part of an album.
** Example: <code><nowiki><span class="haudio">Side two of <span class="album">Meddle</span> opens with <span class="fn">One of These Days</span></span></nowiki></code>
* If 'fn' and one or more 'items's are specified, the hAudio is an audio recording containing multiple sections. Each item is assumed to be an hAudio that is part of the parent hAudio. None of the 'item' properties should implicitly be added to the containing hAudio. In other words, the parser shouldn't parse the contents of the 'item' into the higher-level hAudio object.

==== Language ====

* To explicitly convey the natural language that an hAudio is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="haudio"
**e.g. <code><nowiki><p>I like <span class="haudio" lang="de"><span class="fn">Das Lied von der Erde</span></span> best.</p></nowiki></code>
*If portions of an hAudio (e.g. the item name) are in a different language to the rest of the hAudio, use the 'lang' or 'xml:lang' attribute on those portions.
* hAudio parsers which need to handle the native language of hAudio {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hAudio parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hAudio if no other language is specified on the hAudio.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Notes ===

This section is informative.

* By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the [[rel-license]] microformat.

== XMDP Profile ==
See: [[haudio-profile]].

== Examples ==

This section is informative.

Here are a few examples of text about, and links to, audio content, from real web sites, showing how they could be easily enhanced to use hAudio.



=== Simple Song Example ===

Display:

(This is a live example, detectable in parsers)

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor">Gogol Bordello</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">Gogol Bordello</span>
</div>
</pre>

=== Speech Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">I Have a Dream</span>, a <span class="category">speech</span> by <span class="contributor"><span class="vcard"><span class="fn n"><span class="given-name">Martin</span> <span class="additional-name">Luther</span> <span class="family-name">King</span>, <span class="honorific-suffix">Jr.</span></span></span></span>
</div>

Microformatted XHTML:
<pre>
<div class="haudio">
<span class="fn">I Have a Dream</span>, a
<span class="category">speech</span> by
<span class="contributor">
<span class="vcard">
<span class="fn n">
<span class="given-name">Martin</span>
<span class="additional-name">Luther</span>
<span class="family-name">King</span>,
<span class="honorific-suffix">Jr.</span>
</span>
</span>
</span>
</div>
</pre>

Note the use of [[hcard|hCard]].

=== Song and Album Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor"><span class="vcard"><span class="fn org">Gogol Bordello</span></span></span> found on <span class="album">Underdog World Strike</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">
<span class="vcard">
<span class="fn org">Gogol Bordello</span>
</span>
</span>
found on
<span class="album">Underdog World Strike</span>
</div>
</pre>

Note that for bands, hCard's ''[[hcard#Implied_.22organization-name.22_Optimization|Implied "organization-name" Optimization]]'' is used.

=== Complete Album Example ===

An example that uses every element of hAudio:

[Image] Live Phish, Volume 15 by Phish<br/>
Released: October 31, 2002<br/>
Acquire: Sample, Live Recording, Buy High Quality Track<br/>
Category: [http://www.example.org/tags/live live]<br/>
Duration: 145 minutes, 27 seconds<br/>
Price: $14.99<br/>
<br/>
Tracks:<br/>
1. Sanity (5:48)<br/>
2. Highway To Hell (3:39)

Here is the hAudio Microformat markup:

<pre>
<div class="haudio">
<img class="photo" src="images/live_phish_vol_15.jpg" alt="" />
<span class="album">Live Phish, Volume 15</span>
<span class="contributor">
<span class="vcard">
<span class="fn org">Phish</span>
</span>
</span>
<br/>
Released on:
<abbr class="published" title="2002-10-31">October 31, 2002</abbr>
<br/>
Acquire:
<a rel="sample" href="/samples/live_phish_vol_15_sample.mp3">Sample</a>,
<a rel="enclosure" href="/live/phish_live_phish_vol_15.mp3">Live Recording</a>,
<a rel="payment" href="/buy/phish_live_phish_vol_15">Buy High Quality Track</a>
Category: <a class="category" rel="tag" href="http://www.example.org/tags/live">live</a>
Duration: <abbr class="duration" title="PT145M27S">145 minutes, 27 seconds</abbr>
Price: <div class="price"><abbr class="currency" title="USD">$</abbr><span class="amount">14.99</span></div>
Tracks:
<div class="item">
<span class="position">1</span>.
<span class="fn">Sanity</span>
(<abbr class="duration" title="PT5M48S">5:48</abbr>)
</div>
<div class="item">
<span class="position">2</span>.
<span class="fn">Highway To Hell</span>
(<abbr class="duration" title="PT3M39S">3:39</abbr>)
</div>
</div>
</pre>

=== Multi-part Podcast Example ===

DigitalPlanet Podcast: 29 Oct 07

Forensic computing: is it really possible to delete data from your machine? Grand plans for getting broadband into Africa, checking out the sky at night via the internet and answering your emails to the programme.

Download MP3

<pre>
<div class="haudio">
<p>
<span class="fn">DigitalPlanet Podcast</span>
:
<abbr class="published" title="20071029">29 Oct 07</abbr>
</p>
<p>
<div class="item">
<span class="fn">Forensic computing: is it really possible to delete data from your machine?</span>
</div>
<div class="item">
<span class="fn">Grand plans for getting broadband into Africa</span>
</div>
,
<div class="item">
<span class="fn">checking out the sky at night via the internet</span>
</div>
and
<div class="item">
<span class="fn">answering your emails</span>
</div>
to the programme.
</p>
<p>
<a rel="enclosure" href="/download/episode/DigitalPlanet-2007-10-29">Download MP3</a>
</p>
</div>
</pre>

=== Opera Example ===

(This is a live example, detectable in parsers)

<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span> is an <span class="category">opera</span> in four acts by <span class="contributor" lang="it">Giacomo Puccini</span> to an <span class="category">Italian liberetto</span> by <span class="contributor" lang="it">Luigi Illica</span> and <span class="contributor" lang="it">Giuseppe Giacosais</span>. I saw it performed last week and found <span class="item"> <span class="fn">Act III</span> to be pretty interesting, especially the <span class="item"> "<span class="fn" lang="it">Sa dirmi, scusi</span>"</span> and <span class="item">"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"</span> arias.</span>
</div>

<pre>
<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span>
is an
<span class="category">opera</span>
in four acts by
<span class="contributor" lang="it">Giacomo Puccini</span>
to an
<span class="category">Italian liberetto</span>
by
<span class="contributor" lang="it">Luigi Illica</span>
and
<span class="contributor" lang="it">Giuseppe Giacosais</span>.
I saw it performed last week and found
<span class="item">
<span class="fn">Act III</span>
to be pretty interesting, especially the
<span class="item">
"<span class="fn" lang="it">Sa dirmi, scusi</span>"
</span>
and
<span class="item">
"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"
</span>
arias.
</span>
</div>
</pre>

== Examples in the wild ==

This section is '''informative'''.

* [http://weborganics.co.uk/haudio-rss/ hAudio-RSS] uses hAudio 0.9.1 and XSLT to generate an RSS2 Playlist.
* Tara Hunt of [http://openmediaweb.org/index.php/2008/01/13/publishing-my-workout-music-in-haudio/ Open Media Web] Published her workout Music in hAudio
* Grabb.it The web music player now uses hAudio 0.9 in its [http://grabb.it/users/greg user pages]
* [http://soundcloud.com/ SoundCloud] has hAudio in its pages.
* [http://populizer.com/ Populizer] also has hAudio in its pages.
* The [http://www.numblog.de/ New Urban Music Blog] has hAudio marked up in its pages.
* [http://alpha.libre.fm/ Libre.fm] has marked up on all its user pages in hAudio see : [http://alpha.libre.fm/user/weborganics example]

== Implementations ==

This section is '''informative'''.

*[http://weborganics.co.uk/files/js/haudio.js hAudio 0.9 script] for [[operator|Operator]], updated version of the original hAudio script by David Lehn.
* Matthias Pfefferle has made some [http://notizblog.org/projects/haudio-icons/ hAudio Icons]
* [http://microform.at/ Microformat TransFormr] extracts hAudio 0.9.1 as a RSS2 Podcast.
* [http://buzzword.org.uk/cognition/ Cognition] 0.1-α11 and above will parse hAudio 0.9 and export as RDF/XML or RDF/JSON. As of 0.1-α12, it will also export in M3U playlist format and Turtle.
* [http://weborganics.co.uk/mo-haudio/ hAudio Microformat to RDF Music Ontology], a [http://www.w3.org/TR/grddl/ GRDDL] profile for hAudio 0.9.1, producing [http://musicontology.com/ Music Ontology] RDF.
* The [http://singpolyma.net/plugins/actionstream/ wp-diso-actionstream] plugin produces hAudio for last.fm scrobbles
*...


== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[currency-proposal]]
* [[datetime-design-pattern]]
* [[rel-design-pattern]]
* [[ISO-31-1|ISO-31-1/ISQ]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other audio metadata efforts. See [[audio-info-formats]].

==== Similar Work ====
* [[media-info]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

This document and <span class="vevent"><span class="summary">hAudio specification was placed into the public domain</span> on <span class="dtstart">2008-11-14</span></span> by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* Manu Sporny - Signature /Manu Sporny/
* Alexandre Van de Sande
* [[User:WebOrganics|Martin McEvoy]]
* [[User:DavidLehn|David Lehn]] - Signature /David Lehn/
* [[User:AndyMabbett|Andy Mabbett]]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

[[Category:Draft Specifications]]

hmedia

2010-07-04T08:21:19Z

WebOrganics: /* Implementations */ updating link

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* <span class="author">[[User:WebOrganics| Martin McEvoy]]</span>

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
</dl>
</dd>
<dt>rel</dt>
<dd>
<dl>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

Note (informative). See also an [http://purl.org/microformat/hmedia/ RDF Schema for the hMedia vocabulary].

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://www.norfolkblackhistorymonth.org.uk/events/2009/film.html Norfolk Black Film Festival] marks up movie information with hMedia. Example: the movie [http://www.norfolkblackhistorymonth.org.uk/events/2009/blacula.html Blacula].
* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://microform.at Microformat Transformr] parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces a [http://search.yahoo.com/mrss MediaRSS] Podcast/Vidcast
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* 2009-08-11 The [http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia] article by <span class="vcard"><span class="fn">Tim Aidlin</span></span> on Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick].

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

haudio

2010-07-04T08:09:25Z

WebOrganics: /* Implementations */ updating link

<entry-title>hAudio 0.9.1</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png

[[haudio|hAudio]] is a simple, open, distributed format, suitable for embedding information about audio recordings in (X)HTML, Atom, RSS, and arbitrary XML. hAudio is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hAudio Microformat Draft Specification ==

=== Editors ===
* [[User:ManuSporny | Manu Sporny]] ([http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.)
* [[ user:WebOrganics | Martin McEvoy ]]
=== Authors ===
* [[User:ManuSporny | Manu Sporny]]
* [[ user:WebOrganics | Martin McEvoy ]]

=== Contributors===
[[User:ManuSporny | Manu Sporny]], [[ user:WebOrganics | Martin McEvoy ]], [[ User:AlexandreVandeSande | Alexandre Van De Sande ]], Michael Johnson, Dave Longley, Brian Suda, Ben Wiley Sittler, Scott Reynen, Frances Berriman, James Craig, David Janes, [[User:AndyMabbett|Andy Mabbett]], Danny Ayers, Rudy Desjardins, Edward O'Connor, Ryan King, Chris Griego, Brad Hafichuk, Tantek Çelik, Colin Barrett, Joe Andrieu, Michael Smethurst, [[User:ChrisNewell | Chris Newell]], Julian Stahnke, Justin Maxwell, Paul Wilkins and David I. Lehn.

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

It is difficult for a browser to extract semantic information about an audio recording described on a web page. Metadata such as speaker, musician, publisher, label, title of the work, release date, acquisition link, related image artwork and tags provide relevant context for the audio recording.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a song performed by an artist, it can produce richer interactions. For example, specific searches may be performed for artists and songs via general search services such as Google and Wikipedia. Specific search services may also be queried such as MusicBrainz, The Internet Archive, FreeDB, or Bitmunk. Additionally, classification by crawlers can become more accurate. If there are 20 tracks found on a page done by the same artist, and that content consumes a significant portion of the page, it can be assumed that the page is not only about music, but also about a particular artist.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of audio content, the authors propose the hAudio microformat, an open standard for distributed audio metadata. The authors have researched both numerous [[audio-info-examples]] in the wild and earlier attempts at [[audio-info-formats]], and have designed hAudio around a simple minimal schema for audio content. Feedback is encouraged on the [[haudio-feedback|hAudio feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to media info and audio info in general. Among the many participants are [[RodBegbie]], Dean Hudson, [http://tantek.com/log/ Tantek Çelik], [http://napsterization.org/stories/ Mary Hodder], [http://joshkinberg.com/blog/ Joshua Kinberg], ChrisMessina, and [http://onlisareinsradar.com/ Lisa Rein].

=== Scope ===

Audio content consistently share several common fields. Where possible hAudio has been based on this minimal common subset.

=== Out of scope ===

Fields that are type-specific have been omitted from hAudio. It is important that hAudio be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a universal audio identifier, that is, how to identify the same audio album, song, speech, or podcast across different music and audio sites, though something very useful to have, is outside the scope of this format.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hAudio format is based on a set of fields common to numerous audio content sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] standards.

=== Schema ===

The hAudio schema consists of the following:

* hAudio ('''<code>haudio</code>''')
** '''fn''' or/and '''album''' required. text.
** '''contributor'''. optional. using text or [[hCard]].
** '''duration'''. optional. ISO-8601 time duration. (re-used from [[hcalendar]]).
** '''item''' optional. using text or multiple properties from [[hAudio]].
** '''position''' optional. text.
** '''category'''. optional. text.
** '''published'''. optional.
** '''photo'''. optional. using any element containing a URL, such as IMG.
** '''description''' optional. text.
** '''sample''' (rel). optional. sample file/stream using [[rel-design-pattern]] with <code>sample</code> as the <code>mf-rel-value</code>.
** '''enclosure''' (rel). optional. full download of file using [[rel-enclosure]].
** '''payment''' (rel). optional. link to purchase process using [[rel-payment]].
** '''price''' optional. Using the sub properties '''currency''' and '''amount'''.

=== Field details ===

The fields of the hAudio schema represent the following:

==== hAudio ====

An hAudio is used to identify and describe metadata associated with an audio recording.

* an hAudio element is identified by class name <code>haudio</code>

==== fn ====

The name of a single audio recording is a short textual description used to identify the work among interested parties. This can be the name of a speech, song name, or short description regarding a sound effect.

* The element is identified by the class name <code>fn</code>.
* hAudio {{must}} have <code>fn</code> or/and <code>album</code>.

==== Album ====

The title of a collection of audio recordings, such as those that are represented as a CD, album or LP. The text should be a short textual description used to identify the work among interested parties.

* The element is identified by the class name <code>album</code>.
* hAudio {{must}} have either <code>album</code> or <code>fn</code> or both.

==== Item ====

A container for another hAudio item, which MUST be considered a part of the parent audio recording. An example of an item that is part of an hAudio would be a track in an audio album, a aria in an Opera, or a section of a podcast.

* The element is identified by the class name <code>item</code>.
* hAudio {{may}} have one or more items.
* The element {{must}} be processed opaquely. No sub-elements should be read from any hAudio contained in a track element.
* The contents of the element {{must}} be marked up using properties in hAudio.

==== Position ====

The position is used to describe the position of the hAudio item in a list. Examples of hAudio lists can include album track listings, music top 10 lists, playlists, and podcast chapters.

* The element is identified by the class name <code>position</code>.
* hAudio {{may}} include one <code>position</code> element.
* The contents of the element {{must}} be a number or other sequential identifier.
* The sequential identifier {{may}} be specified out-of-sequence.

==== Contributor ====

A Contributor is any entity that takes part in the creation and distribution of an audio recording. Examples include: artist, composer, publisher, guitarist, vocalist, violinist, lead singer, backup singer, bassist, drummer, manager, and roadie.

* The element is identified by the class name <code>contributor</code>.
* hAudio {{may}} include one or more contributors.
* The contributor's name SHOULD also be marked up as a valid hCard Microformat. [[hcard]]
*# The <code>role</code> attribute {{should}} be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
* The contributor's name {{may}} be specified in plain-text without being enclosed in a hCard Microformat.

==== Published ====

The published date specifies the date that the audio recording was made available to the public. Examples include: The airing date of a radio broadcast, the day a speech was given, or the day a music album was made available for sale.

* The element is identified by the class name <code>published</code>.
* hAudio {{may}} include one or more <code>published</code> elements.
* The contents of the element {{may}} include a date format compliant with the [[datetime-design-pattern]].

==== Sample ====

A Sample URI specifies from where an excerpt of the audio recording may be retrieved.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>sample</code>.
* hAudio {{may}} include one or more URI <code>sample</code>s.
* The URI {{should}} point to a directly accessible stream or file.
* The type of the sample {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Full Download (Enclosure) ====

A Full Download URI specifies from where the full version of an audio recording may be retrieved. The URI {{must}} point to a direct link to a file retrieval process (FTP, HTTP, BitTorrent URI, etc).

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>enclosure</code>.
* hAudio {{may}} include one or more <code>enclosure</code> URIs.
* The type of the file {{should}} be specified by using the <code>type</code> specifier for a URI.

==== Purchase (Payment) ====

A Purchase URI specifies from where the full version of an audio recording may be purchased. The URI {{must}} point to the beginning of a purchase process for the hAudio.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>payment</code>.
* hAudio {{may}} include one or more <code>payment</code> URIs.
* The type of the file {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Photo ====

A photo specifies an image that should be used to summarize the audio recording. Examples include: the image of a speaker, an audio album cover image, or a picture from a concert.

* The element is identified by the class name <code>photo</code>.
* hAudio {{may}} include one or more <code>photo</code> elements.
* The element {{should}} use an <img> element.
* The element {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended.

==== Category ====

The Category specifies the genre or style used to classify the audio recording. Examples include: blues, rock, motivational, spoken word, or sound effect.

* The element is identified by the class name <code>category</code>.
* hAudio {{may}} include one or more <code>category</code> elements.
* This element {{may}} be expressed using the [[rel-tag]] elemental microformat. When a category is expressed using rel-tag, the content of the element is used as the text for the category. For example: <code><a class="category" rel="tag" href="/tags/symphony">Symphonic</a></code> would have "Symphonic" as the text for the category.

==== Duration ====

The Duration specifies the length in time of the audio recording. Examples include: 104 seconds, 3:23, and 4 minutes.

* The element is identified by the class name <code>duration</code>.
* hAudio {{may}} include one <code>duration</code> element.
* The contents of the element {{may}} use the [[abbr-design-pattern]] whose title attribute contains an ISO-8601 formatted duration. An example of 3:23 (i.e 3 minutes 23 seconds) would be "PT3M23S" in ISO 8601 format.
* The element {{may}} contain the following sub properties:
** '''h''' Hour.
** '''min''' Minute.
** '''s''' Second.
Example:
<pre><span class="duration">
<span class="h">1</span>:
<span class="min">3</span>:
<span class="s">23</span>
</span></pre>

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.

* The element is identified by the class name <code>price</code>.
* hAudio {{may}} include one or more <code>price</code> elements.
* The contents of the element {{may}} also use plain text with a currency symbol.
* The contents {{may}} contain the following sub properties:
** '''currency''' an [http://en.wikipedia.org/wiki/ISO_4217#Active_codes ISO 4217] currency name.
** '''amount''' a numerical value.
Example:
<pre><span class="price">
<abbr class="currency" title="GBP">£</abbr>
<span class="amount">4.99</span>
</span></pre>

==== Description ====

An explanation of the contents of the hAudio item. This could explain the significance of a speech, the full-text description of a sound effect, or the meaning of a song or album.

* The element is identified by the class name <code>description</code>.
* hAudio {{may}} include one or more <code>description</code> elements. If more than one description element is defined, the full description for the hAudio is the concatenation, in order, of all <code>description</code> elements.

=== Parser Processing Notes ===

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>
* If only 'album' is specified, then the hAudio is an album.
* If only 'fn' is specified, then the hAudio is a song, audio track, sound effect, speech, or other atomic/singular work.
* If both 'album' and 'fn' are specified, then the hAudio is a atomic/singular work that is part of an album.
** Example: <code><nowiki><span class="haudio">Side two of <span class="album">Meddle</span> opens with <span class="fn">One of These Days</span></span></nowiki></code>
* If 'fn' and one or more 'items's are specified, the hAudio is an audio recording containing multiple sections. Each item is assumed to be an hAudio that is part of the parent hAudio. None of the 'item' properties should implicitly be added to the containing hAudio. In other words, the parser shouldn't parse the contents of the 'item' into the higher-level hAudio object.

==== Language ====

* To explicitly convey the natural language that an hAudio is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="haudio"
**e.g. <code><nowiki><p>I like <span class="haudio" lang="de"><span class="fn">Das Lied von der Erde</span></span> best.</p></nowiki></code>
*If portions of an hAudio (e.g. the item name) are in a different language to the rest of the hAudio, use the 'lang' or 'xml:lang' attribute on those portions.
* hAudio parsers which need to handle the native language of hAudio {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hAudio parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hAudio if no other language is specified on the hAudio.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Notes ===

This section is informative.

* By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the [[rel-license]] microformat.

== XMDP Profile ==
See: [[haudio-profile]].

== Examples ==

This section is informative.

Here are a few examples of text about, and links to, audio content, from real web sites, showing how they could be easily enhanced to use hAudio.



=== Simple Song Example ===

Display:

(This is a live example, detectable in parsers)

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor">Gogol Bordello</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">Gogol Bordello</span>
</div>
</pre>

=== Speech Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">I Have a Dream</span>, a <span class="category">speech</span> by <span class="contributor"><span class="vcard"><span class="fn n"><span class="given-name">Martin</span> <span class="additional-name">Luther</span> <span class="family-name">King</span>, <span class="honorific-suffix">Jr.</span></span></span></span>
</div>

Microformatted XHTML:
<pre>
<div class="haudio">
<span class="fn">I Have a Dream</span>, a
<span class="category">speech</span> by
<span class="contributor">
<span class="vcard">
<span class="fn n">
<span class="given-name">Martin</span>
<span class="additional-name">Luther</span>
<span class="family-name">King</span>,
<span class="honorific-suffix">Jr.</span>
</span>
</span>
</span>
</div>
</pre>

Note the use of [[hcard|hCard]].

=== Song and Album Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor"><span class="vcard"><span class="fn org">Gogol Bordello</span></span></span> found on <span class="album">Underdog World Strike</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">
<span class="vcard">
<span class="fn org">Gogol Bordello</span>
</span>
</span>
found on
<span class="album">Underdog World Strike</span>
</div>
</pre>

Note that for bands, hCard's ''[[hcard#Implied_.22organization-name.22_Optimization|Implied "organization-name" Optimization]]'' is used.

=== Complete Album Example ===

An example that uses every element of hAudio:

[Image] Live Phish, Volume 15 by Phish<br/>
Released: October 31, 2002<br/>
Acquire: Sample, Live Recording, Buy High Quality Track<br/>
Category: [http://www.example.org/tags/live live]<br/>
Duration: 145 minutes, 27 seconds<br/>
Price: $14.99<br/>
<br/>
Tracks:<br/>
1. Sanity (5:48)<br/>
2. Highway To Hell (3:39)

Here is the hAudio Microformat markup:

<pre>
<div class="haudio">
<img class="photo" src="images/live_phish_vol_15.jpg" alt="" />
<span class="album">Live Phish, Volume 15</span>
<span class="contributor">
<span class="vcard">
<span class="fn org">Phish</span>
</span>
</span>
<br/>
Released on:
<abbr class="published" title="2002-10-31">October 31, 2002</abbr>
<br/>
Acquire:
<a rel="sample" href="/samples/live_phish_vol_15_sample.mp3">Sample</a>,
<a rel="enclosure" href="/live/phish_live_phish_vol_15.mp3">Live Recording</a>,
<a rel="payment" href="/buy/phish_live_phish_vol_15">Buy High Quality Track</a>
Category: <a class="category" rel="tag" href="http://www.example.org/tags/live">live</a>
Duration: <abbr class="duration" title="PT145M27S">145 minutes, 27 seconds</abbr>
Price: <div class="price"><abbr class="currency" title="USD">$</abbr><span class="amount">14.99</span></div>
Tracks:
<div class="item">
<span class="position">1</span>.
<span class="fn">Sanity</span>
(<abbr class="duration" title="PT5M48S">5:48</abbr>)
</div>
<div class="item">
<span class="position">2</span>.
<span class="fn">Highway To Hell</span>
(<abbr class="duration" title="PT3M39S">3:39</abbr>)
</div>
</div>
</pre>

=== Multi-part Podcast Example ===

DigitalPlanet Podcast: 29 Oct 07

Forensic computing: is it really possible to delete data from your machine? Grand plans for getting broadband into Africa, checking out the sky at night via the internet and answering your emails to the programme.

Download MP3

<pre>
<div class="haudio">
<p>
<span class="fn">DigitalPlanet Podcast</span>
:
<abbr class="published" title="20071029">29 Oct 07</abbr>
</p>
<p>
<div class="item">
<span class="fn">Forensic computing: is it really possible to delete data from your machine?</span>
</div>
<div class="item">
<span class="fn">Grand plans for getting broadband into Africa</span>
</div>
,
<div class="item">
<span class="fn">checking out the sky at night via the internet</span>
</div>
and
<div class="item">
<span class="fn">answering your emails</span>
</div>
to the programme.
</p>
<p>
<a rel="enclosure" href="/download/episode/DigitalPlanet-2007-10-29">Download MP3</a>
</p>
</div>
</pre>

=== Opera Example ===

(This is a live example, detectable in parsers)

<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span> is an <span class="category">opera</span> in four acts by <span class="contributor" lang="it">Giacomo Puccini</span> to an <span class="category">Italian liberetto</span> by <span class="contributor" lang="it">Luigi Illica</span> and <span class="contributor" lang="it">Giuseppe Giacosais</span>. I saw it performed last week and found <span class="item"> <span class="fn">Act III</span> to be pretty interesting, especially the <span class="item"> "<span class="fn" lang="it">Sa dirmi, scusi</span>"</span> and <span class="item">"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"</span> arias.</span>
</div>

<pre>
<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span>
is an
<span class="category">opera</span>
in four acts by
<span class="contributor" lang="it">Giacomo Puccini</span>
to an
<span class="category">Italian liberetto</span>
by
<span class="contributor" lang="it">Luigi Illica</span>
and
<span class="contributor" lang="it">Giuseppe Giacosais</span>.
I saw it performed last week and found
<span class="item">
<span class="fn">Act III</span>
to be pretty interesting, especially the
<span class="item">
"<span class="fn" lang="it">Sa dirmi, scusi</span>"
</span>
and
<span class="item">
"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"
</span>
arias.
</span>
</div>
</pre>

== Examples in the wild ==

This section is '''informative'''.

* [http://weborganics.co.uk/haudio-rss/ hAudio-RSS] uses hAudio 0.9.1 and XSLT to generate an RSS2 Playlist.
* Tara Hunt of [http://openmediaweb.org/index.php/2008/01/13/publishing-my-workout-music-in-haudio/ Open Media Web] Published her workout Music in hAudio
* Grabb.it The web music player now uses hAudio 0.9 in its [http://grabb.it/users/greg user pages]
* [http://soundcloud.com/ SoundCloud] has hAudio in its pages.
* [http://populizer.com/ Populizer] also has hAudio in its pages.
* The [http://www.numblog.de/ New Urban Music Blog] has hAudio marked up in its pages.
* [http://alpha.libre.fm/ Libre.fm] has marked up on all its user pages in hAudio see : [http://alpha.libre.fm/user/weborganics example]

== Implementations ==

This section is '''informative'''.

*[http://weborganics.co.uk/files/js/haudio.zip hAudio 0.9 script] for [[operator|Operator]], updated version of the original hAudio script by David Lehn.
* Matthias Pfefferle has made some [http://notizblog.org/projects/haudio-icons/ hAudio Icons]
* [http://microform.at/ Microformat TransFormr] extracts hAudio 0.9.1 as a RSS2 Podcast.
* [http://buzzword.org.uk/cognition/ Cognition] 0.1-α11 and above will parse hAudio 0.9 and export as RDF/XML or RDF/JSON. As of 0.1-α12, it will also export in M3U playlist format and Turtle.
* [http://weborganics.co.uk/mo-haudio/ hAudio Microformat to RDF Music Ontology], a [http://www.w3.org/TR/grddl/ GRDDL] profile for hAudio 0.9.1, producing [http://musicontology.com/ Music Ontology] RDF.
* The [http://singpolyma.net/plugins/actionstream/ wp-diso-actionstream] plugin produces hAudio for last.fm scrobbles
*...


== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[currency-proposal]]
* [[datetime-design-pattern]]
* [[rel-design-pattern]]
* [[ISO-31-1|ISO-31-1/ISQ]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other audio metadata efforts. See [[audio-info-formats]].

==== Similar Work ====
* [[media-info]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

This document and <span class="vevent"><span class="summary">hAudio specification was placed into the public domain</span> on <span class="dtstart">2008-11-14</span></span> by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* Manu Sporny - Signature /Manu Sporny/
* Alexandre Van de Sande
* [[User:WebOrganics|Martin McEvoy]]
* [[User:DavidLehn|David Lehn]] - Signature /David Lehn/
* [[User:AndyMabbett|Andy Mabbett]]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

[[Category:Draft Specifications]]

haudio-issues

2010-06-26T10:15:24Z

WebOrganics: /* D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern */ added examples

=hAudio issues=

These are externally raised issues about [[haudio|hAudio]] with broadly varying degrees of merit. Thus some issues are <em style="text-transform:uppercase;">rejected</em> for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be <em style="text-transform:uppercase;">accepted</em> and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible.

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[haudio-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
* You can subscribe to all haudio issues on <nowiki>webcal://feeds.technorati.com/events/http://microformats.org/wiki/haudio-issues</nowiki>

==2008==

=== D1: 2008-01-10 Contributor ===
<div class="vevent">
* {{ResolvedIssue}} D1: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011340.html microformats-discuss/2008-January/011340.html]</span>
<div class="description">
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
*#* A resolution to this issue is outlined in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
*#* ACCEPTED ISSUE The hAudio Contributor Specification is to be changed to:
*#** The element is identified by the class name |contributor|.
*#** hAudio /MAY/ include one or more contributors.
*#** The contributor's name SHOULD also be marked up as a valid hCard Microformat. <http://microformats.org/wiki/hcard>
*#**# The |role| attribute /SHOULD/ be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
*#** The contributor's name MAY be specified in plain-text without being enclosed in a hCard Microformat.
*#* REMOVED:
*#** If multiple contributors are specified, without |role| specifications, it /MAY/ be assumed that the first role mentioned is the primary artist or creator.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
</div>
</div>

=== D2: 2008-01-10 hAudio Title was Overloading "fn".===

<div class="vevent">
* {{ResolvedIssue}} D2: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011342.html] </span>
<div class="description">
The "overloading" of <code>fn</code> for both the tile of a work and the name of a contributor causes problems (see above e-mail for examples). Another example of this problem is a table, where the "artist" column comes before the "title" column. For discussion, see also [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
# Existing Resolution [[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (first choice)
#* +1 [[User:ManuSporny|Sarven Capadisli]] (second choice)
# Resolution 1: [[User:WebOrganics|Martin McEvoy]] proposed change <code>"title"</code> to <code>"name"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-March/001555.html microformats-new/2008-March/001555.html]
# Resolution 2: [[User:WebOrganics|Martin McEvoy]] later propsosed that <code>"title"</code> should be replaced with <code>"htitle"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (second choice)
#* +1 [[User:Csarven|Sarven Capadisli]] (first choice)
# Resolution 3: Use <code>"audio-title"</code> As tentatively proposed by [[User:ManuSporny|Manu Sporny]] see:[http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
# Resolution 4: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/wiki?title=haudio&diff=prev&oldid=25667]
#* +1 [[User:WebOrganics|Martin McEvoy]] Without Reservations see:[http://microformats.org/wiki?title=haudio-issues&diff=0&oldid=28703 haudio-issues&diff=0&oldid=28703]
#* +1 [[User:ManuSporny|Manu Sporny]] (third choice)
#* +1 [[User:DavidJanes]] this is the correct thing to do
#* +1 [[User:Csarven|Sarven Capadisli]] (third choice)
# Don't really care — just pick one. ;-)
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:ManuSporny|Manu Sporny]] - close this damn discussion, already! :)
* ACCEPTED ISSUE, RESOLUTION: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-September/001797.html microformats-new/2008-September/001797.html]
</div>
</div>

=== D3: 2008-01-10 Position. ===
<div class="vevent">
* {{ResolvedIssue}} D3: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011343.html microformats-discuss/2008-January/011343.html]</span>
<div class="description">
*# The [http://microformats.org/wiki/haudio#Complete_Album_Example recommended use of "position" in hAudio] is contrary to the good practice, semantic use of ordered lists (see example and suggested solution in the above e-mail; also [http://microformats.org/discuss/mail/microformats-new/2008-January/001338.html] et seq)
*#* For Cognition I'm considering an extension: if no position has been explicitly marked up, and the item is <code><li class="item"></code> within an ordered list, then the position is taken to be the numerical value of the list marker. (To calculate the numerical value for the list marker, find the most recent sibling <code><li></code> element which has a <code>value</code> attribute. The numerical value is the number in that value attribute added to the count of <code><li></code> elements after that value attribute up to the current one. If there are no such <code><li></code> elements with <code>value</code> attributes, then you should assume that the <code>value</code> attribute of the first list item is equal to the <code>start</code> attribute of the ordered list itself, or "1" if there is no such <code>start</code> attribute. [[User:TobyInk|TobyInk]] 04:24, 29 Jul 2008 (PDT)
*#* A Proposed Resolution was made in this email: ( http://microformats.org/discuss/mail/microformats-new/2008-August/001751.html)
*#* ACCEPTED ISSUE The hAudio Position Specification is to be changed to:
*#** The element is identified by the class name |position|.
*#** hAudio /MAY/ include one |position| element.
*#** The contents of the element /MUST/ be a number or other sequential identifier.
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#* ADDED:
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001708.html
*#* [[User:AndyMabbett|Andy Mabbett]] also Expressed concerns that the [[haudio#Complete_Album_Example|Complete Album Example]] should be marked up as an ordered list this is unnecessary as <code>"position"</code> is not related to the order of a track item in a list.
*#* A tutorial on the correct use of semantic ordered lists and hAudio is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D4: 2008-01-10 rel-enclosure does not allow for links to streaming files ===
<div class="vevent">
* {{ResolvedIssue}} D4: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
*# The required use of [[rel-enclosure]] does not allow for links to streaming files, which are not cacheable, and are thus outside the scope of rel-enclosure. [http://www.bbc.co.uk/radio4/science/livingworld_20041121.shtml An example on the BBC website] has the relevant link is below the heading "LISTEN AGAIN". (see discussion at [http://microformats.org/discuss/mail/microformats-new/2008-January/001339.html microformats-new/2008-January/001339.html] et seq).
*#* A proposal for this issue was first made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001715.html
*#* A second proposal for this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001727.html
*#* This can potentially be solved by recognition of downloadable/streamable MIME types. For performance reasons it is undesirable for parsers to be required to make HTTP requests for each file to determine its MIME type, so authors should be encouraged to include the MIME type in the <code>type</code> attribute. See the [[haudio-brainstorming#Download_links|related section on "brainstorming"]]. [[User:TobyInk|TobyInk]] 14:41, 20 Aug 2008 (PDT)
*#* ACCEPTED ISSUE The hAudio Enclosure Specification is to be changed to:
*#** The element is identified by a URI fitting the rel-design-pattern, the rel content being enclosure.
*#** hAudio MAY include one or more enclosure URIs.
*#** The type of the file SHOULD be specified by using the type specifier for a URI.
*#* CHANGED:
*#** The type of the file MAY be specified by using the type specifier for a URI.
*#*** As suggested by [[User:Tantek|Tantek Çelik]] in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001731.html
*#*** As Proposed by [[User:TobyInk|Toby Inkster]] on 14:41, 20 Aug 2008 (PDT)
*#* A tutorial on the importance of Type Specifiers and hAudio Enclosures is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D5: 2008-01-10 there is no way of linking to an interim page ===
<div class="vevent">
* {{OpenIssue}} D5: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
There appears to be no mechanism to mark up an hAudio, expressed in plain text on page A, which links to an interim page, B, which in turn links to a file download. For example, the radio shows listed on [http://www.westmidlandbirdclub.com/bibliography/radio].
</div>
# Resolution 1: re use <code>"url"</code> from [[hcard|hCard]].
#* +1 [[User:WebOrganics|Martin McEvoy]] all links are not clickable/hyperlinkable.
#* +1 [[User:TobyInk|TobyInk]]
# Resolution 2: use the rel <code>"bookmark"</code> [http://www.w3.org/TR/REC-html40/types.html#type-links HTML Link Type].
</div>

=== D6: 2008-01-10 hAudio notes inconsistency ===
<div class="vevent">
* {{ResolvedIssue}} D6: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011345.html microformats-discuss/2008-January/011345.html]</span>
<div class="description">
*# [[haudio#Notes|The "Notes" section of the hAudio spec]] says "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using rel-license as specified above.". However, that is the first and only reference to [[rel-license]] on the page.
*#* Typing error changed to "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
*#* hAudio Specification SHOULD include the [[rel-license]] microformat [[User:WebOrganics|Martin McEvoy]] 11:57, 18 Aug 2008 (GMT)
*#* A proposed resolution to this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001720.html
*# RESOLVED <code>rel="licence"</code> is not part of this version of hAudio (0.9) see:http://microformats.org/discuss/mail/microformats-new/2008-August/001747.html
</div>
</div>

==2009==

=== D7: 2009-01-11 Endorsement of optimization patterns in schema listing too strong ===
<div class="vevent">
* {{ResolvedIssue}} D7: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes references to multiple optimization patterns (datetime pattern for <code>published</code>, abbr-pattern for <code>duration</code>). It is currently worded as to imply that those patterns ''must'' be used. Given past disagreement over ABBR in particular, I think the spec should avoid specific endorsement of any pattern, at the very least reducing references to patterns to clear ‘You ''may'' use the abbr-pattern with this field' sort of phrasing.</p>
# Resolution 1: Reword schema listing to use ''may'' language clearly.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The schema now uses ''may'' language more clearly
</div>

=== D8: 2009-01-11 Don't link to currency proposal ===
<div class="vevent">
* {{ResolvedIssue}} D8: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes reference to the currency proposal. Since that is still a proposal, the spec should not endorse it or encourage too-early adoption of it, especially since it's not even a ''draft'' at this stage. Should the currency work be completed, hAudio should be updated later, rather than linking it in pre-emptively.</p>
# Resolution 1: Remove reference to currency proposal from hAudio schema.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The hAudio no longer references the currency proposal, only cites it as an Informative reference at the bottom of the page.
</div>

==2010==

=== D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern ===
<div class="vevent">
* {{OpenIssue}} D9: <span class="summary vcard"><span class="dtstart">2010-06-11</span> raised by <span class="fn">[[User:WebOrganics|Martin McEvoy]]</span>.</span>
<p class="description">[[haudio#Duration|hAudio Duration]] and [[haudio#Published|Published]] should adopt the value-title pattern like [[hrecipe#duration|hRecipe Duration]] and [[hatom-profile|hAtom]], to prevent the user from getting machine data in a tooltip.</p>
Example:
<pre><span class="duration">
3 minutes 33 seconds
<span class="value-title" title="PT3M33S">.</span>
</span></pre>
and....
<pre><span class="published">
February 06, 2007
<span class="value-title" title="2007-02-06">.</span>
</span></pre>

# Resolution 1: Adopt the value-title pattern for both hAudio Duration and Published.
#* +1 [[User:WebOrganics|Martin McEvoy]]
#* +1 [[User:AndyMabbett|Andy Mabbett]] via: [http://twitter.com/pigsonthewing/statuses/15935702988 Twitter]
</div>

==template==
{{issues-format}}

==see also==
*[[audio-info-issues]]

==related pages==
{{haudio-related-pages}}

parsers

2010-06-25T22:53:25Z

WebOrganics: /* Transformr */ updating

<entry-title>Microformats Parsers</entry-title>
;shortlinks
:http://ufs.cc/w/parsers (preferred)
:http://tr.im/ufprs
This page lists libraries that consume, transform or convert microformats. This is only a partial list. If you know of other such tools for microformats, please add them and list what specific microformats they support.

Alphabetical listing by programming language:

== Java ==
* [http://code.google.com/p/any23/ Any23 (Anything to Triples)] parses microformats into RDF triples
* [http://zwitserloot.com/org.microformats.hCard/ org.microformats.hCard] by Reinier Zwitserloot

== Javascript ==
=== Sumo ===
* [http://www.danwebb.net/2007/2/9/sumo-a-generic-microformats-parser-for-javascript Sumo! A Generic Microformats Parser For JavaScript]

== Perl ==
=== Data::Microformat ===
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo.
** By Brendan O'Connor / Six Apart

=== HTML::Microformats ===
Perhaps we can capture and update this info on a page like [[perl-html-microformats-parser]].
* [http://search.cpan.org/~tobyink/HTML-Microformats/ HTML::Microformats] is a CPAN module that has support for:
** rel: [[rel-enclosure]], [[rel-license]], [[rel-tag]], [[XFN]].
** class: [[adr]], [[figure]], [[geo]], [[hAtom]], [[hAudio]], [[User:TobyInk/hcalendar-1.1|hCalendar]], [[hCard]], [[hListing]], [[hNews]], [[hProduct]], [[hRecipe]], [[hResume]], [[hReview]], [[hReview-aggregate]], [[VoteLinks]], [[xFolk]], [[XMDP]], [[XOXO]].
*** highly experimental: [[measure]], [[species]].
** poshformats: [http://ocoins.info/ OpenURL COinS].
** By [[User:TobyInk|Toby Inkster]].

Versions and releases notes:
* 2010-06-23 0.00_11
* 2010-05-13 0.00_10
* 2010-05-12 0.00_09
* 2010-04-29 0.00_08
* 2010-04-28 0.00_07
* 2010-04-16 [http://microformats.org/discuss/mail/microformats-dev/2010-April/000651.html 0.00_06]
* 2010-04-16 0.00_05
* 2010-03-20 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000647.html 0.00_04]
* 2010-03-09 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000642.html 0.00_03]
* 2010-02-28 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000641.html 0.00_02]
* 2010-02-24 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000640.html 0.00_01]
* 2010-02-20 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000639.html 0.00_00]
* see also the "Changes" file included in the CPAN distribution.

==== XML::Atom::Microformats ====

[http://search.cpan.org/~tobyink/XML-Atom-Microformats/ XML::Atom::Microformats] provides the same functionality for Atom. It finds microformats in Atom entry content elements.

===Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a parser for both “upper case Semantic Web” (RDF, RDFa) and “lower case semantic web” (microformats) technologies. It includes modules for exporting parsed data in a variety of formats, including RDF, vCard, iCalendar, Atom and KML.
** By Toby Inkster
** Active development has moved to HTML::Microformats (see above).

=== Text::Microformat ===
* Text::Microformat is a microformats parser hosted on [http://code.google.com/p/ufperl/ Google Code] that supports:
** [[hCard]], [[hCalendar]], [[rel-tag]]

== PHP ==
=== XMFP ===
<span id="xmfp">[http://code.google.com/p/xmfp/ XMFP]</span> (eXtensible MicroFormats Parser for PHP 5) by [http://www.metonymie.com Emiliano Martínez Luque] is a set of PHP 5 classes providing a simple API for extracting Microformated Content either from a URI or a String representing HTML/XML. It can return the results as a PHP associative array, a JSON definition or an XML representation of the data. It supports most of the currently accepted microformats and can be easily extended to add new ones, it also has full support of the include pattern and provides basic validation of microformated data.

=== hKit Microformats Toolkit for PHP5 ===
[http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

===PHP Microformats parser===
[http://www.phpclasses.org/browse/package/3597.html Microformats parser] is a PHP package for extracting the microformats data embedded into HTML. The gathered data is stored as an xArray of objects - one for each microformat type container found. [http://malatestapunk-stuff.blogspot.com/2007/01/php-microformats-parser.html Announcement]. The parser supports most of the hCard (missing SOUND), hCalendar, hReview (missing item info; spec really needs some clarification) and rel elements, according to their respective specification on microformats Wiki.

===Transformr===
A Simple set of XSLT and PHP tools for Transforming Microformats Source [http://github.com/WebOrganics/TransFormr available from github] Live webservice available at [http://microform.at/ microform.at].

=== hCard Validator ===
[http://code.google.com/p/hcardvalidator/ Source code] of the [http://hcard.geekhood.net/ hCard Validator] contains XSLT and PHP code for hCard and include microformats.

=== ARC2 ===
[http://arc.semsol.org/ ARC2] is a semantic web toolkit which includes support for hCard, adr, geo, XFN, hCalendar, hAtom, hResume, hReview, xFolk, rel-license and rel-tag. It's tri-licensed under the GPL 2 and 3, and the W3C Software licence.

== Python ==
===AUMP===
* [http://aump.googlecode.com AUMP] is a parser written by David Janes. It supports hCard, hCalendar, hAtom, hReview and hListing.
** Uses Python's [http://docs.python.org/library/xml.dom.minidom.html xml.dom.minidom] after cleaning input through [http://www.w3.org/People/Raggett/tidy/ HTML Tidy].

===Microtron===
* [[Microtron]] is intended to be a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

== Ruby ==
===Prism ===
* [[Prism]]
** by [[implementors#Mark_Wunsch|Mark Wunsch]]
** Library and command line tool for parsing POSH/Microformats
** Uses the [http://nokogiri.org/ Nokogiri] HTML, XML, SAX, and Reader parser

=== mofo ruby microformats parser===
* [http://mofo.rubyforge.org/ mofo], [http://groups.google.com/group/mofo-rb mofo Google Group], [http://github.com/defunkt/mofo/tree/master GitHub repository]
** by [[implementors#Chris Wanstrath|Chris Wanstrath]]
** Uses the [http://wiki.github.com/why/hpricot Hpricot] HTML/XML parser

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== uformats ===
* [http://rubyforge.org/projects/uformats uformats]

=== scrAPI ===
* [http://rubyforge.org/projects/scrapi scrAPI]

== XSLT ==
===Optimus===
* [[Optimus]] is open source XSLT that parses microformats, converts them into JSON or XML, and validates them too.

===X2V===
* [[X2V]] is [http://hg.microformats.org/ open source XSLT for extracting microformats].
** by Brian Suda

== editing this page ==
For now, this page ''copies'' (rather than ''moves'') information from the existing [[implementations | Implementations]] page.

== see also ==
* [[implementations]]
* [[implementors]]
* [[user-interface]]
* [[open-source]]

parsers

2010-06-25T22:50:46Z

WebOrganics: /* Transformr */ updated link

<entry-title>Microformats Parsers</entry-title>
;shortlinks
:http://ufs.cc/w/parsers (preferred)
:http://tr.im/ufprs
This page lists libraries that consume, transform or convert microformats. This is only a partial list. If you know of other such tools for microformats, please add them and list what specific microformats they support.

Alphabetical listing by programming language:

== Java ==
* [http://code.google.com/p/any23/ Any23 (Anything to Triples)] parses microformats into RDF triples
* [http://zwitserloot.com/org.microformats.hCard/ org.microformats.hCard] by Reinier Zwitserloot

== Javascript ==
=== Sumo ===
* [http://www.danwebb.net/2007/2/9/sumo-a-generic-microformats-parser-for-javascript Sumo! A Generic Microformats Parser For JavaScript]

== Perl ==
=== Data::Microformat ===
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo.
** By Brendan O'Connor / Six Apart

=== HTML::Microformats ===
Perhaps we can capture and update this info on a page like [[perl-html-microformats-parser]].
* [http://search.cpan.org/~tobyink/HTML-Microformats/ HTML::Microformats] is a CPAN module that has support for:
** rel: [[rel-enclosure]], [[rel-license]], [[rel-tag]], [[XFN]].
** class: [[adr]], [[figure]], [[geo]], [[hAtom]], [[hAudio]], [[User:TobyInk/hcalendar-1.1|hCalendar]], [[hCard]], [[hListing]], [[hNews]], [[hProduct]], [[hRecipe]], [[hResume]], [[hReview]], [[hReview-aggregate]], [[VoteLinks]], [[xFolk]], [[XMDP]], [[XOXO]].
*** highly experimental: [[measure]], [[species]].
** poshformats: [http://ocoins.info/ OpenURL COinS].
** By [[User:TobyInk|Toby Inkster]].

Versions and releases notes:
* 2010-06-23 0.00_11
* 2010-05-13 0.00_10
* 2010-05-12 0.00_09
* 2010-04-29 0.00_08
* 2010-04-28 0.00_07
* 2010-04-16 [http://microformats.org/discuss/mail/microformats-dev/2010-April/000651.html 0.00_06]
* 2010-04-16 0.00_05
* 2010-03-20 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000647.html 0.00_04]
* 2010-03-09 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000642.html 0.00_03]
* 2010-02-28 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000641.html 0.00_02]
* 2010-02-24 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000640.html 0.00_01]
* 2010-02-20 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000639.html 0.00_00]
* see also the "Changes" file included in the CPAN distribution.

==== XML::Atom::Microformats ====

[http://search.cpan.org/~tobyink/XML-Atom-Microformats/ XML::Atom::Microformats] provides the same functionality for Atom. It finds microformats in Atom entry content elements.

===Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a parser for both “upper case Semantic Web” (RDF, RDFa) and “lower case semantic web” (microformats) technologies. It includes modules for exporting parsed data in a variety of formats, including RDF, vCard, iCalendar, Atom and KML.
** By Toby Inkster
** Active development has moved to HTML::Microformats (see above).

=== Text::Microformat ===
* Text::Microformat is a microformats parser hosted on [http://code.google.com/p/ufperl/ Google Code] that supports:
** [[hCard]], [[hCalendar]], [[rel-tag]]

== PHP ==
=== XMFP ===
<span id="xmfp">[http://code.google.com/p/xmfp/ XMFP]</span> (eXtensible MicroFormats Parser for PHP 5) by [http://www.metonymie.com Emiliano Martínez Luque] is a set of PHP 5 classes providing a simple API for extracting Microformated Content either from a URI or a String representing HTML/XML. It can return the results as a PHP associative array, a JSON definition or an XML representation of the data. It supports most of the currently accepted microformats and can be easily extended to add new ones, it also has full support of the include pattern and provides basic validation of microformated data.

=== hKit Microformats Toolkit for PHP5 ===
[http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

===PHP Microformats parser===
[http://www.phpclasses.org/browse/package/3597.html Microformats parser] is a PHP package for extracting the microformats data embedded into HTML. The gathered data is stored as an xArray of objects - one for each microformat type container found. [http://malatestapunk-stuff.blogspot.com/2007/01/php-microformats-parser.html Announcement]. The parser supports most of the hCard (missing SOUND), hCalendar, hReview (missing item info; spec really needs some clarification) and rel elements, according to their respective specification on microformats Wiki.

===Transformr===
A Simple set of XSLT and PHP tools for Transforming Microformats Source [http://github.com/WebOrganics/TransFormr available from github] Live webservice available at [http://microform.at/].

=== hCard Validator ===
[http://code.google.com/p/hcardvalidator/ Source code] of the [http://hcard.geekhood.net/ hCard Validator] contains XSLT and PHP code for hCard and include microformats.

=== ARC2 ===
[http://arc.semsol.org/ ARC2] is a semantic web toolkit which includes support for hCard, adr, geo, XFN, hCalendar, hAtom, hResume, hReview, xFolk, rel-license and rel-tag. It's tri-licensed under the GPL 2 and 3, and the W3C Software licence.

== Python ==
===AUMP===
* [http://aump.googlecode.com AUMP] is a parser written by David Janes. It supports hCard, hCalendar, hAtom, hReview and hListing.
** Uses Python's [http://docs.python.org/library/xml.dom.minidom.html xml.dom.minidom] after cleaning input through [http://www.w3.org/People/Raggett/tidy/ HTML Tidy].

===Microtron===
* [[Microtron]] is intended to be a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

== Ruby ==
===Prism ===
* [[Prism]]
** by [[implementors#Mark_Wunsch|Mark Wunsch]]
** Library and command line tool for parsing POSH/Microformats
** Uses the [http://nokogiri.org/ Nokogiri] HTML, XML, SAX, and Reader parser

=== mofo ruby microformats parser===
* [http://mofo.rubyforge.org/ mofo], [http://groups.google.com/group/mofo-rb mofo Google Group], [http://github.com/defunkt/mofo/tree/master GitHub repository]
** by [[implementors#Chris Wanstrath|Chris Wanstrath]]
** Uses the [http://wiki.github.com/why/hpricot Hpricot] HTML/XML parser

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== uformats ===
* [http://rubyforge.org/projects/uformats uformats]

=== scrAPI ===
* [http://rubyforge.org/projects/scrapi scrAPI]

== XSLT ==
===Optimus===
* [[Optimus]] is open source XSLT that parses microformats, converts them into JSON or XML, and validates them too.

===X2V===
* [[X2V]] is [http://hg.microformats.org/ open source XSLT for extracting microformats].
** by Brian Suda

== editing this page ==
For now, this page ''copies'' (rather than ''moves'') information from the existing [[implementations | Implementations]] page.

== see also ==
* [[implementations]]
* [[implementors]]
* [[user-interface]]
* [[open-source]]

User:RyanKing

2010-06-19T11:39:26Z

WebOrganics: Undo revision 42697 by Fitrisartika (Talk) *spam*

ryan king

http://theryanking.com

ryan@theryanking.com

----
{{cc-public-domain-release}}

User:WebOrganics

2010-06-12T23:41:51Z

WebOrganics: updated links

<div class="vcard" id="weborganics">
<h1><span class="fn">
<span class="given-name">Martin</span>
<span class="family-name"> McEvoy</span>
</span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url uid"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
<span class="note">
WebOrganics is a small Web Design and Development Company based in Lancashire England.
</span>
</div>

http://weborganics.co.uk/images/hcard-download.png [http://microform.at/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://github.com/WebOrganics/TransFormr TransFormr]: Transformation tools for Microformats

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

haudio-issues

2010-06-11T15:36:14Z

WebOrganics: /* D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern */ +1

=hAudio issues=

These are externally raised issues about [[haudio|hAudio]] with broadly varying degrees of merit. Thus some issues are <em style="text-transform:uppercase;">rejected</em> for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be <em style="text-transform:uppercase;">accepted</em> and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible.

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[haudio-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
* You can subscribe to all haudio issues on <nowiki>webcal://feeds.technorati.com/events/http://microformats.org/wiki/haudio-issues</nowiki>

==2008==

=== D1: 2008-01-10 Contributor ===
<div class="vevent">
* {{ResolvedIssue}} D1: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011340.html microformats-discuss/2008-January/011340.html]</span>
<div class="description">
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
*#* A resolution to this issue is outlined in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
*#* ACCEPTED ISSUE The hAudio Contributor Specification is to be changed to:
*#** The element is identified by the class name |contributor|.
*#** hAudio /MAY/ include one or more contributors.
*#** The contributor's name SHOULD also be marked up as a valid hCard Microformat. <http://microformats.org/wiki/hcard>
*#**# The |role| attribute /SHOULD/ be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
*#** The contributor's name MAY be specified in plain-text without being enclosed in a hCard Microformat.
*#* REMOVED:
*#** If multiple contributors are specified, without |role| specifications, it /MAY/ be assumed that the first role mentioned is the primary artist or creator.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
</div>
</div>

=== D2: 2008-01-10 hAudio Title was Overloading "fn".===

<div class="vevent">
* {{ResolvedIssue}} D2: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011342.html] </span>
<div class="description">
The "overloading" of <code>fn</code> for both the tile of a work and the name of a contributor causes problems (see above e-mail for examples). Another example of this problem is a table, where the "artist" column comes before the "title" column. For discussion, see also [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
# Existing Resolution [[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (first choice)
#* +1 [[User:ManuSporny|Sarven Capadisli]] (second choice)
# Resolution 1: [[User:WebOrganics|Martin McEvoy]] proposed change <code>"title"</code> to <code>"name"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-March/001555.html microformats-new/2008-March/001555.html]
# Resolution 2: [[User:WebOrganics|Martin McEvoy]] later propsosed that <code>"title"</code> should be replaced with <code>"htitle"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (second choice)
#* +1 [[User:Csarven|Sarven Capadisli]] (first choice)
# Resolution 3: Use <code>"audio-title"</code> As tentatively proposed by [[User:ManuSporny|Manu Sporny]] see:[http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
# Resolution 4: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/wiki?title=haudio&diff=prev&oldid=25667]
#* +1 [[User:WebOrganics|Martin McEvoy]] Without Reservations see:[http://microformats.org/wiki?title=haudio-issues&diff=0&oldid=28703 haudio-issues&diff=0&oldid=28703]
#* +1 [[User:ManuSporny|Manu Sporny]] (third choice)
#* +1 [[User:DavidJanes]] this is the correct thing to do
#* +1 [[User:Csarven|Sarven Capadisli]] (third choice)
# Don't really care — just pick one. ;-)
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:ManuSporny|Manu Sporny]] - close this damn discussion, already! :)
* ACCEPTED ISSUE, RESOLUTION: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-September/001797.html microformats-new/2008-September/001797.html]
</div>
</div>

=== D3: 2008-01-10 Position. ===
<div class="vevent">
* {{ResolvedIssue}} D3: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011343.html microformats-discuss/2008-January/011343.html]</span>
<div class="description">
*# The [http://microformats.org/wiki/haudio#Complete_Album_Example recommended use of "position" in hAudio] is contrary to the good practice, semantic use of ordered lists (see example and suggested solution in the above e-mail; also [http://microformats.org/discuss/mail/microformats-new/2008-January/001338.html] et seq)
*#* For Cognition I'm considering an extension: if no position has been explicitly marked up, and the item is <code><li class="item"></code> within an ordered list, then the position is taken to be the numerical value of the list marker. (To calculate the numerical value for the list marker, find the most recent sibling <code><li></code> element which has a <code>value</code> attribute. The numerical value is the number in that value attribute added to the count of <code><li></code> elements after that value attribute up to the current one. If there are no such <code><li></code> elements with <code>value</code> attributes, then you should assume that the <code>value</code> attribute of the first list item is equal to the <code>start</code> attribute of the ordered list itself, or "1" if there is no such <code>start</code> attribute. [[User:TobyInk|TobyInk]] 04:24, 29 Jul 2008 (PDT)
*#* A Proposed Resolution was made in this email: ( http://microformats.org/discuss/mail/microformats-new/2008-August/001751.html)
*#* ACCEPTED ISSUE The hAudio Position Specification is to be changed to:
*#** The element is identified by the class name |position|.
*#** hAudio /MAY/ include one |position| element.
*#** The contents of the element /MUST/ be a number or other sequential identifier.
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#* ADDED:
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001708.html
*#* [[User:AndyMabbett|Andy Mabbett]] also Expressed concerns that the [[haudio#Complete_Album_Example|Complete Album Example]] should be marked up as an ordered list this is unnecessary as <code>"position"</code> is not related to the order of a track item in a list.
*#* A tutorial on the correct use of semantic ordered lists and hAudio is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D4: 2008-01-10 rel-enclosure does not allow for links to streaming files ===
<div class="vevent">
* {{ResolvedIssue}} D4: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
*# The required use of [[rel-enclosure]] does not allow for links to streaming files, which are not cacheable, and are thus outside the scope of rel-enclosure. [http://www.bbc.co.uk/radio4/science/livingworld_20041121.shtml An example on the BBC website] has the relevant link is below the heading "LISTEN AGAIN". (see discussion at [http://microformats.org/discuss/mail/microformats-new/2008-January/001339.html microformats-new/2008-January/001339.html] et seq).
*#* A proposal for this issue was first made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001715.html
*#* A second proposal for this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001727.html
*#* This can potentially be solved by recognition of downloadable/streamable MIME types. For performance reasons it is undesirable for parsers to be required to make HTTP requests for each file to determine its MIME type, so authors should be encouraged to include the MIME type in the <code>type</code> attribute. See the [[haudio-brainstorming#Download_links|related section on "brainstorming"]]. [[User:TobyInk|TobyInk]] 14:41, 20 Aug 2008 (PDT)
*#* ACCEPTED ISSUE The hAudio Enclosure Specification is to be changed to:
*#** The element is identified by a URI fitting the rel-design-pattern, the rel content being enclosure.
*#** hAudio MAY include one or more enclosure URIs.
*#** The type of the file SHOULD be specified by using the type specifier for a URI.
*#* CHANGED:
*#** The type of the file MAY be specified by using the type specifier for a URI.
*#*** As suggested by [[User:Tantek|Tantek Çelik]] in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001731.html
*#*** As Proposed by [[User:TobyInk|Toby Inkster]] on 14:41, 20 Aug 2008 (PDT)
*#* A tutorial on the importance of Type Specifiers and hAudio Enclosures is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D5: 2008-01-10 there is no way of linking to an interim page ===
<div class="vevent">
* {{OpenIssue}} D5: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
There appears to be no mechanism to mark up an hAudio, expressed in plain text on page A, which links to an interim page, B, which in turn links to a file download. For example, the radio shows listed on [http://www.westmidlandbirdclub.com/bibliography/radio].
</div>
# Resolution 1: re use <code>"url"</code> from [[hcard|hCard]].
#* +1 [[User:WebOrganics|Martin McEvoy]] all links are not clickable/hyperlinkable.
#* +1 [[User:TobyInk|TobyInk]]
# Resolution 2: use the rel <code>"bookmark"</code> [http://www.w3.org/TR/REC-html40/types.html#type-links HTML Link Type].
</div>

=== D6: 2008-01-10 hAudio notes inconsistency ===
<div class="vevent">
* {{ResolvedIssue}} D6: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011345.html microformats-discuss/2008-January/011345.html]</span>
<div class="description">
*# [[haudio#Notes|The "Notes" section of the hAudio spec]] says "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using rel-license as specified above.". However, that is the first and only reference to [[rel-license]] on the page.
*#* Typing error changed to "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
*#* hAudio Specification SHOULD include the [[rel-license]] microformat [[User:WebOrganics|Martin McEvoy]] 11:57, 18 Aug 2008 (GMT)
*#* A proposed resolution to this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001720.html
*# RESOLVED <code>rel="licence"</code> is not part of this version of hAudio (0.9) see:http://microformats.org/discuss/mail/microformats-new/2008-August/001747.html
</div>
</div>

==2009==

=== D7: 2009-01-11 Endorsement of optimization patterns in schema listing too strong ===
<div class="vevent">
* {{ResolvedIssue}} D7: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes references to multiple optimization patterns (datetime pattern for <code>published</code>, abbr-pattern for <code>duration</code>). It is currently worded as to imply that those patterns ''must'' be used. Given past disagreement over ABBR in particular, I think the spec should avoid specific endorsement of any pattern, at the very least reducing references to patterns to clear ‘You ''may'' use the abbr-pattern with this field' sort of phrasing.</p>
# Resolution 1: Reword schema listing to use ''may'' language clearly.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The schema now uses ''may'' language more clearly
</div>

=== D8: 2009-01-11 Don't link to currency proposal ===
<div class="vevent">
* {{ResolvedIssue}} D8: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes reference to the currency proposal. Since that is still a proposal, the spec should not endorse it or encourage too-early adoption of it, especially since it's not even a ''draft'' at this stage. Should the currency work be completed, hAudio should be updated later, rather than linking it in pre-emptively.</p>
# Resolution 1: Remove reference to currency proposal from hAudio schema.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The hAudio no longer references the currency proposal, only cites it as an Informative reference at the bottom of the page.
</div>

==2010==

=== D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern ===
<div class="vevent">
* {{OpenIssue}} D9: <span class="summary vcard"><span class="dtstart">2010-06-11</span> raised by <span class="fn">[[User:WebOrganics|Martin McEvoy]]</span>.</span>
<p class="description">[[haudio#Duration|hAudio Duration]] and [[haudio#Published|Published]] should adopt the value-title pattern like [[hrecipe#duration|hRecipe Duration]] and [[hatom-profile|hAtom]], to prevent the user from getting machine data in a tooltip</p>
# Resolution 1: Adopt the value-title pattern for both hAudio Duration and Published.
#* +1 [[User:WebOrganics|Martin McEvoy]]
#* +1 [[User:AndyMabbett|Andy Mabbett]] via: [http://twitter.com/pigsonthewing/statuses/15935702988 Twitter]
</div>

==template==
{{issues-format}}

==see also==
*[[audio-info-issues]]

==related pages==
{{haudio-related-pages}}

haudio-issues

2010-06-11T15:23:43Z

WebOrganics: /* D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern */ change wording so it makes more sense :)

=hAudio issues=

These are externally raised issues about [[haudio|hAudio]] with broadly varying degrees of merit. Thus some issues are <em style="text-transform:uppercase;">rejected</em> for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be <em style="text-transform:uppercase;">accepted</em> and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible.

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[haudio-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
* You can subscribe to all haudio issues on <nowiki>webcal://feeds.technorati.com/events/http://microformats.org/wiki/haudio-issues</nowiki>

==2008==

=== D1: 2008-01-10 Contributor ===
<div class="vevent">
* {{ResolvedIssue}} D1: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011340.html microformats-discuss/2008-January/011340.html]</span>
<div class="description">
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
*#* A resolution to this issue is outlined in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
*#* ACCEPTED ISSUE The hAudio Contributor Specification is to be changed to:
*#** The element is identified by the class name |contributor|.
*#** hAudio /MAY/ include one or more contributors.
*#** The contributor's name SHOULD also be marked up as a valid hCard Microformat. <http://microformats.org/wiki/hcard>
*#**# The |role| attribute /SHOULD/ be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
*#** The contributor's name MAY be specified in plain-text without being enclosed in a hCard Microformat.
*#* REMOVED:
*#** If multiple contributors are specified, without |role| specifications, it /MAY/ be assumed that the first role mentioned is the primary artist or creator.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
</div>
</div>

=== D2: 2008-01-10 hAudio Title was Overloading "fn".===

<div class="vevent">
* {{ResolvedIssue}} D2: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011342.html] </span>
<div class="description">
The "overloading" of <code>fn</code> for both the tile of a work and the name of a contributor causes problems (see above e-mail for examples). Another example of this problem is a table, where the "artist" column comes before the "title" column. For discussion, see also [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
# Existing Resolution [[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (first choice)
#* +1 [[User:ManuSporny|Sarven Capadisli]] (second choice)
# Resolution 1: [[User:WebOrganics|Martin McEvoy]] proposed change <code>"title"</code> to <code>"name"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-March/001555.html microformats-new/2008-March/001555.html]
# Resolution 2: [[User:WebOrganics|Martin McEvoy]] later propsosed that <code>"title"</code> should be replaced with <code>"htitle"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (second choice)
#* +1 [[User:Csarven|Sarven Capadisli]] (first choice)
# Resolution 3: Use <code>"audio-title"</code> As tentatively proposed by [[User:ManuSporny|Manu Sporny]] see:[http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
# Resolution 4: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/wiki?title=haudio&diff=prev&oldid=25667]
#* +1 [[User:WebOrganics|Martin McEvoy]] Without Reservations see:[http://microformats.org/wiki?title=haudio-issues&diff=0&oldid=28703 haudio-issues&diff=0&oldid=28703]
#* +1 [[User:ManuSporny|Manu Sporny]] (third choice)
#* +1 [[User:DavidJanes]] this is the correct thing to do
#* +1 [[User:Csarven|Sarven Capadisli]] (third choice)
# Don't really care — just pick one. ;-)
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:ManuSporny|Manu Sporny]] - close this damn discussion, already! :)
* ACCEPTED ISSUE, RESOLUTION: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-September/001797.html microformats-new/2008-September/001797.html]
</div>
</div>

=== D3: 2008-01-10 Position. ===
<div class="vevent">
* {{ResolvedIssue}} D3: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011343.html microformats-discuss/2008-January/011343.html]</span>
<div class="description">
*# The [http://microformats.org/wiki/haudio#Complete_Album_Example recommended use of "position" in hAudio] is contrary to the good practice, semantic use of ordered lists (see example and suggested solution in the above e-mail; also [http://microformats.org/discuss/mail/microformats-new/2008-January/001338.html] et seq)
*#* For Cognition I'm considering an extension: if no position has been explicitly marked up, and the item is <code><li class="item"></code> within an ordered list, then the position is taken to be the numerical value of the list marker. (To calculate the numerical value for the list marker, find the most recent sibling <code><li></code> element which has a <code>value</code> attribute. The numerical value is the number in that value attribute added to the count of <code><li></code> elements after that value attribute up to the current one. If there are no such <code><li></code> elements with <code>value</code> attributes, then you should assume that the <code>value</code> attribute of the first list item is equal to the <code>start</code> attribute of the ordered list itself, or "1" if there is no such <code>start</code> attribute. [[User:TobyInk|TobyInk]] 04:24, 29 Jul 2008 (PDT)
*#* A Proposed Resolution was made in this email: ( http://microformats.org/discuss/mail/microformats-new/2008-August/001751.html)
*#* ACCEPTED ISSUE The hAudio Position Specification is to be changed to:
*#** The element is identified by the class name |position|.
*#** hAudio /MAY/ include one |position| element.
*#** The contents of the element /MUST/ be a number or other sequential identifier.
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#* ADDED:
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001708.html
*#* [[User:AndyMabbett|Andy Mabbett]] also Expressed concerns that the [[haudio#Complete_Album_Example|Complete Album Example]] should be marked up as an ordered list this is unnecessary as <code>"position"</code> is not related to the order of a track item in a list.
*#* A tutorial on the correct use of semantic ordered lists and hAudio is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D4: 2008-01-10 rel-enclosure does not allow for links to streaming files ===
<div class="vevent">
* {{ResolvedIssue}} D4: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
*# The required use of [[rel-enclosure]] does not allow for links to streaming files, which are not cacheable, and are thus outside the scope of rel-enclosure. [http://www.bbc.co.uk/radio4/science/livingworld_20041121.shtml An example on the BBC website] has the relevant link is below the heading "LISTEN AGAIN". (see discussion at [http://microformats.org/discuss/mail/microformats-new/2008-January/001339.html microformats-new/2008-January/001339.html] et seq).
*#* A proposal for this issue was first made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001715.html
*#* A second proposal for this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001727.html
*#* This can potentially be solved by recognition of downloadable/streamable MIME types. For performance reasons it is undesirable for parsers to be required to make HTTP requests for each file to determine its MIME type, so authors should be encouraged to include the MIME type in the <code>type</code> attribute. See the [[haudio-brainstorming#Download_links|related section on "brainstorming"]]. [[User:TobyInk|TobyInk]] 14:41, 20 Aug 2008 (PDT)
*#* ACCEPTED ISSUE The hAudio Enclosure Specification is to be changed to:
*#** The element is identified by a URI fitting the rel-design-pattern, the rel content being enclosure.
*#** hAudio MAY include one or more enclosure URIs.
*#** The type of the file SHOULD be specified by using the type specifier for a URI.
*#* CHANGED:
*#** The type of the file MAY be specified by using the type specifier for a URI.
*#*** As suggested by [[User:Tantek|Tantek Çelik]] in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001731.html
*#*** As Proposed by [[User:TobyInk|Toby Inkster]] on 14:41, 20 Aug 2008 (PDT)
*#* A tutorial on the importance of Type Specifiers and hAudio Enclosures is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D5: 2008-01-10 there is no way of linking to an interim page ===
<div class="vevent">
* {{OpenIssue}} D5: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
There appears to be no mechanism to mark up an hAudio, expressed in plain text on page A, which links to an interim page, B, which in turn links to a file download. For example, the radio shows listed on [http://www.westmidlandbirdclub.com/bibliography/radio].
</div>
# Resolution 1: re use <code>"url"</code> from [[hcard|hCard]].
#* +1 [[User:WebOrganics|Martin McEvoy]] all links are not clickable/hyperlinkable.
#* +1 [[User:TobyInk|TobyInk]]
# Resolution 2: use the rel <code>"bookmark"</code> [http://www.w3.org/TR/REC-html40/types.html#type-links HTML Link Type].
</div>

=== D6: 2008-01-10 hAudio notes inconsistency ===
<div class="vevent">
* {{ResolvedIssue}} D6: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011345.html microformats-discuss/2008-January/011345.html]</span>
<div class="description">
*# [[haudio#Notes|The "Notes" section of the hAudio spec]] says "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using rel-license as specified above.". However, that is the first and only reference to [[rel-license]] on the page.
*#* Typing error changed to "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
*#* hAudio Specification SHOULD include the [[rel-license]] microformat [[User:WebOrganics|Martin McEvoy]] 11:57, 18 Aug 2008 (GMT)
*#* A proposed resolution to this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001720.html
*# RESOLVED <code>rel="licence"</code> is not part of this version of hAudio (0.9) see:http://microformats.org/discuss/mail/microformats-new/2008-August/001747.html
</div>
</div>

==2009==

=== D7: 2009-01-11 Endorsement of optimization patterns in schema listing too strong ===
<div class="vevent">
* {{ResolvedIssue}} D7: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes references to multiple optimization patterns (datetime pattern for <code>published</code>, abbr-pattern for <code>duration</code>). It is currently worded as to imply that those patterns ''must'' be used. Given past disagreement over ABBR in particular, I think the spec should avoid specific endorsement of any pattern, at the very least reducing references to patterns to clear ‘You ''may'' use the abbr-pattern with this field' sort of phrasing.</p>
# Resolution 1: Reword schema listing to use ''may'' language clearly.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The schema now uses ''may'' language more clearly
</div>

=== D8: 2009-01-11 Don't link to currency proposal ===
<div class="vevent">
* {{ResolvedIssue}} D8: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes reference to the currency proposal. Since that is still a proposal, the spec should not endorse it or encourage too-early adoption of it, especially since it's not even a ''draft'' at this stage. Should the currency work be completed, hAudio should be updated later, rather than linking it in pre-emptively.</p>
# Resolution 1: Remove reference to currency proposal from hAudio schema.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The hAudio no longer references the currency proposal, only cites it as an Informative reference at the bottom of the page.
</div>

==2010==

=== D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern ===
<div class="vevent">
* {{OpenIssue}} D9: <span class="summary vcard"><span class="dtstart">2010-06-11</span> raised by <span class="fn">[[User:WebOrganics|Martin McEvoy]]</span>.</span>
<p class="description">[[haudio#Duration|hAudio Duration]] and [[haudio#Published|Published]] should adopt the value-title pattern like [[hrecipe#duration|hRecipe Duration]] and [[hatom-profile|hAtom]], to prevent the user from getting machine data in a tooltip</p>
# Resolution 1: Adopt the value-title pattern for both hAudio Duration and Published.
#* +1 [[User:WebOrganics|Martin McEvoy]]
</div>

==template==
{{issues-format}}

==see also==
*[[audio-info-issues]]

==related pages==
{{haudio-related-pages}}

haudio-issues

2010-06-11T13:45:48Z

WebOrganics: /* 2010 */ hAudio duration and published should adopt the value-title pattern

=hAudio issues=

These are externally raised issues about [[haudio|hAudio]] with broadly varying degrees of merit. Thus some issues are <em style="text-transform:uppercase;">rejected</em> for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be <em style="text-transform:uppercase;">accepted</em> and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible.

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[haudio-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
* You can subscribe to all haudio issues on <nowiki>webcal://feeds.technorati.com/events/http://microformats.org/wiki/haudio-issues</nowiki>

==2008==

=== D1: 2008-01-10 Contributor ===
<div class="vevent">
* {{ResolvedIssue}} D1: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011340.html microformats-discuss/2008-January/011340.html]</span>
<div class="description">
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
*#* A resolution to this issue is outlined in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
*#* ACCEPTED ISSUE The hAudio Contributor Specification is to be changed to:
*#** The element is identified by the class name |contributor|.
*#** hAudio /MAY/ include one or more contributors.
*#** The contributor's name SHOULD also be marked up as a valid hCard Microformat. <http://microformats.org/wiki/hcard>
*#**# The |role| attribute /SHOULD/ be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
*#** The contributor's name MAY be specified in plain-text without being enclosed in a hCard Microformat.
*#* REMOVED:
*#** If multiple contributors are specified, without |role| specifications, it /MAY/ be assumed that the first role mentioned is the primary artist or creator.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001725.html
</div>
</div>

=== D2: 2008-01-10 hAudio Title was Overloading "fn".===

<div class="vevent">
* {{ResolvedIssue}} D2: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011342.html] </span>
<div class="description">
The "overloading" of <code>fn</code> for both the tile of a work and the name of a contributor causes problems (see above e-mail for examples). Another example of this problem is a table, where the "artist" column comes before the "title" column. For discussion, see also [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
# Existing Resolution [[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (first choice)
#* +1 [[User:ManuSporny|Sarven Capadisli]] (second choice)
# Resolution 1: [[User:WebOrganics|Martin McEvoy]] proposed change <code>"title"</code> to <code>"name"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-March/001555.html microformats-new/2008-March/001555.html]
# Resolution 2: [[User:WebOrganics|Martin McEvoy]] later propsosed that <code>"title"</code> should be replaced with <code>"htitle"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
#* +1 [[User:ManuSporny|Manu Sporny]] (second choice)
#* +1 [[User:Csarven|Sarven Capadisli]] (first choice)
# Resolution 3: Use <code>"audio-title"</code> As tentatively proposed by [[User:ManuSporny|Manu Sporny]] see:[http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
# Resolution 4: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/wiki?title=haudio&diff=prev&oldid=25667]
#* +1 [[User:WebOrganics|Martin McEvoy]] Without Reservations see:[http://microformats.org/wiki?title=haudio-issues&diff=0&oldid=28703 haudio-issues&diff=0&oldid=28703]
#* +1 [[User:ManuSporny|Manu Sporny]] (third choice)
#* +1 [[User:DavidJanes]] this is the correct thing to do
#* +1 [[User:Csarven|Sarven Capadisli]] (third choice)
# Don't really care — just pick one. ;-)
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:ManuSporny|Manu Sporny]] - close this damn discussion, already! :)
* ACCEPTED ISSUE, RESOLUTION: Change <code>"title"</code> back to <code>"fn"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-September/001797.html microformats-new/2008-September/001797.html]
</div>
</div>

=== D3: 2008-01-10 Position. ===
<div class="vevent">
* {{ResolvedIssue}} D3: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011343.html microformats-discuss/2008-January/011343.html]</span>
<div class="description">
*# The [http://microformats.org/wiki/haudio#Complete_Album_Example recommended use of "position" in hAudio] is contrary to the good practice, semantic use of ordered lists (see example and suggested solution in the above e-mail; also [http://microformats.org/discuss/mail/microformats-new/2008-January/001338.html] et seq)
*#* For Cognition I'm considering an extension: if no position has been explicitly marked up, and the item is <code><li class="item"></code> within an ordered list, then the position is taken to be the numerical value of the list marker. (To calculate the numerical value for the list marker, find the most recent sibling <code><li></code> element which has a <code>value</code> attribute. The numerical value is the number in that value attribute added to the count of <code><li></code> elements after that value attribute up to the current one. If there are no such <code><li></code> elements with <code>value</code> attributes, then you should assume that the <code>value</code> attribute of the first list item is equal to the <code>start</code> attribute of the ordered list itself, or "1" if there is no such <code>start</code> attribute. [[User:TobyInk|TobyInk]] 04:24, 29 Jul 2008 (PDT)
*#* A Proposed Resolution was made in this email: ( http://microformats.org/discuss/mail/microformats-new/2008-August/001751.html)
*#* ACCEPTED ISSUE The hAudio Position Specification is to be changed to:
*#** The element is identified by the class name |position|.
*#** hAudio /MAY/ include one |position| element.
*#** The contents of the element /MUST/ be a number or other sequential identifier.
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#* ADDED:
*#** The sequential identifier /MAY/ be specified out-of-sequence.
*#**# As proposed By [[User:ManuSporny|Manu Sporny]] in http://microformats.org/discuss/mail/microformats-new/2008-August/001708.html
*#* [[User:AndyMabbett|Andy Mabbett]] also Expressed concerns that the [[haudio#Complete_Album_Example|Complete Album Example]] should be marked up as an ordered list this is unnecessary as <code>"position"</code> is not related to the order of a track item in a list.
*#* A tutorial on the correct use of semantic ordered lists and hAudio is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D4: 2008-01-10 rel-enclosure does not allow for links to streaming files ===
<div class="vevent">
* {{ResolvedIssue}} D4: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
*# The required use of [[rel-enclosure]] does not allow for links to streaming files, which are not cacheable, and are thus outside the scope of rel-enclosure. [http://www.bbc.co.uk/radio4/science/livingworld_20041121.shtml An example on the BBC website] has the relevant link is below the heading "LISTEN AGAIN". (see discussion at [http://microformats.org/discuss/mail/microformats-new/2008-January/001339.html microformats-new/2008-January/001339.html] et seq).
*#* A proposal for this issue was first made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001715.html
*#* A second proposal for this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001727.html
*#* This can potentially be solved by recognition of downloadable/streamable MIME types. For performance reasons it is undesirable for parsers to be required to make HTTP requests for each file to determine its MIME type, so authors should be encouraged to include the MIME type in the <code>type</code> attribute. See the [[haudio-brainstorming#Download_links|related section on "brainstorming"]]. [[User:TobyInk|TobyInk]] 14:41, 20 Aug 2008 (PDT)
*#* ACCEPTED ISSUE The hAudio Enclosure Specification is to be changed to:
*#** The element is identified by a URI fitting the rel-design-pattern, the rel content being enclosure.
*#** hAudio MAY include one or more enclosure URIs.
*#** The type of the file SHOULD be specified by using the type specifier for a URI.
*#* CHANGED:
*#** The type of the file MAY be specified by using the type specifier for a URI.
*#*** As suggested by [[User:Tantek|Tantek Çelik]] in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001731.html
*#*** As Proposed by [[User:TobyInk|Toby Inkster]] on 14:41, 20 Aug 2008 (PDT)
*#* A tutorial on the importance of Type Specifiers and hAudio Enclosures is to be added to the [[haudio-authoring|hAudio Authoring]] Page
</div>
</div>

=== D5: 2008-01-10 there is no way of linking to an interim page ===
<div class="vevent">
* {{OpenIssue}} D5: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html microformats-discuss/2008-January/011344.html]</span>
<div class="description">
There appears to be no mechanism to mark up an hAudio, expressed in plain text on page A, which links to an interim page, B, which in turn links to a file download. For example, the radio shows listed on [http://www.westmidlandbirdclub.com/bibliography/radio].
</div>
# Resolution 1: re use <code>"url"</code> from [[hcard|hCard]].
#* +1 [[User:WebOrganics|Martin McEvoy]] all links are not clickable/hyperlinkable.
#* +1 [[User:TobyInk|TobyInk]]
# Resolution 2: use the rel <code>"bookmark"</code> [http://www.w3.org/TR/REC-html40/types.html#type-links HTML Link Type].
</div>

=== D6: 2008-01-10 hAudio notes inconsistency ===
<div class="vevent">
* {{ResolvedIssue}} D6: <span class="summary vcard"><span class="dtstart">2008-01-10</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011345.html microformats-discuss/2008-January/011345.html]</span>
<div class="description">
*# [[haudio#Notes|The "Notes" section of the hAudio spec]] says "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using rel-license as specified above.". However, that is the first and only reference to [[rel-license]] on the page.
*#* Typing error changed to "By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
*#* hAudio Specification SHOULD include the [[rel-license]] microformat [[User:WebOrganics|Martin McEvoy]] 11:57, 18 Aug 2008 (GMT)
*#* A proposed resolution to this issue has been made in this email http://microformats.org/discuss/mail/microformats-new/2008-August/001720.html
*# RESOLVED <code>rel="licence"</code> is not part of this version of hAudio (0.9) see:http://microformats.org/discuss/mail/microformats-new/2008-August/001747.html
</div>
</div>

==2009==

=== D7: 2009-01-11 Endorsement of optimization patterns in schema listing too strong ===
<div class="vevent">
* {{ResolvedIssue}} D7: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes references to multiple optimization patterns (datetime pattern for <code>published</code>, abbr-pattern for <code>duration</code>). It is currently worded as to imply that those patterns ''must'' be used. Given past disagreement over ABBR in particular, I think the spec should avoid specific endorsement of any pattern, at the very least reducing references to patterns to clear ‘You ''may'' use the abbr-pattern with this field' sort of phrasing.</p>
# Resolution 1: Reword schema listing to use ''may'' language clearly.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The schema now uses ''may'' language more clearly
</div>

=== D8: 2009-01-11 Don't link to currency proposal ===
<div class="vevent">
* {{ResolvedIssue}} D8: <span class="summary vcard"><span class="dtstart">2009-01-11</span> raised by <span class="fn">[[User:BenWard|Ben Ward]]</span>.</span>
<p class="description">The hAudio spec schema makes reference to the currency proposal. Since that is still a proposal, the spec should not endorse it or encourage too-early adoption of it, especially since it's not even a ''draft'' at this stage. Should the currency work be completed, hAudio should be updated later, rather than linking it in pre-emptively.</p>
# Resolution 1: Remove reference to currency proposal from hAudio schema.
#* +1 [[User:BenWard|Ben Ward]]
#* +1 [[User:TobyInk|TobyInk]]
#* +1 [[User:WebOrganics|Martin McEvoy]]
** RESOLUTION: The hAudio no longer references the currency proposal, only cites it as an Informative reference at the bottom of the page.
</div>

==2010==

=== D9: 2010-06-11 hAudio duration and published should adopt the value-title pattern ===
<div class="vevent">
* {{OpenIssue}} D9: <span class="summary vcard"><span class="dtstart">2010-06-11</span> raised by <span class="fn">[[User:WebOrganics|Martin McEvoy]]</span>.</span>
<p class="description">[[haudio#Duration|hAudio Duration]] and [[haudio#Published|Published]] should adopt the value-title pattern, to prevent the user from getting machine data in a tooltip, like [[hrecipe#duration|hRecipe Duration]] and [[hatom-profile|hAtom]]</p>
# Resolution 1: Adopt the value-title pattern for both hAudio Duration and Published.
#* +1 [[User:WebOrganics|Martin McEvoy]]
</div>

==template==
{{issues-format}}

==see also==
*[[audio-info-issues]]

==related pages==
{{haudio-related-pages}}

implementations

2010-05-17T18:46:58Z

WebOrganics: /* Transformr */ updting url's

<entry-title>Microformats Implementations</entry-title>
{{TOC-right}}
This page lists the applications, plugins, sample code, services, tools that produce or consume microformats.

== help improve this page ==
This is only a partial list. If you know other services or tools for or supporting microformats, please add them to this page, link to their [[implementors]], and list what specific microformats they support.

When you find an implementation:
# Make sure that it is an implementation, rather an publishing example (e.g. [[hcard-examples-in-wild|hCard examples in the wild]], [[hcalendar-examples-in-wild|hCalendar examples]], et.c).
# Note the name of the ''tool or service'' and the name of the ''developer(s)'' who built it.
# Add a third level heading with the name of the tool/service to the Applications / Plugins / Services / Tools section below, sorted alphabetically by name of tool/service. e.g. <p><kbd><nowiki>=== Name of Tool ===</nowiki></kbd></p>
# Add a top level list item just below the heading with an external link to the tool/service, along with a link to evidence of their support for microformats, and mention (and locally link) each microformat that is supported. E.g. <p><kbd>* Link to tool/service, link to their blog post announcing support for e.g. <nowiki>[[hCard]] and [[hReview]]</nowiki></kbd></p>
# Add a nested list item and local to wiki hyperlink the Name of Developer to a fragment identifier in the [[implementors]] page, e.g. Apple Computer would be linked like this: <p><kbd><nowiki>** by [[implementors#Apple_Computer|Apple Computer]]</nowiki></kbd></p>
# Check to see if there is an entry for the developer in the [[implementors|list of implementors]], if not add them there. Add a link to the developer's home page followed by "has implemented microformats in:".
# In the entry for the developer, add a list item and local to wiki hyperlink the Name of Tool to a fragment identifier in this page, e.g. X2V would be linked like this: <p><kbd><nowiki>* [[implementations#X2V|X2V]]</nowiki></kbd></p>
# Save the page and make sure that each fragment ID local hyperlink when clicked scrolls you to the right spot (for the developer, and for the tool). Make any fix-up edits as necessary. That's it!

=== Implementation Details ===
If there are implementation details worth noting, add them them as nested list items under the item for the implementation itself. If the details subsection grows too big for a specific implementation, feel free to move the details to their own page and leave a link in place on the implementations page.

== Reporting Bugs ==
Similar to implementation details, in short, [[put-it-on-the-wiki]]. In particular, add bug reports, with URL(s) to a valid demonstrative test case(s) of course, to the listing of an implementation on this page, OR on the specific implementations wiki page (e.g. [[hcard-implementations]]). Please describe why you think it is a bug (user interface, cosmetic, violates a spec page, e.g. for problems parsing hCards, reference which part of [[hcard-parsing]] the implementation appears to not be following).

If you have a sense of urgency for getting that particular bug fixed in that implementation, you may email [http://microformats.org/discuss/ microformats-dev] with the URL of that implementation on the wiki page, and *summarize* the bug (the full description being on the wiki page instead).

== Formats ==
Most microformat specifications have an "implementations" section, e.g.:
*[[rel-tag#Implementations|rel-tag implementations]]
*[[vote-links#Implementations|vote-link implementations]]
*[[xoxo#Implementations|XOXO implementations]]

In addition, some microformat specifications have separate implementation pages:
*[[hcalendar-implementations|hCalendar implementations]]
*[[hcard-implementations|hCard Implementations]]
*[[xfn-implementations|XFN implementations]]

== Applications / Plugins / Services / Tools ==
This is an alphabetical listing of all applications, plugins (grouped with their app/tool), services and tools that implement microformats, along with the list of microformats that are supported, and the company and/or developers responsible for it.

As a user, the implementations listed below will automatically help you use microformats and help your data portability and interoperability with other apps and services.

Please help complete this list! If you know of additional apps/plugins/services/tools that support microformats, please add them!

Note: this section is only for listing specific ''implementations''. The list of ''implementors'' is in the [[implementors#Companies / Developers / Organizations|Companies / Developers / Organizations]] section on the [[implementors]] page.

Alphabetically:

=== .Mac Webmail ===
* The [http://www.mac.com/webmail .Mac Webmail] ''service'' now [http://factoryjoe.com/blog/2006/10/28/apple-embraces-microformats-in-new-mac-webmail/ supports hcard].
** by [[implementors#Apple_Computer|Apple Computer]]

=== AlchemyPoint ===
* [http://www.orch8.net/ AlchemyPoint] is a structured web / mashup platform that supports parsing hCard, rel-tag and other microformats.
** by [[implementors#Orchestr8|Orchestr8]]

=== Backnetwork ===
* [http://backnetwork.com/ Backnetwork] is a community networking tool for events that supports [[hCard]], [[hCalendar]], and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== Blinksale ===
* [http://blinksale.com Blinksale] uses [[hcard|hCard]] standard throughout for people and companies.

=== BlogMatrix ===
* [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].
** by [[implementors#David_Janes|David Janes]]

=== Blogmarks.net ===
* [http://www.blogmarks.net Blogmarks.net] publish user bookmarks in [[xfolk]]/[[rel-tag]].

=== Bugzilla ===

* [http://www.bugzilla.org/ Bugzilla] [http://www.bugzilla.org/status/2007-08-23.html 3.1.1] includes some microformats on show_bug.cgi and a few other places.

=== cmSiteNavigation ===
* [http://www.christophm.de/software/firefox/cmSiteNavigation/ cmSiteNavigation] extension for Firefox make use of links marked with a [[existing-rel-values|"rel" value]], and parses additional link types also.
** This seems to use rel values defined in the HTML 4 spec, not microformats. This is more of a [[posh|POSH]] implementation than a [[microformats]] implementation.

=== Community Server ===
* [http://communityserver.org Community Server] supports tagging posts with [[rel-tag]], implements [[rel-nofollow]] on links in comments, and allows users to create link lists using [http://gmpg.org/xfn/ XFN].

=== Conferenceer ===
* Built for SXSW 2007, [http://sxsw07.conferenceer.com/ Conferenceer] supports hcalendar and hcard.

=== Citycita===
* [http://www.citycita.org Citycita] supports [[hCal|hCal]] in all event pages for local social groups.
** by [[implementors#Rubio_Jamin|Rubio Jamin]]

=== Cork'd ===
* [http://corkd.com Cork'd] supports [[hcard|hCard]] for user profiles, [[hreview|hReview]] for wine reviews, along with [[rel-tag]] for tagging wines as announced in [http://www.simplebits.com/notebook/2006/06/10/wineformats.html Pairing Wine and Microformats]
** by [[implementors#Dan_Cederhold|Dan Cederholm]]

=== Delicious Generation ===
* [http://deliciousgeneration.com/ Delicious Generation] supports [[hCal|hCal]] for the event and [[hcard|hCard]] for sponsors and people.
** by [[implementors#Chris_Messina|Chris Messina]]

=== Digg ===
* [http://digg.com/ Digg] supports [[hcard|hCards]] for profiles and rel-me for identity consolidation (though they currently mix rel-nofollow with rel-me, negating these links).

=== Dreamweaver ===
==== Microformats Extensions ====
* [http://www.webstandards.org/action/dwtf/microformats Dreamweaver Microformats Extensions] ([http://allinthehead.com/beta/microformats.mxp.zip download]) support authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] as [http://allinthehead.com/retro/282/microformats-in-dreamweaver announced by Drew]
** by [[implementors#Drew_Mclellan|Drew McLellan]]

=== Drupal ===
==== Upcoming module for Drupal ====
* [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]
** by [[implementors#Brian_Del_Vecchio|Brian Del Vecchio]]

=== Eventful ===
* [http://eventful.com Eventful] supports [[hcalendar|hCalendar]] for over 1,000,000 event listings and [[hcard|hCard]] for venues.

=== Facebook ===
* [http://facebook.com/ Facebook] supports [[hcard|hCard]] for some public profiles '''(example needed)'''.
* There is also an [http://www.facebook.com/apps/application.php?id=2400943827&ref=s hCard application] (a plug-in) for Facebook users.
* Note also the [http://www.facebook.com/group.php?gid=2374732285 microformats group], which Facebook users who support microformats can join.

=== Ficlets ===
* [http://ficlets.com Ficlets] supports [[hcard]] for author data and [[hatom]] for stories and lists of stories.
** [http://sixtwothree.org Jason Garber] and [http://lawver.net Kevin Lawver] for [http://aol.com AOL]

=== Firefox ===
* See [[firefox-extensions|Firefox Extensions]]

=== Flickr People ===
* [http://flickr.com/ Flickr]'s profiles on its people pages supports both [[hcard|hCard]] and [http://gmpg.org/xfn XFN].
** by [[implementors#Cal_Henderson|Cal Henderson]]
**[http://flickr.com/people/tantek example]

=== Flickr Photos ===
* [http://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat.

=== Flock Web Browser ===
* The [http://flock.com Flock web browser] supports the [[rel-tag]] microformat.
** by [[implementors#Flock|Flock]]

=== Google Chrome ===
* See [[chrome-extensions|Chrome Extensions]]

=== Google Search ===
* Consumes microformats via rich snippets: [[search engines | wiki page]], [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 rich snippets docs]
* supports [[rel-nofollow]]
** by [[implementors#Google|Google]]

=== Google Blogger ===
* [http://blogger.com/ Blogger] supports [[hatom|hAtom]] (citation to blog post needed - 2007)
** by [[implementors#Google|Google]]

=== Google Creative Commons Search ===
* [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]
** by [[implementors#Google|Google]]

=== Google Maps ===
* [http://maps.google.com/ Google Maps] supports [[hcard|hCard]] (see [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html 2007-06-31 announcement by Google])
* Google maps also allows reviewers and map creators to [http://maps.google.com/maps/me attach a public profile], which includes hCard and rel="me' XFN markup. See [http://google-latlong.blogspot.com/2007/10/put-yourself-on-map.html 2007-10-17 announcement]. Sample profile: [http://maps.google.com/maps/user?uid=109581870574956225297 Kevin Marks].
** by [[implementors#Google|Google]]
**Unfortunately, [http://microformats.org/discuss/mail/microformats-discuss/2007-July/010311.html Google Map's implementation is broken]. [http://microformats.org/discuss/mail/microformats-discuss/2007-August/010457.html Google are aware; a fix is awaited].
** Also, there is no hCard nor any XFN rel values on the [http://maps.google.com/maps/user?uid=109581870574956225297 sample profile] itself, it appears to include a [http://maps.google.com/maps/c/widgets/ProfileViewer?js=RAW&maximize=true&hide=false&width=40&noTitle=true&theme=theme_2&service=local&uid=109581870574956225297&height=0&background=transparent&serverbased=true&border=NONE&eventCallback=ParentStub1192999211538&zx=dc574o15j0wrv frame] which then has an hCard and rel="me" to the user's blog.

=== Gravatar Commenters as hCards ===
* [http://thedredge.org Andy Hume] added code to his blogging software to automatically mark-up the names and URLs of commenters on his blog with [[hcard|hCard]].
** by [[implementors#Andy_Hume|Andy Hume]]
** Andy - any chance of open sourcing your code to turn Gravatars into hCards?

=== Greasemonkey ===
* [http://greasemonkey.makedatamakesense.com/google_hcalendar/ Google hCalendar] - Adds hCalendar data to Google Calendar.
* [http://www.nickpeters.net/?p=35 Social xFolk] - Adds xFolk links to social bookmarking sites del.icio.us and ma.gnolia.
* [http://monkeyformats.org/ Monkeyformats] - a collection of GreaseMonkey scripts that add actual hCard and hCalendar microformat markup to several international phone directories.

=== hCalendar creator ===
* [http://microformats.org/code/hcalendar/creator hCalendar creator] (originally [http://theryanking.com/microformats/hcalendar-creator.html published by Ryan King]) is a javascript form for creating [[hcalendar|hCalendar]] events.
** by [[implementors#Ryan_King|Ryan King]]

=== hCard to Gmail Service ===
* [http://jkg3.com/Journal/81/bookmarklet hCard to gmail] is a bookmarklet / service which will convert hCard formatted data to the .CSV file for importing to gmail.
** by [[implementors#Jamie_Knight|Jamie Knight]]

=== hCard creator ===
* The open source [http://microformats.org/code/hcard/creator hCard creator] (originally [http://tantek.com/microformats/hcard-creator.html published by Tantek]) is a very simple, yet illustrative, open source user interface / form / script which creates an [[hcard|hCard]] in real-time as you type in a set of contact information.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Helios Calendar ===
* [http://www.helioscalendar.com/ Helios Calendar] is a commercial PHP script for event publishing that [http://www.helioscalendar.com/index.php?com=features&d=1 supports hCalendar and hCard].
** by [[implementors#Refresh Web Development|Refresh Web Development]]

=== hKit Microformats Toolkit for PHP5 ===
* [http://hkit.googlecode.com/ hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

=== hReview creator ===
* [http://microformats.org/code/hcalendar/creator hReview creator] (originally [http://theryanking.com/microformats/hreview-creator.html published by Ryan King]) is a javascript form for creating [[hreview|hReviews]].
** by [[implementors#Ryan_King|Ryan King]]

=== iChat buddy list to hCards ===
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Internet Explorer ===
* See [[internet-explorer-extensions]]

=== JobiJoba ===
* [http://www.jobijoba.com JobiJoba : moteur de recherche emploi] parses and supports [[hCard|hCard]] and [[rel-tag|rel-tag]] for over 40,000 job listings.

=== JSCalendar ===
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses [[hcalendar|hCalendar]] and produces a displayable HTML table/CSS-based calendar.

=== Konqueror ===
* [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]

=== Last.fm ===
* [http://last.fm Last.fm] - [http://factoryjoe.com/blog/2006/10/31/lastfm-adds-support-for-hcalendar/ Last.fm supports] [[hcalendar|hCalendar]]

=== LinkedIn ===
* [http://www.linkedin.com LinkedIn] - LinkedIn includes [[hcard|hCard]] and [[xfn|XFN]] on contacts, [[hresume|hResume]] for public profiles and [[hreview|hReview]] on service provider recommendations

=== Live Clipboard ===
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/techPreview.html Live Clipboard Technical Introduction]
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/clipboardexample.html Live Clipboard Example]

=== LiveJournal ===
* [http://www.livejournal.com LiveJournal]
** supports tagging posts with [[rel-tag]]
** supports [[hcard-supporting-user-profiles|hCard user profiles]] and [[XFN]] ([http://community.livejournal.com/lj_releases/24768.html 2007-09-27 release #15]).
** by [[implementors#Six Apart|Six Apart]] (at the time of implementation)

=== LJFind ===
* [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].

=== LouderVoice ===
* [http://www.loudervoice.com Publishes and aggregates hreview content] - The LouderVoice site provides a variety of tools to publish hreview to blogs and it also aggregates hreview content from any registered RSS Feed so that users can search/rate/collect distributed reviews.

=== Ma.gnolia ===
* [http://ma.gnolia.com Ma.gnolia] has wide [http://wiki.ma.gnolia.com/Ma.gnolia_Feeds_Guide#Microformats support for a variety of microformats] including [[rel-tag]], [[xfolk]], [[hreview]], [[xfn]] and [[hcard]].

=== Mash Maker ===
* [http://mashmaker.intel.com/ Intel Mash Maker] supports microformats as of 2007-11-15 (see [http://softwareblogs.intel.com/2007/11/15/bookmarks-microformats-and-bug-fixes/ announcing blog post])
** by [[implementors#Intel|Intel]]

=== Maxthon ===
[http://maxthon.com Maxthon] is a browser for Microsoft Windows that uses the Trident rendering engine and provides additional user interface. Maxthon has built and published a plugin for their browser that recognizes microformats in web pages and allows users to take action with them, similar to Operator for [[Firefox]].
* [http://forum.maxthon.com/index.php?showtopic=65408 Microformats Button Version 1.0.0 Release Candidate 1]
** Description: "Microformats Button extracts Microformats from websites and allows you to export the data to vCard, vCalendar, Google Maps, Yahoo Maps and other sites."

=== Microformat Base ===
* [http://randomchaos.com/microformats/base/ Microformat Base]
** by [[implementors#Scott Reynen|Scott Reynen]]

=== Microformat Bookmarklet Overlay ===
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] for Safari, Firefox and Camino, supports [[hcard|hCard]] and [[hcalendar|hCalendar]] and allows the user to import individual microformats on the fly.
** by [[implementors#Remy_Sharp|Remy Sharp]]

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== Movable Type ===
* [http://movabletype.org Movable Type] (MT) open source blogging software supports:
** [[XFN]] [[rel-me]] "other profiles" UI, and [[hAtom]] activity streams (as of MT v4.1 - see [http://www.sixapart.com/about/news/2008/01/time_for_action.html announcement] and [http://www.movabletype.org/2008/01/building_action_streams.html technical details].)
** by [[implementors#Six Apart|Six Apart]]
See also [[movable-type]].

=== MyMap.yam.com ===
* support [[geo]] microformat in the POI page. example: [http://mymap.yam.com/place/point/charleschuang/6695/ a book store in Tamsui].

=== National eXtension Initiative ===
* [http://www.extension.org/ eXtension Home] - content marked-up with [[hatom|hAtom]] and events marked-up as [[hcalendar|hCalendar]] entries.
** by [[implementors#James E. Robinson, III|James E. Robinson, III]]

=== Nature Network Boston ===
* [http://network.nature.com/boston/ Nature Network Boston], a social networking community for scientists, supports [[reltag|rel-tag]], [[hcard|hCard]] for user profiles and [[hcalendar|hCalendar]] for marking up events across the site.
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== Nature Protocols ===
* [http://www.nature.com/nprot/ Nature Protocols], a forum for scientists to upload and comment on protocols, supports [[hcard|hCard]] and [[XOXO]].
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== NetNewsWire ===
*[http://www.newsgator.com/Individuals/NetNewsWire/ NetNewsWire] is an easy-to-use RSS and Atom reader for your Mac. NetNewsWire 3.0 detects, extracts and converts hcard and hcalendar data from feed entries.
** by [[implementors#NewsGator|NewsGator]]

=== Netscape Navigator ===
* Version 9.0+ supports [[Firefox extensions]], e.g. [[Operator]]:
** [http://notizblog.org/2007/10/21/operator-unter-navigator-90/ Operator unter Navigator 9.0]

=== Nutch ===
* [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]
* [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]

=== ODEO ===
* [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].

=== Open-Xchange ===
* The [http://www.open-xchange.com Open-Xchange] collaboration appliance supports publishing and subscribing of contacts in hCard format (in addition to exporting vcard) officially since v6.16. The format is extended by additional fields (like "date of marriage") in the OXMF microformat.

=== Optimus ===
*[http://microformatique.com/optimus/ Optimus]. Output formats: XML, JSON, JSON-P.

=== phpMicroformats ===
* [http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformat entries for [[hcalendar|hCalendar]] and [[hcard|hCard]]. It is released under GPL.

=== Portable Social Network Profile Parser ===
* [http://lab.backnetwork.com/ufXtract-psn/ Portable Social Network Profile Parser] implements parsing of [[hCard]], [[XFN]], and in particular [[rel-me]] for [[identity-consolidation]] for [[social-network-portability]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== PostNuke ===
''[http://www.postnuke.com PostNuke] is an Application Framework/Content Management Systeme''
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=96 hCards4Pagesetter] - hCards Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=97 hCalendar4Pagesetter] - hCalendar Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=98 hReview4Pagesetter] - hReview Publication Type for the PostNuke module "Pagesetter"
* [http://noc.postnuke.com/frs/?group_id=256&release_id=477 Blogroll] - XFN Block/Modul
* [http://noc.postnuke.com/frs/?group_id=256&release_id=628 nofollow] - nofollow Hook

=== Pownce ===
*[http://pownce/ Optimus]. Output formats: XML, JSON, JSON-P.

=== Profiler ===
* [http://microformat.makedatamakesense.com/profiler/ Profiler] works as a proxy service adding microformat profiles to documents that appear to contain microformats.

=== Realcom HAKONE for Notes ===
* [http://www.realcom.co.jp/en/hakone2.html HAKONE for Notes] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== Realcom KnowledgeMarket ===
* [http://www.realcom.co.jp/en/enterprisesuite2.html KnowledgeMarket] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== RFC2629.xslt ===
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate [[hcard|hCard]] information ([http://ietf.org/rfc/rfc2629 RFC2629] in an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])

=== Salesforce ===
* [http://salesforce.com Salesforce] [http://flickr.com/photos/kingsleyj/175689109/ supports] [[hcard|hCard]]
** by [http://flickr.com/people/kingsleyj/ Kingsley Joseph]
==== Spanning Salesforce ====
* [http://spanningsalesforce.com/ Spanning Salesforce] supports [[hcalendar|hCalendar]].

=== Sivitools ===
<blockquote>
Sivitols is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. This library is being written and maintained for a tag sharing project undertaken by Video Vertigo.
</blockquote>
[http://blog.blip.tv/blog/microformats/ Annoucement], [http://pokkari.com/microformat/javadoc/ Docs]

=== Safari Microformats plugin ===
<blockquote>
The Safari Microformats plugin notifies you when the author of the website has published Microformats and allows you to easily import hCards and hCalendars in Address Book and iCal. This plugin was inspired by the idea and mockup of Jon Hicks.
</blockquote>
[http://www.zappatic.net/safarimicroformats/ Safari Microformats Plugin]
* Note - the latest version, 3.1, currently only works w/Mac OS 10.5 (Leopard)

=== SPRACI ===
* [http://www.spraci.com SPRACI] - nightlife/events - [[hcalendar|hCalendar]] published in events listings, aggregator can read hCalendar

=== stuckUnstuck ===
* [http://stuckunstuck.com stuckUnstuck] supports [[hcard|hCard]] and [[hatom|hatom]].

<div id="cognition">
=== Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a Perl framework and script (usable online via CGI, and downloadable for local use) that supports:
** [[hatom|hAtom]]
** [[haudio|hAudio]]
** [[User:TobyInk/hcalendar-1.1|hCalendar]]
** [[hcard|hCard]], [[adr]], [[geo]], [[jCard]], [[xfn|XFN]] (1.0 and 1.1) and [http://xen.adactio.com XEN]
** [[hresume|hResume]]
** [[hreview|hReview]]
** [[rel-tag]], [[rel-enclosure]] and [[rel-license]]
** [[figure]]
** [[measure]]
** [[species]]
** [[xfolk|xFolk]]
** [[xoxo|XOXO]]
** several non-microformat semantic HTML techniques, including GRDDL, RDFa, eRDF and COinS.
** by [[implementors#Toby_Inkster|Toby Inkster]]
** no longer actively developed, see [[parsers#HTML::Microformats|HTML::Microformats]] for its replacement.
</div>

=== Technorati Contacts Feed Service ===
* [http://feeds.technorati.com/contacts/ Technorati Contacts Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcard|hCards]] to vCard (.vcf) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Events Feed Service ===
* [http://feeds.technorati.com/events/ Technorati Events Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcalendar|hCalendar]] events to iCalendar (.ics) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Microformats Search ===
* Technorati [http://kitchen.technorati.com/search/ Microformats Search]. Search for contacts ([[hcard|hCard]]), events ([[hcalendar|hCalendar]]), or reviews ([[hreview|hReview]]) published on blogs and other web sites.
** by [[implementors#Ryan_King|Ryan King]]
** first version (2006 May) by [[implementors#Tantek_Çelik|Tantek Çelik]], [[implementors#Ryan_King|Ryan King]], [[implementors#Kevin_Marks|Kevin Marks]], [[implementors#Josh_Smith|Josh Smith]]

=== Technorati Search ===
* [http://technorati.com/ Technorati] [http://technorati.com/search Search] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.
** by [http://technorati.com/about/staff.html Technorati Staff]

=== Technorati Tags ===
* [http://technorati.com/tags/ Technorati Tags] pages aggregate blog posts tagged with the [[rel-tag]] open tagging standard, in addition to recent tagged photos and links.

=== Textpattern ===
==== Microformats Plugin ====
* [http://placenamehere.com/TXP/pnh_mf/ Textpattern Microformats Plugin] supports authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] in the [http://www.textpattern.com/ Textpattern] CMS/blogging tool
** by [http://placenamehere.com/ Chris Casciano]

=== Tomota ===
* The [http://www.tomota.de Tomota] allows import, export and conversion from and to hcards.
** by [[implementors#RalfEngels|Ralf Engels]]

=== Transformr ===
* [http://github.com/WebOrganics/TransFormr Transformr] Is a microformats transformation toolkit. Transformr is also available as a [http://microform.at/ webservice]
** by [[implementors#Martin_McEvoy|Martin McEvoy]]

=== TYPO3 ===
* [http://www.typo3.com TYPO3]
==== Getting Started ====
* [http://typo3.org TYPO3 Developer Ressource]
* [http://www.acqal.com/a/article/getting-help-with-typo3-98.html Getting Help With TYPO3]
==== tt_address extension====
* [http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address] - hCard support with the tt_address extension version 2.0.0
** by [[implementors#Ingo_Renner|Ingo Renner]]
==== TIMTAB extension====
* [http://typo3.org/extensions/repository/view/timtab/0.5.11/ TIMTAB] - XFN support for blogrolls with the TIMTAB weblog extension for TYPO3
** by [[implementors#Ingo_Renner|Ingo Renner]]

=== Tweeterboard ===
* Tweeterboard supports [hcard|hCard]], and [http://gmpg.org/xfn XFN] on profile pages ([http://tweeterboard.com/user/missrogue example]).

=== Twitter ===

* [http://twitter.com Twitter] [http://twitter.com/al3x/statuses/53982402 supports] [[hatom|hAtom]], [[hcard|hCard]], and [http://gmpg.org/xfn XFN].
** hCards for groups are marked up with "fn" not "fn org". See, for example, [http://twitter.com/microformats microformats on Twitter]
** Improper address mark-up (no child properties; though this may be all that can be achieved, if the user enters a value like "Birmingham, England")
** Uses <code>class="label"</code> for non-hCard purpose.

=== ufXtract ===
* [http://lab.backnetwork.com/ufXtract/ ufXtract] implements [[parsing]] of microformats such as [[hCard]] and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]]. See [http://www.glennjones.net/Post/831/ufXtractmicroformatsparser.htm blog post announcement].

=== Upcoming.org ===
* [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.
** by [[implementors#Andy_Baio|Andy Baio]], [[implementors#Leonard_Lin|Leonard Lin]], [[implementors#Gordon_Luk|Gordon Luk]]

=== vCardExplorer ===
* [http://vcardexplorer.corefault.de/ vCardExplorer for MacOSX] - browses local vcards and converts hcards from URLs.

=== VIREL Microformats Search Engine===
* [http://www.virel.de/ microformats search engine] - website friendly crawler. searches for public informations embedded as microformats in web pages.

=== WindowsLiveWriter ===
* [[implementors#Microsoft|Microsoft's]] WindowsLiveWriter (WLW) [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 event plugin] supports [[hcalendar|hCalendar]].

=== WordPress ===
*See [[wordpress|WordPress]].

=== X2V ===
* Brian Suda has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.
** by [[implementors#Brian_Suda|Brian Suda]]

=== XWiki ===
* [http://xwiki.org XWiki] (as of [http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWiki10Beta5 version 10Beta5]) publishes the user profiles using [[hcard | hCard]], the events in the calendar application using [[hCalendar | hCalendar]], the blog entries using [[hAtom | hAtom]] and homepage links using [[rel-home | rel-home]].

=== xfn-spider ===

* [http://sphinx.net.ru/hg/xfn-spider xfn-spider] — simple crawler extracting microformats with XSLT ([http://sphinx.net.ru/blog/entry/simple-microformat-xslt-extraction/ Original article in Russian] circa summer 2007) and exporting information to OPML feedlist, tag cloud etc.

* See [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- XFN visualization] example at IBM's Many Eyes made using data extracted with xfn-spider

=== Yahoo Creative Commons Search ===
* [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.

=== Yahoo Local ===
* [http://local.yahoo.com Yahoo local] supports [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]].

=== Yahoo Tech ===
* [http://tech.yahoo.com Yahoo! Tech] supports [[hreview|hReview]].

=== Yahoo UK Movies ===
* [http://movies.yahoo.co.uk Yahoo! UK Movies] supports [[hreview|hReview]].
** by Mark Norman Francis

=== Yalwa - Local directory ===
* [http://www.yalwa.com/ Yalwa - Local Directory] supports [[hreview|hReview]].
Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Listing]

=== Yedda ===
* [http://yedda.com Yedda] supports [[hcard|hCard]] for exposing users information, [[hatom|hAtom]] for exposing data that is already exposed via feeds (like list of questions and answers) and [[rel-tag|rel-tag]] for every tag used to tag questions and users.

== Validators ==

See [[debugging-tools]].

==Search engines==
See [[search-engines]]

== Companies / Developers / Organizations ==
See [[implementors]]

The following have been moved from the sections above due to problems, stated below:

== Other ==
Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]

User:WebOrganics

2010-04-17T01:46:14Z

WebOrganics: removing some links

<div class="vcard" id="weborganics">
<h1><span class="fn">
<span class="given-name">Martin</span>
<span class="family-name"> McEvoy</span>
</span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url uid"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
<span class="note">
WebOrganics is a small Web Design and Development Company based in Lancashire England.
</span>
</div>

http://weborganics.co.uk/images/hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

hatom

2010-04-17T01:43:05Z

WebOrganics: /* Implementations */ updating link

<entry-title>hAtom 0.1</entry-title>
{{Template:DraftSpecification}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

<div class="vcard">
;<span class="role">Editor/Author</span>
:<span class="fn">[http://blogmatrix.blogmatrix.com/ David Janes]</span> <span class="org">([http://www.blogmatrix.com BlogMatrix, Inc.])</span>
</div>

;Contributors
:<span class="vcard"><span class="fn">[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]</span></span>
:<span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span> and before at [http://technorati.com Technorati, Inc.])</span>

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

== Introduction ==
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== Copyright ==
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional <span id="languages">languages</span>:
* [[hatom-fr|français]]

haudio

2010-03-16T02:13:24Z

WebOrganics: /* Implementations */ updating link

<entry-title>hAudio 0.9.1</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png

[[haudio|hAudio]] is a simple, open, distributed format, suitable for embedding information about audio recordings in (X)HTML, Atom, RSS, and arbitrary XML. hAudio is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hAudio Microformat Draft Specification ==

=== Editors ===
* [[User:ManuSporny | Manu Sporny]] ([http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.)
* [[ user:WebOrganics | Martin McEvoy ]]
=== Authors ===
* [[User:ManuSporny | Manu Sporny]]
* [[ user:WebOrganics | Martin McEvoy ]]

=== Contributors===
[[User:ManuSporny | Manu Sporny]], [[ user:WebOrganics | Martin McEvoy ]], [[ User:AlexandreVandeSande | Alexandre Van De Sande ]], Michael Johnson, Dave Longley, Brian Suda, Ben Wiley Sittler, Scott Reynen, Frances Berriman, James Craig, David Janes, [[User:AndyMabbett|Andy Mabbett]], Danny Ayers, Rudy Desjardins, Edward O'Connor, Ryan King, Chris Griego, Brad Hafichuk, Tantek Çelik, Colin Barrett, Joe Andrieu, Michael Smethurst, [[User:ChrisNewell | Chris Newell]], Julian Stahnke, Justin Maxwell, Paul Wilkins and David I. Lehn.

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

It is difficult for a browser to extract semantic information about an audio recording described on a web page. Metadata such as speaker, musician, publisher, label, title of the work, release date, acquisition link, related image artwork and tags provide relevant context for the audio recording.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a song performed by an artist, it can produce richer interactions. For example, specific searches may be performed for artists and songs via general search services such as Google and Wikipedia. Specific search services may also be queried such as MusicBrainz, The Internet Archive, FreeDB, or Bitmunk. Additionally, classification by crawlers can become more accurate. If there are 20 tracks found on a page done by the same artist, and that content consumes a significant portion of the page, it can be assumed that the page is not only about music, but also about a particular artist.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of audio content, the authors propose the hAudio microformat, an open standard for distributed audio metadata. The authors have researched both numerous [[audio-info-examples]] in the wild and earlier attempts at [[audio-info-formats]], and have designed hAudio around a simple minimal schema for audio content. Feedback is encouraged on the [[haudio-feedback|hAudio feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to media info and audio info in general. Among the many participants are [[RodBegbie]], Dean Hudson, [http://tantek.com/log/ Tantek Çelik], [http://napsterization.org/stories/ Mary Hodder], [http://joshkinberg.com/blog/ Joshua Kinberg], ChrisMessina, and [http://onlisareinsradar.com/ Lisa Rein].

=== Scope ===

Audio content consistently share several common fields. Where possible hAudio has been based on this minimal common subset.

=== Out of scope ===

Fields that are type-specific have been omitted from hAudio. It is important that hAudio be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a universal audio identifier, that is, how to identify the same audio album, song, speech, or podcast across different music and audio sites, though something very useful to have, is outside the scope of this format.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hAudio format is based on a set of fields common to numerous audio content sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] standards.

=== Schema ===

The hAudio schema consists of the following:

* hAudio ('''<code>haudio</code>''')
** '''fn''' or/and '''album''' required. text.
** '''contributor'''. optional. using text or [[hCard]].
** '''duration'''. optional. ISO-8601 time duration. (re-used from [[hcalendar]]).
** '''item''' optional. using text or multiple properties from [[hAudio]].
** '''position''' optional. text.
** '''category'''. optional. text.
** '''published'''. optional.
** '''photo'''. optional. using any element containing a URL, such as IMG.
** '''description''' optional. text.
** '''sample''' (rel). optional. sample file/stream using [[rel-design-pattern]] with <code>sample</code> as the <code>mf-rel-value</code>.
** '''enclosure''' (rel). optional. full download of file using [[rel-enclosure]].
** '''payment''' (rel). optional. link to purchase process using [[rel-payment]].
** '''price''' optional. Using the sub properties '''currency''' and '''amount'''.

=== Field details ===

The fields of the hAudio schema represent the following:

==== hAudio ====

An hAudio is used to identify and describe metadata associated with an audio recording.

* an hAudio element is identified by class name <code>haudio</code>

==== fn ====

The name of a single audio recording is a short textual description used to identify the work among interested parties. This can be the name of a speech, song name, or short description regarding a sound effect.

* The element is identified by the class name <code>fn</code>.
* hAudio {{must}} have <code>fn</code> or/and <code>album</code>.

==== Album ====

The title of a collection of audio recordings, such as those that are represented as a CD, album or LP. The text should be a short textual description used to identify the work among interested parties.

* The element is identified by the class name <code>album</code>.
* hAudio {{must}} have either <code>album</code> or <code>fn</code> or both.

==== Item ====

A container for another hAudio item, which MUST be considered a part of the parent audio recording. An example of an item that is part of an hAudio would be a track in an audio album, a aria in an Opera, or a section of a podcast.

* The element is identified by the class name <code>item</code>.
* hAudio {{may}} have one or more items.
* The element {{must}} be processed opaquely. No sub-elements should be read from any hAudio contained in a track element.
* The contents of the element {{must}} be marked up using properties in hAudio.

==== Position ====

The position is used to describe the position of the hAudio item in a list. Examples of hAudio lists can include album track listings, music top 10 lists, playlists, and podcast chapters.

* The element is identified by the class name <code>position</code>.
* hAudio {{may}} include one <code>position</code> element.
* The contents of the element {{must}} be a number or other sequential identifier.
* The sequential identifier {{may}} be specified out-of-sequence.

==== Contributor ====

A Contributor is any entity that takes part in the creation and distribution of an audio recording. Examples include: artist, composer, publisher, guitarist, vocalist, violinist, lead singer, backup singer, bassist, drummer, manager, and roadie.

* The element is identified by the class name <code>contributor</code>.
* hAudio {{may}} include one or more contributors.
* The contributor's name SHOULD also be marked up as a valid hCard Microformat. [[hcard]]
*# The <code>role</code> attribute {{should}} be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
* The contributor's name {{may}} be specified in plain-text without being enclosed in a hCard Microformat.

==== Published ====

The published date specifies the date that the audio recording was made available to the public. Examples include: The airing date of a radio broadcast, the day a speech was given, or the day a music album was made available for sale.

* The element is identified by the class name <code>published</code>.
* hAudio {{may}} include one or more <code>published</code> elements.
* The contents of the element {{may}} include a date format compliant with the [[datetime-design-pattern]].

==== Sample ====

A Sample URI specifies from where an excerpt of the audio recording may be retrieved.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>sample</code>.
* hAudio {{may}} include one or more URI <code>sample</code>s.
* The URI {{should}} point to a directly accessible stream or file.
* The type of the sample {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Full Download (Enclosure) ====

A Full Download URI specifies from where the full version of an audio recording may be retrieved. The URI {{must}} point to a direct link to a file retrieval process (FTP, HTTP, BitTorrent URI, etc).

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>enclosure</code>.
* hAudio {{may}} include one or more <code>enclosure</code> URIs.
* The type of the file {{should}} be specified by using the <code>type</code> specifier for a URI.

==== Purchase (Payment) ====

A Purchase URI specifies from where the full version of an audio recording may be purchased. The URI {{must}} point to the beginning of a purchase process for the hAudio.

* The element is identified by a URI fitting the [[rel-design-pattern]], the rel content being <code>payment</code>.
* hAudio {{may}} include one or more <code>payment</code> URIs.
* The type of the file {{may}} be specified by using the <code>type</code> specifier for a URI.

==== Photo ====

A photo specifies an image that should be used to summarize the audio recording. Examples include: the image of a speaker, an audio album cover image, or a picture from a concert.

* The element is identified by the class name <code>photo</code>.
* hAudio {{may}} include one or more <code>photo</code> elements.
* The element {{should}} use an <img> element.
* The element {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended.

==== Category ====

The Category specifies the genre or style used to classify the audio recording. Examples include: blues, rock, motivational, spoken word, or sound effect.

* The element is identified by the class name <code>category</code>.
* hAudio {{may}} include one or more <code>category</code> elements.
* This element {{may}} be expressed using the [[rel-tag]] elemental microformat. When a category is expressed using rel-tag, the content of the element is used as the text for the category. For example: <code><a class="category" rel="tag" href="/tags/symphony">Symphonic</a></code> would have "Symphonic" as the text for the category.

==== Duration ====

The Duration specifies the length in time of the audio recording. Examples include: 104 seconds, 3:23, and 4 minutes.

* The element is identified by the class name <code>duration</code>.
* hAudio {{may}} include one <code>duration</code> element.
* The contents of the element {{may}} use the [[abbr-design-pattern]] whose title attribute contains an ISO-8601 formatted duration. An example of 3:23 (i.e 3 minutes 23 seconds) would be "PT3M23S" in ISO 8601 format.
* The element {{may}} contain the following sub properties:
** '''h''' Hour.
** '''min''' Minute.
** '''s''' Second.
Example:
<pre><span class="duration">
<span class="h">1</span>:
<span class="min">3</span>:
<span class="s">23</span>
</span></pre>

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.

* The element is identified by the class name <code>price</code>.
* hAudio {{may}} include one or more <code>price</code> elements.
* The contents of the element {{may}} also use plain text with a currency symbol.
* The contents {{may}} contain the following sub properties:
** '''currency''' an [http://en.wikipedia.org/wiki/ISO_4217#Active_codes ISO 4217] currency name.
** '''amount''' a numerical value.
Example:
<pre><span class="price">
<abbr class="currency" title="GBP">£</abbr>
<span class="amount">4.99</span>
</span></pre>

==== Description ====

An explanation of the contents of the hAudio item. This could explain the significance of a speech, the full-text description of a sound effect, or the meaning of a song or album.

* The element is identified by the class name <code>description</code>.
* hAudio {{may}} include one or more <code>description</code> elements. If more than one description element is defined, the full description for the hAudio is the concatenation, in order, of all <code>description</code> elements.

=== Parser Processing Notes ===

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>
* If only 'album' is specified, then the hAudio is an album.
* If only 'fn' is specified, then the hAudio is a song, audio track, sound effect, speech, or other atomic/singular work.
* If both 'album' and 'fn' are specified, then the hAudio is a atomic/singular work that is part of an album.
** Example: <code><nowiki><span class="haudio">Side two of <span class="album">Meddle</span> opens with <span class="fn">One of These Days</span></span></nowiki></code>
* If 'fn' and one or more 'items's are specified, the hAudio is an audio recording containing multiple sections. Each item is assumed to be an hAudio that is part of the parent hAudio. None of the 'item' properties should implicitly be added to the containing hAudio. In other words, the parser shouldn't parse the contents of the 'item' into the higher-level hAudio object.

==== Language ====

* To explicitly convey the natural language that an hAudio is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="haudio"
**e.g. <code><nowiki><p>I like <span class="haudio" lang="de"><span class="fn">Das Lied von der Erde</span></span> best.</p></nowiki></code>
*If portions of an hAudio (e.g. the item name) are in a different language to the rest of the hAudio, use the 'lang' or 'xml:lang' attribute on those portions.
* hAudio parsers which need to handle the native language of hAudio {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hAudio parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hAudio if no other language is specified on the hAudio.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Notes ===

This section is informative.

* By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content {{may}} be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using the [[rel-license]] microformat.

== XMDP Profile ==

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>haudio</dt>
<dd>
Used to identify and describe metadata associated with an individual audio recording.
</dd>
<dt>fn</dt>
<dd>
A short textual description used to identify an audio recording among interested parties.
</dd>
<dt>album</dt>
<dd>
A short textual description used to identify an audio recording that is an album among
interested parties.
</dd>
<dt>contributor</dt>
<dd>
An entity that takes part in the creation and distribution of an audio recording.
</dd>
<dt>published</dt>
<dd>
The date that the audio recording was made available to the public.
</dd>
<dt>description</dt>
<dd>
A verbose description of the audio recording.
</dd>
<dt>photo</dt>
<dd>
An image that should be used to summarize the audio recording.
</dd>
<dt>item</dt>
<dd>
Contains a sub-part of the current audio recording, which is marked-up using any element available in hAudio.
</dd>
<dt>sample</dt>
<dd>
A URI specifying a method of sampling a section of the audio recording.
</dd>
<dt>enclosure</dt>
<dd>
A URI specifying a method of downloading the complete version of the audio recording.
</dd>
<dt>purchase</dt>
<dd>
A URI specifying a method of purchase resulting in the acquisition of a complete version of the audio recording.
</dd>
<dt>category</dt>
<dd>
The genre or style used to classify the audio recording.
</dd>
<dt>duration</dt>
<dd>
The length of the audio recording.
</dd>
<dt>price</dt>
<dd>
The amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.
</dd>
</dl>
</dd>
</dl>
</pre>

== Examples ==

This section is informative.

Here are a few examples of text about, and links to, audio content, from real web sites, showing how they could be easily enhanced to use hAudio.



=== Simple Song Example ===

Display:

(This is a live example, detectable in parsers)

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor">Gogol Bordello</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">Gogol Bordello</span>
</div>
</pre>

=== Speech Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">I Have a Dream</span>, a <span class="category">speech</span> by <span class="contributor"><span class="vcard"><span class="fn n"><span class="given-name">Martin</span> <span class="additional-name">Luther</span> <span class="family-name">King</span>, <span class="honorific-suffix">Jr.</span></span></span></span>
</div>

Microformatted XHTML:
<pre>
<div class="haudio">
<span class="fn">I Have a Dream</span>, a
<span class="category">speech</span> by
<span class="contributor">
<span class="vcard">
<span class="fn n">
<span class="given-name">Martin</span>
<span class="additional-name">Luther</span>
<span class="family-name">King</span>,
<span class="honorific-suffix">Jr.</span>
</span>
</span>
</span>
</div>
</pre>

Note the use of [[hcard|hCard]].

=== Song and Album Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
<span class="fn">Start Wearing Purple</span> by <span class="contributor"><span class="vcard"><span class="fn org">Gogol Bordello</span></span></span> found on <span class="album">Underdog World Strike</span>
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="fn">Start Wearing Purple</span> by
<span class="contributor">
<span class="vcard">
<span class="fn org">Gogol Bordello</span>
</span>
</span>
found on
<span class="album">Underdog World Strike</span>
</div>
</pre>

Note that for bands, hCard's ''[[hcard#Implied_.22organization-name.22_Optimization|Implied "organization-name" Optimization]]'' is used.

=== Complete Album Example ===

An example that uses every element of hAudio:

[Image] Live Phish, Volume 15 by Phish<br/>
Released: October 31, 2002<br/>
Acquire: Sample, Live Recording, Buy High Quality Track<br/>
Category: [http://www.example.org/tags/live live]<br/>
Duration: 145 minutes, 27 seconds<br/>
Price: $14.99<br/>
<br/>
Tracks:<br/>
1. Sanity (5:48)<br/>
2. Highway To Hell (3:39)

Here is the hAudio Microformat markup:

<pre>
<div class="haudio">
<img class="photo" src="images/live_phish_vol_15.jpg" alt="" />
<span class="album">Live Phish, Volume 15</span>
<span class="contributor">
<span class="vcard">
<span class="fn org">Phish</span>
</span>
</span>
<br/>
Released on:
<abbr class="published" title="2002-10-31">October 31, 2002</abbr>
<br/>
Acquire:
<a rel="sample" href="/samples/live_phish_vol_15_sample.mp3">Sample</a>,
<a rel="enclosure" href="/live/phish_live_phish_vol_15.mp3">Live Recording</a>,
<a rel="payment" href="/buy/phish_live_phish_vol_15">Buy High Quality Track</a>
Category: <a class="category" rel="tag" href="http://www.example.org/tags/live">live</a>
Duration: <abbr class="duration" title="PT145M27S">145 minutes, 27 seconds</abbr>
Price: <div class="price"><abbr class="currency" title="USD">$</abbr><span class="amount">14.99</span></div>
Tracks:
<div class="item">
<span class="position">1</span>.
<span class="fn">Sanity</span>
(<abbr class="duration" title="PT5M48S">5:48</abbr>)
</div>
<div class="item">
<span class="position">2</span>.
<span class="fn">Highway To Hell</span>
(<abbr class="duration" title="PT3M39S">3:39</abbr>)
</div>
</div>
</pre>

=== Multi-part Podcast Example ===

DigitalPlanet Podcast: 29 Oct 07

Forensic computing: is it really possible to delete data from your machine? Grand plans for getting broadband into Africa, checking out the sky at night via the internet and answering your emails to the programme.

Download MP3

<pre>
<div class="haudio">
<p>
<span class="fn">DigitalPlanet Podcast</span>
:
<abbr class="published" title="20071029">29 Oct 07</abbr>
</p>
<p>
<div class="item">
<span class="fn">Forensic computing: is it really possible to delete data from your machine?</span>
</div>
<div class="item">
<span class="fn">Grand plans for getting broadband into Africa</span>
</div>
,
<div class="item">
<span class="fn">checking out the sky at night via the internet</span>
</div>
and
<div class="item">
<span class="fn">answering your emails</span>
</div>
to the programme.
</p>
<p>
<a rel="enclosure" href="/download/episode/DigitalPlanet-2007-10-29">Download MP3</a>
</p>
</div>
</pre>

=== Opera Example ===

(This is a live example, detectable in parsers)

<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span> is an <span class="category">opera</span> in four acts by <span class="contributor" lang="it">Giacomo Puccini</span> to an <span class="category">Italian liberetto</span> by <span class="contributor" lang="it">Luigi Illica</span> and <span class="contributor" lang="it">Giuseppe Giacosais</span>. I saw it performed last week and found <span class="item"> <span class="fn">Act III</span> to be pretty interesting, especially the <span class="item"> "<span class="fn" lang="it">Sa dirmi, scusi</span>"</span> and <span class="item">"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"</span> arias.</span>
</div>

<pre>
<div class="haudio" lang="en">
<span class="fn" lang="fr">La Bohème</span>
is an
<span class="category">opera</span>
in four acts by
<span class="contributor" lang="it">Giacomo Puccini</span>
to an
<span class="category">Italian liberetto</span>
by
<span class="contributor" lang="it">Luigi Illica</span>
and
<span class="contributor" lang="it">Giuseppe Giacosais</span>.
I saw it performed last week and found
<span class="item">
<span class="fn">Act III</span>
to be pretty interesting, especially the
<span class="item">
"<span class="fn" lang="it">Sa dirmi, scusi</span>"
</span>
and
<span class="item">
"<span class="fn" lang="it">O buon Marcello, aiuto!</span>"
</span>
arias.
</span>
</div>
</pre>

== Examples in the wild ==

This section is '''informative'''.

* [http://weborganics.co.uk/haudio-rss/ hAudio-RSS] uses hAudio 0.9.1 and XSLT to generate an RSS2 Playlist.
* Tara Hunt of [http://openmediaweb.org/index.php/2008/01/13/publishing-my-workout-music-in-haudio/ Open Media Web] Published her workout Music in hAudio
* Grabb.it The web music player now uses hAudio 0.9 in its [http://grabb.it/users/greg user pages]
* [http://soundcloud.com/ SoundCloud] has hAudio in its pages.
* [http://populizer.com/ Populizer] also has hAudio in its pages.
* The [http://www.numblog.de/ New Urban Music Blog] has hAudio marked up in its pages.
* [http://alpha.libre.fm/ Libre.fm] has marked up on all its user pages in hAudio see : [http://alpha.libre.fm/user/weborganics example]

== Implementations ==

This section is '''informative'''.

*[http://weborganics.co.uk/files/js/haudio.zip hAudio 0.9 script] for [[operator|Operator]], updated version of the original hAudio script by David Lehn.
* Matthias Pfefferle has made some [http://notizblog.org/projects/haudio-icons/ hAudio Icons]
* [http://transformr.co.uk/ TransFormr] extracts hAudio 0.9.1 as a RSS2 Podcast.
* [http://buzzword.org.uk/cognition/ Cognition] 0.1-α11 and above will parse hAudio 0.9 and export as RDF/XML or RDF/JSON. As of 0.1-α12, it will also export in M3U playlist format and Turtle.
* [http://weborganics.co.uk/mo-haudio/ hAudio Microformat to RDF Music Ontology], a [http://www.w3.org/TR/grddl/ GRDDL] profile for hAudio 0.9.1, producing [http://musicontology.com/ Music Ontology] RDF.
* The [http://singpolyma.net/plugins/actionstream/ wp-diso-actionstream] plugin produces hAudio for last.fm scrobbles
*...


== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[currency-proposal]]
* [[datetime-design-pattern]]
* [[rel-design-pattern]]
* [[ISO-31-1|ISO-31-1/ISQ]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other audio metadata efforts. See [[audio-info-formats]].

==== Similar Work ====
* [[media-info]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

This document and <span class="vevent"><span class="summary">hAudio specification was placed into the public domain</span> on <span class="dtstart">2008-11-14</span></span> by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* Manu Sporny - Signature /Manu Sporny/
* Alexandre Van de Sande
* [[User:WebOrganics|Martin McEvoy]]
* [[User:DavidLehn|David Lehn]] - Signature /David Lehn/
* [[User:AndyMabbett|Andy Mabbett]]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

[[Category:Draft Specifications]]

parsers

2010-03-09T02:14:36Z

WebOrganics: /* Transformr */ updating link to current source

<entry-title>Microformats Parsers</entry-title>
;shortlinks
:http://ufs.cc/w/parsers (preferred)
:http://tr.im/ufprs
This page lists libraries that consume, transform or convert microformats. This is only a partial list. If you know of other such tools for microformats, please add them and list what specific microformats they support.

Alphabetical listing by programming language:

== Java ==
* [http://code.google.com/p/any23/ Any23 (Anything to Triples)] parses microformats into RDF triples
* [http://zwitserloot.com/org.microformats.hCard/ org.microformats.hCard] by Reinier Zwitserloot

== Javascript ==
=== Sumo ===
* [http://www.danwebb.net/2007/2/9/sumo-a-generic-microformats-parser-for-javascript Sumo! A Generic Microformats Parser For JavaScript]

== Perl ==
=== Data::Microformat ===
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo.
** By Brendan O'Connor / Six Apart

=== HTML::Microformats ===
Perhaps we can capture and update this info on a page like [[perl-html-microformats-parser]].
* [http://search.cpan.org/~tobyink/HTML-Microformats/ HTML::Microformats] is a CPAN module that has support for:
** rel: [[XFN]], [[rel-license]], [[rel-enclosure]], [[rel-tag]]
** class: [[hCard]], [[adr]], [[geo]], [[hAtom]], [[hNews]], and others.
** By Toby Inkster

Versions and releases notes:
* 2010-02-28 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000641.html 0.00_02]

===Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a parser for both “upper case Semantic Web” (RDF, RDFa) and “lower case semantic web” (microformats) technologies. It includes modules for exporting parsed data in a variety of formats, including RDF, vCard, iCalendar, Atom and KML.
** By Toby Inkster

=== Text::Microformat ===
* Text::Microformat is a microformats parser hosted on [http://code.google.com/p/ufperl/ Google Code] that supports:
** [[hCard]], [[hCalendar]], [[rel-tag]]

== PHP ==
=== XMFP ===
<span id="xmfp">[http://code.google.com/p/xmfp/ XMFP]</span> (eXtensible MicroFormats Parser for PHP 5) by [http://www.metonymie.com Emiliano Martínez Luque] is a set of PHP 5 classes providing a simple API for extracting Microformated Content either from a URI or a String representing HTML/XML. It can return the results as a PHP associative array, a JSON definition or an XML representation of the data. It supports most of the currently accepted microformats and can be easily extended to add new ones, it also has full support of the include pattern and provides basic validation of microformated data.

=== hKit Microformats Toolkit for PHP5 ===
[http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

===PHP Microformats parser===
[http://www.phpclasses.org/browse/package/3597.html Microformats parser] is a PHP package for extracting the microformats data embedded into HTML. The gathered data is stored as an xArray of objects - one for each microformat type container found. [http://malatestapunk-stuff.blogspot.com/2007/01/php-microformats-parser.html Announcement]. The parser supports most of the hCard (missing SOUND), hCalendar, hReview (missing item info; spec really needs some clarification) and rel elements, according to their respective specification on microformats Wiki.

===Transformr===
A Simple set of XSLT and PHP tools for Transforming Microformats [http://github.com/WebOrganics/TransFormr available from github].

=== hCard Validator ===
[http://code.google.com/p/hcardvalidator/ Source code] of the [http://hcard.geekhood.net/ hCard Validator] contains XSLT and PHP code for hCard and include microformats.

== Python ==
===AUMP===
* [http://aump.googlecode.com AUMP] is a parser written by David Janes. It supports hCard, hCalendar, hAtom, hReview and hListing.
** Uses Python's [http://docs.python.org/library/xml.dom.minidom.html xml.dom.minidom] after cleaning input through [http://www.w3.org/People/Raggett/tidy/ HTML Tidy].

===Microtron===
* [http://github.com/amccollum/microtron Microtron] is intended to be a general-purpose microformat parser/transformer. It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).
** Requires [http://codespeak.net/lxml/ lxml] and [http://pypi.python.org/pypi/isodate/ isodate]

== Ruby ==
===Prism ===
* [[Prism]]
** by [[implementors#Mark_Wunsch|Mark Wunsch]]
** Library and command line tool for parsing POSH/Microformats
** Uses the [http://nokogiri.org/ Nokogiri] HTML, XML, SAX, and Reader parser

=== mofo ruby microformats parser===
* [http://mofo.rubyforge.org/ mofo], [http://groups.google.com/group/mofo-rb mofo Google Group], [http://github.com/defunkt/mofo/tree/master GitHub repository]
** by [[implementors#Chris Wanstrath|Chris Wanstrath]]
** Uses the [http://wiki.github.com/why/hpricot Hpricot] HTML/XML parser

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== uformats ===
* [http://rubyforge.org/projects/uformats uformats]

=== scrAPI ===
* [http://rubyforge.org/projects/scrapi scrAPI]

== XSLT ==
===Optimus===
* [[Optimus]] is open source XSLT that parses microformats, converts them into JSON or XML, and validates them too.

===X2V===
* [[X2V]] is [http://hg.microformats.org/ open source XSLT for extracting microformats].
** by Brian Suda

== editing this page ==
For now, this page ''copies'' (rather than ''moves'') information from the existing [[implementations | Implementations]] page.

== see also ==
* [[implementations]]
* [[implementors]]
* [[user-interface]]
* [[open-source]]

hmedia

2010-02-25T01:28:44Z

WebOrganics: /* Examples in the wild */ removing dead link

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* <span class="author">[[User:WebOrganics| Martin McEvoy]]</span>

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
</dl>
</dd>
<dt>rel</dt>
<dd>
<dl>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

Note (informative). See also an [http://purl.org/microformat/hmedia/ RDF Schema for the hMedia vocabulary].

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://www.norfolkblackhistorymonth.org.uk/events/2009/film.html Norfolk Black Film Festival] marks up movie information with hMedia. Example: the movie [http://www.norfolkblackhistorymonth.org.uk/events/2009/blacula.html Blacula].
* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* 2009-08-11 The [http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia] article by <span class="vcard"><span class="fn">Tim Aidlin</span></span> on Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick].

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

hmedia

2009-11-03T13:09:57Z

WebOrganics: add author tag (for hatom)

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* <span class="author">[[User:WebOrganics| Martin McEvoy]]</span>

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

Note (informative). See also an [http://purl.org/microformat/hmedia/ RDF Schema for the hMedia vocabulary].

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* An example of [http://weborganics.co.uk/dataset/dataset-article.html hMedia and html 5] using the <code><audio></code> and <code><video></code> tags.
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* 2009-08-11 The [http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia] article by <span class="vcard"><span class="fn">Tim Aidlin</span></span> on Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick].

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

hmedia

2009-11-03T13:00:58Z

WebOrganics: /* Articles */ removed nested hAtom entry inside entry-content (invalid hAtom)

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

Note (informative). See also an [http://purl.org/microformat/hmedia/ RDF Schema for the hMedia vocabulary].

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* An example of [http://weborganics.co.uk/dataset/dataset-article.html hMedia and html 5] using the <code><audio></code> and <code><video></code> tags.
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* 2009-08-11 The [http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia] article by <span class="vcard"><span class="fn">Tim Aidlin</span></span> on Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick].

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

User:WebOrganics

2009-10-25T11:06:12Z

WebOrganics: add note

<div class="vcard" id="weborganics">
<h1><span class="fn">
<span class="given-name">Martin</span>
<span class="family-name"> McEvoy</span>
</span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url uid"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
<span class="note">
WebOrganics is a small Web Design and Development Company based in Lancashire England.
</span>
</div>

http://weborganics.co.uk/images/hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://weborganics.co.uk/haudio-rss/ hAudio to RSS] Hypertext Playlist (hAudio)
* [http://weborganics.co.uk/hFoaF/ hFoaF]: Hypertext Friend of a Friend (hCard+XFN+rel=bookmark to FoaF)
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats
* [http://weborganics.co.uk/hCast/ hCast]: hAtom + Media Info to RSS2+MRSS
* [http://weborganics.co.uk/mo-haudio/ Mo-hAudio]: GRDDL Profile to extract Music Ontology from hAudio

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

User:WebOrganics

2009-10-25T10:59:06Z

WebOrganics: add uid

<div class="vcard" id="weborganics">
<h1><span class="fn"><span class="given-name">Martin</span> <span class="family-name"> McEvoy</span></span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url uid"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
</div>

http://weborganics.co.uk/images/hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://weborganics.co.uk/haudio-rss/ hAudio to RSS] Hypertext Playlist (hAudio)
* [http://weborganics.co.uk/hFoaF/ hFoaF]: Hypertext Friend of a Friend (hCard+XFN+rel=bookmark to FoaF)
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats
* [http://weborganics.co.uk/hCast/ hCast]: hAtom + Media Info to RSS2+MRSS
* [http://weborganics.co.uk/mo-haudio/ Mo-hAudio]: GRDDL Profile to extract Music Ontology from hAudio

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

hmedia

2009-09-18T10:40:51Z

WebOrganics: /* Examples in the wild */ HTML 5 example

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

Note (informative). See also an [http://purl.org/microformat/hmedia/ RDF Schema for the hMedia vocabulary].

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* An example of [http://weborganics.co.uk/dataset/dataset-article.html hMedia and html 5] using the <code><audio></code> and <code><video></code> tags.
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* <span class="hentry"><span class="published">2009-08-11</span> The <cite class="entry-title">[http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia]</cite> article by <span class="author vcard"><span class="fn">Tim Aidlin</span></span> on <span class="entry-summary">Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick]</span></span>.

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

hmedia

2009-09-12T15:33:32Z

WebOrganics: /* Implementations */ typo!!!

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* The [http://purl.org/microformat/hmedia/ hMedia RDF Vocabulary]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* <span class="hentry"><span class="published">2009-08-11</span> The <cite class="entry-title">[http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia]</cite> article by <span class="author vcard"><span class="fn">Tim Aidlin</span></span> on <span class="entry-summary">Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick]</span></span>.

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

hmedia

2009-09-12T15:32:17Z

WebOrganics: /* Implementations */ RDF Vocab

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

==Examples in the wild==
This section is '''informative'''.

The following sites have implemented [[hMedia]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hMedia, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-examples-in-wild]].

* [http://rhizohm.net/music/ Rhizohm: some experiments / compositions] - music
* [http://thunderkick.us/index_hMedia.html Thunderkick] - photos
* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]]) with the Transformr web-service hMedia implementation (documented below)
* ...

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse [[hMedia]] content. If you have an hMedia implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[hmedia-implementations]].

* [[Oomph]] supports parsing hMedia on pages and displaying a friendly media player interface to easily browse music, movies, and pictures on the page.
* [http://transformr.co.uk Transformr] is a web-service that parses [[hmedia|hMedia]] + [[hatom|hAtom]] and produces [http://search.yahoo.com/mrss MediaRSS]
* The [http://purl.org/microformat/media/ hMedia RDF Vocabulary]
* ...

== Articles ==
This section is '''informative'''.

The following articles have been written which discuss [[hMedia]]. If you have an hMedia article or blog post, feel free to add it to the '''top''' of this list using [[hAtom]] markup. Once the list grows too big, we'll make a separate wiki page like [[hmedia-articles]].

* <span class="hentry"><span class="published">2009-08-11</span> The <cite class="entry-title">[http://visitmix.com/Opinions/I-3-hMedia I <3 hMedia]</cite> article by <span class="author vcard"><span class="fn">Tim Aidlin</span></span> on <span class="entry-summary">Mix Online discusses viewing two examples with hMedia with [[oomph|Oomph]], music on [http://rhizohm.net/music Rhizohm] and photos on [http://thunderkick.us/index_hMedia.html Thunderkick]</span></span>.

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

User:WebOrganics

2009-09-12T15:29:30Z

WebOrganics: updating icon

<div class="vcard" id="weborganics">
<h1><span class="fn"><span class="given-name">Martin</span> <span class="family-name"> McEvoy</span></span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
</div>

http://weborganics.co.uk/images/hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://weborganics.co.uk/haudio-rss/ hAudio to RSS] Hypertext Playlist (hAudio)
* [http://weborganics.co.uk/hFoaF/ hFoaF]: Hypertext Friend of a Friend (hCard+XFN+rel=bookmark to FoaF)
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats
* [http://weborganics.co.uk/hCast/ hCast]: hAtom + Media Info to RSS2+MRSS
* [http://weborganics.co.uk/mo-haudio/ Mo-hAudio]: GRDDL Profile to extract Music Ontology from hAudio

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

hmedia

2009-07-23T16:35:50Z

WebOrganics: removing reference to hypermedia, I like the idea that the 'h' is for Horatio (Caine)

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

== Implementations ==

* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]])
* There is a web-service that extracts [[hmedia|hMedia]] + [[hatom|hAtom]] as [http://search.yahoo.com/mrss MediaRSS] available at [http://transformr.co.uk Transformr]

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

media-info-brainstorming

2009-07-23T16:31:11Z

WebOrganics: adding template

= Brainstorming for Media Microformat =

This is a brainstorm for media microformat. Examples of media-info can be found here [http://microformats.org/wiki/media-info-examples media-info-examples]

== Contributors ==

* [http://napsterization.org/stories/ Mary Hodder]
* [http://onlisareinsradar.com/ Lisa Rein]
* [http://microformats.org/wiki/User:ChrisNewell Chris Newell]
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:WebOrganics|Martin McEvoy]]

== The Problem ==

There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described. Having a single publishing format to relate them as needed in an organized structure makes sense.

== Elements that come up often in practice ==
Here are some examples of elements that might be included because they seem to come up often in user generated media publishing, either on their own blogs or on service sites, include the following:

<strong>Base elements:</strong>
* Title
* Html URL
* Media URL
* Image URL (video and audio)
* Tags
* Description / summary
* Quotes (subsets of the object: a video quote and tags/description associated with it, a region annotation note for a photo, or the quote of a podcast or audio piece, with tags/description -- the technical detail for these subsets exists in the 'more info' section below)
* Creator
* License (defaults to copyright, if none exists, but it's there, by US law, and many other areas of the world)
* XML Feed URL
* Contributor

and for audio and visual:
* Episode
* Duration
* Interval

<strong>Other info</strong>:
(This is not the same for all types of media, and is published by users in very limited ways in practice, or is captured from the device or service or in some way, invisible to the user, and therefore often depends on a service to pick it up. It should only appear in a publishing tool under 'more data' at then end, for enthusiast users.)

<table border="1" cellspacing="2" cellpadding="2">

<tr><th><strong>JPG</strong></th><th><strong>Video</strong></th><th><strong>Audio</strong></th></tr>

<tr><th>Device</th><th>Device</th><th>Device</th></tr>

<tr><th>Ratio</th><th>Aspect Ratio</th><th>?</th></tr>

<tr><th>file size</th><th>file size</th><th>file size</th></tr>

<tr><th>.</th><th>audio codec</th><th>audio codec</th></tr>

<tr><th>.</th><th>video codec</th><th>.</th></tr>

<tr><th>.</th><th>bit / frame rate</th><th>bit rate</th></tr>

<tr><th>Portrait or Landscape</th><th>.</th><th>.</th></tr>

<tr><th>Region Annotation (subphotos: calculation of location, size)</th><th>Quotes of Video (subvideo: in and out points)</th><th>Quotes of Audio (subaudio: in and out points)</th></tr>

<tr><th>iPod compliant?</th><th>iPod compliant?</th><th>iPod compliant?</th></tr>

<tr><th>Time</th><th>Time</th><th>Date</th></tr>

<tr><th>Date</th><th>Date</th><th>Date</th></tr>

<tr><th>Inclusion in playlist?</th><th>Inclusion in playlist?</th><th>Inclusion in playlist?</th></tr>

</table>
<br>

== Combining with other microformats ==

Although media items are sometimes presented in isolation they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the media microformat as a child (or in some cases a parent) of these microformats.

=== [http://microformats.org/wiki/hatom hAtom] ===
Podcast feeds reference a sequence of media items. A media microformat could therefore be used as a child element of hAtom.

=== [http://microformats.org/wiki/hcalendar hCalendar] ===
A media microformat may used to describe a continuous media stream e.g. a TV channel. An event or a schedule of events on the channel can be signaled using hEvents as child elements. This combination would provide what is necessary to capture a specific event; the media stream information and the timing information.

== Schema ==

=== Analysis of all Media Info examples ===

Common discovered properties occuring 70% or more of the time across all [[media-info-examples|media info examples]] completed 2008-11-07

<table border="1">
<tr>
<th>[[media-info-examples#Analysis_of_Photo_Sites|Photo]]</th>
<th>[[media-info-examples#Analysis_of_Video_Sites|Video]]</th>
<th>[[media-info-examples#Analysis_of_Podcasting_Sites|Podcasting]]</th>
<th>[[media-info-examples#Analysis_of_Individual_Publishing_of_Speech_Sites|Speech]]</th>
<th>[[media-info-examples#Analysis_of_Music_Sites|Music]]</th>
</tr>
<tr>
<td>Title 93.33%</td>
<td>Title 100%</td>
<td>Title 100%</td>
<td>Title 100%</td>
<td>Title 92%</td>
</tr>
<tr>
<td>Creator 96.66%</td>
<td></td>
<td>Creator 95.65%</td>
<td>Creator 100%</td>
<td>Creator 100%</td>
</tr>
<tr>
<td>Description 73.33%</td>
<td></td>
<td>Description 95.65%</td>
<td>Description 100%</td>
<td></td>
</tr>
<tr>
<td>Photo 100%</td>
<td>Video 100%</td>
<td>Download 95.65%</td>
<td>Download 95.65%</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Published 91.42%</td>
<td>Published 95.65%</td>
<td>Published 83.33%</td>
<td>Published 77%</td>
</tr>
<tr>
<td>Comments 70%</td>
<td>Comments 88.57%</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Feed 100%</td>
<td>Feed 100%</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Tag 71.42%</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Tracks 85%</td>
</tr>
</table>

=== hMedia Schema ===

Proposed hmedia schema and description defined by common elements discovered during the analysis of all [[media-info-brainstorming#Analysis_of_all_Media_Info_examples|Media Info examples]].

<table border="1">
<tr>
<th><code>hmedia</code></th>
<th>Definition</th>
</tr>
<tr>
<td><code>fn</code></td>
<td>The name of a media. Reused from [[hcard|hcard]]</td>
</tr>
<tr>
<td><code>contributor</code></td>
<td>A Contributor is any person or organization that takes part in the creation or distribution of the Media. Reused from [[haudio|haudio]]</td>
</tr>
<tr>
<td><code>description</code></td>
<td>A full-text description of the Media. Reused from [[hreview|hreview]]</td>
</tr>
<tr>
<td><code>photo</code></td>
<td>An embedded Image or Photograph of the Media. Reused from [[hcard|hcard]]</td>
</tr>
<tr>
<td><code>video</code></td>
<td>The contents are an embedded video or movie of the Media. {{NewMarker}}</td>
</tr>
<tr>
<td><code>enclosure</code></td>
<td>Indicates that the referred url is a download of the Media. Using [[rel-enclosure|rel-enclosure]].</td>
</tr>
<tr>
<td><code>published</code></td>
<td>Represents the date that the Media was made available to the public. Reused from [[hatom|hatom]]</td>
</tr>
<tr>
<td><code>comment</code></td>
<td>A user/visitor submitted comment on the media, see: [[media-info-brainstorming#Media_Comments|Media Comments]]{{NewMarker}}</td>
</tr>
<tr>
<td><code>alternate</code></td>
<td>Designates an alternate version for the document or Media typically an RSS, Atom or XML feed using the [[rel-design-pattern]] {{NewMarker}}</td>
</tr>
<tr>
<td><code>category</code></td>
<td>An author-designated "category" or a keyword/subject of the Media. Reused from [[hcalendar|hcalendar]], additionaly keywords may be defined using [[rel-tag|rel-tag]].</td>
</tr>
<tr>
<td><code>item</code></td>
<td>A container element for another Media item. Reused from [[haudio|haudio]]</td>
</tr>
</table>

=== Media Comments ===

User submitted comments are highly prevalent across all media domains the following table is a definition of the discovered elements of a comment. A separate analysis was made on 25 model examples, the results are available at [[media-info-examples#Media_comments|Media comments examples]]

Please see the [[comment|comment discussion]] on how to mark up a comment

== Comments ==

=== Differentiating File Content from File Format ===

We should consider splitting file content from file format. A song (content) can be represented as an MP3 audio file (format), or an MPEG-2 music video (format). media-info should be used to describe file content with a separate microformat or link-rel design pattern to describe file format.

Example 1:

* media-info (content): A song called "Hung Up" by "Madonna"
* file-format (format): 4.5MB MP3 file encoded at 192Kbps bitrate.

Example 2:

* media-info (content): A music video called "Hung Up" by "Madonna"
* file-format (format): 35MB AVI file, MP3 audio codec encoded at 192Kbps, DiVX video codec encoded at 600Kbps

[[User:ManuSporny|ManuSporny]] 06:50, 5 Apr 2007 (PDT)

=== Microformats and Democracy Player/Miro ===

Democracy (soon to be Miro) is a desktop program attempting to create a more television like experience for internet video.
Microformats present several unique challenges to our project. This is my (Nick Nassar's) attempt to summarize them. My opinions don't reflect the opinion of my employer (PCF). My email address at pculture.org is nassar.

Re-reading this, I realize it sounds very negative. Please, tell me why I'm totally wrong. I hope I'm totally wrong. :)

==== Loose specifications are difficult to parse and create ====

This is a problem we're seeing with RSS that could potentially multiply with the popularity of microformats.

The RSS "standard" is very loose, and our experience is that most feeds don't even conform to that standard. Because of this, we lose the main benefits of XML: easy parsing and creation. On the parsing end, we're forced to use complex third party libraries such as [http://www.feedparser.org/ Feed Parser] rather than just being able to parse with a simple XML parser. This is the same problem we saw with HTML in the 90s where the "standard" involves doing the right thing in a lot of non-standard cases.

Content creators need to use complex validators like [http://www.feedvalidator.org/ Feed Validator] rather than just being able to write valid XML so they make sure they don't do things that confuse reg-exp based parsers. It's much more difficult to create a program you trust to conform to a loose spec than one you trust to conform to a more rigid spec.

For search engines and other applications where exact data isn't important, this isn't a big deal. For an application that's expected to show exactly the videos the author published, it's a lot of work to get the parsing right. Even in "valid" RSS we see people faking the length and type attributes for enclosures all the time, forcing programs like ours not to trust that information.

Microformats could easily make those problems explode. In general, microformats are more dangerous because they're even looser, and they're embedded in the XHTML, so the data is tied to the presentation. In practice, you need extra divs and spans to get XHTML formatting right. Inserting that extra div tag to get the formatting right will change the data. The formats must be well defined enough to deal with this.

When I tell this to people, they say "Nick, you're crazy. It's easy to generate valid XML." To prove my point, there are two real world examples of this on your own site. The [http://microformats.org/code/hcalendar/creator hCalendar creator] and the [http://microformats.org/code/hcard/creator hCard creator] don't deal with quotes and angle brackets in the input, resulting in invalid XHTML when those characters are included. I don't bring this up to pick on this site, just to point out that this sort of mistake is the norm in supposedly easy to create XML formats.

One way to mostly solve this is to write a parser, a validator, and a generator for each format when you define it. This way there's a de facto correct implementation that can act like Netscape did for HTML or the perl implementation does for perl. It would also force a real world implementation of the "standard" before it gets adopted. If it's difficult to parse correctly, you can go back and redefine it to be more easily parsable.

''Strict formats are easier for everyone. As long as you insist on keeping it loose, writing parsers, validators, and generators for each format are a step forward.''

===== HTML data =====

A complex problem for authors of feed readers is how to deal with HTML encoded areas such as the description. HTML can contain JavaScript, plugins, and other "dangerous" content that you don't necessarily want in your program. [http://www.feedparser.org/ Feed Parser] only allows white listed tags and attributes. This is generally accepted as the right thing to do, but causes problems in programs like Democracy player when content authors expect certain tags to appear but they get blocked. This might be tricky when combined with the problem of allowing extra divs and spans without altering the data itself.

A microformat spec should include details on what fields content creators can expect to show up in an application such as Democracy Player

===== Character Sets =====

A very common problem with RSS feeds is incorrect character sets. The XML header might specify utf-8, but the document is actually latin-1, which causes it not to parse. Requiring or strongly recommending that all microformat documents are UTF-8 might improve the situation.

==== Mime types are useful ====

Another problem we're seeing with RSS that could get worse with microformats is the lack of a mime type. There is no standard RSS mimetype and extension (although application/xml+rss and .rss are finally catching on), so an application doesn't know what to do with an RSS file saved to disk. We have to assume that text/xml links sent into Democracy are RSS. Feed readers can't just associate with the mime type like most programs, they need to hook in in different ways.

Combining data into XHTML means there's no way to determine what programs can handle that page without downloading it first. If an XHTML page with media information is saved to disk, we have no way of determining it has data that can be used in Democracy player without first opening it up.

''This is a fundamental problem with microformats. You will never be able to load microformat documents into the correct program without parsing them.''

==== Media specific concerns ====

It should always be possible to use media microformats as a feed. It would be a very poor experience if, for example, media items were duplicated in programs like Democracy whenever their HTML changed. Making them an extension of the hAtom format should cover this. Recommend that real world implementations do correct HTTP caching so programs like Democracy can avoid downloading the entire file every time.

The format shouldn't require any fields other than URL and title. As is, most sites fake the length and type attributes for RSS enclosures. Don't make people fake data they don't have.

Tag each piece of data. It's difficult for us to parse strings like "35MB AVI file, MP3 audio codec encoded at 192Kbps, DiVX video codec encoded at 600Kbp" into anything useful, but if those fields are separated out with span tags, we can actually use that data.

''Make media microformats feeds. Don't require any fields. Tag each piece of data.''

{{Template:hmedia-related-pages}}

media-info-formats

2009-07-23T16:30:47Z

WebOrganics: adding template

==Contributors==

* [[User:ManuSporny | Manu Sporny]], [http://blog.digitalbazaar.com Digital Bazaar], Inc.

==Metadata Formats==

What follows is a list of metadata formats for audio, video and images.

===Video Metadata Formats===

* [http://reactor-core.org/ogg-tagging.html OGG Tagging Specification] - Optional comment specification for Ogg files.

===Image Metadata Formats===

* [http://park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html EXIF File Format] - Used for tagging images with a thumbnail and source camera information.

{{Template:hmedia-related-pages}}

media-info-examples

2009-07-23T16:30:12Z

WebOrganics: /* Related pages */ adding template

= Media Info Examples =

{{TOC-right}}

== Contributors ==

* [[User:RodBegbie | RodBegbie]]
* [http://tantek.com/log/ Tantek Çelik]
* [http://napsterization.org/stories/ Mary Hodder]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:MikeJohnson | Mike Johnson]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:WebOrganics| Martin McEvoy]]

== Introduction ==

Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.

== Emphasis on Practical, Simple, and Minimal ==

Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.

Thus for now, this document is deliberately restricted to examples that are:
* ''Actual'' examples in practice on the Web '''with URLs''' to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.

Any examples added which do not conform to these requirements will be deleted.

Any generic analysis will also be deleted. Analysis before examples is premature. Once there are sufficient media-info-examples, and hopefully a simple/clean listing of [[media-info-formats]], we'll hopefully start a [[media-info-brainstorming]] page to do aggregate analysis of the examples.

===Note on proposals===

Because the hMedia became a task so big that it seems impossible to make it "simple and minimal" discussions started on splitting them by media type.

see: [[audio-info-brainstorming]]

== Real World Examples ==

=== Overall Notes About Examples ===
These examples are organized into a short list of top level media categories, in the hopes that it will be easier to determine if there are media specific publishing behaviors, in addition to common behaviors across multiple types of media. Some may be subcategorized and distinguished by whether it was published by an individual publisher or a service:
* [[media-info-examples#Audio|Audio]] (Speech, Music)
* [[media-info-examples#Video|Video]]
* [[media-info-examples#Photos|Photos]]

The numbers after some of the examples' descriptions are based on numbers found pulling in media records at Dabble. Others may have higher numbers and would be encouraged to restate them if that's true.

=== Audio ===

==== Speech ====
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing. Quotes of audio files are beginning to appear, and publishers are putting up files with links to other audio files they've quoted from. Most audio appears to often have the same base elements as video and photos, with the exception of quotes.

===== Individual Publishing of Speech =====

* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]
** Appears to be composed of:
*** title/summary of the recording
*** clickable hyperlink to the recording (MP3)
*** comments
** Contextual:
*** (primary) speaker is indicated in nearby text

* [http://www.thechrispirilloshow.com/help/20060119_chuck_cummins_on_windows_vista_interface_design.phtml Chris Pirillo podcast]
** This example has a Title, Html URL, media URL(s), description or summary, categories/tags underneath what is viewable, and date. +10k

* [http://yukelzon.blogspot.com/2006/01/podcasts.html Reflog's Random Thoughts podcast]
** This example has a Title, Html URL, description or summary, creator, tags and publish time and date. NOTE, record also contains an [http://images.apple.com/r/ipodstore/ipodviews/0.jpg image], comments +10k records.

* [http://www.evilgeniuschronicles.org/wordpress/2006/01/12/egc-clambake-for-january-12-2006/ Evil Genius Chronicles podcast]
** This example has a Title, Html URL, description or summary, quotes URLs and descriptions, licence, creator, comments, tags and publish time and date. +10k records.

* [http://www(dot)bizbyjake.com/2006/01/how-are-you-doing.html media published from a blog, Jake Steinfeld's Audio Blog] NOTE: this record had trouble because mediawiki blocks any DOTbiz domains and so while this domain coincidentally has a DOTbizbyjake.com name that is not a TLD, it was still blocked in the loading of the page with this example. So please adjust the URL manually and then visit the site.
** This example has a Title, Html URL, media URL, creator and publish time and date. +10k records.

* [http://podcast.rubyonrails.org/ Ruby on rails Podcast]
** Feed, title, published, description, author, contributor, download, format

* [http://www.cnet.com/8300-11455_1-10.html Buzz out loud]
** Feed, title, description, published, episode, download, author

===== Analysis of Individual Publishing of Speech Sites =====

7 examples, 6 available

* post-title 100%
* audio-title 100%
* download 100%
* author 100%
* contributor 100%
* description 100%
* published 83.33%
* feed 66.66%
* category 50%
* comments 50%
* format 33.33%
* episode 16.66%
* photo 16.66%

==== Music ====

===== Individual Publishing of Music =====

* [http://www.bradsucks.net/music/ Brad Sucks » music]
** Has album title, song title, separate link to more info, inline flash player, and play link (to mp3)

* [http://www.scottandrew.com/music/ Scott Andrew - lo-fi acoustic pop superhero! > music >]
** Has album title, song title, licensing info, remixing policy, multiple formats such as streaming link (to m3u), play links (to mp3, OGG, FLAC)
** Record contains album cover image.

* [http://www.hearingdouble.co.uk/dumb/index2.html Portishead Remixed]
** Whole page is for one album (a mash-up remix of a Portishead album). Has Album Track Number and Title (linked to mp3) and Remixer's name. Also a link to multiple formats such as the BitTorrent download of the whole album.
** Record contains album cover images.

* More examples here please....

===== Analysis of Individual Publishing of Music Sites =====

3 examples, 2 available

* post-title: 100%
* audio-title: 100%
* download: 100%
* contributor: 100%
* published: 100%
* duration: 100%
* photo: 100%
* payment: 100%
* album title: 100%
* category: 50%

===== Music Podcasting sites=====

* [http://www.coverville.com/archives/2008/10/coverville_517.html Coverville]
** description, title, published, contributor, position, download, comments

* [http://magnatune.com/podcasts/details/magnatune_middle-eastern_podcast_2006_12_14 Magnatune]
** Feed, title, section, genre, length, published, contributor, interval, download

* [http://www.mutantpop.net/radioclash/archives/2007/03/24/rc-113/ Mutantpop]
** Feed, description, title, photo, format, duration, size, published, contributor, download, category, comments

* [http://www.btpodshow.com/shows/?sId=21&mId=5332173 btpodshow]
** Feed, description, title, episode , category, published, contributor, position, comments

* [http://indiecastwp.podshow.com/?p=76 Indiecast]
** Feed, description, title, section, format, category, length, published, contributor, episode

* [http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/ Accidenthash]
** Feed, description, title, category, length, published, contributor, episode, download, comments

* [http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/ Strong words inc]
** Feed, description, title, duration, published, episode, download, author, comments

* [http://threehive.libsyn.com/index.php?post_id=111596 Three hive]
** Feed, description, title, photo, format, category, published, contributor[s] author, episode, download, comments

* [http://music.for-robots.com/archives/002495.html For Robots]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.fluxblog.org/2008/10/when-the-work-is-done fluxblog]
** Feed, title, published, description, contributor, download, comments

* [http://www.3hive.com/2008/10/photons.php 3hive]
** Feed, title, published, photo, description, author, contributor, download[s] , format, category, comments

* [http://www.saidthegramophone.com/archives/complete_coverage.php said the gramophone]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.archasung.com/playlist/playlist-cloudy-days Archasung]
** Feed, title, published, photo, description, contributor, download[s], comments

* [http://betterpropaganda.com/content.aspx?id=840 Better Propaganda]
** Feed, title, photo, description, contributor, download[s], episode

* [http://freakytrigger.co.uk/ft/2008/10/a-bite-of-stars-a-slug-of-time-and-thou-episode-14/ Freaky Trigger]
** Feed, title, published, description, author, contributor, download, episode, comments

* [http://www.catbirdseat.org/archives/001093.php Cat Bird Seat]
** Feed, title, published, description, contributor, download[s], format

* [http://the-big-ticket.blogspot.com/2007/09/all-in-game-indeed.html The Big Ticket]
** Feed, title, published, description, author, contributor, download, format, category, comments

* [http://sixeyes.blogspot.com/2008/10/sixeyes-saturday-mix-oct-4th.html Six Eyes]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.spoiltvictorianchild.co.uk/2007/11/no-vice-my-arse.html Spoilt Victorian Child]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.scissorkick.com/2008/09/midnight-lab-band/ Scissorkick]
** Feed, title, published, photo, description, author, contributor, download, format, category, comments

* [http://loki23.blogspot.com/2008/09/flower-electronics.html loki23]
** Feed, title, published, photo, description, author, contributor, download[s], format, category, comments

* [http://www.sweetthunder.org/tapes/weekonehundredandsix.html sweetthunder]
** Feed, title, published, photo, description, contributor, download, duration, comments

* [http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html Arjan writes]
** Feed, title, published, photo, description, contributor, download, duration, format, comments

===== Analysis of Podcasting Sites =====

23 examples

* feed 100%
* post-title 100%
* audio-title 100%
* contributor 95.65%
* description 95.65%
* download 95.65%
* published 95.65%
* comments 78.26%
* photo 56.52%
* author 52.17%
* category 39.13%
* format(eg: mp3) 39.13%
* episode(number) 30.43%
* duration 13.04%

properties occurring less than 10%

* interval

===== Service Publishing of Music =====

* [http://audiofind.ru/ AudioFind]
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Album Example]
*** Information displayed: artist (link), title, genre (link), style (link), release date, label, summary, web-based purchase (link), price, artist rating, album rating.
*** Record contains cover image
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Song Example]
*** Information displayed: track number, title, length, rating, price, sample (link), web-based purchase (link)
*** Record contains cover image

* [http://bigpondmusic.com Telstra BigPond]
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Album Example]
*** Information displayed: artist (link), title, genre, release date, label, summary, web-based purchase (link), subscriber price, non-subscriber price, cover image
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Song Example]
*** Information displayed: track number, title, artist, album, price, add to pop-list (link), sample (link), web-based purchase (link)

* [http://www.bitmunk.com/ Bitmunk]
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068744 Album Example]
*** Information displayed: artist, album title, publisher, release date, genre (link), summary, long description, payees, total price, sample (link), tracks, web-based purchase (link), p2p-based purchase (link)
*** Record contains cover image
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068746 Song Example]
*** Information displayed: artist, song title, composer, publisher, release date, genres, album, payees, total price, web-based purchase (link), p2p-based purchase (link)

* [http://downloadpunk.com Download Punk]
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Album Example]
*** Information displayed: title, artist (link), label (link), physical-based purchase (link), web-based purchase (link)
*** Record contains cover image
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Song Example]
*** Information displayed: title, sample (link), price, web-based purchase (link)

* [http://www.fye.com FYE]
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Album Example]
*** Information displayed: title, artist (link), format, release date, label (link), UPC, product id, genre, styles, regular price, store price, savings, physical-based purchase (link), tracks, description, reviews, production credits
*** Record contains cover image
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Song Example]
*** Information displayed: track number, title, artist

* [http://imusic.libero.it/ iMusic]
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Album Example]
*** Information displayed: title, artist (link), genre, release date, publisher, number of tracks, length, tracks, web-based purchase (link)
*** Record contains cover image
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Song Example]
*** Information displayed: track number, length, sample (link), release date, price, web-based purchase (link)

* [http://musicdownload.aon.at/v7/ AON Music ]
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Album Example]
*** Information displayed: artist (link), album, price, format, bitrate, label, genre, number of tracks, sample (link), add bookmark (link), web-based purchase (link), tracks
*** Record contains cover image
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Song Example]
*** Information displayed: track number, title, length, format, price, sample (link), add bookmark (link), web-based purchase (link)

* [http://music.msn.com MSN]
** [http://music.msn.com/album/?album=50538895 Album Example]
*** Information displayed: artist (link), title, release date, label, album rating.
*** Record contains cover image
** Song Example (store wasn't working correctly - no song info found)

* [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/Call?htmltemplate=./index.htm TDC Online]
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Album Example]
*** Information displayed: title, artist (link), length, release date, label, format, web-based purchase (link), price, tracks
*** Record contains cover image
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Song Example]
*** Information displayed: track number, title (link), price, sample (link), web-based purchase (link)

* [http://www.audiolunchbox.com Audio Lunchbox]
** [http://www.audiolunchbox.com/album?a=75751 Album Example]
*** Information displayed: title, artist (link), label (link), genre (link), release date (link), format, bitrate, price, price in credits, web-based purchase (link), add to wishlist (link), sample (flash applet), tracks
*** Record contains cover image
** [http://www.audiolunchbox.com/album?a=75751 Song Example]
*** Information displayed: track number, title, length, price, price in credits, web-based purchase (link), sample (flash applet)

* [http://www.chaosmusic.com/music/ Chaos Music]
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Album Example]
*** Information displayed: title, artist (link), genre, format, release date, price, physical-based purchase (link), add to wishlist (link), tracks, description, availability
*** Record contains cover image
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Song Example]
*** Information displayed: track number, title

* [http://www.connect-europe.com Sony Connect]
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, length, publisher, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Song Example]
*** Information displayed: title, artist, length, price, sample (link), web-based purchase (link)

* [http://www.digirama.co.nz/ Digirama]
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Album Example]
*** Information displayed: title, artist (link), genre (link), label, release date, price, web-based purchase (link), license, related albums, also bought, reviews, tracks
*** Record contains cover image
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Song Example]
*** Information displayed: track number, title, length, sample (link), price, web-based purchase (link)

* [http://www.emusic.com eMusic]
** [http://www-v3.emusic.com/album/10917/10917324.html Album Example]
*** Information displayed: title, artist (link), sample (link), save to playlist (link), genre (link), styles (link), label (link), album rating, reviews, length, tracks, web-based purchase (link)
** [http://www-v3.emusic.com/album/10917/10917324.html Song Example]
*** Information displayed: track number, sample (link), tracks, length, web-based purchase (link)

* [http://www.fnacmusic.com/ FNAC]
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Album Example]
*** Information displayed: title, artist (link), length, add to playlist (link), web-based purchase (link), tracks, price, genre
*** Record contains cover image
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Song Example]
*** Information displayed: sample (link), add to playlist (link), track number, title, length, web-based purchase (link), price

* [http://sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Album Example]
*** Information displayed: title, artist (link), release date, catalog ID, SKU, label, price, price in points, summary, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Song Example]
*** Information displayed: track number, title

* [http://www.misrolas.com/ MisRolas]
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Album Example]
*** Information displayed: title, artist (link), cover image, release date, number of tracks, album rating, price, web-based purchase (link), tracks, reviews
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Song Example]
*** Information displayed: track number, title, sample (link), artist, price, web-based purchase (link), add to wishlist (link)

* [http://www.mtv.com MTV]
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Album Example]
*** Information displayed: title (link), artist (link), release date, label, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Song Example]
*** Information displayed: track number, title, sample (link), video sample (link)

* [http://www.musica360.com/ Musica360]
** [http://musica360.com/store/product_info.php?products_id=232 Album Example]
*** Information displayed: title, artist, price, samples (flash), tracks, web-based purchase (link)
*** Record contains cover image
** [http://musica360.com/store/product_info.php?products_id=232 Song Example]
*** Information displayed: title, artist, price, web-based purchase (link)

* [http://www.musicload.de/ Musicload]
** [http://www.musicload.de/item.ml?releaseid=1884260_2 Album Example]
*** Information displayed: title, artist (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), tracks, comments
** [http://www.musicload.de/item.ml?releaseid=1884261_4 Song Example]
*** Information displayed: title, artist (link), album (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), comments

* [http://www.napster.com Napster]
** [http://www.napster.com/view/album/index.html?id=12376484 Album Example]
*** Information displayed: title, artist (link), release date, track count, label, sample (link), share (link), web-based purchase (link), review, tracks
** [http://www.napster.com/view/album/index.html?id=12376484 Song Example]
*** Information displayed: artist (link), title, track number, album title, length, web-based purchase (link)

* [http://www.partymob.com/edl/browse/?tab=music PartyMob]
** [http://www.partymob.com/edl/details/default.aspx?album=2089814 Album Example]
*** Information displayed: title, artist (link), total length, release date, format, quality, genre, sample (link), price, web-based purchase (link), tracks
** [http://www.partymob.com/edl/details/default.aspx?track=234418 Song Example]
*** Information displayed: title, artist, length, release date, format, quality, genre, sample (link), price, web-based purchase (link), DRM information

* [http://www.peerimpact.com Peer Impact]
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449 Album Example]
*** Information displayed: title, artist (link), price, purchase (application link), format, track count, genre, release date, label, tracks
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449# Song Example]
*** Information displayed: track number, sample (link), title, artist (link), length, price

* [http://www.puretracks.com Pure Tracks]
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Album Example]
*** Information displayed: artist, title, label, total length, disc count, release date, price, web-based purchase (link), DRM information, tracks
*** Record contains cover image
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Song Example] (in popup window)
*** Information displayed: track number, sample (link), title, artist, length, price, web-based purchase (link), label (popup)

* [http://www.reggaecountry.com Reggae Country]
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Album Example]
*** Information displayed: title, artist, release date, label, web-based purchse (link), price, tracks
*** Record contains cover image
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Song Example]
*** Information displayed: sample (link), track number, title, artist, length, web-based purchase (link), price

* [http://www.rhapsody.com Real/Rhapsody]
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Album Example]
*** Information displayed: artist, title, sample (link), label, release date, tracks
*** Record contains cover image
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Song Example]
*** Information displayed: sample (link), track number, title

* [http://www.ruckusnetwork.com Ruckus]
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Album Example]
*** Information displayed: title, artist, release date, genre, label, tracks
*** Record contains cover image
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Song Example]
*** Information displayed: track number, title, length

* [http://www.sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Album Example]
*** Information displayed: title, artist (link), release date, catalog id, label, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Song Example]
*** Information displayed: sample, track number, title

* [http://www.starzik.com/starzik.php Starzik SARL]
** Album Example (hidden url)
*** Information displayed: title, artist (link), genre, label, release date, length, format, bitrate, size, web-based purchase (link), tracks
*** Record contains cover image
** Song Example (hidden url, separate from album example)
*** Information displayed: title, artist (link), album title, genre, label, release date, length, creators, composer, performance artist, format, bitrate, size, web-based purchase (link)

* [http://www.thecellcity.com CellCity]
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=fuzzyquery&CDMdepartment=music&cdmalbum=What's%20The%20Word%20Vol.%201&CDMReturnURL=/music/albumdetails.shtml] Album Example]
*** Information displayed: artist, label, release date, genre, tracks
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=GetProductDetail&CDMProductID=A00001148172&CDMReturnURL=/music/product_detail.shtml Song Example]
*** Information displayed: title, price, web-based purchase (link)

* [http://www.top100.cn top100.cn]
** [http://www.top100.cn/product/specialall/S0027876000.htm Album Example]
*** Information displayed: title, artist (link), release date, sample (link), web-based purchase (link), label (link), genre (link), long description, tracks
** [http://www.top100.cn/product/SongFiles/0027876/M0027876001.htm Song Example]
*** Information displayed: title, artist (link), label (link), genre (link), price, sample (link), web-based purchase (link), description, comments

* [http://www.wippit.com/default.aspx Wippit]
** [http://www.wippit.com/AlbumDet.aspx?StrId=28724&StrCatType=S Album Example]
*** Information displayed: title, artist (link), price, genre (link), format, release date, tracks, web-based purchase (link)
** [http://www.wippit.com/DetailItem.aspx?StrItemID=28724&StrMediaID=724904&StrMediaType=S Song Example]
*** Information displayed: title, artist (link), album (link), genre, format, release date, size, track number, file type, price, web-based purchase link

* [http://www.yanga.ru Yanga]
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, price, web-based purchase (link), rating, tracks
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Song Example]
*** Information displayed: sample, track number, title, length, rating, price, web-based purchase (link)

* [http://www.somesongs.com/ somesongs]
** [Album Example]
*** Information displayed:
** [http://www.somesongs.com/song_info.php?select=4713 Song Example]
*** Information displayed: title, artist (link), rating, sample (link), summary, reviews, release date

* [http://magnatune.com/ Magnatune]
** [http://magnatune.com/artists/albums/ammonite-recon/ Album Example]
*** Information displayed: artist (link), title, cover image, total time, length, release date, artist location (link), web-based purchase (link), physical-based purchase (link), license (link), tracks, summary
** [http://magnatune.com/artists/albums/ammonite-recon/ Song Example]
*** Information displayed: track number, title, length, sample (link)

* [http://www.songfight.org/ SONG FIGHT!]
** [http://www.songfight.org/artistpage.php?key=15-16_puzzle&sortkey=date Album Example]
*** Information displayed: artist (link), cover image, artist location, summary, title,
** [ Song Example]
*** Information displayed: release date, sample (link), title

* [http://www.yes.com/ Yes.com]
** [http://www.yes.com/ Album Example]
*** Information displayed: cover image, artist (link)
*** Record contains cover image
** [http://www.yes.com/ Song Example]
*** Information displayed: cover image, artist (link), rank, web-based purchase (link), played-by radio station

* [http://www.myspace.com MySpace]
** [http://myspace.com/theradioknives Album Example]
*** Information displayed: artist, title, sample (link), cover image, number of plays, tracks
*** Record contains cover image
** [http://myspace.com/theradioknives Song Example]
*** Information displayed: artist, title, number of plays, sample (link), lyrics (link)

* [http://musicbrainz.org MusicBrainz.org]
** [http://musicbrainz.org/release/1138abc1-77f4-4ba9-900d-5cf52baaf4bf.html Album Example]
*** Information displayed: artist (link), title, cover image, tracks, disc id
*** Record contains cover image
** [http://musicbrainz.org/show/track/?trackid=435002 Song Example]
*** Information displayed: title, artist, length, id (link), length, album (link), album id (link), artist, artist id (link), relationship (link), track number

* [http://reactor-core.org/ogg-tagging.html Vorbis Comment Recommendations]
** [http://reactor-core.org/ogg-tagging.html Album Example]
*** Information displayed: artist, publisher, copyright, disc number, isrc, ean/upn, label, label catalog number, license, opus, source media, title, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment
** [http://reactor-core.org/ogg-tagging.html Song Example]
*** Information displayed: album, artist, publisher, copyright, disc number, isrc, ean/upn, label, label number, license, opus, source media, title, track number, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment

* [http://www.apple.com/itunes/podcasts/techspecs.html iTunes RSS extensions]
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Album Example]
*** Information displayed: title, website (link), language, licensing, summary, description, owner, owner e-mail, cover image, genre
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Song Example]
*** Information displayed: title, artist, summary, description, sample (link), length, format, id, release date, tags

* [http://www.discogs.com/ Discogs]
** [http://www.discogs.com/release/705805 Album Example]
*** Information displayed: artist, title, label (link), catalog id, format, country, release date, genre, style, notes, rating, tracks
** [http://www.discogs.com/release/705805 Song Example]
*** Information displayed: artist (link), title, track number

* [http://www.last.fm/ Last.fm]
** [http://www.last.fm/music/Muse/+albums Album Example]
*** Information displayed: cover image, artist, title, release date, label (link), number of tracks, sample (link), physical-based purchase (link), tracks
** [http://www.last.fm/music/Muse/Absolution Song Example]
*** Information displayed: track number, sample (link), title, length, number of plays

===== In-active Music Services =====

* [http://music.yahoo.com/ Yahoo! Music Unlimited]
* [http://www.musicmatch.com Musicmatch] (Merged with Yahoo! Jukebox)
* [http://www.musicnet.com MusicNet] (Service Provider)
* [http://www.musicnow.com AOL Music Now] (Merged with Napster)
* [http://www.nate.com Nate.com] (Appears to be Korean, cannot find album examples)
* [http://www.nextradiosolutions.com Next Radio] (Service Provider)
* [http://www.soundbuzz.com Soundbuzz] (Requires MS IE6)
* [http://www.starbucks.com Starbucks] (Requires Flash 8 player)
* [http://www.streetcds.com/ Street CDs] (parked domain name)
* [http://www.synacor.com/content/index.php Synacor] (Service provider)
* [http://www.telecomitalia.com/ Telecom Italia] (Service provider)
* [http://www.terra.es/pixbox/ Pixbox (Terra) ] (Windows application)
* [http://www.virgin.com/downloads Virgin Digital] (merged with Napster)
* [http://www.virginmega.fr/ Virgin] (Requires Windows)
* [http://www.yeahronimo.nl Yeahronimo (Commodoreworld)]

===== Analysis of Music Sites =====

Shown below is the most popular information listed for music albums. This includes analysis of over 85 online music sites.

'''Album Statistics'''
* 100%: artist
* 92%: title
* 85%: tracks
* 77%: release date
* 67%: label
* 62%: genre
* 62%: web-based purchase
* 59%: cover image
* 49%: price
* 26%: format
* 23%: sample
* 21%: length
* 18%: summary
* 15%: physical-based purchase
* 10%: publisher
* 10%: reviews

Shown below is the most popular information listed for songs. Keep in mind that along with the information listed below - for over 80% of the cases, album information was listed on the same page.

'''Song/Track Statistics'''
* 95%: title
* 69%: track number
* 67%: sample
* 62%: web-based purchase
* 59%: artist
* 54%: price
* 54%: length
* 26%: release date
* 15%: album
* 15%: genre
* 13%: format
* 10%: rating
* 10%: label

=== Video ===
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player. *Many videos include a thumbnail jpg which is clickable to the media object and player.* Some video includes links to those other source videos, photos and audio that have been quoted. Most videos have the same base elements as photos and audio, with the exception of quotes.

==== Individual publishing of video ====

* [http://FreeVlog.org FreeVlog]
** [http://www.freevlog.org/index.php/2007/01/24/new-vlog-moments-in-turkey/ Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments (link)

* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]
** [http://joshkinberg.com/popupmaker/ Video Example]
*** Information displayed: title, download (link), preview image

* [http://ryanedit.blogspot.com/ Ryanne's Video Blog]
** [http://ryanedit.blogspot.com/2006/01/light-water-music-2.html Video Example]
*** Information displayed: title, post date, preview image, download (link), tags, comments (link)

* [http://www.prototypen.com/blog/vjblog/ Artificial Eye]
** [http://www.prototypen.com/blog/vjblog/archives/001240.html Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, website (link), comments

* [http://www.itsjerrytime.com/ It's JerryTime!]
** [http://www.itsjerrytime.com/?p=89 Video Example]
*** Information displayed: title, preview image, video (link), comments, tags

* [http://www.bottomunion.com/blog/ Bottom Union]
** [http://bottomunion.com/blog/?p=403 Video Example]
*** Information displayed: title, preview image, video (link), video (embedded), post date, summary, website (link), comments, tags, feed subscription (link)

* [http://rocketboom.com/vlog/ Rocketboom]
** [http://www.rocketboom.com/stories/rb_07_mar_26 Video Example]
*** Information displayed: title, preview image, download (link), post date, video (embedded), comments (link), tags (link), feed subscription (link)

* [http://www.chesslodge.com/ Chess Lodge]
** [http://www.chesslodge.com/2007/03/chess-video-lesson-2/ Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, video (embedded), website (link), comments (link), tags, feed subscription (link)

* [http://pechesscast.blogspot.com/ PE Chesscast]
** [http://pechesscast.blogspot.com/2007_03_01_archive.html#4209870902184134583 Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, comments (link), tags (link), feed subscription (link), e-mail to friend (link)

* [http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html Steve Garfield]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv media]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv.jpg image]
*** Information displayed: title, preview image, download (link), post date, summary, commennts (link), tags, description, feed subscription, licensing.
*** Quoting / credits: music included.

==== Service publishing of video (there are 350+ so this is a short list) ====

* [http://blip.tv/ blip.tv]
** [http://thedailyreel.blip.tv/file/181901?filename=Thedailyreel-TheDailyReelMarch28629.flv Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, review rating, content rating (link), category, video (embedded), number of comments, comments (link), tags, e-mail forward (link), feed subscription (link)

* [http://youtube.com/ YouTube]
** [http://youtube.com/watch?v=KKTDRqQtPO8 Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link), e-mail to friend (link), save to favorites, add to groups, number of views, number of comments, number of honors, number of links, number of responses, permalink, related

* [http://mefeedia.com/ Mefeedia]
** [http://mefeedia.com/entry/2303506/ Video Example]
*** Information displayed: creator (link), title, preview image, download (link), post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link)

* [http://vimeo.com/ Vimeo]
** [http://vimeo.com/clip:162754 Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments

* [http://DailyMotion.com/ DailyMotion]
** [http://www.dailymotion.com/us/featured/video/x1l9qx_sad-kermit-hurt Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, content rating, category, summary, video (embedded), website (link), comments, tags, add to favorites (link), add to blog (link), e-mail to friend (link), length, filming location, permalink

* [http://www.nbc.com NBC]
** [http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/ Video Example]
*** Information displayed: title, summary, video(embeded), duration, tags, views, rating, comments, permalink(url)

* [http://abc.go.com ABC]
** [http://abc.go.com/primetime/watercooler/index?pn=index Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, season, episode, rating

* [http://video.google.com Google Video]
** [http://video.google.com/videoplay?docid=-5177576155567667810&hl=en Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.videosift.com Video Sift]
** [http://www.videosift.com/video/Idiot-Cop-never-heard-of-the-Constitution Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.footbag.org/gallery/video Footbag]
** [http://www.footbag.org/gallery/show/8830 Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, download(enclosure), size

* [http://www.break.com Break]
** [http://www.break.com/index/powerful-tornado-throws-cars.html Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.collegehumor.com College Humor]
** [http://www.collegehumor.com/video:1886239 Video Example]
*** Information displayed: title, creator, video(embeded), published, rating, tags, comments

* [http://www.ebaumsworld.com Ebaum's World]
** [http://www.ebaumsworld.com/video/watch/1044597/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, tags, views, share(link), comments

* [http://www.holylemon.com/ Holylemon]
** [http://www.holylemon.com/The-Animator--v818.html Video Example]
*** Information displayed: title, description, video(embeded), published, rating, views, share(link), comments

* [http://www.crooksandliars.com/ Crooks and Liars]
** [http://crooksandliars.com/david-neiwert/get-ready-rights-post-election-delig Video Example]
*** Information displayed: title, description, creator, video(embeded), published, tags, share(link), comments

* [http://video.yahoo.com Yahoo Video]
** [http://video.yahoo.com/watch/3786346/10380005 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://www.myspace.com MySpace Videos]
** [http://vids.myspace.com/index.cfm?fuseaction=vids.individual&VideoID=44857402 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://video.aol.com/ AOL Video]
** [http://uncutvideo.aol.com/tags/art-&-animation/adf34e0b55f492d0210491e9c4906362?index=7 Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, views, share(link), comments

* [http://www.heavy.com/ Heavy]
** [http://www.heavy.com/channel/1179 Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.ifilm.com/ iFilm] now [http://www.spike.com/ Spike]
** [http://www.spike.com/video/spider-man-3-trailer/2783985 Video Example]
*** Information displayed: title, description, creator/s, video(embeded), published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.metacafe.com/ Metacafe]
** [http://www.metacafe.com/watch/1932833/universe/ Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments

* [http://www.atomfilms.com/ Atom Films]
** [http://www.atom.com/funny_videos/border_vcast_interview/ Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, tags, views, share(link), comments, contributors

* [http://www.veoh.com/ Veoh]
** [http://www.veoh.com/videos/v16297680ZFN5cMXb Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments, permalink(url)

* [http://grouper.com/ Grouper] now [http://crackle.com/ Crackle]
** [http://crackle.com/c/Quantum_of_Solace/Quantum_Of_Solace/2327783#ml=o%3d12%26fpl%3d297691%26fx%3d Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, views, comments, permalink(url)

* [http://revver.com/ Revver]
** [http://revver.com/video/1281276/beer-goggles-commercial/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, download(enclosure), size, format, rating, share(link), comments, permalink(url)

==== Analysis of Video Sites ====

35 total examples Analysed

* title 100%
* video(embeded) 100%
* published 91.42%
* comments 88.57%
* tags 71.42%
* rating 65.71%
* summary 62.85%
* creator 60%
* share(link) 51.42%
* views 45.71%
* download(enclosure) 42.85%
* duration 31.42%
* permalink(url) 28.57%
* description 25.71%

other discovered elements less than 10%

* video size
* feed url
* preview image
* contributor/s

=== Photos ===
* A few photos online have region annotation and quoting. But as tools are developed that are usable for mass publishers, this will likely increase.
* Many videos have thumbnails that are jpgs, and are effectivly quotes of the video.
* Many videos use pictures and therefore the pictures themselves are quotes from the video.
* Most photos have the same elements as videos and audio, including quotes that are derived from the original photo.

==== Individual Publishing of Photos ====

* [http://blog.bouckenooghe.com/2005/09/01/em6-a-est-fache-avec-le-centimetre/ Blog A Brac » E=m6 a est fâché avec le centimètre - photo with annotated screen-caps]
** This example has a Title, Html URL, media URL, description or summary, creator, quotes and descriptions, tags/categories, and publish date and time. +200 across all individually blogged photos.

* [http://scribbling.net/projects/fotonotesrolloverviewer/fotonotesplugin.php?p=helicopterovernyc.jpg Scribbling.net implementation of Fotonotes Plugin demonstrating the fotonotes annotation tool for photos]
** This example has media url, quotes or "notes" and descriptions, creator. +200 across all individually blogged photos.

* [http://community.livejournal.com/boston_photos/ Boston photos]
** [http://www.bobspixels.com/view_album.php?album=2008/2008_10_31&photo=md_oct_31_2008_121452.jpg Photo Example]
*** Information displayed: title, summary, creator, photo, published, resolution, album

* [http://mute.rigent.com/ Mute]
** [http://mute.rigent.com/index.php?ladat=2008-11-03 Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://www.durhamtownship.com/ Durham township]
** [http://www.durhamtownship.com/blog-archives/002245.html Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://blog.magnumphotos.com/ Magnum Photos]
** [http://blog.magnumphotos.com/2008/11/surfing_the_archive_a_contest.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights

* [http://www.boston.com/bigpicture/ Boston Big picture]
** [http://www.boston.com/bigpicture/2008/11/conflict_in_congo_refugees_on.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights, share

* [http://amysteinphoto.blogspot.com/ Amy Stein Photo]
** [http://amysteinphoto.blogspot.com/2008/11/brand-new-funky-president.html Photo Example]
*** Information displayed: title, description, creator, photo, tag, published, comments, rights, share

* [http://blog.photoblogs.org/ Photoblogs Blog]
** [http://blog.photoblogs.org/2008/10/31/saturday-nights-alright-for-fighting-by-treeswing/ Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments

* [http://www.aminus3.com/ Aminus Photoblogs]
** [http://krikis.aminus3.com/image/2008-11-04.html Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments, rights, exif

* [http://johnsfoto.blogspot.com/ Johns Foto]
** [http://johnsfoto.blogspot.com/2008/11/my-world-drammen-norway.html Photo Example]
*** Information displayed: title, description, creator, photo/s, tag, published, comments, rights

* For more work along the lines of 2d annotations, please see (and add to) [[photo-note-examples]].

==== Service publishing of photos ====

* [http://www.flickr.com/photos/500hats/50282408/ Flickr - Photo Sharing instance of a photo.]
** This example has a Title, Html URL, media URL, description or summary, quotes URLs and descriptions, licence, tags, upload time, playlist (set), license, creator, and other capture data. +millions across all hosters. Many photos are also part of a "set" or "viewlist." So the photo can be considered a quote of the set, or a piece of it. +millions of records.

* [http://www.webshots.com/ Webshots.]
** [http://www.webshots.com/g/32/579-sh/25695.html Photo Example.]
*** Information displayed: title, description, creator, photo, published, tag, comments, download, share, album

* [http://zooomr.com/ Zooomr - Photo sharing site]
** [http://www.zooomr.com/photos/flwrgrl/6168222/ Photo Example.]
*** Information displayed: title, creator, photo, published, tag, comments, download, share, location, rating, exif

* [http://www.deviantart.com Deviant Art]
** [http://littlemewhatever.deviantart.com/art/Autumn-Morning-102650017 Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, views, comments, file-size, resolution, download-count, download

* [http://moblog.co.uk Moblog]
** [http://moblog.net/view/861286/voted-bitches Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share

* [http://www.tabblo.com/studio Tabblo]
** [http://www.tabblo.com/studio/stories/view/1653958/?nextnav=recent Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share, slides

* [http://www.corbis.com Corbis Photograpy]
** [http://pro.corbis.com/popup/Enlargement.aspx?mediauids={59a81f5c-165d-4461-945c-702ecbf19f43} Photo Example]
*** Information displayed: title, summary, creator, photo, tag, file-size, slides, payment, rights, id

* [http://www.istockphoto.com istockphoto]
** [http://www.istockphoto.com/file_closeup.php?id=000004484543 Photo Example]
*** Information displayed: title, summary, creator, photo, tag, views, comments, file-size, resolution, slides, payment, rights, id

* [http://www.sxc.hu Stock.XCHNG]
** [http://www.sxc.hu/photo/478557 Photo Example]
*** Information displayed: title, creator, photo, tag, views, comments, file-size, print-size, resolution, slides, payment, rights, id, download-count, download, exif

* [http://www.photos.com/ Photos.com]
** [http://www.photos.com/en/search/close-up?oid=11525603&hoid=6cb716176348ec2870265408a3ac5d29 Photo Example]
*** Information displayed: title, description, photo, tag, resolution, slides, payment, rights, id

* [http://elfwood.lysator.liu.se/elfwood.pike Elfwood]
** [http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html Photo Example]
*** Information displayed: title, creator, description, photo, tag, comments, rights, technique, share

* [http://www.epilogue.net/cgi/database/art/editors.pl/ Epilogue]
** [http://www.epilogue.net/cgi/database/art/view.pl?id=117980&genre=2 Photo Example]
*** Information displayed: title, creator, description, photo, comments, rights, medium

* [http://ackegard.com/gallery/main.php Ackegard]
** [http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, resolution

* [http://www.caligari.com/Gallery/ImagesGallery/default.asp?Cate=GImages Caligari Images Gallery]
** [http://www.caligari.com/Gallery/ImagesGallery/2008/sep/winner.asp?img=3771&email=harri.pakarinen@gmail.com&name=Harri%20Pakarinen Photo Example]
*** Information displayed: creator, photo, contact

* [http://www.amateurillustrator.com/ Amateur Illustrator]
** [http://www.amateurillustrator.com/articles/?p=1191 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, comments, download, share

* [http://www.cgchannel.com/gallery/ CG channel]
** [http://www.cgchannel.com/gallery/viewimage.jsp?imgID=85 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, vote, rate, views, software

* [http://www.alrioart.com/ Alrioart]
** [http://alrioart.com/details.php?image_id=3246 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, views, file-size

* [http://www.freeart.org/ Freeart]
** [http://www.freeart.org/display.cgi?v=s&i=2 Photo Example]
*** Information displayed: title, creator, description, published, photo, rate, id

* [http://www.dreamstime.com/ Dreamstime]
** [http://www.dreamstime.com/family-image6933295 Photo Example]
*** Information displayed: title, description, creator, photo, tag, views, file-size, print-size, resolution, slides, payment, rights, id, download-count, download

==== Analysis of Photo Sites ====

30 total examples

* photo 100%
* creator 96.66%
* title 93.33%
* description 73.33%
* comments 70%
* tag 63.33%
* rights 43.33%
* resolution(screen) 23.33%
* slides(slide show) 23.33%
* download 20%
* file-size 20%
* views 20%
* file-size 20%
* summary 16.66%
* payment 16.66%
* id 13.33%

Other discovered properties occurring less than 10%

* download-count
* exif(extended information, camera, exposure time, etc)
* album(collection)
* print-size
* location(geo coordinates)
* rating
* technique(Artist style)
* software(Imaging application ie: photoshop)

=== Media comments ===

The following urls are examples of user/visitor comments about media items.

* http://ryanedit.blogspot.com/2006/01/light-water-music-2.html
** Information displayed: author, author-url, comment

* http://prototypen.com/blog/vjblog/archives/001318.html
** Information displayed: author, author-url, comment, published

* http://www.itsjerrytime.com/?p=89
** Information displayed: author, author-url, comment, published

* http://bottomunion.com/blog/?p=469
** Information displayed: author, author-url, comment, published

* http://www.rocketboom.com/rb_07_mar_26/
** Information displayed: author, author-url, comment, published, comments-link

* http://www.chesslodge.com/2007/03/chess-video-lesson-2/
** Information displayed: author, author-url, comment, published

* http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html
** Information displayed: author, author-url, comment, published

* http://blip.tv/file/1425655/
** Information displayed: author, author-url, comment, published

* http://uk.youtube.com/watch?v=KKTDRqQtPO8
** Information displayed: author, author-url, comment, published, reply-url, vote

* http://vimeo.com/162754
** Information displayed: author, author-url, comment, published

* http://www.dailymotion.com/commented-week/lang/en/video/x7a2my_lewis-hamilton-champion-f1-2008_sport
** Information displayed: author, author-url, comment, published

* http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/
** Information displayed: author, author-url, author-photo, comment, published

* http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/
** Information displayed: author, author-url, comment, published, comment-link

* http://freakytrigger.co.uk/ft/2008/11/blondie-call-me/
** Information displayed: author, author-url, comment, published, comment-link

* http://www.scissorkick.com/2008/09/midnight-lab-band/
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html
** Information displayed: author, author-url, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://loki23.blogspot.com/2008/09/flower-electronics.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://videogum.com/archives/the-hunt-for-the-worst-movie-of-all-time/the-hunt-for-the-worst-movie-o-30_032141.html
** Information displayed: author, author-url, author-photo, comment, published, comment-link, vote, reply-url

* http://www.haloscan.com/comments/empirestatehuman/7424868678376349884/
** Information displayed: author, author-url, comment, published, comment-link, reply-link

* http://www.3hive.com/2008/10/1000_robata.php#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://www.musicload.de/album/1884260_2/nik-p--dj-%C3%B6tzi/ein-stern-der-deinen-namen-tr%C3%A4gt/item.html
** Information displayed: author, comment, published, rating

* http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/#comments
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1
** Information displayed: author, comment, published

* http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html#addnewcmt
** Information displayed: author, author-url, comment, published

==== Analysis of Media comments ====

25 examples

* author 100%
* comment 100%
* published 100%
* author-url 92%
* comment-link 40%
* author-photo 16%
* reply-url 12%

Other properties occuring less than 10%

* vote

== Notes on Existing Practices ==

Mary Hodder:
* We are finding at Dabble as we look at millions of user generated media records, that almost all have html and/or media urls, titles, uploader or creator, and at least a default licensing of Copyright. Most have tags whose functionality is made available through the hosting service (the richer the media, the more likely tagging goes toward 100% of the items), thumbnail URL(s), publishing date, and about 25% have quoting information of some sort (quotes of video or audio, and region quotes of photos).
* Tags apparently appear at the upload point on 61% of photos in Flickr, and within a short period, 80+% have tags. 12% of users in Flickr apparently tag photos other than their own.

Manu Sporny (on music):
* There is an increasing number of sites that link to different methods of acquiring content displayed on a web page. These may include links to high-quality, or full versins of the media being described on the page. The various options include: free, streaming with ads, one-time purchase, and rental.
* Summaries, long descriptions and reviews are also prevalent in some of the content.

Manu Sporny (on video):
* We should attempt to support the basic information on sites that have been operational for years such as IMDB and Rotten Tomatoes among others. These sites tend to have very detailed information on all things related to video and TV - other sites will follow their lead because their meta-data seems to be the most complete on the web - thus making every other site contain a sub-set of their meta-data.

== Next Steps ==
# Add more real-world, simple, minimal examples.
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.
# Start [[media-info-brainstorming]] based on examples.

== See Also ==
* [[media-metadata-examples]] - previous attempt to catalog and organize top down metadata systems generated by engineers and committees, as examples of elements, and includes formats which should be in a separate page. Useful as a source of research but this microformat needs to embrace the bottomup ways users are publishing photos, video and audio online.

{{Template:hmedia-related-pages}}

hmedia-issues

2009-07-23T16:29:42Z

WebOrganics: adding template

= hMedia 0.1 issues =

This page defines the current issues with the [[hmedia|hMedia draft specification]]. Any issues that have not yet been resolved are marked with an {{OpenIssue}} tag.
{{TOC-right}}

== Contributors ==

In order of contribution:

* ...

== Issues Template ==

{{issues-format}}

== 2009 issues ==

<div class="vevent">
* {{ClosedIssue}} <span class="summary vcard"><span class="dtstart">2009-01-10</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
*# hMedia should not be marked as a "Draft" for the following reasons:
*## It has not gone through a media-info-proposal stage of the Microformats Process.
*##*Please see: http://microformats.org/wiki/media-info-proposal
*## There has been hardly any discussion regarding the attributes selected for the vocabulary.
*##* Please see: http://microformats.org/wiki/hmedia#History, and http://microformats.org/discuss/mail/microformats-new/2008-November/001866.html
*## It is a bad idea to formalize hMedia until at least hVideo and hImage has been completed.
*##* It is unrealistic a hMedia proposal to Wait until hVideo and hVideo is completed as there has been no Interest or activity in either of those formats
*## Marking hMedia a Draft may confuse new Microformats users into believing that it has as much thought put into it as geo, hAtom or hResume.
*##* There has Please see again: http://microformats.org/wiki/hmedia#History although incomplete at this time documents over three years of discussion.
</div>
</div>

{{Template:hmedia-related-pages}}

Template:hmedia-related-pages

2009-07-23T16:28:56Z

WebOrganics: /* Work in progress */ oops bad copy and paste (lazy!)

== Related Pages ==

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

Template:hmedia-related-pages

2009-07-23T16:27:37Z

WebOrganics: /* Related Pages */ bigger header

== Work in progress ==

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

Template:hmedia-related-pages

2009-07-23T16:26:50Z

WebOrganics: adding title

=== Related Pages ===

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

hmedia

2009-07-23T16:25:32Z

WebOrganics: /* Related pages */ adding template

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' ("[http://en.wikipedia.org/wiki/Hypermedia Hypermedia]") is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

== Implementations ==

* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]])
* There is a web-service that extracts [[hmedia|hMedia]] + [[hatom|hAtom]] as [http://search.yahoo.com/mrss MediaRSS] available at [http://transformr.co.uk Transformr]

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

{{Template:hmedia-related-pages}}

[[Category:Draft Specifications]]

Template:hmedia-related-pages

2009-07-23T16:24:08Z

WebOrganics: creating template for hMedia related pages, saves me doing lots of edits ;)

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

hmedia

2009-07-23T16:08:31Z

WebOrganics: /* Related pages */ updated

<entry-title>hMedia</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}

'''[[hmedia|hMedia]]''' ("[http://en.wikipedia.org/wiki/Hypermedia Hypermedia]") is a simple and open format for publishing Images Video and Audio. hMedia may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. hMedia is one of several open [[microformats|microformat]] standards.

== hMedia Draft Specification 2009-01-04 ==

=== Editor/Author ===

* [[User:WebOrganics| Martin McEvoy]]

=== Contributors ===

In historical order of contribution

* [http://tantek.com/log/ Tantek Çelik]
* [[User:Kevin_Marks|Kevin Marks]]
* [http://napsterization.org/stories/ Mary Hodder]
* [[User:RodBegbie | Rod Begbie]]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisNewell | Chris Newell]]
* [[User:ManuSporny | Manu Sporny]]
* [[User:MikeJohnson | Mike Johnson]]
* [[User:WebOrganics| Martin McEvoy]]

=== Inspiration and Acknowledgements ===

Many thanks to [http://tantek.com/log/ Tantek Çelik], [[User:Kevin_Marks|Kevin Marks]], [http://napsterization.org/stories/ Mary Hodder], [[User:ChrisNewell|Chris Newell]], [[User:ChrisMessina | Chris Messina]], [http://changelog.ca/ Charles Iliya Krempeaux] and [http://blog.digitalbazaar.com Manu Sporny] for their valuable contributions to Media Info and Media Metadata in general.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

== Scope ==

Images, Video and Audio regularly share several common fields. hMedia has been based on a minimal common subset based on the analysis of 225 media related web pages. All fields discovered during analysis occur more than 80% of the time or more across each of the target domains listed on the [[media-info-examples|Media Info Examples]] page. hMedia was developed using the [[process|Microformats Process]] and [[principles|Design Principles]].

== Introduction ==

<cite>[http://napsterization.org/stories/ Mary Hodder] - 22 Jan 2006</cite>
<blockquote>There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described.</blockquote>

== Format ==

=== Abstract ===

hMedia is a single media publishing format that relates to Images, Video and Audio with an Emphasis on Practical, Simple, and Minimal. Wherever possible field names have been chosen from those defined by the [[hcard|hCard]] standard.

=== Schema ===

See [[hmedia#Key|key]].

* hMedia '''hmedia'''{1}.
** '''fn'''. {1}.
** ''contributor'' *. Using text or [[hcard]].
** photo ?. Using the HTML IMG element.
** player ?. Using use any appropriate html element such as OBJECT.
** ''enclosure'' *. A <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]]

{{cheatsheet-key}}

=== Schema Definition ===

{{rfc-2119-intro}}

==== hmedia ====

hMedia is used to describe information associated with Images, Videos and Audio.

====fn====

The name of a media.

* The element is identified by the class name <code>fn</code>.
* hMedia {{must}} include one <code>fn</code> element.

==== contributor ====

A Contributor is any person or organization that takes part in the creation or distribution of the Media

* The element is identified by the class name <code>contributor</code>.
* hMedia {{may}} include one or more contributors.
* The contents of the element {{may}} include a valid [[hcard|hCard]].

==== photo ====

An embedded Image or Photograph of the Media

* The element is identified by the class name <code>photo</code>.
* hMedia {{may}} include one <code>photo</code> element.
* The element {{should}} use an <img> element.
* The <img> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>photo</code>

==== player ====

The contents are an embedded video or movie of the Media such as a Flash Movie.

* The element is identified by the class name <code>player</code>.
* hMedia {{may}} include one <code>player</code> element.
* The element {{may}} use any appropriate html element such as <object>.
* The <object> element attributes <code>height</code> and <code>width</code> {{may}} be used to determine the dimensions of a <code>player</code>

==== enclosure ====

Indicates that the referred <abbr title="uniform resource locator">url</abbr> is a download of the Media.

* The element is identified by a <abbr title="Uniform Resource Locator">URL</abbr> using the [[rel-design-pattern]], the rel attribute {{should}} contain the value of <code>enclosure</code>..
* hMedia {{may}} include one or more <code>enclosure</code>'s.
* The media type of the enclosure {{should}} be specified by using a <code>type</code> specifier for a <abbr title="uniform resource locator">url</abbr>, the contents {{may}} be any [http://www.iana.org/assignments/media-types/ iana assigned media type] .
* Multiple enclosure elements {{should}} be used for different representations of the same Audio, video or Image.

=== XMDP Profile ===

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hmedia</dt>
<dd>
Used to describe semantic information associated with Images, Videos and Audio.
</dd>
<dt>fn</dt>
<dd>
The name of a media
</dd>
<dt>contributor</dt>
<dd>
A Contributor is any person or organization that takes part in the creation or distribution of the Media
</dd>
<dt>photo</dt>
<dd>
An embedded Image or Photograph of the Media.
</dd>
<dt>player</dt>
<dd>
An embedded video or movie of the Media.
</dd>
<dt>enclosure</dt>
<dd>
Indicates that the referred url is a download of the Media.
</dd>
</dl>
</dd>
</dl>
</pre>

== Modularity ==

Although media items are sometimes presented on their own they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the hMedia microformat as a child (or in some cases a parent) of these microformats.

=== Media Distribution and Syndication ===

* [[hatom|hAtom]]

Podcast and <abbr title="Video Podcast">Vidcast</abbr> feeds reference a sequence of media items. hMedia can therefore be used as a child element of hAtom.

Please see: [[hmedia#hAtom_and_hMedia|hAtom+hMedia example]].

=== Media Events ===

* [[hcalendar|hCalendar]]

hMedia may used to describe a continuous media stream for example a TV channel. An event or a schedule of events on the channel can be signaled using [[hcalendar#Root_Class_Name|vevent]] as child elements. A combination of hMedia and hCalendar may provide what is necessary to capture a specific event, the media stream information and the timing information.

Please see: [[hmedia#hCalendar_and_hMedia|hCalendar and hMedia]].

=== Media Reviews ===

* [[hreview|hReview]]

A Review about Audio, Video or Images often occurs in media publishing, hMedia reviews can often be published using hReview, capturing the reviewer, the reviewed item, a rating, a description, and the Date of a media review. hMedia may therefore be published as a child element of a [[hreview#Schema|hReview item]]

Please see: [[hmedia#hReview_and_hMedia|hReview and hMedia]].

== Examples ==

Using Real world Examples found on the [[media-info-examples]] page

=== Images ===

<pre>
<div class="hmedia">
<a rel="enclosure" type="image/jpeg" href="http://www.treeswing.net/index.php?showimage=355">
<img class="photo" alt="Saturday Nights alright for fighting, by treeswing"
src="http://cache1.photoblogs.org/thumbnail/?hash=9bece0678c5610bd4b631d9037286df7&size=450"/>
</a>
<span class="fn">Saturday Night's Alright For Fighting</span>,
<em>by <span class="contributor vcard">
<a class="url fn" href="http://www.treeswing.net/">Treeswing</a>
(<a class="url" href="http://www.photoblogs.org/profile/treeswing.net/">profile</a>)
</span></em>
</div>
</pre>

=== Video ===

<pre>
<div class="hmedia">
<span class="fn">Introduction to the Open Media Web</span>
<object class="player" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<ul>
<li><a rel="enclosure" type="video/mp4" title="Download the original source file for this movie"
href="/explore/factoryjoe/videos/2.m4v">Original</a></li>
</ul>
</div>
</pre>

=== Audio ===

<pre>
<span class="hmedia">
<a rel="enclosure" type="audio/mpeg" href="http://homepage.mac.com/mr.gilbert/.Music/earle_waydownhole.mp3">
<span class="contributor vcard">
<span class="fn">Steve Earle</span>
</span> -
<span class="fn">"Way Down in the Hole" (Tom Waits cover)</span>
</a>
</span>
</pre>

=== Combined ===

==== hAtom and hMedia ====
<pre><div id="example" class="hentry hmedia">
<h2 class="entry-title"><a class="fn" href="#example" rel="bookmark">Introduction to the Open Media Web</a></h2>
<p>by <cite class="author vcard"><span class="fn">Author</span></cite> on:
<abbr class="updated" title="2008-12-14T11:08:00+01:00">14th Dec, 2008</abbr></p>
<div class="entry-content"><p>The introductory video describing the Open Media Web project and where it's -- roughly -- going!</p></div>
<object class="player" width="545" height="451" type="application/x-shockwave-flash" data="http://www.viddler.com/player/1d6265f3/">
<param name="movie" value="http://www.viddler.com/player/1d6265f3/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
<p>Download: <a rel="enclosure" type="video/mp4;length=18454938" href="http://www.viddler.com/explore/factoryjoe/videos/2.m4v">
Original</a>
</p>
</div></pre>

==== hCalendar and hMedia ====
<pre><div class="hmedia">
<div id="bip-play-emp">
<object class="player" height="395" width="640"
data="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog&domId=bip-play-emp
&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"
name="bbc_emp_embed_bip-play-emp"
id="bbc_emp_embed_bip-play-emp"
type="application/x-shockwave-flash">
<param name="movie" value="http://www.bbc.co.uk/emp/9player.swf?revision=7276&embedPageUrl=
http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor/#anchor-info-dialog
&domId=bip-play-emp&config=http://www.bbc.co.uk/emp/iplayer/config.xml
&playlist=http://www.bbc.co.uk/iplayer/playlist/b00gd1mr
&guidance=unset"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
<param name="wmode" value="default"/>
<param name="quality" value="high"/>
</object>
</div>
<div class="vevent">
<span class="summary">
<a class="url fn" href="http://www.bbc.co.uk/iplayer/episode/b00gd1mr/Doctor_Who_The_Next_Doctor">
Doctor Who: The Next Doctor
</a>
</span>,
Broadcast on: <span class="location">BBC One</span>,
<abbr class="dtstart" title="2008-12-25T18:10:00+01:00">6:00pm Thursday 25th December</abbr>,
Duration:
<abbr class="duration" title="PT60M">60</abbr> minutes,
Available until:
<abbr class="dtend" title="2009-01-08T15:49:00+01:00">3:49pm Thursday 8th January</abbr>
</div>
</div></pre>

==== hReview and hMedia ====
<pre><div class="hreview">
Reviewed by: <span class="reviewer vcard">
<span class="fn">anonymous</span>,
</span>
On: <abbr class="dtreviewed" title="2009-01-03">January 3rd, 2009</abbr>.
<div class="item hmedia">
<p><a class="url fn" rel="enclosure" href="http://mediaweb.musicradio.com/mp3/Mis-takes.mp3" type="audio/mpeg">Mis-takes</a>
by: <span class="contributor vcard">
<span class="fn">The Charlatans</span>
</span></p>
</div>
<div>Rating: <abbr class="rating" title="4">****</abbr> out of 5 stars</div>
<div class="description">
<p>This is a great track from The Charlatans latest album You Cross My Path, well worth a listen.</p>
</div>
</div></pre>

== Implementations ==

* The [http://weborganics.co.uk/hCast/ Hypermedia Podcast] uses [[hmedia|hMedia]] + [[hatom|hAtom]] to generate a [http://search.yahoo.com/mrss MediaRSS] feed ([[hmedia#hAtom_and_hMedia|as demonstrated above]])
* There is a web-service that extracts [[hmedia|hMedia]] + [[hatom|hAtom]] as [http://search.yahoo.com/mrss MediaRSS] available at [http://transformr.co.uk Transformr]

== History ==
* Dougal Campbell first talks about [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000229.html microformats for various types of media?] on Jul 13th 2005

* Thu Sep 1st 2005, a discussion about a Playlist Microformat by Lucas Gonze, [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000835.html hPlaylist]

* Tantek Çelik starts Initial exploration about a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000843.html media-info microformat] on Sep 3rd 2005

* Joshua Kinberg discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-September/000992.html media/enclosure microformat] on Sep 20th 2005

* On November 2nd 2005 Chris Messina discusses [http://microformats.org/discuss/mail/microformats-discuss/2005-November/001833.html a microformat for audio track metadata].

* On December 6th 2005 Charles Iliya Krempeaux discusses a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002292.html TV show microformat].

* On Jan 1st 2006 Tantek Çelik calls for a simple media microformat which describes the 80/20 of information about a particular piece of media and nothing more. see: [http://microformats.org/discuss/mail/microformats-discuss/2006-January/002551.html]

* March 24th 2006 Rod Begbie [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003383.html Proposed a Music microformat].

* Enric discusses a [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004419.html media file example of hAtom] on Jun 13th 2006

* Steve Williams (Digg) discusses [http://microformats.org/discuss/mail/microformats-discuss/2006-August/005139.html Media Metadata, Specifically Video Thumbnails] on Aug 16th 2006

* First [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008626.html hMedia microformat] Propsal by Chris Newell on Feb 8th 2007

* More interest in a [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008848.html music/media-info microformat] by Marian Steinbach on Feb 26th 2007 and later on [http://microformats.org/discuss/mail/microformats-new/2007-March/000028.html Microformats New]

* Martin McEvoy Renews interest in a [http://microformats.org/discuss/mail/microformats-new/2008-November/001861.html Media Microformat] on Nov 9th 2008

* hMedia 0.1 Draft Specification 2009-01-04

== References ==

=== Normative References ===

* [[hcard]]
* [[rel-design-pattern]]
* [[rel-enclosure]]

=== Informative References ===

* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.2 HTML4 Image element]
* [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3 HTML4 Object element]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML4 rel Definition]
* [http://www.alistapart.com/articles/byebyeembed/ Article on why you should not use embed] from A List Apart.

== Similar Work ==

* [[media-chapters|Media Chapters]]
* [[haudio|hAudio]]
* [[video-info-examples|Video Info]]
* [[photo-note-examples|Photo Notes]]

== Work in progress ==

=== Brainstorming ===

Do you want to help develop the next version of [[hmedia|hMedia]]? Please add your thoughts and insight on the [[hmedia-brainstorming]] page.

=== Discussions ===

* Please forward questions and ideas to the [http://microformats.org/mailman/listinfo/microformats-new Microformats New] mailing list.

=== Issues ===

Please see: [[hmedia-issues]]

==Related pages==

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

[[Category:Draft Specifications]]

media-info-formats

2009-07-23T16:07:11Z

WebOrganics: /* Related pages */ updated

media-info-examples

2009-07-23T16:06:45Z

WebOrganics: /* Related pages */ updating

hmedia-issues

2009-07-23T16:06:07Z

WebOrganics: adding related pages

media-info-brainstorming

2009-07-23T16:05:08Z

WebOrganics: adding related pages

media-info-formats

2009-07-23T16:03:41Z

WebOrganics: adding related pages

media-info-examples

2009-07-23T16:02:23Z

WebOrganics: adding related pages

hatom-issues

2009-07-18T17:44:12Z

WebOrganics: /* entry-title optionality */ accepting only "should" not be an empty string

<entry-title> hAtom issues </entry-title>
These are externally raised issues about [[hAtom]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hatom-faq|hAtom FAQ]] and the [[hatom-issues-resolved|hAtom resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

== closed issues ==
See: [[hatom-issues-closed]]

== resolved issues ==
See: [[hatom-issues-resolved]]

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2009===
==== too many required hentry properties ====
* {{OpenIssue}} 2009-05-26 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 requires numerous properties for an hentry (often based directly on required elements from the Atom standard). Given the broad variety of situations that hAtom is used in content, many (or even most) of these properties are not already specified in such content, and thus it is poor methodology to require them because there is a good chance (experience has shown) either (a) the content author will ignore the requirement, or (b) will make something up to satisfy the requirement. A few similar/overlapping/sub-issues are noted below (e.g. [[#Author|author is required]], and not always available).
*#* Proposed resolution. Make nearly all hentry properties "optional" in hAtom 0.2. Consider keeping at most only one required property, perhaps "updated" - that is, if there is no date of update/publication in the content you are trying to mark up, then perhaps it doesn't make sense to mark up that content with hAtom, since hAtom is for episodic, time-based/stamped content.
*#** consider pattern abstraction: all microformats should minimize "required" properties for the same reason, and perhaps ''only'' require at most a single property which is indicative of what that microformat is for, that is, if the author does not publish that one required property, then perhaps they should not be using the microformat that requires that one property.
*#* I have the same problem. I'm collecting various feeds to analyse them. The sources are often RSS 0.9, but I want to put the results into an Atom feed. --[[User:Simon Brodtmann|Simon Brodtmann]] 00:51, 1 July 2009 (UTC)
*#** entry:author should be optional and could be either a hCard or a string
*#** entry lacks a [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.category category] and it shuld either use rel-tag or just be a string
* 2009-07-18 [[User:DavidJanes]] I would like to break this into a separate issue for each currently required element, as we're likely to have to define defaulting rules

==== entry-title optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]] but not recommended.
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model value should be
*** the empty string
**** +1 [[User:DavidJanes]]
**** -1 [[User:WebOrganics|Martin McEvoy]]
*** the value should not be blank.
**** +1 [[User:WebOrganics|Martin McEvoy]] see: [http://www.atomenabled.org/developers/syndication/#requiredEntryElements Required Entry Elements] from Atom Enabled.
**** [[User:DavidJanes]] what should it be then, if physically representing it is optional? Since Atom makes this a SHOULD and not a MUST (I'm not shouting, just following RFC convention), and we're assuming there's a good reason for the entry-title not to be present in the first place, why not an empty string?
***** [[User:WebOrganics|Martin McEvoy]] entry:title is a required attribute of atom at both feed and entry level, in both instances it says "Contains a human readable title" (a requirement) an empty string is not anything human readable (personal oppinion), maybe hAtom 0.2 should only recommend that the value of entry-title "should" not be an empty string.
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]]

==== updated optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] ... the demand for optionality of the issue is high (cf the microsoft web clips) and if it remains required we're just going to reinvent hAtom without this element
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** the page creation date
**** +1 [[User:DavidJanes]]
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

==== author optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] for the same reason 'updated' should be optional: we'll just reinvent hAtom slightly differently otherwise
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** "anonymous" (somewhat like [[hreview]]), except not explicit
**** +0.5 [[User:DavidJanes]]
*** make this implementation defined
*** something constructed from the page's URL & other information
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

=== 2008 ===
==== add url property to hentry ====
* {{OpenIssue}} 2008-09-10 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 uses [[rel-bookmark]] for permalinks. Permalinks may not always be hyperlinks or hyperlinkable. Thus I propose we re-use the <code>url</code> property (from [[hCard]], [[hCalendar]], [[hReview]], etc.) as a sub-property of the <code>hentry</code> property/container/root.
*#* Proposed resolution. Add "url" sub-property to "hentry" in hAtom 0.2.
*# {{ToDo}} can anyone provide examples where this would be used? [[User:DavidJanes]]

==== misuse of address element ====
* {{OpenIssue}} 2008-06-07 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 says "an Entry Author element SHOULD be encoded in an <code><address></code> element" and "find the Nearest In Parent <code><address></code> element(s) with class name author and that is/are a valid hCard" - this is a misuse of the address element. The address element means the ''contact'' for the page or major portion thereof (see [[hcard-faq#Should_I_use_ADDRESS_for_hCards|hCard FAQ: Should I use ADDRESS for hCards]]), which ''may'' also be the ''author'' but is not necessarily. See [[hcards-and-pages]] for more details on this semantic distinction.
*#* Proposed resolution: Eliminate all requirements and recommended use of the <code><address></code> element from hAtom.
*#** +1 --[[User:Csarven|Sarven Capadisli]] 11:57, 11 Nov 2008 (PST)
*#** +1 [[User:DavidJanes]]
*# include in hAtom 0.2
*#* +1 [[User:DavidJanes]]

=== 2007 ===
==== marking up comments ====
* {{OpenIssue}} 2007-11-25 raised by [http://www.wirewd.com/ Ken Wronkiewicz].
*# There's no currently defined way to exactly handle threaded discussions. I think this is quite useful to have.
*#* The prior art is RFC [http://tools.ietf.org/html/rfc4685 4864]. The microformat solution should map fairly cleanly to this.
*# include in hAtom 0.2
*#* -1 [[User:DavidJanes]] I think hAtom Comments should be a separate spec

==== atom:category scheme ====
* {{OpenIssue}} 2007-06-01 raised by [http://theryanking.com/ Ryan King].
*# ''[[rel-tag#Tag_Spaces|rel-tag tagspaces]] should map to atom:category schemes''
*#* hAtom already defines how to map term and label. It seems that the tagspace can easily map to scheme
*# {{ToDo}} can we get a real-world example mapping of this? [[User:DavidJanes]]

=== 2006 ===
====Geo====
* {{OpenIssue}} 2006-02-03 raised by [[BrianSuda]]
** We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
** +1 [[User:DavidJanes]] - this is just making explicit a particular composition. is it not? Also: if there's a geo in a hfeed (outside of hentry), should it be considered to apply to all entries?
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

==== Relationship of rel-bookmark to url+uid ====
The concept of permalink is available in hCard and hCalendar as the classes url and uid. This combination matches the permalink semantics by indicating that the url should be derefenced to find a more dynamic or up-to-date version of the content, and that that url is a stable unique id that can be used to identify the content.

hAtom 0.1 uses rel-bookmark for the permalink concept. The current state of [[uid-brainstorming]] indicates that the hCard and hCalendar permalink concept is likely to be used in subsequent microformats. It may be important to reconcile hAtom with that trajectory. Possible reconcilliations include:

1) To leave things as they are. The two permalink concepts are to be kept separate.

2) Treat the two concepts as equivalent. Allow both in hAtom, and consider allowing both in other formats. eg <a rel="bookmark" href="http://example.com/"> would fill out uid and url values if they are not supplied explicitly.

3) Choose one over the other for hAtom and perhaps for future microformats also. "url uid" allows for some greater freedom (uid can be pointed at a non-url uid), but it is unclear at this stage whether that freedom is warranted or advisable to permit.

==== Datetime format (atom:<i>updated</i> and atom:<i>published</i>) ====
* 2006-05-23 raised by [[User:RobertBachmann|Robert Bachmann]]
** Atom requires the use RFC3339 datetimes, while hAtom 0.1 does not specify which datetime formats may be used.
*** ACCEPTED FAQ - hAtom references datetime-design-pattern, which discusses which date format to use

==== Feed <i>id</i> (atom:<i>id</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
*# atom:<i>id</i> is required for atom:feed. Thus it should be available in hAtom to.

It is suggested the Feed permalink should be used as the feed ID, however a piece by Mark Pilgrim (http://diveintomark.org/archives/2004/05/28/howto-atom-id) makes arguments against using permalinks and in favour of Tag URIs.

==== Feed <i>permalink</i> (atom:<i>permalink</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]</small>
** I'm proposing the following rules:
**# a Feed Permalink element is identified by [[rel-bookmark]] at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed <del>SHOULD</del><ins>MAY</ins> have a Feed Permalink
**# a Feed Permalink element represents the concept of an Atom link in a feed.
**# if the Feed Permalink is missing, use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI
** 2006-04-03 [[User:ChrisCasciano|ChrisCasciano]] - I'm not sure that having a rel-boomkark-able link element at the feed level / to designate a feed in an html page separate for the other content is anything close to normal usage on the web, so I'd be very hesitant on suggesting this element "SHOULD" exist. I'm also curious when this element would link to anything but the current page (or some element on the current page) for this to be useful in the context of the HTML doc. I think taking the "id" on the feed is a more workable solution in most cases.
** 2006-04-03 [[User:RobertBachmann|Robert Bachmann]]: I've replaced "SHOULD" with "MAY".
** 2006-04-24 [[User:RobertBachmann|Robert Bachmann]]: Maybe we could simplify my proposal to:
*** "''Use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI''"
*** IMO this would be good enough for at least 80% of the cases.
** 2006-04-12 [[User:DavidJanes]]: can we find an example of this in the wild and if so we should add it to the -examples page.
** [[User:Singpolyma|singpolyma]] 00:05, 13 Apr 2006 (PDT) : since the link is going to be pointing to the home page for the item wouldn't [[rel-home]] make more sense? That's what I'm using in the XOXO Blog Format and my reasoning was that if hAtom ever defined this rel=home made the most sense for what you would add, because the feed's link is not to a part of the site by to the home of the site.

==== Feed <i>updated</i> (atom:<i>updated</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>updated</i> is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# The Feed Updated element is identified by the class name <code>updated</code> at the feed level (inside a Feed element but not inside an Entry element)
**# If no element with the class name <code>updated</code> is present, use the youngest <code>updated</code> from the feed's entries.
** 2006-04-12 [[User:DavidJanes]] I like this. And the definition of "feed level"
** 2007-06-20 [[User:MikeKaply]] The "youngest" thing is a really bad idea. If a page has 100 hAtom entries, a parser would have to go through all 100 looking for a low date. That's crazy.
*** 2008-03-20 [[User:TobyInk]] Not crazy at all. I've just implemented an hAtom to Atom converter and I do precisely this. Most (useful) hAtom parsers will "go through all 100 entries" anyway, won't they? So why not look for the youngest updated date as part of that loop. The only slight annoyance is that in RFC 4287, the <atom:updated> element must occur before the first <atom:entry> element -- this is easily solved by inserting a placeholder <atom:updated> element, looping through the entries and then going back and filling in the date. This is really, really, '''not''' a difficult thing to implement.

==== Feed <i>title</i> (atom:<i>title</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>title</i> is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# a Feed Title element is identified by the class name <code><del>entry</del><ins>feed</ins>-title</code>
**# a Feed SHOULD have an Feed Title
**# a Feed Title element represents the concept of an Atom feed title
**# if the Feed Title is missing, use
**#* <del>the first <code><h#></code> element in the Feed, or</del>
**#* the <code><title></code> of the page, or
**#* assume it is the empty string
** 2006-04-01 [[User:ChrisCasciano|ChrisCasciano]] - I think that the fall back to using the first h# on the page is dangerous.. depending on the pge it may be something that changes often (first h# is a post title) or is otherwise ambiguous. I would think using <code><title></code> before h# would be prefered if not the most common desire of the page author.
** 2006-04-05 [[User:RobertBachmann|Robert Bachmann]]: Okay. Deleted "the first <code><h#></code> element in the Feed, or"
** 2006-04-12 [[User:DavidJanes]] Note also in support of this decision that many blogs use <code><h#></code> to encode the date for a group of postings
** 2006-04-12 [[User:DavidJanes]]: why <code>entry-title</code> for the feed title. Why not <code>fn</code> or <code>feed-title</code>?
** 2006-04-12 [[User:RobertBachmann|Robert Bachmann]]: Sorry, this was a "copy & paste" mistake. Fixed now.
** 2007-02-26 [[User:MikeKaply|Mike Kaply]]: I think a feed title should be mandatory if an hfeed is present. If you have multiple feeds on a page, there is no way in a user interface to distinguish between different feeds.

==== Feed <i>author</i> and Entry author (atom:<i>author</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules for Feed author:
**# a Feed Author element is represented by class name <code>author</code> at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed Author element represents the concept of a Atom author
**# a Feed Author element MUST be encoded in a [[hcard|hCard]]
**# a Feed Author element SHOULD be encoded in a <code><address></code> element
**# a Feed MAY have more than one Feed Author elements
**# if the Feed Author is missing
**#* find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
**#* otherwise <del>the Feed is invalid hAtom</del> <ins>there is no Feed Author</ins>
** I'm proposing the following rules for entry author:
**# an Entry Author element is represented by class name <code>author</code>
**# an Entry Author element represents the concept of an Atom author
**# an Entry Author element MUST be encoded in an [[hcard|hCard]]
**# an Entry Author element SHOULD be encoded in an <code><address></code> element
**#<del> If a Feed has no Feed author each Entry MUST have at least one Entry Author element</del>
**# <ins>If an Entry is enclosed by a Feed and this Feed has no Feed author, each Entry MUST have at least one Entry Author element. If an Entry is not enclosed by a Feed and has no Entry Author:
**#* find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
**#* otherwise the Entry is invalid hAtom</ins>
**# an Entry MAY have more than one Entry Author elements
** [[User:Singpolyma|singpolyma]] 00:11, 13 Apr 2006 (PDT) : feed should not be invalid hAtom if feed-level has no author -- it should be invalid if feed-level has no author AND one or more entries have no author. Also, one or more entries may be missing an author IF feed-level has an author.
** 2006-04-17 [[User:RobertBachmann|Robert Bachmann]]: I replaced "the Feed is invalid hAtom" with "there is no Feed Author"

==== Entry <i>id</i> (atom:<i>id</i>) ====
* {{OpenIssue}}2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>id</i> is required for atom:entry. Thus it should be available in hAtom to. The Entry permalink should be used as the entry id.
** --[[User:Federico|Federico]] 19:52, 25 Apr 2006 (PDT): I would add "Only if the id attribute is not defined for the element that contains the entry". The id attribute can be a tag uri. If you use always use the Entry permalink as the entry id and the Atom feed uses tag uris, you would end with two different ids for the same entry.
** 2006-12-31 response by [[User:ComputerKid|Emanla Eraton]] No, it shouldn't be a permalink. It should be a "tag:" id for entries.
** 2007-06-06 [[RyanKing]] - the syntax of tag URIs and html id attributes are incompatible. HTML disallows forward-slash (/) in ids [http://www.w3.org/TR/html401/types.html#type-name], while tag URIs require them [http://www.faqs.org/rfcs/rfc4151.html].

==== Author ====
===== author as an hcard is too much to require =====
The following 3 items were extracted from the conversation starting on irc with [http://rbach.priv.at/Microformats-IRC/2006-03-24#T152248 logs available starting around here]

* [[User:Fil|Fil]] If, for example, you are programming an "aggregator" of news syndicated from many sources like in [http://sedna.spip.org/sedna/ Sedna], chances are that you don't control what "authors" look like; they can be nicely microformated (if coming from an mf-enabled system), but most probably they will be internally represented by a string that contains, in some random order, a name, and/or an email, and so on. If you want to pass on this information in an hAtom feed, you can't possibly reformat it to an hCard. But you still want to pass it on in a <div class="author"> element.
** [[Tantek]] I don't believe the "can't possibly" statement. Please provide a URL to a concrete example that you think you can't possibly reformat into an hCard so we can all take a look.
** [[User:ChrisCasciano|ChrisCasciano]] details of Fil's extraction [http://rbach.priv.at/Microformats-IRC/2006-03-24#T153453 in irc logs] including sting data passed to his app in the form of "Béatrice XXXXXXX beatrice.xxxxxx@@zzzzzzzzz.com"
** [[User:Fil|Fil]] the example url was given up there (Sedna); note that the author information comes from syndication links; nobody is going to edit them to outline what is the name, what is the email and so on, as everything is flowing through automatically... so here the "author" data is dirty, and will not be cleaned into an hCard. We can force it to be in an hCard but it will be meaningless if the source (original data) wasn't built on an mf-enabled software.

* [[pnhChris]] i don't disagree.. the field often comes from places too dumb to follow these rules well; even cases like wordpress that allow users to present their name 1 of 6 or 8 difference ways (from username to LF, FN) .. its not just writing a template to output as hatom at that point... you have to go further upstream where the string to be displayed is chosen .. I also think its pointless to have 10 vcards on the same page whose only data is a generic name like "Chris"
** [[Tantek]] 10 vcards that are the same is pointless yes, but identifying who the author of 10 posts are is not pointless - that's the difference.
** [[User:ChrisCasciano|ChrisCasciano]] Agreed, but I still have concerns that "author" in hAtom does not always make for good hCards, though the situations where it does is optimal. My comments in the conversation were old comments I've made before over concerns and hardships or the lack of desire to make crappy data more portable, in neither of these cases do I think my two comments alone provide reasons to make change from the hAtom 0.1 spec
***[[User:Phae|Frances]] - Just thought I'd mention a scenario I have where the author of an entry does make a pretty useless vCard - the author in each case is an entire team ("creative team", "technical department") etc., rather than a specific, identifiable, person. Some use may be regained when URL to specific team/information is included, in this circumstance.
****[[User:TobyInk]] - A vCard (thus an hCard) does not have to represent a person -- it could represent an organisation, or a department or team.
* [[User:Fil|Fil]] for the moment, to comply losely with hAtom 0.1, I will use <code><nowiki><span class="author"><span class="vcard"><span class="fn">My Name</span></span></span></nowiki></code> ; but it's not good
** [[Tantek]] You can actually simplify that (one fewer span) with: <code><nowiki><span class="author vcard"><span class="fn">My Name</span></span></nowiki></code>

==== Entry <i>source</i> (atom:<i>source</i>) ====
* raised by [[User:Kevin Marks|Kevin Marks]]

When defining hAtom 0.1, atom:source was omitted. We should consider adding this back in as a useful element for providing citations of composite feeds.

== Other Questions and Issues ==
General comments, modeling issues, algorithm issues, should have issues, etc. go here.

=== Entry Updated Required? -- Blogger Issue ===
moved to [[hatom-brainstorming]]

=== 'MAY have multiple Feed elements' -- details and viability of multiple feeds ===
moved to [[hatom-brainstorming]]

== pre 0.1 issues ==
'''This section is more or less closed, as hAtom 0.1 is out the door. If there are open issues that you are championing that didn't make it into hAtom 0.1, move them up above to the hAtom 0.2 section'''

See: [[hatom-issues-pre-0.1]]

== Template ==
{{issues-format}}

== See Also ==
* [[hatom|hAtom]] - the draft proposal
* [[hatom-faq]] - knowledge base
* [[hatom-issues-resolved]]
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[mfo-examples]]
* [[naming-principles]]

hatom-issues

2009-07-18T14:58:09Z

WebOrganics: /* entry-title optionality */ adding votes and the value should not be blank.

<entry-title> hAtom issues </entry-title>
These are externally raised issues about [[hAtom]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hatom-faq|hAtom FAQ]] and the [[hatom-issues-resolved|hAtom resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

== closed issues ==
See: [[hatom-issues-closed]]

== resolved issues ==
See: [[hatom-issues-resolved]]

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2009===
==== too many required hentry properties ====
* {{OpenIssue}} 2009-05-26 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 requires numerous properties for an hentry (often based directly on required elements from the Atom standard). Given the broad variety of situations that hAtom is used in content, many (or even most) of these properties are not already specified in such content, and thus it is poor methodology to require them because there is a good chance (experience has shown) either (a) the content author will ignore the requirement, or (b) will make something up to satisfy the requirement. A few similar/overlapping/sub-issues are noted below (e.g. [[#Author|author is required]], and not always available).
*#* Proposed resolution. Make nearly all hentry properties "optional" in hAtom 0.2. Consider keeping at most only one required property, perhaps "updated" - that is, if there is no date of update/publication in the content you are trying to mark up, then perhaps it doesn't make sense to mark up that content with hAtom, since hAtom is for episodic, time-based/stamped content.
*#** consider pattern abstraction: all microformats should minimize "required" properties for the same reason, and perhaps ''only'' require at most a single property which is indicative of what that microformat is for, that is, if the author does not publish that one required property, then perhaps they should not be using the microformat that requires that one property.
*#* I have the same problem. I'm collecting various feeds to analyse them. The sources are often RSS 0.9, but I want to put the results into an Atom feed. --[[User:Simon Brodtmann|Simon Brodtmann]] 00:51, 1 July 2009 (UTC)
*#** entry:author should be optional and could be either a hCard or a string
*#** entry lacks a [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.category category] and it shuld either use rel-tag or just be a string
* 2009-07-18 [[User:DavidJanes]] I would like to break this into a separate issue for each currently required element, as we're likely to have to define defaulting rules

==== entry-title optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]]
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model value should be
*** the empty string
**** +1 [[User:DavidJanes]]
**** -1 [[User:WebOrganics|Martin McEvoy]]
*** the value should not be blank.
**** +1 [[User:WebOrganics|Martin McEvoy]] see: [http://www.atomenabled.org/developers/syndication/#requiredEntryElements Required Entry Elements] from Atom Enabled.
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]]

==== updated optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] ... the demand for optionality of the issue is high (cf the microsoft web clips) and if it remains required we're just going to reinvent hAtom without this element
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** the page creation date
**** +1 [[User:DavidJanes]]
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

==== author optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] for the same reason 'updated' should be optional: we'll just reinvent hAtom slightly differently otherwise
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** "anonymous" (somewhat like [[hreview]]), except not explicit
**** +0.5 [[User:DavidJanes]]
*** make this implementation defined
*** something constructed from the page's URL & other information
*** ... your proposal here, your vote in a sublist ...
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

=== 2008 ===
==== add url property to hentry ====
* {{OpenIssue}} 2008-09-10 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 uses [[rel-bookmark]] for permalinks. Permalinks may not always be hyperlinks or hyperlinkable. Thus I propose we re-use the <code>url</code> property (from [[hCard]], [[hCalendar]], [[hReview]], etc.) as a sub-property of the <code>hentry</code> property/container/root.
*#* Proposed resolution. Add "url" sub-property to "hentry" in hAtom 0.2.
*# {{ToDo}} can anyone provide examples where this would be used? [[User:DavidJanes]]

==== misuse of address element ====
* {{OpenIssue}} 2008-06-07 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 says "an Entry Author element SHOULD be encoded in an <code><address></code> element" and "find the Nearest In Parent <code><address></code> element(s) with class name author and that is/are a valid hCard" - this is a misuse of the address element. The address element means the ''contact'' for the page or major portion thereof (see [[hcard-faq#Should_I_use_ADDRESS_for_hCards|hCard FAQ: Should I use ADDRESS for hCards]]), which ''may'' also be the ''author'' but is not necessarily. See [[hcards-and-pages]] for more details on this semantic distinction.
*#* Proposed resolution: Eliminate all requirements and recommended use of the <code><address></code> element from hAtom.
*#** +1 --[[User:Csarven|Sarven Capadisli]] 11:57, 11 Nov 2008 (PST)
*#** +1 [[User:DavidJanes]]
*# include in hAtom 0.2
*#* +1 [[User:DavidJanes]]

=== 2007 ===
==== marking up comments ====
* {{OpenIssue}} 2007-11-25 raised by [http://www.wirewd.com/ Ken Wronkiewicz].
*# There's no currently defined way to exactly handle threaded discussions. I think this is quite useful to have.
*#* The prior art is RFC [http://tools.ietf.org/html/rfc4685 4864]. The microformat solution should map fairly cleanly to this.
*# include in hAtom 0.2
*#* -1 [[User:DavidJanes]] I think hAtom Comments should be a separate spec

==== atom:category scheme ====
* {{OpenIssue}} 2007-06-01 raised by [http://theryanking.com/ Ryan King].
*# ''[[rel-tag#Tag_Spaces|rel-tag tagspaces]] should map to atom:category schemes''
*#* hAtom already defines how to map term and label. It seems that the tagspace can easily map to scheme
*# {{ToDo}} can we get a real-world example mapping of this? [[User:DavidJanes]]

=== 2006 ===
====Geo====
* {{OpenIssue}} 2006-02-03 raised by [[BrianSuda]]
** We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
** +1 [[User:DavidJanes]] - this is just making explicit a particular composition. is it not? Also: if there's a geo in a hfeed (outside of hentry), should it be considered to apply to all entries?
** include in hAtom 0.2
*** +1 [[User:DavidJanes]]

==== Relationship of rel-bookmark to url+uid ====
The concept of permalink is available in hCard and hCalendar as the classes url and uid. This combination matches the permalink semantics by indicating that the url should be derefenced to find a more dynamic or up-to-date version of the content, and that that url is a stable unique id that can be used to identify the content.

hAtom 0.1 uses rel-bookmark for the permalink concept. The current state of [[uid-brainstorming]] indicates that the hCard and hCalendar permalink concept is likely to be used in subsequent microformats. It may be important to reconcile hAtom with that trajectory. Possible reconcilliations include:

1) To leave things as they are. The two permalink concepts are to be kept separate.

2) Treat the two concepts as equivalent. Allow both in hAtom, and consider allowing both in other formats. eg <a rel="bookmark" href="http://example.com/"> would fill out uid and url values if they are not supplied explicitly.

3) Choose one over the other for hAtom and perhaps for future microformats also. "url uid" allows for some greater freedom (uid can be pointed at a non-url uid), but it is unclear at this stage whether that freedom is warranted or advisable to permit.

==== Datetime format (atom:<i>updated</i> and atom:<i>published</i>) ====
* 2006-05-23 raised by [[User:RobertBachmann|Robert Bachmann]]
** Atom requires the use RFC3339 datetimes, while hAtom 0.1 does not specify which datetime formats may be used.
*** ACCEPTED FAQ - hAtom references datetime-design-pattern, which discusses which date format to use

==== Feed <i>id</i> (atom:<i>id</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
*# atom:<i>id</i> is required for atom:feed. Thus it should be available in hAtom to.

It is suggested the Feed permalink should be used as the feed ID, however a piece by Mark Pilgrim (http://diveintomark.org/archives/2004/05/28/howto-atom-id) makes arguments against using permalinks and in favour of Tag URIs.

==== Feed <i>permalink</i> (atom:<i>permalink</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]</small>
** I'm proposing the following rules:
**# a Feed Permalink element is identified by [[rel-bookmark]] at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed <del>SHOULD</del><ins>MAY</ins> have a Feed Permalink
**# a Feed Permalink element represents the concept of an Atom link in a feed.
**# if the Feed Permalink is missing, use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI
** 2006-04-03 [[User:ChrisCasciano|ChrisCasciano]] - I'm not sure that having a rel-boomkark-able link element at the feed level / to designate a feed in an html page separate for the other content is anything close to normal usage on the web, so I'd be very hesitant on suggesting this element "SHOULD" exist. I'm also curious when this element would link to anything but the current page (or some element on the current page) for this to be useful in the context of the HTML doc. I think taking the "id" on the feed is a more workable solution in most cases.
** 2006-04-03 [[User:RobertBachmann|Robert Bachmann]]: I've replaced "SHOULD" with "MAY".
** 2006-04-24 [[User:RobertBachmann|Robert Bachmann]]: Maybe we could simplify my proposal to:
*** "''Use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI''"
*** IMO this would be good enough for at least 80% of the cases.
** 2006-04-12 [[User:DavidJanes]]: can we find an example of this in the wild and if so we should add it to the -examples page.
** [[User:Singpolyma|singpolyma]] 00:05, 13 Apr 2006 (PDT) : since the link is going to be pointing to the home page for the item wouldn't [[rel-home]] make more sense? That's what I'm using in the XOXO Blog Format and my reasoning was that if hAtom ever defined this rel=home made the most sense for what you would add, because the feed's link is not to a part of the site by to the home of the site.

==== Feed <i>updated</i> (atom:<i>updated</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>updated</i> is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# The Feed Updated element is identified by the class name <code>updated</code> at the feed level (inside a Feed element but not inside an Entry element)
**# If no element with the class name <code>updated</code> is present, use the youngest <code>updated</code> from the feed's entries.
** 2006-04-12 [[User:DavidJanes]] I like this. And the definition of "feed level"
** 2007-06-20 [[User:MikeKaply]] The "youngest" thing is a really bad idea. If a page has 100 hAtom entries, a parser would have to go through all 100 looking for a low date. That's crazy.
*** 2008-03-20 [[User:TobyInk]] Not crazy at all. I've just implemented an hAtom to Atom converter and I do precisely this. Most (useful) hAtom parsers will "go through all 100 entries" anyway, won't they? So why not look for the youngest updated date as part of that loop. The only slight annoyance is that in RFC 4287, the <atom:updated> element must occur before the first <atom:entry> element -- this is easily solved by inserting a placeholder <atom:updated> element, looping through the entries and then going back and filling in the date. This is really, really, '''not''' a difficult thing to implement.

==== Feed <i>title</i> (atom:<i>title</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>title</i> is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# a Feed Title element is identified by the class name <code><del>entry</del><ins>feed</ins>-title</code>
**# a Feed SHOULD have an Feed Title
**# a Feed Title element represents the concept of an Atom feed title
**# if the Feed Title is missing, use
**#* <del>the first <code><h#></code> element in the Feed, or</del>
**#* the <code><title></code> of the page, or
**#* assume it is the empty string
** 2006-04-01 [[User:ChrisCasciano|ChrisCasciano]] - I think that the fall back to using the first h# on the page is dangerous.. depending on the pge it may be something that changes often (first h# is a post title) or is otherwise ambiguous. I would think using <code><title></code> before h# would be prefered if not the most common desire of the page author.
** 2006-04-05 [[User:RobertBachmann|Robert Bachmann]]: Okay. Deleted "the first <code><h#></code> element in the Feed, or"
** 2006-04-12 [[User:DavidJanes]] Note also in support of this decision that many blogs use <code><h#></code> to encode the date for a group of postings
** 2006-04-12 [[User:DavidJanes]]: why <code>entry-title</code> for the feed title. Why not <code>fn</code> or <code>feed-title</code>?
** 2006-04-12 [[User:RobertBachmann|Robert Bachmann]]: Sorry, this was a "copy & paste" mistake. Fixed now.
** 2007-02-26 [[User:MikeKaply|Mike Kaply]]: I think a feed title should be mandatory if an hfeed is present. If you have multiple feeds on a page, there is no way in a user interface to distinguish between different feeds.

==== Feed <i>author</i> and Entry author (atom:<i>author</i>) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules for Feed author:
**# a Feed Author element is represented by class name <code>author</code> at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed Author element represents the concept of a Atom author
**# a Feed Author element MUST be encoded in a [[hcard|hCard]]
**# a Feed Author element SHOULD be encoded in a <code><address></code> element
**# a Feed MAY have more than one Feed Author elements
**# if the Feed Author is missing
**#* find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
**#* otherwise <del>the Feed is invalid hAtom</del> <ins>there is no Feed Author</ins>
** I'm proposing the following rules for entry author:
**# an Entry Author element is represented by class name <code>author</code>
**# an Entry Author element represents the concept of an Atom author
**# an Entry Author element MUST be encoded in an [[hcard|hCard]]
**# an Entry Author element SHOULD be encoded in an <code><address></code> element
**#<del> If a Feed has no Feed author each Entry MUST have at least one Entry Author element</del>
**# <ins>If an Entry is enclosed by a Feed and this Feed has no Feed author, each Entry MUST have at least one Entry Author element. If an Entry is not enclosed by a Feed and has no Entry Author:
**#* find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
**#* otherwise the Entry is invalid hAtom</ins>
**# an Entry MAY have more than one Entry Author elements
** [[User:Singpolyma|singpolyma]] 00:11, 13 Apr 2006 (PDT) : feed should not be invalid hAtom if feed-level has no author -- it should be invalid if feed-level has no author AND one or more entries have no author. Also, one or more entries may be missing an author IF feed-level has an author.
** 2006-04-17 [[User:RobertBachmann|Robert Bachmann]]: I replaced "the Feed is invalid hAtom" with "there is no Feed Author"

==== Entry <i>id</i> (atom:<i>id</i>) ====
* {{OpenIssue}}2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:<i>id</i> is required for atom:entry. Thus it should be available in hAtom to. The Entry permalink should be used as the entry id.
** --[[User:Federico|Federico]] 19:52, 25 Apr 2006 (PDT): I would add "Only if the id attribute is not defined for the element that contains the entry". The id attribute can be a tag uri. If you use always use the Entry permalink as the entry id and the Atom feed uses tag uris, you would end with two different ids for the same entry.
** 2006-12-31 response by [[User:ComputerKid|Emanla Eraton]] No, it shouldn't be a permalink. It should be a "tag:" id for entries.
** 2007-06-06 [[RyanKing]] - the syntax of tag URIs and html id attributes are incompatible. HTML disallows forward-slash (/) in ids [http://www.w3.org/TR/html401/types.html#type-name], while tag URIs require them [http://www.faqs.org/rfcs/rfc4151.html].

==== Author ====
===== author as an hcard is too much to require =====
The following 3 items were extracted from the conversation starting on irc with [http://rbach.priv.at/Microformats-IRC/2006-03-24#T152248 logs available starting around here]

* [[User:Fil|Fil]] If, for example, you are programming an "aggregator" of news syndicated from many sources like in [http://sedna.spip.org/sedna/ Sedna], chances are that you don't control what "authors" look like; they can be nicely microformated (if coming from an mf-enabled system), but most probably they will be internally represented by a string that contains, in some random order, a name, and/or an email, and so on. If you want to pass on this information in an hAtom feed, you can't possibly reformat it to an hCard. But you still want to pass it on in a <div class="author"> element.
** [[Tantek]] I don't believe the "can't possibly" statement. Please provide a URL to a concrete example that you think you can't possibly reformat into an hCard so we can all take a look.
** [[User:ChrisCasciano|ChrisCasciano]] details of Fil's extraction [http://rbach.priv.at/Microformats-IRC/2006-03-24#T153453 in irc logs] including sting data passed to his app in the form of "Béatrice XXXXXXX beatrice.xxxxxx@@zzzzzzzzz.com"
** [[User:Fil|Fil]] the example url was given up there (Sedna); note that the author information comes from syndication links; nobody is going to edit them to outline what is the name, what is the email and so on, as everything is flowing through automatically... so here the "author" data is dirty, and will not be cleaned into an hCard. We can force it to be in an hCard but it will be meaningless if the source (original data) wasn't built on an mf-enabled software.

* [[pnhChris]] i don't disagree.. the field often comes from places too dumb to follow these rules well; even cases like wordpress that allow users to present their name 1 of 6 or 8 difference ways (from username to LF, FN) .. its not just writing a template to output as hatom at that point... you have to go further upstream where the string to be displayed is chosen .. I also think its pointless to have 10 vcards on the same page whose only data is a generic name like "Chris"
** [[Tantek]] 10 vcards that are the same is pointless yes, but identifying who the author of 10 posts are is not pointless - that's the difference.
** [[User:ChrisCasciano|ChrisCasciano]] Agreed, but I still have concerns that "author" in hAtom does not always make for good hCards, though the situations where it does is optimal. My comments in the conversation were old comments I've made before over concerns and hardships or the lack of desire to make crappy data more portable, in neither of these cases do I think my two comments alone provide reasons to make change from the hAtom 0.1 spec
***[[User:Phae|Frances]] - Just thought I'd mention a scenario I have where the author of an entry does make a pretty useless vCard - the author in each case is an entire team ("creative team", "technical department") etc., rather than a specific, identifiable, person. Some use may be regained when URL to specific team/information is included, in this circumstance.
****[[User:TobyInk]] - A vCard (thus an hCard) does not have to represent a person -- it could represent an organisation, or a department or team.
* [[User:Fil|Fil]] for the moment, to comply losely with hAtom 0.1, I will use <code><nowiki><span class="author"><span class="vcard"><span class="fn">My Name</span></span></span></nowiki></code> ; but it's not good
** [[Tantek]] You can actually simplify that (one fewer span) with: <code><nowiki><span class="author vcard"><span class="fn">My Name</span></span></nowiki></code>

==== Entry <i>source</i> (atom:<i>source</i>) ====
* raised by [[User:Kevin Marks|Kevin Marks]]

When defining hAtom 0.1, atom:source was omitted. We should consider adding this back in as a useful element for providing citations of composite feeds.

== Other Questions and Issues ==
General comments, modeling issues, algorithm issues, should have issues, etc. go here.

=== Entry Updated Required? -- Blogger Issue ===
moved to [[hatom-brainstorming]]

=== 'MAY have multiple Feed elements' -- details and viability of multiple feeds ===
moved to [[hatom-brainstorming]]

== pre 0.1 issues ==
'''This section is more or less closed, as hAtom 0.1 is out the door. If there are open issues that you are championing that didn't make it into hAtom 0.1, move them up above to the hAtom 0.2 section'''

See: [[hatom-issues-pre-0.1]]

== Template ==
{{issues-format}}

== See Also ==
* [[hatom|hAtom]] - the draft proposal
* [[hatom-faq]] - knowledge base
* [[hatom-issues-resolved]]
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[mfo-examples]]
* [[naming-principles]]

Main Page

2009-05-19T23:10:27Z

WebOrganics: /* Drafts */ linking hmedia to front page

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==

This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[http://microformats.org/wiki/posh <abbr title="Plain Old Semantic HTML">POSH</abbr>]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

Also, this wiki has a number of neat enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hproduct|hProduct]]
* [[recipe|hRecipe]]
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 
* [[elemental-microformat|elemental microformats]]
* [[compound-microformat|compound microformats]]

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
<span id="microformats_wiki_translations_in_other_languages">You may read and edit microformats articles in many other languages:</span>

* languages with over 100 articles
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span>
* languages with over 10 articles
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]
* languages just started
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

User:WebOrganics

2009-04-23T20:41:02Z

WebOrganics: Undo revision 38407 by WebOrganics (Talk) just a test sorry

<div class="vcard" id="weborganics">
<h1><span class="fn"><span class="given-name">Martin</span> <span class="family-name"> McEvoy</span></span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email">info@weborganics.co.uk</div>
</div>

http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://weborganics.co.uk/haudio-rss/ hAudio to RSS] Hypertext Playlist (hAudio)
* [http://weborganics.co.uk/hFoaF/ hFoaF]: Hypertext Friend of a Friend (hCard+XFN+rel=bookmark to FoaF)
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats
* [http://weborganics.co.uk/hCast/ hCast]: hAtom + Media Info to RSS2+MRSS
* [http://weborganics.co.uk/mo-haudio/ Mo-hAudio]: GRDDL Profile to extract Music Ontology from hAudio

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}

User:WebOrganics

2009-04-23T20:40:26Z

WebOrganics: tesr

<div class="vcard" id="weborganics">
<h1><span class="fn"><span class="given-name">Martin</span> <span class="family-name"> McEvoy</span></span></h1>
<span class="org">'''WebOrganics'''</span>.
* <span class="url"><nowiki>http://weborganics.co.uk/</nowiki></span>
* <div class="email"></div>
</div>

http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-download.png [http://transformr.co.uk/hcard/http://microformats.org/wiki/User:WebOrganics Download vCard]

'''WebOrganics Projects'''
* [http://weborganics.co.uk/haudio-rss/ hAudio to RSS] Hypertext Playlist (hAudio)
* [http://weborganics.co.uk/hFoaF/ hFoaF]: Hypertext Friend of a Friend (hCard+XFN+rel=bookmark to FoaF)
* [http://transformr.co.uk/ TransFormr]: Transformation tools for Microformats
* [http://weborganics.co.uk/hCast/ hCast]: hAtom + Media Info to RSS2+MRSS
* [http://weborganics.co.uk/mo-haudio/ Mo-hAudio]: GRDDL Profile to extract Music Ontology from hAudio

'''Contributions and activities'''
*[[haudio | hAudio 0.9.1]] http://farm2.static.flickr.com/1216/604867362_da0921136a_o.png
*[[ISO-31-1]]
*[[hmedia|hMedia 0.1]]
*[[comment]]

{{public-domain-release}}