Microformats Wiki - User contributions [en]

haudio

2008-02-16T23:41:56Z

Tonydm: /* XMDP Profile */

<h1>hAudio 0.9</h1>
{{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 ==

; Editor: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
; Contributors: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc., [[ 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 ==

=== 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>''')
** '''title''' and/or '''album''' required. text.
** '''contributor'''. optional. using text or [[hCard]].
** '''duration'''. optional. ISO-8601 time duration using [[abbr-design-pattern]] (re-used from [[hcalendar]]).
** '''item''' optional. using text or multiple properties from [[hAudio]].
** '''position''' optional. text.
** '''category'''. optional. text.
** '''published'''. optional. using [[datetime-design-pattern]].
** '''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 text or [[currency-proposal]].

=== 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>

==== Title ====

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

* The element is identified by the class name <code>title</code>.
* hAudio {{must}} have <code>title</code> and/or <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>title</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.

==== 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 contents of the element {{should}} include a valid [[hcard|hCard microformat]].
** The <code>role</code> attribute {{should}} be used to specify the contributor's responsibility related to the audio recording if hCard is utilized.
* The contents of the element {{may}} be specified in plain-text.
* If multiple contributors are specified, without <code>role</code> specifications, it {{may}} be assumed that the first role mentioned is the primary artist or creator. This applies to plain-text contributor markup as well.

==== 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 {{must}} 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 {{may}} 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 {{should}} 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.

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording. Examples include: One Dollar, $2, and £4.

* 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 {{should}} use the [[currency-proposal]].
* The contents of the element {{may}} also use plain text with a currency symbol.

==== 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

=== 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 'title' is specified, then the hAudio is a song, audio track, sound effect, speech, or other atomic/singular work.
* If both 'album' and 'title' are specified, then the hAudio is a atomic/singular work that is part of an album.
** Example: <code><nowiki>Side two of Meddle opens with One of These Days</nowiki></code>
* If 'title' 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>I like Das Lied von der Erde best.</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 [[rel-license]] as specified above.

== XMDP Profile ==

<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<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>.
<dl>
<dt>haudio</dt>
<dd>
Used to identify and describe metadata associated with an individual audio recording.
</dd>
<dt>title</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>
</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">
Start Wearing Purple by Gogol Bordello
</div>

Microformatted XHTML:

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

=== Speech Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
I Have a Dream, a speech by Martin Luther King, Jr.
</div>

Microformatted XHTML:
<pre>
<div class="haudio">
I Have a Dream, a
speech by



Martin
Luther
King,
Jr.



</div>
</pre>

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

=== Song and Album Example ===

(This is a live example, detectable in parsers)

Display:

<div class="haudio">
Start Wearing Purple by Gogol Bordello found on Underdog World Strike
</div>

Microformatted XHTML:

<pre>
<div class="haudio">
Start Wearing Purple by


Gogol Bordello


found on
Underdog World Strike
</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 
Released: October 31, 2002 
Acquire: Sample, Live Recording, Buy High Quality Track 
Category: [http://www.example.org/tags/live live] 
Duration: 145 minutes, 27 seconds 
Price: $14.99 
 
Tracks: 
1. Sanity (5:48) 
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="" />
Live Phish, Volume 15


Phish


 
Released on:
<abbr class="published" title="2002-10-31">October 31, 2002</abbr>
 
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 14.99">$14.99</abbr></div>
Tracks:
<div class="item">
1.
Sanity
(<abbr class="duration" title="PT5M48S">5:48</abbr>)
</div>
<div class="item">
2.
Highway To Hell
(<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">

DigitalPlanet Podcast
:
<abbr class="published" title="20071029">29 Oct 07</abbr>


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


<a rel="enclosure" href="/download/episode/DigitalPlanet-2007-10-29">Download MP3</a>

</div>
</pre>

=== Opera Example ===

(This is a live example, detectable in parsers)

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

<pre>
<div class="haudio" lang="en">
La Bohème
is an
opera
in four acts by
Giacomo Puccini
to an
Italian liberetto
by
Luigi Illica
and
Giuseppe Giacosais.
I saw it performed last week and found

Act III
to be pretty interesting, especially the

"Sa dirmi, scusi"

and

"O buon Marcello, aiuto!"

arias.

</div>
</pre>

== Examples in the wild ==

This section is '''informative'''.

* [http://weborganics.co.uk/haudio-rss/ hAudio-RSS] almost exclusively uses hAudio 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]

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

*[http://weborganics.co.uk/files/js/item.js.zip item script] for [[operator|Operator]].
**Only detects <code>item</code>; does not detect hAudio using <code>title</code> or <code>album</code>, such as "La Bohème", in the [[#Opera_Example|live example on this page]].
*...


== 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]]

=== 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-examples]]
* [[media-info-formats]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

This document and hAudio specification was placed into the public domain on 2007-07-25 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 ===

The authors of this Microformat have not and will not apply for patents covering any invention covering this Microformat in part or as a whole. There are no claims to any patent in this document. Each author is required to report any known patent issues immediately under this section.

This document and specification is distributed under a royalty free patent policy, e.g. per the W3C Patent Policy (http://www.w3.org/Consortium/Patent-Policy-20040205/), and IETF RFC3667 (http://www.ietf.org/rfc/rfc3667.txt) & RFC3668 (http://www.ietf.org/rfc/rfc3668.txt).

=== 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)

media-metadata-examples

2008-01-21T14:59:47Z

Tonydm: /* Comparison Table */

= Media Metadata Examples =

{{TOC-right}}

This is an exploratory page to be used for storage of various multimedia data and metadata profiles, formats, and practices currently in use around the web. As this is a very, very early exploration, we should include as many types of multimedia as possible in the opening discussion - but please be sure to place your information in the correct portion of this page.

== Purpose of this exploration (or : The Problem) ==

The purpose of the studies on this page is to determine the feasibility and demand for a flexible, semantic markup format for multimedia related paradigms.

This includes such things as:
<ul>
<li>Providing metadata alongside linked multimedia files.Typically, multimedia metadata is stored within the header of the media file itself - which has massive implications for any application where metadata is to be indexed, searched, or made externally accessible. Of course, even if you could easily access the correct portions of a media file remotely, you'd still have to cope with a multitude of open and proprietary metadata formats, each with it's own distinct fieldset, nomenclature and storage method.
</li>
<li>What is called: Internet TV, IPTV, [http://newtube.org/ NewTube], vlogging, vidblogging, vidlogging, vodcasting, etc.</li>
<li>What is called: Podcasting, IPradio, etc.</li>
</ul>

This study aims to make a start at solving this problem.

== Contributors ==

These folks have contributed real-world examples and research to this document, and are interested in helping with a solution.

* Christopher Allen
* Dougal Campbell
* Dr. Ernie
* Rohit Khare
* Ryan King
* Kevin Marks
* Lisa Rein
* Mary Hodder
* Dan Glegg
* Chris Messina
* [http://changelog.ca/ Charles Iliya Krempeaux]
* Thomas Winningham

If you contribute new real-world examples or research, and wish to help with a solution, please add your name as well.

= Examples on the Web today =

Below is a list of strawman models based on real work examples. (Links to actual examples have been omitted since many of them have been found on adult sites, and it is believed that it would be inappropriate to list these here. -- [[User:Charles|Charles]])

=== Show Strawman #1 ===
Single clip with a preview image. The clip is the full show.
<nowiki>
<a href="clip.mpeg"><img src="preview.png" /></a>
</nowiki>

=== Show Strawman #2 ===
Single clip with a preview image. The clip is the teaser of the
full show. And there is a link that you can go to pay to see the full
show.
<nowiki>
<a href="teaser.mpeg"><img src="preview.png" /></a>

<a href="http://example.com/go">Pay to View</a>
</nowiki>

=== Show Strawman #3 ===
A show divided up in multiple clips, each with a preview image.
Together the clips make up the show.
<nowiki>
<a href="clip-1.mpg"><img src="preview-1.png" /></a>

<a href="clip-2.mpg"><img src="preview-2.png" /></a>

<a href="clip-3.mpg"><img src="preview-3.png" /></a>
</nowiki>

=== Show Strawman #4 ===
A set of teasers for a show. Together they don't make up the full
show. And the may or may not overlap in time. There's a "Pay to
View" link there too.
<nowiki>
<a href="clip-blue.mpg"><img src="preview-blue.png" /></a>

<a href="clip-red.mpg"><img src="preview-red.png" /></a>

<a href="clip-green.mpg"><img src="preview-green.png" /></a>

<a href="http://example.com/go">Pay to View</a>
</nowiki>

=== Show Strawman #5 ===
A single clip that comes in different formats. (Could be a
teaser, a clip, or a full show.)
<nowiki>
<img src="preview.png" />
<a href="clip.mpg">MPEG</a>
<a href="clip.ogm">Ogg</a>
<a href="clip.avi">AVI</a>
</nowiki>

=== Show Strawman #6 ===
A single preview image with the show given in 2 different methods. The first is the show broken up into a series of pieces (which makes it easier to download.) And the second is the full show in one file
<nowiki>
<img src="preview.png" />

<a href="part-1.mpg">[1]</a>
<a href="part-2.mpg">[2]</a>
<a href="part-3.mpg">[3]</a>

<a href="full.mpg">full</a>
</nowiki>

=== Show Strawman #7 ===
A single clip with a preview image. The title of the show is given with an image (and thus the actual machine-readable title is the ''alt attribute'' of the image) and is linked with the main URL for the show. There's also a link to older episodes of the show.
<nowiki>
<a href="..."><img src="the-name-of-the-show-png" alt="The Name of the Show" /></a>

<a href="episode123-clip.mpeg"><img src="episode123-preview.png" /></a>

<a href="older-shows">older shows</a>
</nowiki>

=== Show Strawman #8 ===
A series of clips with preview images. The title of the show is given with an image (and thus the actual machine-readable title is the ''alt attribute'' of the image) and is linked with the main URL for the show. There's also a links to older and news episodes of the show.
<nowiki>
<a href="..."><img src="the-name-of-the-show-png" alt="The Name of the Show" /></a>

<a href="episode123-clip.mpeg"><img src="episode123-preview.png" /></a>
<a href="episode122-clip.mpeg"><img src="episode122-preview.png" /></a>
<a href="episode121-clip.mpeg"><img src="episode121-preview.png" /></a>
<a href="episode120-clip.mpeg"><img src="episode120-preview.png" /></a>

<a href="newer-shows">[next]</a>
<a href="older-shows">[previous]</a>
</nowiki>

=== Show Strawman #9 ===
A series of preview images. The title of the show is given in text. A link to all the show's files via a torrent. Other metadata is also typically included too, in plain text; some is shown here. Also, sometimes metadata is put in the description.
<nowiki>
The Name of the Show

<img src="preview1.png" />
<img src="preview2.png" />

<a href="show.torrent">...</a>

Torrent Info Hash: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Description: blah blah blah .... here some URLs to previews...
blah blah blah .... this is 24 fps
blah blah blah

Content: tag1, tag2, tag3

Resolution: 320px x 240px

Run Time: 24mins 57secs

Size: 125.42 MB (131,509,108 bytes)

Type: Movie Clip

Published/Uploaded By: someone

<a href="...">Link to page with list of files in torrent</a>
<a href="...">Link to page with list of people on the torrent</a>
</nowiki>

=== Show Strawman #10 ===
An embedded object citing a specific plugin, or simply a link to the media itself, as an object parameter. The rest of the parameters include plugin OR media-specific metadata, and any URIs used are usually unique to the media content.

<nowiki>
<object
width='400' height='326' type='application/x-shockwave-flash'
data='http://video.google.com/googleplayer.swf?docId=3807826142091223684&hl=en'>
<param name='allowScriptAccess' value='never' />
<param name='movie'
value='http://video.google.com/googleplayer.swf?docId=3807826142091223684&hl=en'/>
<param name='quality' value='best'/>
<param name='bgcolor' value='#ffffff' />
<param name='scale' value='noScale' />
<param name='wmode' value='window'/>
</object>
</nowiki>

or:

<nowiki>
<embed
src="http://media.revver.com/qt;sharer=14854/137027.mov"
pluginspage="http://www.apple.com/quicktime/download/"
scale="tofit" kioskmode="false"
qtsrc="http://media.revver.com/qt;sharer=14854/137027.mov"
cache="false" controller="true" type="video/quicktime" autoplay="true" height="272" width="320">
</nowiki>

= Current / Previous Standards =

== Still image ==

* [http://www.exif.org/Exif2-2.PDF EXIF]
* [http://www.tasi.ac.uk/2000/09/rdfmeta/ RDF for self-describing images]
* [http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html An Indexing and Querying System for Online Images Based on the PNG Format and Embedded Metadata]
* [http://www.w3.org/TR/photo-rdf/ Describing and retrieving photos using RDF and HTTP]
* [http://www.pheed.com/pheed/ Pheed RSS extension for photo syndication]

== Audio Metadata Formats ==

* [http://www.id3.org/ ID3v2]

* iTunes
** Album : String
** Artist : String
** Beats Per Minute : Number
** Bit Rate : Number
** Comment : Blob
** Composer : String
** Genre : String or Foreign ID
** Disc Number : Number
** Kind : Proprietary - could be implimented as MIME type
** My Rating : Number < 5 (actually an integer from the range 0-100. 1-5 "stars" implemented by incrementing by 20)
** Sample Rate : Number
** Size : Number
** Time : Number
** Track Number : Number
** Year : Number
**Additional metadata used internally by the application : Date Added (Timestamp), Date Modified (Timestamp), Equalizer (foreign ID), Play Count (Number), Grouping (Internal)
**Noteable absences : Tags, [[rel-license|License]], Copyright year. Also note common complaints about [http://www.everything2.com/index.pl?node_id=1707402 ID3 and classical music].

* [http://www.xspf.org/ XSPF] (see also [http://gonze.com/playlists/playlist-format-survey.html A survey of playlist formats] and [http://www.xspf.org/xspf-v0.html The XSPF Playlist Format, version 0])
** album
** creator
** duration
** info
** title
** trackNum

== Podcasts ==

* '''iTunes podcast:''' http://phobos.apple.com/static/podcast_specifications.pdf
(HTML version of spec: [http://labs.commerce.net/~rohit/How%20To%20Publish%20a%20Podcast%20on%20iTunes%20Music%20Store.html local archive], [http://labs.commerce.net/~rohit/iTunesRSS.html updated version from Apple Chapter Tool Beta docs], [http://phobos.apple.com/static/iTunesRSS.html online copy at Apple])

iTunes release 4.9 was widely heralded as an advance for mainstream acceptance of podcasting. However, while some advocates resist even the fragment of a trademarked name in the label for the phenomenon, the use of "itunes:" in the namespace is one of many design decisions in Apple's original specification that became focal points of debate. While Apple has a tradition of working on breakthrough features very quietly, they have been open to public input after its initial release. Many [http://daringfireball.net/2005/07/podcast_pocket other bloggers] have [http://usefulinc.com/edd/blog/contents/2005/06/28-rss-apple-itunes/read chronicled] [http://www.intertwingly.net/blog/2005/07/05/Insensitive-iTunes some of the feedback], as well as some [http://tantek.com/log/2005/07.html#d10t0130 face-to-face discussions].

A mailing list may be coming soon...

* '''Media RSS:''' http://search.yahoo.com/mrss

Media RSS has [http://www.ysearchblog.com/archives/000111.html been in the works longer], but doesn't have the overnight-adoption advantage of iTunes. However, it has a much broader ambit, including [http://www.ysearchblog.com/archives/000060.html video]; and a much broader [http://groups.yahoo.com/group/rss-media/ community of interest].

=== A Podcasting Microformat? ===

The best starting point for understanding these two proposals is [http://www.w3.org/2005/07/media-and-rss W3C's summary table, by Karl Dubost].

There are (at least) two paths to consider when 'porting' these proposals into Microformats:
# '''Standalone.''' What is the most straightforward rendering of each proposal into XHTML? This keeps the interests of the developers of ''consuming'' applications foremost: how can the migration be made as painless as possible?
# '''Refactored.''' Given the existing core of Microformats, what is the minimal (!) necessary to add on to RelLicense, RelTag, hReview, and so forth? This favors (we'd hope) content ''publishing'' applications: how can the marginal migration costs of adding media be made as painless as possible.

Mapping the existing specs requires understanding the data definitions set forth in each specification, and finding the optimal equivalents (where available). The following is a partial summary of one possible mapping:

==== Comparison Table ====

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>Atom</th>
<th>iTunes RSS</th>
<th>Media RSS</th>
<th>M3U</td>
<th>RSS 2.0</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Authorship</td>
<td><ul><li><atom:author></li><li><atom:contributor></li></ul></td>
<td><ul><li><itunes:author></li><li><itunes:owner></li><li><itunes:name></li><li><itunes:email></li></ul></td>
<td><media:credit></td>
<td>nothing</td>
<td><copyright> <author> <source></td>
<td style="background-color:#eeeeee;color:black;"><ul><li><cite></li><li>[[hcard|hCard]]</li><li>[[rel-author]]</li><li>[[rev-author]]</li><li><address></li></ul>need a way of specifying the role of the author or contributor.<dl><dt>proposal for role</dt>
<dd>By using class atribute, this allows diferent formating of authors and contributors, also is usable for <cite> and <adress> <pre><div class="author vcard"> ...hCard code here </div></pre>

-- [[User:Tonydm|tonydm]] 21 Jan 2007
</dd></dl>
</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Categorization</td>
<td><atom:category></td>
<td><itunes:category> <itunes:keywords></td>
<td><media:category></td>
<td>nothing</td>
<td><category></td>
<td style="background-color:#eeeeee;color:black;">[[rel-tag]] - requires a way to do sub categories?</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Description</td>
<td><atom:summary> <atom:content></td>
<td><itunes:subtitle> <itunes:summary></td>
<td><media:text></td>
<td>nothing</td>
<td><description></td>
<td style="background-color:#eeeeee;color:black;">XHTML (e.g. <nowiki><blockquote></nowiki> )</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Licensing</td>
<td><atom:copyright> <atom:rights></td>
<td><itunes:block> <copyright> <link></td>
<td>Not explicitly mentioned</td>
<td>nothing</td>
<td><ttl></td>
<td style="background-color:#eeeeee;color:black;">[[rel-license]]</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Metadata</td>
<td></td>
<td><itunes:duration> <itunes:image></td>
<td><media:thumbnail> <media:hash> <pre><media:content
url="http://www.example.com/movie.mov"
fileSize="12216320"
type="video/quicktime"
isDefault="true"
expression="full"
bitrate="128"
framerate="25"
duration="185"
height="200"
width="300"
/></pre></td>
<td>nothing</td>
<td></td>
<td style="background-color:#eeeeee;color:black;">needs a new microformat e.g., <dl><dt>proposal for duration</dt><dd><pre><abbr class="duration" title="00:27:35">
27 minutes, 35 seconds
</abbr></pre>
-- [[User:jkinberg|jkinberg]] 11:51, 19 Sept 2005 (PDT))
</dd></dl></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Preview</td>
<td>nothing</td>
<td>nothing</td>
<td>For Video Media: <media:thumbnail> For Audio Media: nothing</td>
<td>nothing</td>
<td>nothing</td>
<td style="background-color:#eeeeee;color:black;">need a new microformat for this
<dl><dt>proposal for video preview</dt><dd><pre><img class="preview" src="..." /></pre>
-- [[User:Charles|Charles]]
</dd></dl></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Rating</td>
<td>nothing</td>
<td><itunes:explicit></td>
<td><s><media:adult></s> <media:rating></td>
<td>nothing</td>
<td><rating></td>
<td style="background-color:#eeeeee;color:black;">[[rel-tag]]</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Title</td>
<td><atom:title> <atom:subtitle></td>
<td><itunes:subtitle> <title></td>
<td><media:title> <title></td>
<td>nothing</td>
<td><title></td>
<td style="background-color:#eeeeee;color:black;">
<ul>
<li><h1>...</h1></li>
<li><h2>...<h2></li>
<li><h3>...</h3></li>
<li><h4>...</h4></li>
<li><h5>...</h5></li>
<li><h6>...</h6></li>
<li>title="..."</li>
<li>Microformats with class="title"</li>
</ul>
</td>
</tr>
<tr>
<td colspan="7"> </td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Show Concept</td>
<td><ul><li><atom:feed></li><li><link rel="self" href="..." /></li></ul></td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td>A M3U file.</td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td style="background-color:#eeeeee;color:black;">need a new microformat</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Episode Concept</td>
<td><ul><li><atom:entry></li><li><link rel="alternate" href="..." /></li></ul></td>
<td><ul><li><item></li><li><link></li></ul></td>
<td><ul><li><item></li><li><link></li></ul></td>
<td>A single URL line.</td>
<td><ul><li><item></li><li><link></li></ul></td>
<td style="background-color:#eeeeee;color:black;">need a new microformat</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Media Concept</td>
<td><ul><li><atom:link rel="enclosure" href="..." /></li><li>also... dependent on type of data embedded in or referenced from <atom:content></li></ul></td>
<td><enclosure></td>
<td><media:content></td>
<td>Simply the inclusion of a URL on a line.</td>
<td><enclosure></td>
<td style="background-color:#eeeeee;color:black;"><img> <a href=""> <object> <embed> </td>
</tr>
</table>

== Video ==
* [http://www.exif.org/Exif2-2.PDF EXIF] - (Yes, the spec deals with video taken by still cameras. -- RyanKing)
* [http://www.chiariglione.org/mpeg/standards/mpeg-7/mpeg-7.htm MPEG-7] - MPEG-7, formally named "Multimedia Content Description Interface", is a standard for describing the multimedia content data that supports some degree of interpretation of the information meaning, which can be passed onto, or accessed by, a device or a computer code. (Very powerful, but you have to pay for documentation -- [[User:ChristopherA|ChristopherA]] 01:53, 29 Jun 2005 (PDT))
**An OWL ontology of MPEG-7 is available at http://rhizomik.net/ontologies/2005/03/Mpeg7-2001.owl -tmw
* [http://www.w3.org/AudioVideo/ SMIL] - Synchronized Multimedia Integration Language (SMIL, pronounced "smile") enables simple authoring of interactive audiovisual presentations. (Not exactly video, but has a lot of useful video-related features in it. -- [[User:ChristopherA|ChristopherA]] 01:55, 29 Jun 2005 (PDT))
* [[video-metadata-model| Video Metadata Model - a starting point]]

== Interactive ==
* [http://www.w3.org/Graphics/SVG/ SVG]
* [http://www.w3.org/AudioVideo/ SMIL]
* QTVR?

== Offline Media ==
* [http://xspf.org XSPF] (media may be either offline or online)

=== Printed Publications (books/magazines) ===
* [http://amazon.com/ Amazon]

=== Movies ===
* [http://imdb.com/ IMDB]
* [http://amazon.com/ Amazon]

=== Music ===
* [http://freedb.org/ FreeDB]
* [http://musicbrainz.org/ MusicBrainz]
* [http://amazon.com/ Amazon]

== Container Formats ==
The purpose of container formats is to allow the muxing of multiple codecs into a single file or stream. For example, if you want audio, video, and text (subtitles) combined into a single stream.

The purpose of the muxing is for synchronization and so that you can stream the file and view it without having to jump around -- seek -- in the file.

Container formats include:
* AVI
* MPEG
* Ogg
* QuickTime

=== Container Format Comparison Table ===

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>AVI</th>
<th>MPEG</th>
<th>Ogg</td>
<th>QuickTime</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Audio</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Video</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Text</td>
<td></td>
<td></td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Error Detection</td>
<td></td>
<td></td>
<td>Yes</td>
<td></td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
</table>

=== Notes for Microformats ===
One of the problems with container formats is that it is often difficult and sometimes impossible to know the disposition of what they contain ahead of time (without reading the file).

For example, Ogg files use the MIME type application/ogg and generally use the extension .ogg. With only these 2 pieces of information, you cannot tell whether such an Ogg file contains video data or not.

There is room for a microformat to help with this. Perhaps something like:
<div style="font-family:monospace;white-space:pre;padding:1.5em;background-color:black;color:white;"><a class="moving-image" type="application/ogg" href="my.ogg">...</a></div>
Although, this can be done in other ways too. For example, using [http://changelog.ca/log/2005/08/21/rss-disposition-hinting-proposal disposition hinting] one could do something like:
<div style="font-family:monospace;white-space:pre;padding:1.5em;background-color:black;color:white;"><a type="application/ogg;disposition-type:moving-image" href="my.ogg">...</a></div>

Anothing thing for any Microformat to consider is that it may be the case that the data files that are muxed in the container format may also be offered in non-muxed forms. This is important when alternatives are offered.

== Audio Formats ==

Audio formats include:
* AAC
* MP3
* PCM WAV
* Speex
* Vorbis
* WMA

=== Audio Format Comparison Table ===

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>AAC</th>
<th>MP3</th>
<th>PCM WAV</td>
<th>Speex</th>
<th>Vorbis</th>
<th>WMA</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Lossless</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td></td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Lossy</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Streamable</td>
<td>Yes</td>
<td>Yes</td>
<td></td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
</table>

=== Notes for Microformats ===
* Knowing whether audio data is streamable or not can affect pre-fetching. And can be a metric used when alternatives of the same file is given.
* Having audio data marked as lossy or lossless can be useful when alternatives of the same file is made.

== Playing Formats ==
Playing formats include:
* ASX
* Atom
* Atom+SMIL
* Atomic RSS
* Atomic RSS+SMIL
* Extended M3U
* HTML+Time
* iTunes RSS
* KPL
* M3U
* MAGMA
* Media RSS
* PLS
* RAM
* RSS 2.0
* SMIL
* WAX
* WVX

=== Playing Format Comparison Table ===
<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>ASX</th>
<th>Atom</th>
<th>Atom+SMIL</th>
<th>Atomic RSS</th>
<th>Atomic RSS+SMIL</th>
<th>Extended M3U</th>
<th>HTML+Time</th>
<th>iTunes RSS</th>
<th>Media RSS</th>
<th>M3U</td>
<th>RSS 2.0</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Alternatives Playing</td>
<td></td>
<td>nothing</td>
<td></td>
<td></td>
<td><smil:switch></td>
<td></td>
<td></td>
<td>nothing</td>
<td><media:group></td>
<td>nothing</td>
<td>nothing</td>
<td style="background-color:#eeeeee;color:black;">need a new microformat</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Parallel Playing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td style="background-color:#eeeeee;color:black;">need a new microformat</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Sequence Playing</td>
<td></td>
<td>if you consider the Atom file a show, then nothing. if you consider the Atom file an episode, then the list of <atom:entry>'s provides a sequence.</td>
<td></td>
<td></td>
<td><smil:seq></td>
<td></td>
<td></td>
<td>if you consider the RSS file a show, then nothing. if you consider the RSS file an episode, then the list of <item>'s provides a sequence.</td>
<td>if you consider the RSS file a show, then nothing. if you consider the RSS file an episode, then the list of <item>'s provides a sequence.</td>
<td>if you consider the M3U file a show, then nothing. if you consider the M3U file an episode, then the URL lines provide a sequence.</td>
<td>if you consider the RSS file a show, then nothing. if you consider the RSS file an episode, then the list of <item>'s provides a sequence.</td>
<td style="background-color:#eeeeee;color:black;">need a new microformat</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Pre-Fetching</td>
<td></td>
<td><link rel="enclosure" href="..." /></td>
<td><ul><li style="white-space:pre;"><link rel="enclosure" href="..." /></li><li><smil:prefetch></li></ul></td>
<td><link rel="enclosure" href="..." /></td>
<td></td>
<td></td>
<td></td>
<td><enclosure></td>
<td><media:content></td>
<td>The M3U format is just list of URL's, with each URL on its own line. Pre-Fetching would be accomplished by just added a URL to the list.</td>
<td><enclosure></td>
<td style="background-color:#eeeeee;color:black;">[[rel-enclosure]]</td>
</tr>
</table>

== Raster Graphic Formats ==
Raster graphic formats include:
* GIF
* PNG
* JPEG

== Vector Graphic Formats ==
Vector graphic formats include:
* SVG

= Formats & Protocols =

== AAC ==
AAC (Advanced Audio Coding) is a lossy audio format. Like MP3, AAC is part of the MPEG standard. Since April 2003, AAC has become an integral part of Apple's iPod and iTunes products. This association between AAC and Apple has become so strong among some that AAC is also sometimes call Apple Audio Codec.

References:
* http://en.wikipedia.org/wiki/Advanced_Audio_Coding

== ASF ==
ASF is an Audio/Video format. ASF files that contain only audio data are typically called WMA files.

References:
* http://en.wikipedia.org/wiki/Advanced_Streaming_Format

== Atom ==
Atom is a XML-based syndication format that was developed by certain members of the RSS community.

References:
* http://atomenabled.org/developers/syndication/
* [http://www.faqs.org/rfcs/rfc3339.html RFC 3339]

== Atom+SMIL ==
Atom+SMIL is Atom with SMIL used in the <atom:content>.

(This was originally used by [http://changelog.ca/ Charles Iliya Krempeaux] for "Internet TV". Also see Atomic RSS+SMIL)

== Atomic RSS ==
Atomic RSS is a syndication format that is RSS with Atom used as an extension module.

References:
* http://www.tbray.org/ongoing/When/200x/2005/07/27/Atomic-RSS

== Atomic RSS+SMIL ==
Atomic RSS+SMIL is Atomic RSS with SMIL use in the <atom:content>.

(This was originally used by [http://changelog.ca/ Charles Iliya Krempeaux] for "Internet TV".)

== AVI ==
AVI is a container format for Audio/Video formats.

References:
* http://en.wikipedia.org/wiki/AVI

== B4S ==
B4S is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#B4S

== BitTorrent ==
BitTorrent is a P2P protocol.

References:
* http://www.bittorrent.com/protocol.html
* http://en.wikipedia.org/wiki/Bittorrent
* http://wiki.theory.org/BitTorrentFAQ

== Creative Commons RDF ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#Creative

== DAAP ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#DAAP

== Extended M3U ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#M3U
* http://hanna.pyxidis.org/tech/m3u.html
* http://en.wikipedia.org/wiki/M3U

== FLAC ==
Free Lossless Audio Codec (FLAC)
* http://flac.sourceforge.net/

== GIF ==
GIF is a raster graphics format and a movie format.

== HTML+Time ==

References:
* http://www.w3.org/TR/NOTE-HTMLplusTIME
* http://gonze.com/playlists/playlist-format-survey.html#HTML

== HTTP ==

References:
* http://www.w3.org/Protocols/

== iTunes Library ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#iTunes

== iTunes RSS ==

References:
* http://www.apple.com/itunes/podcasts/techspecs.html

== JPEG ==
JPEG is a raster graphics format.

== Kapsule ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#Kapsule

== KPL ==
KPL is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#KPL

== M3U ==
M3U is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#M3U

== MAGMA ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#MAGMA

== Media RSS ==
Media RSS is a syndication format that is RSS with the addition of the Media RSS Module.

== MKV/MKA ==
Matroska MKV/MKA are video and audio containers, respectively.
* http://www.matroska.org/

== MNG ==
MNG is a Video format.

== MP3 ==
MP3 is an Audio format.

== MPEG ==
ASF is an Audio/Video format.

== MusicBrainz ==

References:
* [http://www.MusicBrainz.org MusicBrainz.org]
* [http://wiki.musicbrainz.org MusicBrainz wiki]
* http://gonze.com/playlists/playlist-format-survey.html#musicbrainz

== Ogg ==
Ogg is a media container format.

References:
* http://xiph.org/ogg/
* http://en.wikipedia.org/wiki/Ogg
* [http://xiph.org/ogg/doc/rfc3533.txt RFC 3533] - The Ogg Encapsulation Format Version 0
* [http://xiph.org/ogg/doc/rfc3534.txt RFC 3534] - The application/ogg Media Type

== PLS ==
PLS is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#PLS
* http://en.wikipedia.org/wiki/PLS_(file_format)

== RAM ==
RAM is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#RAM

== RSS 2.0 ==
RSS 2.0 is the defacto standard syndication format.

References:
* http://developer.mozilla.org/en/docs/RSS

== RTSP ==

References:
* http://www.rtsp.org/
* [http://www.ietf.org/rfc/rfc1889.txt RFC 1889]
* http://en.wikipedia.org/wiki/Real_Time_Streaming_Protocol

== SMIL ==

References:
* http://www.w3.org/AudioVideo/

== Speex ==

References:
* http://www.speex.org/

== SVG ==
SVG is a vector graphics format.

== Theora ==
Theora is an Audio/Video format/

References:
* http://www.theora.org/
* http://en.wikipedia.org/wiki/Theora

== Vorbis ==
Vorbis is an Audio format.

References:
* http://xiph.org/vorbis/
* http://vorbis.com/
* http://en.wikipedia.org/wiki/Vorbis

== WAX ==
WAX is an SGML-based playlist for that looks exactly like ASX and WVX, except that it can only reference to ASF or WMA, but NOT to WMV files.

References:
* http://gonze.com/playlists/playlist-format-survey.html#WAX

== WMA ==
WMA is an Audio format.

References:
* http://en.wikipedia.org/wiki/Windows_Media_Audio

== WMV ==
WMV is an Audio/Video format.

References:
* http://en.wikipedia.org/wiki/Windows_Media_Video

== WVX ==
WVX is an SGML-based playlist format that looks exactly like ASX and WAX, except that it can reference ASF, WMA, and WMV media files.

References:
* http://gonze.com/playlists/playlist-format-survey.html#WVX

= Comments =

* See separate [[media-metadata-issues]] document.
* See separate [[media-info-examples]] document.

= See Also =

* [[video-metadata-models]]

User:Tonydm

2008-01-21T14:58:38Z

Tonydm:

Student of Faculty of Informatics and Information Technology, Slovak University of Technology. Curretly I am exploring microformats and their practical usage in Digital Assets Management systems, web portals and so.