Microformats Wiki - User contributions [en]

project-examples

2015-10-21T06:07:04Z

Meterprikluts:

= Project Examples =

There have been several efforts to define data formats for posting "projects" on the Web.

This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]

__TOC__

== Contributors ==

* Derek Lewis

== See Also ==
* [[project]]
* [[project-examples]]
* [[project-brainstorming]]
* [[project-formats]]

== Examples on the Web ==

There are two types of projects being documented on the web. Practical (how-you-can-do-it) and Abstract (what-we're-doing).
Fields in [brackets] have already been accommodated for.

== Practical Projects (how-you-can-do-it) ==

=== 43things ===
How I did a project
* http://43things.com

** goal title [fn]
** last words [summary]
** how [instructions]
** lessons
** time taken [duration]
** resources

=== Poncho ===
How to make a poncho
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html

** project title [fn]
** [summary]
** Material [requirement]
** Gauge
** directions [instructions]

=== RX-8 iPod Install ===
How to install an iPod into an RX-8
* http://www.whatsmyip.org/ipodrx8/

** title [fn]
** [author]
** date [published]
** Car Compatibility List [summary]
** Basic Idea [instructions]
** Tools Needed [requirement]
** notes
** WARNING

=== How to fix a CD player ===
* http://www.kuro5hin.org/story/2004/3/24/45212/6874

** title [fn]
** by [author]
** date and time submitted [published]
** [tags]
** description
** [summary]
** [instructions]

== Abstract Projects (what-we're-doing) ==

=== CORDIS ===
Community Research and Development Information Service
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]

** project title [fn]
** Research area
** Coordinator [author]
** Project description [summary]
** Project details
*** Project Acronym
*** Project Reference
*** Start Date
*** [duration]
*** Project Cost
*** Contract Type
*** End Date [due]
*** Project Status
*** Project Funding[http://crowdfund.co .]
** Participants

=== Freshmeat.net ===
Description of the software project
* http://freshmeat.net

** full project name (This is the publicly visible project name.) [fn]
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)
** full description
** short description [summary]
** name of author [author]
** email address
** branch name
** branch description
** license
** homepage [url]
** Tar/GZ
** Tar/BZ2
** Zip
** Changelog
** RPM package
** Debian package
** OS X package
** Bittorrent
** BSD Ports URL
** Autopackage URL
** Jar
** Purchase
** CVS tree (cvsweb)
** Bug tracker
** Mailing list archive
** Mirror site
** Demo site
** version
** release focus
** Dependencies

=== Moldova Aid Project ===
A humanitarian aid project
* http://www.moldovaaidproject.org.uk/

** title [fn]
** [summary]
** achievements

=== The World Bank ===
Moldova Community Forestry Project
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]

** project title [fn]
** Project ID
** Project Status
** Approval Date
** Closing Date [due]
** Total Project Cost
** Region
** Major Sector (Sector) (%)
** Old Major Sector
** Old Sector
** Environmental Category
** Bank Team Lead
** Borrower
** Implementing Agency
** Project Goals [goal]
** Available Project Documents
** Related Country Information

== Analysis of Examples (Based on 8 examples.)==

=== Common practical project fields ===
* fn (100%)
* summary (100%)
* author (50%)
* instructions (100%)
* requirement (50%)
* published (50%)
* duration (25%)
* tags (25%)

=== Common abstract project fields ===
* fn (100%)
* summary (75%)
* author (50%)
* due (50%)
* goal (25%)
* duration (25%)

== See Also ==
* [[project]]
* [[project-examples]]
* [[project-brainstorming]]
* [[project-formats]]

See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.

hcard-examples-fr

2015-10-03T09:37:46Z

Meterprikluts:

<entry-title>Exemples de hCard</entry-title>

Exemples de [[hcard-fr|hCards]].

== Auteurs ==
* [http://tantek.com/ Tantek Çelik]
* Brian Suda
* Traduction [[Christophe Ducamp]]

== Exemples Instructifs ==

=== Auteurs de Pages et de Billets ===
[http://www.la-grange.net/w3c/html4.01/struct/global.html#h-7.5.6 Selon la spécification HTML4.01], "les auteurs devraient employer l'élément <code><address></code> pour fournir les informations de contact du document ou d'une partie essentielle de celui-ci" c'est-à-dire :

<source lang=html4strict>
<address>
<a href="http://tantek.com/">Tantek Çelik</a>
</address>
</source>

En ajoutant [[hcard-fr|hCard]] à un tel XHTML sémantique, vous pouvez indiquer explicitement le nom de la personne, son URL, etc. :

<source lang=html4strict>
<address class="vcard">
<a class="fn url" href="http://tantek.com/">Tantek Çelik</a>
</address>
</source>

Ceci pourrait être affiché comme :

[http://tantek.com/ Tantek Çelik]

Ceci fonctionne non seulement pour l'ensemble de pages, mais aussi pour les "parties essentielles" des pages, par exemple les billets de blog.

Voir le [http://microformats.org/blog/ blog microformats.org] (visualisez la source) pour un exemple vivant. L'auteur de chaque billet de blog sur le blog microformats.org est balisé comme un élément <code><address class="vcard"></code> comme dans l'exemple montré ci-dessus.

=== Références aux Personnes et aux Organisations ===

Un modèle commun dans les billets de blog est de lier les citations des noms de personnes vers leurs blogs, et/ou les organisations vers leurs pages d'accueil.
Par exemple :

<source lang=html4strict>
<cite>
<a href="http://meyerweb.com/">Eric Meyer</a>
a écrit un billet
(<cite>
<a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">
Tax Relief
</a>
</cite>)
à propos d'une lettre involontairement humoristique qu'il a reçue du
<a href="http://irs.gov/">Internal Revenue Service</a>.
</source>

En ajoutant hCard à un tel balisage, vous pouvez explicitement indiquer à la fois la personne et l'organisation par le nom et l'URL :

<source lang=html4strict>
<cite class="vcard">
<a class="fn url" href="http://meyerweb.com/">Eric Meyer</a>
</cite>
a écrit un billet
(<cite>
<a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">
Tax Relief
</a>
</cite>)
à propos d'une lettre involontairement humoristique qu'il a reçue du
<span class="vcard">
<a class="fn org url" href="http://irs.gov/">Internal Revenue Service</a>
</span>.
</source>

Remarquez les noms de classe "fn org url" sur l'hyperlien entourant IRS. Utiliser la même valeur (ou élément pour ce qui compte) pour "fn" et "org" indique que le hCard décrit une organisation plutôt qu'une personne.

Ceci pourrait être affiché comme :

''[http://meyerweb.com/ Eric Meyer]'' a écrit un billet (''[http://www.irstaxreliefsettlement.com/ Tax Relief]'') à propos d'une lettre involontairement humoristique qu'il a reçue du [http://irs.gov/ Internal Revenue Service].

==== une personne qui travaille pour une organisation ====
Les personnes s'associent souvent elles-mêmes avec une société ou une organisation pour lesquelles elles travaillent. Par exemple :

<source lang=html4strict>
<span class="vcard">
<span class="fn">Jeremy Keith</span>,
<span class="org">Clearleft</span>
</span>
</source>

Bien sûr à cette heure, presque tout le monde a une URL à la fois pour soi-même et pour sa société. Il est facile d'ajouter une URL pour la personne dans l'exemple de la hCard au-dessus :

<source lang=html4strict>
<span class="vcard">
<a class="fn url" href="http://adactio.com/">Jeremy Keith</span>,
<span class="org">Clearleft</span>
</span>
</source>

Mais pour ajouter une URL vers la société, il n'existe pas de propriété "org-url" (et il ne devrait pas y en avoir), au lieu de cela, utilisez la modularité et une hCard imbriquée pour la société elle-même :

<source lang=html4strict>
<span class="vcard">
<a class="fn url" href="http://adactio.com/">Jeremy Keith</span>,
<span class="org vcard"><a class="url fn org" href="http://clearleft.com">Clearleft</a></span>
</span>
</source>

En outre, si la hCard de cette personne est sur une page qui la représente (c'est à dire une [[representative hCard-fr|hcard représentative]]), alors vous pouvez aussi utiliser la relation [[rel-group-fr|rel-group]] expérimentale sur l'hyperlien vers la société pour indiquer que la société est un "groupe" auquel appartient la personne.

<source lang=html4strict>
<span class="vcard">
<a class="fn url" href="http://adactio.com/">Jeremy Keith</span>,
<span class="org vcard"><a class="url fn org" rel="group" href="http://clearleft.com">Clearleft</a></span>
</span>
</source>

=== hCard et XFN ===
==== Références vers des Personnes dans les Billets de Blog ====

Dans l'exemple au-dessus, une personne (le blogueur) fait référence à une autre personne (Eric Meyer). En plus d'utiliser hCard pour baliser explicitement la référence comme une personne, le blogueur peut utiliser [http://gmpg.org/xfn/ XFN] (Le XHTML Friends Network) pour indiquer sa relation avec Eric Meyer, par ex. :

<source lang=html4strict>
<cite class="vcard">
<a class="fn url" rel="friend colleague met" href="http://meyerweb.com/">
Eric Meyer
</a>
</cite>
a écrit un billet
(<cite>
<a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a>
</cite>)
à propos d'une lettre involontairement humoristique qu'il a reçue du
<span class="vcard">
<a class="fn org url" href="http://irs.gov/">
Internal Revenue Service
</a>
</span>.
</source>

Cela s'afficherait de la même façon que dans l'exemple précédent.

==== Références aux Personnes dans les Blogrolls ====

Beaucoup de blogueurs utilisent XFN (en utilisant souvent une interface utilisateur facile qui est construite dans [http://wordpress.org WordPress]) pour indiquer explicitement leurs relations avec les personnes dans leurs blogrolls :

<source lang=html4strict>
<ul>
<li>
<a href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a>
</li>
<li>
<a href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a>
</li>
</ul>
</source>

En ajoutant le balisage hCard à une blogroll d'amis XFN, vous pouvez indiquer explicitement le nom et l'URL de la personne en plus de sa relation :

<source lang=html4strict>
<ul>
<li class="vcard">
<a class="fn url" href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a>
</li>
<li class="vcard">
<a class="fn url" href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a>
</li>
</ul>
</source>

qui pourrait s'afficher comme :
* [http://meyerweb.com Eric Meyer]
* [http://photomatt.net Matt Mullenweg]

Ceci fait référence aux [[hcard-xfn-supporting-friends-lists-fr|listes d'amis supportant hCard et XFN]], et c'est un bloc-de-construction-clé de la [[social-network-portability-fr|portabilité du réseau social]].

Pour plus d'informations sur XFN, voir la [http://gmpg.org/xfn/ page d'accueil XFN], [http://gmpg.org/xfn/join rejoindre XFN] et [http://gmpg.org/xfn/background données de base sur XFN].

La technique est utilisée dans le plugin [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll].

=== Nouveaux Types d'Information de Contact ===

Depuis que la vCard a été conçue, il y a eu plusieurs autres services qui fournissent des individus avec des adresses ou d'autres moyens de contact, par ex. la messagerie instantanée, la voip, etc.

Est-ce que cela veut dire que vCard (et par conséquent hCard) doit être étendu pour les représenter ?

Grâce à la flexibilité de la propriété URL, la réponse est non, aucune extension n'est nécessaire. Au lieu de cela, nous utilisons l'URL appropriée pour le service qui identifie le service (protocole, machine et/ou chemin), et plaçons l'adresse de l'individu à l'intérieur de cela.

==== AOL Instant Messenger (AIM) ====
Les ids AOL Instant Messenger (AIM) peuvent être représentées en utilisant le protocole <code>aim:</code>. Beaucoup de personnes qui publient leurs ids AIM le font ainsi avec des URLs cliquables par ex. :

<source lang=html4strict>
<a href="aim:goim?screenname=ShoppingBuddy">IM avec l'AIM ShoppingBuddy</a>
</source>

Par conséquent pour hCard, nous adopterons ce comportement existant d'éditeur, et le saisirons simplement comme un autre URL pour le hCard :

<source lang=html4strict>
<a class="url" href="aim:goim?screenname=ShoppingBuddy">IM avec l'AIM ShoppingBuddy</a>
</source>

==== Yahoo! Messenger ====
De la même manière, les ids de Yahoo Instant Messenger (YIM) peuvent être représentées en utilisant le protocole <code>ymsgr:</code>. Et de la même manière, beaucoup publient leurs ids YIM comme des URLs cliquables par ex :

<source lang=html4strict>
<a href="ymsgr:sendIM?QuelqueAmiYahoo">IM avec QuelqueAmiYahoo</a>
</source>

A nouveau, pour hCard, nous adopterons ce comportement de publication de contenu existant, et le saisirons simplement comme un autre URL pour la hCard :
<source lang=html4strict>
<a class="url" href="ymsgr:sendIM?QuelqueAmiYahoo">IM avec QuelqueAmiYahoo</a>
</source>

==== MSN Messenger ====
Les ids de MSN Messenger (MSNIM) peuvent être représentées en utilisant le protocole <code>msnim:</code>. Et de la même façon, beaucoup publient leurs ids MSNIM comme des URLs cliquables par ex :

<source lang=html4strict>
<a href="msnim:chat?contact=jeandupont@hotmail.com">IM avec jeandupont@hotmail.com</a>
</source>

Pour hCard, nous adopterons ce comportement de publication existant et le saisirons simplement comme un autre URL pour le microformat hCard :

<source lang=html4strict>
<a class="url" href="msnim:chat?contact=jeandupont@hotmail.com">IM avec jeandupont@hotmail.com</a>
</source>

Voir les [[hcard-examples-issues-fr#MSN_Messenger|problématiques en rapport]].

==== XMPP (Jabber) ====
Les idées [http://www.xmpp.org/ Extensible Messaging and Presence Protocol (XMPP)] peuvent être représentées en utilisant le protocole <code>xmpp:</code>, par exemple :

<source lang=html4strict>
<a class="url" href="xmpp:username@jabberservice.com">IM with username@jabberservice.com</a>
</source>

Le protocole permet des URLs beaucoup plus riches, voir [http://www.faqs.org/rfcs/rfc4622.html RFC4622].

Il n'y a pas beaucoup de [http://wiki.jabber.org/index.php/XMPP_URIs#Jabber_Clients clients supportant actuellement le protocole].

==== Skype ====
Skype peut être représenté en utilisant le protocole <code>skype:</code>. Il peut être utilisé pour ouvrir une session de chat ou produire un appel Skype.

<source lang=html4strict>
<a href="skype:echo-chinese?chat">IM avec Skype echo service (Chinois) </a>
</source>

<source lang=html4strict>
<a href="skype:echo-chinese?call">Appel Skype vers Skype echo service (Chinois) </a>
</source>

De ce fait pour hCard, nous pourrions adopter ce comportement de publication existant, et le saisir simplement comme une autre URL pour la hCard :
<source lang=html4strict>
<a class="url" href="skype:echo-chinese?chat">IM avec Skype echo service (Chinois) </a>
</source>

<source lang=html4strict>
<a class="url" href="skype:echo-chinese?call">Appel Skype vers Skype echo service (Chinois)</a>
</source>

==== ICQ ====
ICQ n'a pas de schéma URL. Au lieu de cela, ICQ fait un lien sur le web en utilisant les hyperliens HTTP pour télécharger une ressource de contenu-type <code>application/x-icq</code> que le système d'exploitation ouvre alors avec le client utilisateur ICQ du client.

Par conséquent nous pouvons marquer ces hyperliens HTTP avec le contenu-type réglé explicitement pour conmmuniquer la sémantique ICQ :

<source lang=html4strict>

<a class="url"
type="application/x-icq"
href="http://www.icq.com/people/cmd.php?uin=[NUMEROICQ]&action=message">
Contact avec ICQ</a>
</source>

En remplaçant [NUMEROICQ] avec le véritable numéro ICQ de l'utilisateur.

==== Profils de Sites ====
Les blogueurs indiquent souvent leur identité sur les services d'hébergement de contenu en utilisant l'URL de leur page d'accueil, fil ou profil sur ces services. En les étiquetant comme des propriétés d'URL, ces facettes supplémentaires d'identité peuvent être aussi bien publiées dans hCard.

* <code>[http://del.icio.us delicious]:</code>
** <code><a class="url" href="http://del.icio.us/rbach">les liens de Robert Bachmann</a></code>
* <code>[http://flickr.com Flickr]:</code>
** <code><a class="url" href="http://flickr.com/photos/tantek/">Voir mes photos</a></code>
** <code><a class="url" href="http://flickr.com/people/tantek/">Profil Flickr</a></code>
* <code>[http://technorati.com/ Technorati]:</code>
** <code><a class="url" href="http://technorati.com/profile/tantek/">Profil Technorati</a></code>
* Complétez ici...
** ....

==== lister vos autres profils ====
Le cas le plus commun des sites listant d'autres profils sont les blogueurs qui listent leurs propres autres profils, ou un site permettant à un utilisateur de lister son profil sur ce site, et de lier vers ses autres profils. Du fait que l'auteur indique clairement que tous ces profils signifient la même personne, il est mieux de les marquer avec <code>rel="me"</code> de [[xfn-fr|XFN]] pour une consolidation d'identité explicite, par exemple si ces liens étaient sur le blog de Tantek ou d'autres profils de réseaux sociaux :

* <code>[http://del.icio.us delicious] :</code>
** <code><a class="url" href="http://del.icio.us/rbach">lien de Robert Bachmann</a></code>
* <code>mon [http://flickr.com Flickr] :</code>
** <code><a class="url" href="http://flickr.com/photos/tantek/">Voir mes photos</a></code>
** <code><a rel="me" class="url" href="http://flickr.com/people/tantek/">Profil Flickr</a></code>
* <code>[http://technorati.com/ Technorati] :</code>
** <code>my <a rel="me" class="url" href="http://technorati.com/profile/tantek/">Profil Technorati</a></code>
* Ajoutez-en plus ici...
** ....

Une telle consolidation d'identité explicite menée par l'utilisateur est aussi un bloc de construction-clé pour la [[social-network-portability-fr|portabilité-du-réseau-social]] qui est expliquée plus à fond dans le contexte des [[hcard-xfn-supporting-friends-lists-fr|listes-d'amis-supportant-hCard-et-XFN]].

=== Profils Canoniques sur les Sites ===
Les sites ont parfois différentes pages pour la "home" page d'une persone, et cette page profil de l'utilisateur.

Par exemple, Flick a :
* votre page d'accueil est sur une URL comme : <code>http://flickr.com/photos/</code> suivie par votre nom d'utilisateur, par ex. :
** http://flickr.com/photos/tantek/
* votre page profil est sur une URL comme <code>http://flickr.com/people/</code> suivie par votre nom d'utilisateur, par ex. :
** http://flickr.com/people/tantek/

En outre, les sites on souvent une URL <em>canonique</em> pour une personne et plusieurs URLs alternatives.

Comme cela a été noté au-dessus, les liens vers ces URLs à l'intérieur de hCards qui représentent ces personnes devraient avoir un nom de classe "url".

En outre, de tel(s) lien(s) dans les hCards vers l'URL canonique d'une personne sur ce site devrai(en)t aussi avoir le nom de classe "uid". Cette technique a été proposée par Ryan King au premier [[events/2007-08-28-social-network-portability-today|déjeuner Social Network Portability Today]].

Construit sur l'exemple en partant de la sections précédente :
* [http://flickr.com Flickr] :
** <code><a class="url" href="http://flickr.com/photos/tantek/">Voir mes photos</a></code>
** <code><a rel="me" class="url uid" href="http://flickr.com/people/tantek/">Profil Flickr</a></code>

Une telle propriété "url" + "uid" pourrait aussi être utilisé par un site sous l'URL [[OpenID-fr|OpenID]] de la personne.

=== Organisations et Départements ===
Les départements sont balisés en utilisant le nom de classe "organization-unit" à l'intérieur de l'élément "org", avec le nom de l'organisation "organization-name" spécifiquement balisé pur le distinguer du département :

<source lang=html4strict>
<div class="vcard">
<div class="org fn">
<div class="organization-name">Pages Jaunes France</div>
<div class="organization-unit">Apprentissage et Plomberie : Design Microformats</div>
</div>
</div>
</source>

Le département peut aussi faire partie de l'adresse, cas dans lequel vous pourrez vouloir le baliser explicitement comme "extended-address" (adresse étendue) en plus de "organization-unit".

<source lang=html4strict>
<div class="vcard">
<div class="adr">
<div class="org fn">
<div class="organization-name">Pages Jaunes France</div>
<div class="organization-unit extended-address">Apprentissage et Plomberie : Design Microformats</div>
</div>
<div class="street-address">7 avenue de la Cristallerie</div>
<span class="postal-code">92310</span>
<span class="locality">Sèvres</span>,
<abbr title="Ile de France" class="region">IDF</abbr>
</div>
</div>
</source>

Remarquez qu'en imbriquant le org dans l'adresse, nous avons évité de dupliquer le nom du département.

=== Listes d'Organisations ===
De la même façon que dans les [[hcard-examples-fr#R.C3.A9f.C3.A9rences_aux_Personnes_dans_les_Billets_de_Blog|listes de personnes]], les listes d'organisations (par exemple les groupes de musique) devraient utiliser une liste (non ordonnée à moins qu'il n'y ait une raison spécifique de la trier) avec des items de liste vers les pages d'accueil respectives des organisations.

par exemple ce simple [[posh-fr|CHIC]] :

<source lang=html4strict>
<ul>
<li>
<a href="http://microformateurs.org/">microformateurs.org</a>
</li>
<li>
<a href="http://technorati.com/">Technorati</a>
</li>
<li>
<a href="http://www.w3.org/">World Wide Web Consortium</a>
(W3C)
</a>
</li>
</ul>
</source>

peut être amélioré facilement avec hCard :

<source lang=html4strict>
<ul>
<li class="vcard">
<a class="fn org url" href="http://microformateurs.org/">microformateurs.org</a>
</li>
<li class="vcard">
<a class="fn org url" href="http://technorati.com/">Technorati</a>
</li>
<li class="vcard">
<a class="fn org url" href="http://www.w3.org/">World Wide Web Consortium</a>
(<span class="nickname">W3C</span>)
</a>
</li>
</ul>
</source>

== Exemples <nowiki>RFC 2426</nowiki> dans la hCard ==

voir : [[hcard-examples-rfc2426-fr|exemples hcard rfc2426]]

== Test de Casses ==
Ce sont des exemples [[hcard-fr|hCard]] qui ont été trouvés particulièrement utiles pour trouver des bugs dans les parseurs hCard (par ex. X2V).

=== Problème avec Information BDAY ===
cet exemple :

<source lang=html4strict>

<div class="bday">
<dt>Anniversaire</dt>
<dd>
<abbr class="value" title="1985-10-27T00:00:00Z">27 octobre 1985</abbr>
</dd>
</div>
</source>

devrait produire "BDAY:1985-10-27T00:00:00Z" mais il produit "BDAY:Birthday October 27\, 1985". [dans quoi ? cette déclaration apparaît sans sens]. Le fait intéressant est que le carnet d'adresses apple est encore en train de vouloir l'accepter de cette façon.

* Peut-être provoqué par une erreur de parsage HTML, parce que <code><dt></code> et <code><dd></code> ne sont pas permis en tant qu'enfants de <code><div></code>.
=== INSENSIBILITE à la casse des valeurs type ===

* "home" vs. "Home"

cet exemple fonctionne avec X2V :

<source lang=html4strict>
<div class="tel">
<dt>Téléphone (<span class="type">home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</source>

ceci non, mais le devrait. Mais au lieu de ça il devient simplement TEL sans un type dans la vcard

<source lang=html4strict>
<div class="tel">
<dt>Téléphone (<span class="type">Home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</source>

=== GEO parsing ===
la hCard suivante :

<source lang=html4strict>
<div class="vcard">
<span class="fn n">
<a class="url" href="http://t37.net">
<span class="given-name">Fréderic</span>
<span class="family-name">de Villamil</span>
</a>
</span>
<span class="nickname">neuro</span>
<a class="email" href="mailto:neuroNOSPAM@t37.net">
<span class="type">pref</span>erred<span> email</span>
</a>
<span class="org">Omatis</span>
<span class="adr">
<abbr class="type" title="dom">France</abbr>
<span class="type">home</span> address
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<span class="street-address">12 rue Danton</span>
<span class="locality">Le Kremlin-Bicetre</span>
<span class="postal-code">94270</span>
<span class="country-name">France</span>
</span>
<span class="geo">
<abbr class="latitude" title="48.816667">N 48° 81.6667</abbr>
<abbr class="longitude" title="2.366667">E 2° 36.6667</abbr>
</span>
</div>
</source>

devrait être traduite dans la vCard suivante :

<source lang=html4strict>
BEGIN:VCARD
VERSION:3.0
URL:http://t37.net
ORG:Omatis;;
NICKNAME:neuro
N:de Villamil;Frederic;;Mr.;
EMAIL;TYPE=INTERNET,PREF:neuroNOSPAM@t37.net
ADR;TYPE=HOME:;;12 rue danton;le Kremlin-Bicetre;;94270;France
GEO:48.816667;2.366667
END:VCARD
</source>

X2V (2005-12-18) échoue à cette heure pour parser/exporter la propriété GEO.

== Pages Apparentées ==
* [[hcard-examples-issues-fr|hcard-exemples-problématiques]]
{{hcard-related-pages-fr}}

receipt-formats

2015-10-03T09:34:46Z

Meterprikluts:

=Existing receipt formats=

==Contributors==
*Leif Arne Storset

==Quicken Interchange Format (QIF)==
Quicken Interchange Format (QIF) is an open specification for reading and writing financial data to media (i.e. files). It's unclear what invoice/receipt support is available, but invoice accounts are mentioned in the Wikipedia article. Further analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/QIF Wikipedia article]

==Open Financial Exchange==
Analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/Open_Financial_Exchange Wikipedia article]

==Google Checkout API==
Google Checkout offers an API for submitting invoice information. Two variants are provided: a simple HTML form method and a more sophisticated XML API.

===Simple HTML form===
*Item information
**name (required)
**description (required)
**quantity
**price (required)
**currency
*Shipping methods
**name
**price
**currency
**U. S. area where the method is available
*Tax
**U. S. state in which you charge tax
**[http://www.irstaxreliefsettlement.com/ tax rate]

===XML API===
*Shopping cart with item information and optional expiry date
**name
**description
**unit price
**quantity
**item id (in merchant's database)
**tax table to use
**whether the item is digitally delivered and how (e-mail or download key)
**other information
*Checkout-flow support
**tax tables
***whether shipping is taxed
***tax rate
***geographic area
**shipping options
***pickup
***flat-rate shipping
****price
****applicable areas
***calculated by custom web service
*Order-processing support
**how to convey authorization information

===Further reading===
*[http://code.google.com/apis/checkout/developer/google_checkout_html_api.html#checkout_api Google Checkout HTML API]
*[http://code.google.com/apis/checkout/developer/index.html#checkout_api Google Checkout XML API]

== See Also ==
* [[receipt]]

haudio

2015-10-03T09:31:05Z

Meterprikluts:

<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][http://www.irstaxreliefsettlement.com .]

=== 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://en.wikipedia.org/wiki/Category:Articles_with_hAudio_microformats Wikipedia] has 119,555 songs and albums marked up in hAudio format.
* [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]]