Microformats Wiki - User contributions [en]

HCalendar

2008-02-03T20:29:47Z

VanGore: rev, sorry

#REDIRECT [[Hcalendar]]

HCalendar

2008-02-03T20:27:02Z

VanGore: double redir

#REDIRECT [[hCalendar]]

project

2008-01-16T17:46:28Z

VanGore: hToDo

<h1>Project</h1>
{{formatset|Project}}
'''Please note : This spec is under construction. For now, it is only a dump of ideas.'''
Work to develop a format to describe the various aspects of a public project like open-source software or other kinds of artistic distributions. One if its primary intent is to allow robots to automatically classify projects in a freshmeat  manner by browsing the web.

[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)

== real world examples ==
Please document in [[project-examples]] per [[process]].

== existing formats ==
Please document in [[project-formats]].
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project-specific), [http://dannyayers.com:88/xmlns/hdoap/profile/index.xhtml hDOAP] is a [[poshformat]] projection of DOAP into HTML, deployed at [http://doapspace.org doapspace.org] and cited in the [http://www.w3.org/2003/g/data-view GRDDL namespace doc]
* [http://dannyayers.com:88/xmlns/project/index.htm RDF Project Vocabulary] (general purpose)
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]

== Related microformats ==
* [[hCalendar]] for timelines and milestones (?)
* [[hToDo]] TODOs
* Ressources
** [[hCard]] for attending/participating" people (staff)
** [[product]] for stuff(?)
*** [[rel-payment]]
* [[hReview]] for debriefing

== brainstorming ==
Please document in [[project-brainstorming]].

=== markup sample ===

<pre><nowiki>
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57">
<img class="logo" src="..." />
<span class="name">Microformats</span>
<span class="desc">An initiative to extract common patterns from POSH</span>

<h1>Some informations</h1>
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a>
<a href="..." rel="source">Here you can find its source code.</a>
<a href="..." rel="release">Get the releases.</a>
<-- Every hCard is looked as a participant [including venues? ] -->

<h1>Project's tags</h1>
<ul>
<li class="tag">open</li>
<li class="tag">format</li>
<li class="tag">standard</li>
</ul>
</div>
</nowiki></pre>

=== CSS selection specification ===

A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.

<pre><nowiki>
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).
A unique identifier for the project.
It is used to resolve name clashes.
.project .name : the content describes the project name.
Should not appear more that one time per project.
.project IMG.logo : the src is a link to the logo.
Can have different sizes with by adding "low | mid | high" classes.
.project A[@rel=home] : a project's home page
.project A[@rel=source] : a link to the project's source.
If it is a scm, it is generally solved by using different uris.
Like git:// or bzr:// or http+git://
.project A[@rel=release] : the linked pages contains file releases.
This page can contain hRelease microformat.
.project A[@rel=...] : many extensions can be imagined, like :
"blog | wiki | parent-project | ..."
.project .tag : the content describes a project tag. You can
have as many as you wish.
</nowiki></pre>

== to-do ==
* Lots of discussion I guess, to satisfy different kinds of projects
* Semantic approval of experts

== Notes ==
Please, keep the format simple. Unlike hCard, it doesn't follow an existing standard, which permits to keep it simple. I'd much more prefer to develop sub-standards instead of being verbose. For example, the uuid:.. or scm:// ones.

== Related ideas ==
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.

project

2008-01-14T18:37:54Z

VanGore: /* Related microformats */ rel-payment

<h1>Project</h1>
{{formatset|Project}}
'''Please note : This spec is under construction. For now, it is only a dump of ideas.'''
Work to develop a format to describe the various aspects of a public project like open-source software or other kinds of artistic distributions. One if its primary intent is to allow robots to automatically classify projects in a freshmeat  manner by browsing the web.

[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)

== Existing pattern ==
existing pattern for projects
* [http://usefulinc.com/doap/ DOAP: Description of a Project]
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]

== Related microformats ==
* [[hCalendar]] for timelines and milestones (?)
* Ressources
** [[hCard]] for attending/participating" people (staff)
** [[product]] for stuff(?)
*** [[rel-payment]]
* [[hReview]] for debriefing

== possible code example ==

<pre><nowiki>
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57">
<img class="logo" src="..." />
<span class="name">Microformats</span>
<span class="desc">An initiative to extract common patterns from POSH</span>

<h1>Some informations</h1>
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a>
<a href="..." rel="source">Here you can find its source code.</a>
<a href="..." rel="release">Get the releases.</a>
<-- Every hCard is looked as a participant [including venues? ] -->

<h1>Project's tags</h1>
<ul>
<li class="tag">open</li>
<li class="tag">format</li>
<li class="tag">standard</li>
</ul>
</div>
</nowiki></pre>

== CSS selection specification ==

A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.

<pre><nowiki>
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).
A unique identifier for the project.
It is used to resolve name clashes.
.project .name : the content describes the project name.
Should not appear more that one time per project.
.project IMG.logo : the src is a link to the logo.
Can have different sizes with by adding "low | mid | high" classes.
.project A[@rel=home] : a project's home page
.project A[@rel=source] : a link to the project's source.
If it is a scm, it is generally solved by using different uris.
Like git:// or bzr:// or http+git://
.project A[@rel=release] : the linked pages contains file releases.
This page can contain hRelease microformat.
.project A[@rel=...] : many extensions can be imagined, like :
"blog | wiki | parent-project | ..."
.project .tag : the content describes a project tag. You can
have as many as you wish.
</nowiki></pre>

== to-do ==

* Lots of discussion I guess, to satisfy different kinds of projects
* Semantic approval of experts

== Notes ==

Please, keep the format simple. Unlike hCard, it doesn't follow an existing standard, which permits to keep it simple. I'd much more prefer to develop sub-standards instead of being verbose. For example, the uuid:.. or scm:// ones.

== Related ideas ==

* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.

project

2008-01-14T18:32:14Z

VanGore: Existing pattern, Related microformats

<h1>Project</h1>
{{formatset|Project}}
'''Please note : This spec is under construction. For now, it is only a dump of ideas.'''
Work to develop a format to describe the various aspects of a public project like open-source software or other kinds of artistic distributions. One if its primary intent is to allow robots to automatically classify projects in a freshmeat  manner by browsing the web.

[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)

== Existing pattern ==
existing pattern for projects
* [http://usefulinc.com/doap/ DOAP: Description of a Project]
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]

== Related microformats ==
* [[hCalendar]] for timelines and milestones (?)
* Ressources
** [[hCard]] for attending/participating" people (staff)
** [[product]] for stuff(?)
* [[hReview]] for debriefing

== possible code example ==

<pre><nowiki>
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57">
<img class="logo" src="..." />
<span class="name">Microformats</span>
<span class="desc">An initiative to extract common patterns from POSH</span>

<h1>Some informations</h1>
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a>
<a href="..." rel="source">Here you can find its source code.</a>
<a href="..." rel="release">Get the releases.</a>
<-- Every hCard is looked as a participant [including venues? ] -->

<h1>Project's tags</h1>
<ul>
<li class="tag">open</li>
<li class="tag">format</li>
<li class="tag">standard</li>
</ul>
</div>
</nowiki></pre>

== CSS selection specification ==

A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.

<pre><nowiki>
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).
A unique identifier for the project.
It is used to resolve name clashes.
.project .name : the content describes the project name.
Should not appear more that one time per project.
.project IMG.logo : the src is a link to the logo.
Can have different sizes with by adding "low | mid | high" classes.
.project A[@rel=home] : a project's home page
.project A[@rel=source] : a link to the project's source.
If it is a scm, it is generally solved by using different uris.
Like git:// or bzr:// or http+git://
.project A[@rel=release] : the linked pages contains file releases.
This page can contain hRelease microformat.
.project A[@rel=...] : many extensions can be imagined, like :
"blog | wiki | parent-project | ..."
.project .tag : the content describes a project tag. You can
have as many as you wish.
</nowiki></pre>

== to-do ==

* Lots of discussion I guess, to satisfy different kinds of projects
* Semantic approval of experts

== Notes ==

Please, keep the format simple. Unlike hCard, it doesn't follow an existing standard, which permits to keep it simple. I'd much more prefer to develop sub-standards instead of being verbose. For example, the uuid:.. or scm:// ones.

== Related ideas ==

* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.

Template:formatset

2008-01-14T18:11:07Z

VanGore: border E8E8E8

<div style=" float: right; width: 250px; padding: 3px; margin-left: 2em; border: 1px solid #E8E8E8; background-color: #EDEDED; ">This format has got the [[process#Pages to create|process-status]] already. <small>Start always with number one.</small>
The '''{{{1}}}-*'''
# [[{{{1}}}-examples|*examples]]
# [[{{{1}}}-formats|*formats]]
# [[{{{1}}}-brainstorming|*brainstorming]]
# [[h{{{1}}}]]
# [[{{{1}}}-faq|faq]]
# [[{{{1}}}-implementations|*implementations]]
Please read [[process#Pages to create|process]] '''first''', before creating new pages!</div>

User:VanGore

2007-12-16T20:04:55Z

VanGore:

= Klaus Mueller =
... for more see [http://klml.de klml.de].

I like microformats!

== Favourite ==
;[[hListing]]
:I'm not a neocon, but I belief free markets can make a better world. I mean real free markets, not the monopolitic farce already existing. All the tiny great producers should deal with the consumers. Without all the big traders. I want to have hListing for the [http://www.lasterdienst.de/html/sortiment_komplett.htm Lasterdienst (engl: viceservice) ;)]

== Todo & Notice ==

== Test ==
{{Status|'||||}}
{{Status|||'||}}

cite-formats

2007-12-16T15:59:49Z

VanGore: revandal

#REDIRECT [[citation-formats]]

cite-rel-profile

2007-12-14T11:13:10Z

VanGore: rev

==cite-rel Meta Data Profile==
===Authors===
* Eran Globen
* Ryan King

===Status===
This document and the profile included in it are still in draft status. As such they are subject to change and modification at any time.

===Profile===
The authors believe this profile provides a set of class attribute values sufficient to be used in working implementations of cit-rel. This profile is still in draft status and therefore is subject to change as cite-rel evolves.
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a> This meta data profile defines
some 'class' attribute values (class names) and their meanings as suggested
by a <a href="http://www.w3.org/TR/WD-htmllink-970328#profile">draft of
"Hypertext Links in HTML"</a>.</p>

<p>All values are defined according to the semantics defined in the
<a href="http://microformats.org/wiki/cite-rel">cite-rel specification</a></p>

<dl>
<dt>via</dt>
<dd>
Indicates a hat-tip or via link.
</dd>
<dt>rev-reply</dt>
<dd>
Indicates a reply relationship.
The linking document is in reply to the target document.
</dd>
<dt>rev-forward</dt>
<dd>
Indicates forwarding or re-publishing a document.
The linking document forwards the target document.
</dd>
<dt>rev-update</dt>
<dd>
Indicates an updated version.
The linking document is an update to the target document.
</dd>
<dt>rel-reply</dt>
<dd>
Indicates a reply relationship.
The target document is in reply to the linking document.
</dd>
<dt>rel-forward</dt>
<dd>
Indicates forwarding or re-publishing a document.
The target document forwards the linking document.
</dd>
<dt>rel-update</dt>
<dd>
Indicates an updated version.
The target document is an update to the linking document.
</dd>
</dl>
</dd>
</dl>
</pre>

User:VgfZ4x

2007-12-11T22:57:08Z

VanGore: vandal

User:MrcW1k

2007-12-09T14:41:36Z

VanGore: vandal

User:NqgFtn

2007-12-05T21:09:23Z

VanGore:

start-simple

2007-12-02T13:14:02Z

VanGore: revert spam

= Simple Start (Draft) =

Note: Name Change, "Start Simple" is a Trademark in the Technology Sector (usability).

<em>Starting simple</em> means solving a specific, immediate problem with your efforts. Often, the simplest possible solution turns out to be the most effective solution. No more work is needed.

The Microformats [[process]] emphasises [[reuse | reusing]] previous efforts as much as possible, enabling greater efficacy in existing standards and their semantics. Starting simple keeps the focus on what can be accomplished effectively and immediately, rather than spending additional time chasing conceptual or theoretical chimeras; possibilities that <em>might</em> have a general impact when implementing the standard, but then again <em>might not</em>.

Microformats should remain as simple as possible for as long as possible, collecting additional element semantics <em>only</em> when a significant practical need has been demonstrated for such additions.

=== Case Study - hAtom ===

* Removing Atom specific person/author constructs in favour of hCards
* Not dealing with feed level metadata - leave this to the web page context

Template:formatset

2007-12-02T02:05:10Z

VanGore: smaller

<div style=" float: right; width: 250px; padding: 3px; border: 1px solid green; background-color: #EDEDED; ">This format has got the [[process#Pages to create|process-status]] already. <small>Start always with number one.</small>
The '''{{{1}}}-*'''
# [[{{{1}}}-examples|*examples]]
# [[{{{1}}}-formats|*formats]]
# [[{{{1}}}-brainstorming|*brainstorming]]
# [[h{{{1}}}]]
# [[{{{1}}}-faq|faq]]
# [[{{{1}}}-implementations|*implementations]]
Please read [[process#Pages to create|process]] '''first''', before creating new sites!</div>

bankaccount-brainstorming

2007-12-02T01:59:00Z

VanGore:

{{formatset|bankaccount}}
<h1>Bankaccount-Brainstorming</h1>

== The Problem ==
A microformat for account numbers would allow people to act on the data in a page and avoid the terrible consequences of getting a bank account number wrong!

== To be incorporated ==
* [[rel-payment]] for the links pointing on this sites.
* [[currency-proposal]] for bills

bankaccount-brainstorming

2007-12-02T01:56:30Z

VanGore:

Template:formatset

2007-12-02T01:43:52Z

VanGore: + color, + the "no good idea h"

<div style=" float: right; width: 350px; padding: 3px; border: 1px solid green; background-color: #FAFAFA; ">This format has got the [[process#Pages to create|process-status]] already. Start always with number one.
# [[{{{1}}}-examples]]
# [[{{{1}}}-formats]]
# [[{{{1}}}-brainstorming]]
# [[h{{{1}}}]]
# [[{{{1}}}-faq]]
# [[{{{1}}}-examples]]
# [[{{{1}}}-implementations]]
# [[{{{1}}}-brainstorming]]
Please read [[process#Pages to create|process]] '''first''', before creating new sites!</div>

bankaccount-examples

2007-12-02T01:39:33Z

VanGore: formatset

{{formatset|bankaccount}}
<h1>Bank Account Examples</h1>

Per the microformats [[process]] this is an [[examples]] page documenting existing real world examples of bank account references published on the Web. Next steps are to research [[bankaccount-formats]] and then (only ''after'' that), proceed with [[bankaccount-brainstorming]]. Only URLs to actual bank account numbers/references please.

== Contributors ==

* Klaus Muller
* Guillaume Lebleu
* Corsin Camichel

== Examples ==

=== Amazon.de (Germany) ===

[http://www.amazon.de/gp/help/seller/shipping.html?ie=UTF8&seller=A11MRI5N4LBZ82#policies Amazon.de]

<pre>
<br>
Unsere deutsche Bankverbindung:<br>
<br>
Empire Merchandising GmbH<br>
Volksbank Darmstadt/Deutschland<br>
Bankleitzahl (BLZ) 508 900 00<br>
Konto-Nr. 1757814<br>

BIC: GENODEF1VBD<br>
IBAN: DE 0750 8900 0000 0175 7814<br>
<br>
</pre>

This bank account reference is composed of:
* Bank account name (i.e. the name of the bank account, typically the same as the name of the bank account owner)
* Name and partial address of the bank maintaining the account
* [http://de.wikipedia.org/wiki/Bankleitzahl Bankleitzahl]: literaly, number that leads to the bank. A number issued by the Bundesbank to a bank or one of its branches (i.e. to a bank account issuer). It is composed of:
** 3 digit identifying the local Bundesbank code (the first digit is the clearing region).
** 1 digit identifying the bank group (ex. savings bank, commercial bank, etc.)
** 4 digits identifying the bank/branch
* Actual account number issued by the bank
* BIC: a number issued by SWIFT to a bank or one of its branches (i.e. to a bank account number issuer). See [http://www.swift.com/biconline/ SWIFT BIConline]
* IBAN: this is actually a [http://www.ecbs.org/iban.htm standardized] country specific concatenation/serialization of various account informations that together guarantees the account number uniqueness worldwide for use in any transaction, international or not. Note that even though IBAN is globally unique, the BIC must be provided in financial messages. For Germany, the IBAN is composed of:
** country code
** 2 check digits
** Bankleitzahl
** Account number

=== neckermann.de (Germany) ===

A link cannot be provided but if you want to see the sample below, go to the Web site and click Impressum.

<pre>
<p class="copytext">Bankverbindung: neckermann.de GmbH, 60279 Frankfurt.
<br>Bayerische Landesbank, Kto. 50 55 400, BLZ 700 500 00</p>
</pre>

=== Christchurch city (New Zealand) ===

http://www.ccc.govt.nz/QuickAnswers/BylawsLicensing/Miscellaneous/F3635.asp

=== EDPNet (Belgium) ===

http://en.wiki.edpnet.be/index.php/What_is_the_bank_account_number_of_EDPnet

=== csa.gov.uk (UK) ===

http://www.csa.gov.uk/en/employers/payment.asp

=== Birmingham.gov.uk ===

http://www.birmingham.gov.uk/GenerateContent?CONTENT_ITEM_ID=557&CONTENT_ITEM_TYPE=0&MENU_ID=301

=== Bank of America Web banking (not from the public Web) ===

<pre>
<A href="/cgi-bin/ias/15_LXhvFyxHfHakKPIj_BukEUpZkH_aOGHTJAKA39e163375/2/WelcomeControl?action=account_details&accountIndex=0" class=linknormal>

Checking-8723</A>
</pre>

Just putting this one here to show an example of obfuscated bank account number. The actual account identifier used by the server is "0" (in combination of the user session), which is really a transient identifier. Another, user-friendly, identifier is presented to the user composed of the last four digits of the account number and the type of the account.

=== Haas School (USA) ===

http://www.haas.berkeley.edu/EWMBA/finaid/BillingPayOptions#WireTransfer

<pre>
<blockquote>

<p> <strong>University's bank name</strong>: Bank of America, NA<br />
<strong>Bank routing number</strong>: 0260-0959-3 (wire transfer only)<br />
<strong>Bank account number</strong>: 0175380001<br />
<strong>Bank address</strong>: 1655 Grant Street; Concord, CA 94520<br />

<strong>Bank SWIFT code</strong>: BOFAUS 3N<br />
<strong>Bank CHIPS Address</strong>: 0959<br />
<strong>Beneficiary</strong>: Regents of the University of California<br />
<strong>Reference</strong>: The eight-digit UC Berkeley Student ID Number and student name. </p>
</blockquote>

</pre>

=== Hostpoint AG (Switzerland) ===

http://hostpoint.ch/ueber-hostpoint/kontakt/bankverbindungen (includes examples for Germany, France and Austria as well)
<pre>
Credit Suisse
<br>
8640 Rapperswil-Jona
<br>
Schweiz
<br>
<br>
IBAN: CH95 0483 5095 7545 7100 1
<br>
BIC: CRESCHZZ80A
<br>
BC (BLZ): 4835
<br>
<br>
Konto-Nr. 957545-71-1
</pre>

=== aerzte-ohne-grenzen ===
http://www.aerzte-ohne-grenzen.de/Spenden/Spenden/Spendenkonto.php

<pre>
<div id="mCont">
<div id="mLead">Spendenkonto 97 0 97<br>
Bankleitzahl 370 205 00<br>
Bank für Sozialwirtschaft
</div>
<...>
<p><strong>Für Überweisungen aus dem Ausland: </strong></p>
<p>IBAN: DE72 3702 0500 0009 7097 00</p>
<p> SWIFT-BIC: BFSWDE33</p><p>
</p>
</pre>

Template:Status

2007-12-02T01:38:13Z

VanGore: revert my own

<div style=" float: right; width: 200px; padding: 3px; border: 1px solid green; ">This item has got the [[process]]-status:
* {{{1}}}''problem statement''{{{1}}}
* {{{2}}}''research/discussion''{{{2}}}
* {{{3}}}''proposal/draft''{{{3}}}
* {{{4}}}''standard''{{{4}}}</div>

Template:formatset

2007-12-02T01:37:46Z

VanGore:

<div style=" float: right; width: 350px; padding: 3px; border: 1px solid green; ">This format has got the [[process#Pages to create|process-status]] already:
# [[{{{1}}}-examples]]
# [[{{{1}}}-formats]]
# [[{{{1}}}-brainstorming]]
# [[{{{1}}}]]
# [[{{{1}}}-faq]]
# [[{{{1}}}-examples]]
# [[{{{1}}}-implementations]]
# [[{{{1}}}-brainstorming]]
Please read [[process#Pages to create|process]] '''first''', before creating new sites!</div>

Template:Status

2007-12-02T01:35:49Z

VanGore:

process-de

2007-12-02T01:09:39Z

VanGore: interwiki

Bitte lesen Sie die [[introduction-de|Einführung]], falls dies Ihr erster Besuch ist.

<h1>Sie wollen also ein neues microformat entwickeln?</h1>
{{TOC-right}}

== Grundlegende vorausgesetzte Kenntnisse ==
Bevor Sie beginnen beachten Sie bitte folgendes:

# Bringen Sie Ihre persönliche Seite in den [[POSH]]-Standard.
# Fügen Sie Ihrer eigenen Seite <em>existierende</em> microformate wie [[hcard-de|hCard]] für Kontaktdaten, [[hcalendar|hCalendar]] für Termine, [[hatom|hAtom]] regelmäßig aktualisierte Inhlate (z.B. blogs) hinzu. Auf der Seite [[get-started-de]] erhalten Sie mehr spezifische Beispiele für Microformate.

Das hilft Ihnen mit dem [[POSH-de|POSH-Konzept]] und [[microformats-de|Mikroformaten]] vertrauter und erfahrener zu werden. Diese praktischen Erfahrungen werden Ihnen helfen neue Mikroformate zu entwickeln.

Dann fragen Sie sich selbst:

== Warum? ==
Als erstes brauchen Sie eine existierende Problemstellung welche gelöst werden soll. Kein Problem, kein Microformat.!

Dann wenn Sie "Ihr" Problem definiert haben fragen Sie sich selbst: 'gibt es eine einfachere Problemstellung?'. Ist dem so, so sollten Sie erst dieses lösen. Wir wollen die einfachste Form zuerst lösen und erst dann weitere komplexe Problemstellungen lösen.

Weiter sollten Sie recherchieren ob jemand anderes die gleiche Problemstellung wie Sie definiert hat. Stellen Sie dann fest das Sie immer noch ein ungelöstes Problem haben, schreiben Sie an die [http://microformats.org/mailman/listinfo/microformats-new/ microformats-new] Mailing-Liste oder wenden Sie sich an einen anderen Diskussionskanal ([http://microformats.org/discuss/ microformats.org/discuss]).

So stellen wir sicher das alle Interessierten an der Diskussion teilnehmen. Bitte fragen sie '''<span style="text-transform: uppercase;">erst</span>''' nach bevor Sie eine Wikiseite eröffnen. Das Wiki dient hier nicht als zentraler "Notizzettel". Wenn Sie sich nicht in der Lage sehen Ihre Problemstellung darzustellen und Sie meinen einen langen Text schreiben zu müssen, kann das daran liegen das Sie ein großes Problem lösen wollen - und dann gilt der obige Absatz.

== Darstellung aktueller Sachverhalte ==
Zeigen Sie Beispiele konkrete Beispiele. [[why-examples-de|Warum man erst Beispiele benötigt?]]

Es gibt das Konzept [http://ifindkarma.typepad.com/relax/2004/12/microformats.html paving the cowpaths] - um mit der Entwicklung zu beginnen muss man erst den Weg dahin finden.

Ihre Beispiele sollten Seiten sein, die Daten und Informationen enthalten welche Sie mit Mikroformaten strukturieren wollen. Aus diesen Seiten sollten Markup-Beispiele aufzeigen und Lösungen vorschlagen.

Diese Beispiele sollten öffentlich zugänglich sein, vorzugsweise dann im Wiki, da so eine gemeinsame Bearbeitung erst möglich ist.


Die Seite [[reviews-formats]] ist in diesem Fall ein gutes Beispiel über die notwendige Recherchearbeit vor der Erstellung von Mikroformaten. Vor der Entwicklung von [[hreview|hReview]] wurden dort erst die Struktur und Arbeitsweise von Bewertungseiten untersucht und dann eine Analysen der darin enthalten Schemata dargestellt.

Es ist möglich das sie während der Recherche auf "Ihr" Problem treffen der sogar auf jemanden der dieses gelöst hat

Das wichtigste ist ein Dialog mit Anderen die an das selbe Problem herangehen. Wir möchten keine Mauern zwischen konkurrierenden Gruppen ziehen, welche am gleichen Problem arbeiten; alle sollen an geeigneten Lösungen zusammen arbeiten die möglichst viele Anforderungen abdecken.

== Vorschlag eines Microformat ==
Am wichtigsten ist: <strong style="text-transform:uppercase;">machs nicht!</strong>

Es gibt weiter Dinge die man vor einer Neuentwicklung versuchen sollte:
# Existiert bereits ein standard Element in XHTML
# Existiert bereits Zusammenstellungen auf XHTML-Basis
# Wenn die Antwort hier zwei mal "Nein" war, dann kann man über eine neues Micorformat diskutieren.

Weiteres zum Thema semantisches XHTML, Beispiele und XHTML-Zusammenstellungen gibt es auf [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML].

Weiter gilt es die [[microformats#the microformats principles|microformats Richtlinien]] einzuhalten.

Haben Sie diese Verstanden sollten Sie sich selbst fragen ob es "etablierte, interoperabel eingeführte Standards welche das Problem bereits angehen, gibt". So wurde hCard and hCalendar auf den IETF Standards für vCard und iCal aufgebaut.

{{Interwiki|
* [[process|Englisch]]
* [[process-fr|Französich]]}}

Template:Interwiki

2007-12-02T01:08:48Z

VanGore: typo nofloat

<div style=" padding: 3px; border: 1px solid green; ">This article is also available in the following lanuages:
{{{1}}}</div>

Template:Status

2007-12-02T01:05:31Z

VanGore: - wrong style

Template:Interwiki

2007-12-02T01:05:07Z

VanGore:

<div style=" float: right; width: 200px; padding: 3px; border: 1px solid green; ">This article is availible in the following lanuages:
{{{1}}}</div>

Template:Status

2007-12-02T00:39:56Z

VanGore: border, list, float

<div style=" list-style-type: none ; float: right; width: 200px; padding: 3px; border: 1px solid green; ">This item has got the [[process]]-status:
* {{{1}}}''problem statement''{{{1}}}
* {{{2}}}''research/discussion''{{{2}}}
* {{{3}}}''proposal/draft''{{{3}}}
* {{{4}}}''standard''{{{4}}}</div>

User:VanGore

2007-12-02T00:29:45Z

VanGore: status test

= Klaus Mueller =
... for more [http://klml.de klml.de]

== Todo & Notice ==

== Test ==
{{Status|'||||}}
{{Status|||'||}}

Template:Status

2007-12-02T00:27:53Z

VanGore:

<div>This item has got the [[process]]-status: {{{1}}}''problem statement''{{{1}}} → {{{2}}}''research/discussion''{{{2}}} → {{{3}}}''proposal/draft''{{{3}}} → {{{4}}}''standard''{{{4}}}</div>

bankaccount-examples

2007-12-01T23:32:29Z

VanGore: "div"ed example

<h1>Bank Account Examples</h1>

Per the microformats [[process]] this is an [[examples]] page documenting existing real world examples of bank account references published on the Web. Next steps are to research [[bankaccount-formats]] and then (only ''after'' that), proceed with [[bankaccount-brainstorming]]. Only URLs to actual bank account numbers/references please.

== Contributors ==

* Klaus Muller
* Guillaume Lebleu
* Corsin Camichel

== Examples ==

=== Amazon.de (Germany) ===

[http://www.amazon.de/gp/help/seller/shipping.html?ie=UTF8&seller=A11MRI5N4LBZ82#policies Amazon.de]

<pre>
<br>
Unsere deutsche Bankverbindung:<br>
<br>
Empire Merchandising GmbH<br>
Volksbank Darmstadt/Deutschland<br>
Bankleitzahl (BLZ) 508 900 00<br>
Konto-Nr. 1757814<br>

BIC: GENODEF1VBD<br>
IBAN: DE 0750 8900 0000 0175 7814<br>
<br>
</pre>

This bank account reference is composed of:
* Bank account name (i.e. the name of the bank account, typically the same as the name of the bank account owner)
* Name and partial address of the bank maintaining the account
* [http://de.wikipedia.org/wiki/Bankleitzahl Bankleitzahl]: literaly, number that leads to the bank. A number issued by the Bundesbank to a bank or one of its branches (i.e. to a bank account issuer). It is composed of:
** 3 digit identifying the local Bundesbank code (the first digit is the clearing region).
** 1 digit identifying the bank group (ex. savings bank, commercial bank, etc.)
** 4 digits identifying the bank/branch
* Actual account number issued by the bank
* BIC: a number issued by SWIFT to a bank or one of its branches (i.e. to a bank account number issuer). See [http://www.swift.com/biconline/ SWIFT BIConline]
* IBAN: this is actually a [http://www.ecbs.org/iban.htm standardized] country specific concatenation/serialization of various account informations that together guarantees the account number uniqueness worldwide for use in any transaction, international or not. Note that even though IBAN is globally unique, the BIC must be provided in financial messages. For Germany, the IBAN is composed of:
** country code
** 2 check digits
** Bankleitzahl
** Account number

=== neckermann.de (Germany) ===

A link cannot be provided but if you want to see the sample below, go to the Web site and click Impressum.

<pre>
<p class="copytext">Bankverbindung: neckermann.de GmbH, 60279 Frankfurt.
<br>Bayerische Landesbank, Kto. 50 55 400, BLZ 700 500 00</p>
</pre>

=== Christchurch city (New Zealand) ===

http://www.ccc.govt.nz/QuickAnswers/BylawsLicensing/Miscellaneous/F3635.asp

=== EDPNet (Belgium) ===

http://en.wiki.edpnet.be/index.php/What_is_the_bank_account_number_of_EDPnet

=== csa.gov.uk (UK) ===

http://www.csa.gov.uk/en/employers/payment.asp

=== Birmingham.gov.uk ===

http://www.birmingham.gov.uk/GenerateContent?CONTENT_ITEM_ID=557&CONTENT_ITEM_TYPE=0&MENU_ID=301

=== Bank of America Web banking (not from the public Web) ===

<pre>
<A href="/cgi-bin/ias/15_LXhvFyxHfHakKPIj_BukEUpZkH_aOGHTJAKA39e163375/2/WelcomeControl?action=account_details&accountIndex=0" class=linknormal>

Checking-8723</A>
</pre>

Just putting this one here to show an example of obfuscated bank account number. The actual account identifier used by the server is "0" (in combination of the user session), which is really a transient identifier. Another, user-friendly, identifier is presented to the user composed of the last four digits of the account number and the type of the account.

=== Haas School (USA) ===

http://www.haas.berkeley.edu/EWMBA/finaid/BillingPayOptions#WireTransfer

<pre>
<blockquote>

<p> <strong>University's bank name</strong>: Bank of America, NA<br />
<strong>Bank routing number</strong>: 0260-0959-3 (wire transfer only)<br />
<strong>Bank account number</strong>: 0175380001<br />
<strong>Bank address</strong>: 1655 Grant Street; Concord, CA 94520<br />

<strong>Bank SWIFT code</strong>: BOFAUS 3N<br />
<strong>Bank CHIPS Address</strong>: 0959<br />
<strong>Beneficiary</strong>: Regents of the University of California<br />
<strong>Reference</strong>: The eight-digit UC Berkeley Student ID Number and student name. </p>
</blockquote>

</pre>

=== Hostpoint AG (Switzerland) ===

http://hostpoint.ch/ueber-hostpoint/kontakt/bankverbindungen (includes examples for Germany, France and Austria as well)
<pre>
Credit Suisse
<br>
8640 Rapperswil-Jona
<br>
Schweiz
<br>
<br>
IBAN: CH95 0483 5095 7545 7100 1
<br>
BIC: CRESCHZZ80A
<br>
BC (BLZ): 4835
<br>
<br>
Konto-Nr. 957545-71-1
</pre>

=== aerzte-ohne-grenzen ===
http://www.aerzte-ohne-grenzen.de/Spenden/Spenden/Spendenkonto.php

<pre>
<div id="mCont">
<div id="mLead">Spendenkonto 97 0 97<br>
Bankleitzahl 370 205 00<br>
Bank für Sozialwirtschaft
</div>
<...>
<p><strong>Für Überweisungen aus dem Ausland: </strong></p>
<p>IBAN: DE72 3702 0500 0009 7097 00</p>
<p> SWIFT-BIC: BFSWDE33</p><p>
</p>
</pre>

product-examples

2007-11-25T23:05:42Z

VanGore: /* Existing schema */NACE

= Product Examples =

This is an exploratory page to document product examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed product microformat.

== Authors ==

* Aaron Gustafson
* Adam Craven
* Craig Cook
* Ronnos

== Examples ==

=== Amazon ===

==== CD ====
* buying - contains unstructured data
** album (product name)
** artist
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** release date
** # of discs
** label
** ASIN

==== Book ====
Please also see [[book-info-formats]] and [[book-info-examples]].
* buying - contains unstructured data
** title (product name)
** format
** author
* prodImage
* listprice
* price (actual price '''and''' "you save")
* productDetails - contains unstructured data
** format
** page count
** publisher
** publication date
** language
** ISBN
** dimensions
** weight

==== Video Game ====
* buying - contains unstructured data
** title (product name)
** publisher
** platform
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (game info)
** ESRB Rating
** genre
* productDetails - contains unstructured data
** ASIN
** SKN
** release date

==== Outdoor Product ====
* buying - contains unstructured data
** product name
** brand
* prodImage
* listprice
* price (actual price '''and''' "you save")
* bucket (product features)
* productDetails - contains unstructured data
** dimensions
** weight
** ASIN
** model number

=== Buy.com ===

==== CD ====
* productTitle
* artist (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** label
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Book ====
* productTitle
* author (unstructured)
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** ISBN
** publication date
** publisher
** dimensions
** SKU
** item #
* prodInfoSec_1 - additional details
** description

==== Video Game ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** actual price
** shipping
** total (augmented by quantity)
* prodPriceSec_2 - actually product details
** format
** release date
** publisher
** sku
* prodInfoSec_1 - additional details
** description

==== TV ====
* productTitle
* image (unstructured)
* mainPricSection - contains unstructured data
** list price (msrp)
** you save
** price
** shipping
** actual price
* prodPriceSec_2 - actually product details
** manufacturer (brand)
** part #
** SKU
** item #
* prodInfoSec_1 - additional details
** description
* prodInfoSec_2 - tech specs (unstructured)
** type (product description summary)
** display area
** native resolution
** contrast ratio
** viewing angles
** power
** weight
** warranty
** etc.

=== Ben Sherman ===

==== Clothes ====

Link to product rather than actual product immediately available for sale. Personally marked-up and used rel-product ideas to link to the shop.

* Image
** Thumbnail
* Product
** Type
** Title
* Properties
** Colour
* Link
** Buy this Online (rel=product)

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<img src="#" alt="polo shirt" class="product-thumb" />
<h3 class="product-type">Polo Shirt</h3>
<h4 class="product-title">Coxmoor</h4>
<p class="p-v"><span class="property">Colour:</span> <span class="value">289 Rush</span></p>
<p><a href="poloshirt/coxmoor/" title="Buy This Online" rel="product">Buy This Online</a></p>
</div>
</nowiki></pre>

==== CDs ====

Additionally the site has links to products on Amazon.

* Image
** Thumbnail
* Product
** Title
* Properties
** Artist
* Link
** Buy this Online (rel=product)
* Currency implementation

'''Mark-up:'''

<pre><nowiki>
<div class="hproduct">
<a href="#" rel="product">
<img src="assets/images/timeline/amazon/small-faces.gif" alt="Small Faces Album" class="product-thumb" />
</a>
<h3 class="product-title"><a href="#" rel="product">Ogdens' Nut Gone Flakes</a></h3>
<h4 class="p-v"><span class="property artist">Small Faces</span></h4>
<p class="product-buy"><a href="#" title="Buy this online" rel="product">Buy from Amazon</a></p>
<p class="money"><abbr class="currency" title="GBP">£</abbr><span class="amount">6.99</span></p>
</div>
</nowiki></pre>

The use of [[hproduct-brainstorming#Non-visible_property_names|Non-visible property names]] made it possible to have an invisible property of 'artist'. Having 'Artist: Small Faces' was not in the visual specification of the Ben Sherman site.

=== Atomic Books ===

==== Books ====
* Image
** Thumbnail
* Product
** Title (productname)
** Author
** Publisher
* Properties
** Page Count
** Size
* Notes
* Date Published (can be in future to indicate "not yet released")

=== Walmart ===

=== Cell phone ===
* Productname
* Photo's (Photo)
** Productimage (Pdi)
** Thumbnails (PdiThumbs)
* Price (PriceInfo)
** Productprice (ProdPrice)
** Shipping options (Ship)
** Availability (Avail)
** Pricing options (PriceOptions)
* Description (Description)
* Features
* Included Accessories

==Existing schema==
* Per [http://en.wikipedia.org/wiki/Global_Trade_Item_Number Wikipedia: Global Trade Item Number]:
<blockquote>Global Trade Item Number (GTIN) is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council).</blockquote>
: [[User:AndyMabbett|Andy Mabbett]] 09:14, 31 Aug 2007 (PDT)
* Using [http://en.wikipedia.org/wiki/Nomenclature_Generale_des_Activites_Economiques_dans_L%60Union_Europeenne NACE] for vendors or product-categories. [[User:VanGore|vanGore]] 15:05, 25 Nov 2007 (PST)

== See Also ==
* [[currency]]
* [[hproduct-brainstorming|hProduct Brainstorming]]
* [[hproduct-feedback|hProduct Discussion]]
* [[hproduct-formats|hProduct Formats]]
* [[hproduct-challenges|hProduct Challenge Examples]]

process-de

2007-11-19T23:12:38Z

VanGore: typos, ein bischen weiter

process-de

2007-11-15T00:26:39Z

VanGore: sorry 2 typos

process-de

2007-11-15T00:25:28Z

VanGore: first part

User:VanGore

2007-11-13T10:05:50Z

VanGore:

= Klaus Mueller =
... for more [http://klml.de klml.de]

== Todo & Notice ==
info.xml

shopinfo.xml

how-to-play-de

2007-11-12T01:03:01Z

VanGore: update from how-to-play,

Bitte lesen Sie die [[introduction-de|Einführung]], falls dies Ihr erster Besuch ist.

= Spielregeln =
{{TOC-right}}
Bevor Sie etwas beisteuern, beachten Sie bitte die folgenden Richtlinien:
# Sie müssen ein Benutzerkonto anlegen (<abbr title="vergleiche" lang="de">vgl.</abbr> [http://de.wikipedia.org/wiki/Wikipedia:Anmelden Benutzernamen-Richtlinien der Wikipedia]), bevor Sie Seiten bearbeiten oder anlegen.
# Versuchen Sie es erst einmal mit einer der [http://microformats.org/discuss Mailinglisten {{ForeignLanguageLinkEnglish-de}}] (und lesen Sie vorher die Seite [[mailing-lists|mailing-lists {{ForeignLanguageLinkEnglish-de}}]]).
# Wenn Sie etwas schreiben, das eine eigene Meinung enthält, unterschreiben Sie es bitte mit Ihrem Benutzernamen (schreiben Sie dazu <nowiki>--~~~~</nowiki>).
# Erstellen Sie in diesem Wiki bitte nur Seiten, die in direktem Zusammenhang zu Mikroformaten stehen. Andere Seiten werden vermutlich gelöscht.
# Bitte richten Sie sich nach den [[naming-conventions|Bennenungsvereinbarungen {{ForeignLanguageLinkEnglish-de}}]], wenn Sie Seiten erstellen.
# Benutzen Sie keine Diskussionsseiten. Siehe 2.
# Versuchen Sie bitte gültiges XHTML zu erstellen.
# Wenn Sie Code einfügen, fügen Sie bitte nach einer angemessenen Zeilenlänge einen Zeilenumbruch ein.
# Bitte benutzen Sie keine Fragezeichen oder andere Satzzeichen in den Seitentiteln und Überschriften – dies verkürzt die URLs und macht sie lesbarer und einfacher zu kopieren und einzufügen.
# Überschriften können ausdrücklich durch <h1>- oder <h2>-Tags ausgezeichnet sein, damit sie nicht im Inhaltsverzeichnis erscheinen und dieses unnötig aufblähen. Sollten Sie solche Überschriften auf einer Seite finden, '''ändern Sie sie bitte nicht''' zu „=“- oder „==“-Überschriften.
# Bitte vermeiden Sie es, Überschriften zu verändern, und sei es nur ihre Groß- und Kleinschreibung. Überschriften werden oft als Permalinks benutzt, und durch Änderungen an den Überschriften würden bereits benutzte Permalinks ins Leere zeigen.
# Bitte vermeiden Sie große Änderungen der Umbauten. Wenn Sie der Meinung sind grundsätzliche Dinge ändern zu wollen tragen sie dies auf der [[to-do]]-Liste ein oder Fragen sie auf der Mailingliste nach. Wird keine Antwort gegeb ist dies als Nicht-Interesse und Ablehung zu werten. Die Admins werden von Zeit zu Zeit Spam entfernen, Dinge reparieren oder große Änderungen rückgängig machen.
# Bitte vermeiden Sie auch, einfach widersprechend auf Fragen und Probleme zu antworten (<abbr title="zum Beispiel" lang="de">z. B.</abbr> „nein“). Geben Sie stattdessen zumindest eine kurze Begründung, die Auskünfte gibt, die über das bereits in der Frage Enthaltene hinausgehen.
# Bitte entfernen Sie keine roten links oder legen Platzhalterseiten an, nur das diese nicht mehr rot sind. Die roten links haben die Funktion Andere darauf hinzuweisen der entsprechende Artikel gewünscht wird und noch niemand die Zeit oder das Wissen hatte diese zu erstellen. Rote links sind so eine Art ToDo-Liste. Eine Ausnahme sind rote links zu Lemmas die nichts mit Microformaten zu tun haben, diese sollten entfernt werden.
# Es werden keine ''Mediawiki Kategorien'' verwendet. <strike><nowiki>[[Category:Mikroformatvorschläge]]</nowiki></strike>
# Bitte erstellen Sie keine Benutzerseiten (''User:Foobar'') per Hand. Benutzerseiten sollen nur durch das folgen auf einen roten link in einer Signatur, Benutzerlistung (z.B. in den recent change) oder für den Benutzer oben an der Seite erfolgen. So wird sichergestellt das wenn ein Benutzer angelegt wird dieser auch mit seine Benutzerseite verknüpft wird.
# Nach dem ''Seitenverschieben'' sollte man in allen Seiten die auf die zu Verschiebende verweisen diese ändern. Alle verweisenden Seiten erhält man mit ''Was zeigt hierhin'' in der linken Navigationsleiste.
# Gebräuchlich ist die deutsche Rechtschreibung
# Benutzen sie [[rfc-2119#Templates|templates]] für '''RFC 2119''' Ausdrücke wie {{must}}.
# Verweise zu (X)HTML-Elementen sollten klein geschrieben werden und mit <nowiki><code>...</code></nowiki>, z.B. dem <code>input</code> Element, ausgezeichnet werden. Diese Konvention ist aus dem [http://www.w3.org/2001/06/manual/ W3C Manual of Style] übernommen.
# Für theoretische URls soll <nowiki>example.org</nowiki> verwendet werden, da erfunden Domains nachträglich angemeldet werden könnten (z.B. für Spam). Weiter ist hier <code><nowiki></code> zu verwenden (<code><nowiki><nowiki>http://example.org/</nowiki></nowiki></code>) das die URL von Mediawiki nicht automatisch verlinkt wird. Um den Unterschied zwischen mehreren Domains darzustellen kann man Subdomains nutzen (<nowiki>example.net or example.com</nowiki> or subdomains of <nowiki>example.org like foo.example.org</nowiki>).
# Stelle Sie fest das jemand wiederholt Seiten editiert, welche Sie editieren möchten ([[Special:Recentchanges]]), warten Sie 10 Minuten um einen Bearbeitungskonflikt zu verhindern. Planen Sie mehrere Änderungen an einer Seite so können Sie das [[Template:inuse]] mit '''<nowiki>{{Template:inuse}}</nowiki>''' oben auf der Seite platzieren. Aber bitte vergessen Sie nicht dieses wider zu entfernen.
# Bitte entfernen Sie '''keine''' anscheinend kaputten Links (404 etc). Wenn Sie diese nicht selbst reparieren können können diese mit dem Tag <nowiki><nowiki></nowiki> entlinkt werden. Auch können Sie am link anmerken das dieser nicht funktioniert (z.B. mit einem Listenpunkt <nowiki>*</nowiki> oder einem eingerückten Satz <nowiki>:</nowiki>)). Derjenige der den link gesetzt hat oder dafür verantwortlich ist kann so versuchen den link zu reparieren, andere können die Inhalte im [http://archive.org/ Internet Archive] nachlesen.

== Zugänglichkeit ==
# Für Akronyme soll die Großschreibung verwendet werden. Dazu soll als Syntax <code><nowiki><strong style="text-transform:uppercase"></nowiki></code> verwendet werden. Für Fettschrift soll "<strong style="text-transform:uppercase">do not</strong>". Dies verbessert die Lesbarkeit für Textlesesoftware und andere Programme.

== Wiki Cleaning ==
See [[spam-removal]].

Findet man Bereiche in welchen sehr viel aufgeräumt werden muss, so kann man sich an die Admins oder im [[IRC]]-Channel oder der Mailingsliste melden. Das ist meist einfacher als es selbst zu tun.

== Siehe auch ==
Die Seite [[mediawiki-customization]] gibt eine Übersicht über die Anpasungen und Unterschiede zu einer standardmäßigen Mediawiki-Installation. Für die Benennung von neuen Seiten sind die [[naming-conventions]] masgebend.

hreview

2007-11-10T21:30:49Z

VanGore: Category:Drafts

<h1> hReview 0.3 </h1>

[[hreview|hReview]] is a simple, open, distributed format, suitable for embedding reviews (of products, services, businesses, events, etc.) in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it.

== Microformats Draft Specification 2006-02-22 ==
; Editor: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])
; Authors: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])
: [http://360.yahoo.com/alidiabali Ali Diab] ([http://yahoo.com Yahoo! Inc.])
: [http://spaces.msn.com/members/ianmcallister/ Ian McAllister] ([http://microsoft.com/ Microsoft Corporation])
: [http://journals.aol.com/panzerjohn/abstractioneer John Panzer] ([http://www.aol.com America Online, Inc.])
: [http://ifindkarma.com/blog Adam Rifkin] ([http://labs.commerce.net/ CommerceNet Labs])
: [http://sippey.typepad.com/ Michael Sippey] ([http://sixapart.com Six Apart, Ltd])

Microformats [http://microformats.org/wiki/hreview#Copyright copyright] and [http://microformats.org/wiki/hreview#Patents patents] statements apply.

__TOC__

== Introduction ==
Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

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

{{rfc-2119-intro}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], Mark Nottingham, [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hReview. It is important that hReview 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 object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

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

== Format ==
=== In General ===
The hReview format is based on a set of fields common to numerous review 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]] and [[hcalendar|hCalendar]] standards.

=== Schema ===
The hReview schema consists of the following:

* hReview ('''<code>hreview</code>''')
** '''<code>version</code>'''. optional. text.
** '''<code>summary</code>'''. optional. text.
** item '''<code>type</code>'''. optional. product | business | event | person | place | website | url.
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event)
** '''<code>reviewer</code>'''. optional. '''[[hcard|hCard]]'''.
** '''<code>dtreviewed</code>'''. optional. ISO8601 absolute date time.
** '''<code>rating</code>'''. optional. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>value</code>'''.
** '''<code>description</code>'''. optional. text with optional valid XHTML markup.
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.
** license. optional, using '''[[rel-license]]'''.

=== Field details ===
The fields of the hReview schema represent the following:

'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.3".

'''summary''':: This optional field serves as a title for the review itself.

'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url. If omitted, then in some cases the item type may be inferred. If the item is also an [[hcard|hCard]], then the item type is a "business" or a "person" based upon which of those the hCard represents. If the item is also an [[hcalendar|hCalendar]] event, then the item type is an "event".

'''item info''':: This required field {{must}} have at a minimum the name ("fn" - the formatted text corresponding to the name, except for an event item which {{must}} have the "summary" property inside the respective hCalendar "vevent") of ''the'' item (an hReview describes only one item), {{should}} provide at least one URI ("url") for the item, and {{may}} provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) {{must}} be encapsulated in an [[hcard|hCard]]. For items of type event, the item info {{should}} be encapsulated in an [[hcalendar|hCalendar]] "vevent". Non-URL unique item IDs (e.g. ISBNs, UPCs) {{may}} be represented as a URN ("url") for the item. Encapsulated microformats (e.g. [[hcard|hCard]] and [[hcalendar|hCalendar]] events for now) may be set on the item itself (e.g. class="item vcard"). However, when using item info subproperties ("fn", "url", "photo"), they {{must}} be nested <em>inside</em> the item element.

'''reviewer''':: The optional field specifies the person who authored the review. If the reviewer is specified, an hCard representing the reviewer {{must}} be provided. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer. If no "reviewer" is found inside the hReview, parsers {{should}} look outside the hReview, in the context of the page, for the "reviewer". If there is no "reviewer" outside either, then parsers {{should}} use the author defined by the containing document language, e.g. for (X)HTML documents, the <code><nowiki><address></nowiki></code> contact info for the page (which is ideally marked up as an [[hcard|hCard]] as well), for Atom 1.0 the <code><nowiki><entry></nowiki></code> <code><nowiki><author></nowiki></code> if present and if not the <code><nowiki><feed></nowiki></code> <code><nowiki><author></nowiki></code>, for RSS the <code><nowiki><author></nowiki></code> inside the containing <code><nowiki><item></nowiki></code> element.

'''dtreviewed''':: This optional field when present {{must}} provide an [[ISO-8601|ISO8601]] absolute date time of when the review was written or otherwise authored. This field {{should}} use UTC, but {{may}} use the time zone offset syntax. If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the creation date (or modified date if that is missing) information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime) as the dtreviewed.

'''rating''':: The rating is a fixed point integer (one decimal point of precision) from 1.0 to 5.0 inclusive indicating a rating for the item, higher indicating a better rating by default. Optionally a different integral "worst" value and/or "best" value {{may}} be specified to indicate a different range (e.g. 6 from 0-10). The "best" value may be numerically smaller than the "worst" value.

'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field {{may}} include valid XHTML markup (e.g. paragraphs). User agents {{should}} preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) {{should}} be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer {{may}} optionally provide a tag-specific rating inside each [[rel-tag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and {{may}} also have a custom worst...best range specified. Authors {{may}} also invert this structure for the same semantic if it is more convenient for their markup, that is, place the [[rel-tag]] inside a rating to indicate a rated tag. Note: rated tags {{should}} ideally use a tag space that explains what the ratings for that tag mean. E.g. Food:18/30 {{should}} link to a tags space for Food that explains what an 18 out of 30 means for the Food tag.

'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> {{must}} be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> {{must}} be included among the space-separated set of values in the attribute. Indexers {{may}} treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink {{may}} also be used to indicate or imply the origin of the review. Authors {{may}} use the classname of "permalink" on the element representing the permalink.

'''license''':: This optional field links to the license under which the contents of the hReview itself is licensed, using the '''[[rel-license]]''' microformat.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, photo, description</code>. In addition, items and reviewers described by hCards {{may}} contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

=== More Semantic Equivalents ===

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

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with the class name 'hreview' in hReview.
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code><abbr></code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code><abbr class="rating" title="3.0">***</abbr></code>. This is further explored in the next section.

==== Language ====
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code><div class="hreview" lang="en"> ... </div></code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.

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

Similarly, 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.

=== Object Includes ===

hReview 0.3 includes support for the object [[include-pattern]].

Often a single page lists an item, and then several reviews for that item. In order to avoid having to repeat the item info for each review of the item, the first review should be marked up as an hReview, with a unique "id" attribute on the item info, and then following reviews should use the object [[include-pattern]] to include the item info from the first review.

=== Notes ===
This section is informative.

* By marking up a review with the hReview microformat, the expectation is communicated that the review MAY be indexed. This has no impact on the copyright of the review itself which the publisher may explicitly specify using [[rel-license]] as specified above.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hReview fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.
* Most rating systems use the range 1.0 to 5.0, and most of those represent the rating as a number (and possibly half) of stars. Sites may use whatever graphic they wish to represent the rating.

== Examples ==
Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it on your blog.

=== Restaurant reviews ===

Here is an example of a simple online restaurant review:

<pre><nowiki>
<div>
<span>5 stars out of 5 stars</span>
<h4>Crepes on Cole is awesome</h4>
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span>
<blockquote><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Adding hReview to this review is quite simple:

<pre><nowiki>
<div class="hreview">
<span><span class="rating">5</span> out of 5 stars</span>
<h4 class="summary">Crepes on Cole is awesome</h4>
<span class="reviewer vcard">Reviewer: <span class="fn">Tantek</span> -
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr></span>
<div class="description item vcard"><p>
<span class="fn org">Crepes on Cole</span> is one of the best little
creperies in <span class="adr"><span class="locality">San Francisco</span></span>.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></div>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars<br />
'''Crepes on Cole is awesome'''<br />
Reviewer: Tantek - April 18, 2005<br />

Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.

Visit date: April 2005<br />
Food eaten: Florentine crepe<br />

==== Multidimensional Restaurant Review ====
Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>
<span class="adr">
<span class="street-address">1010 El Camino Real</span>,
<span class="locality">Menlo Park</span>,
<span class="region">CA</span>
<span class="postal-code">94025</span>,
</span>
<span class="tel">+1-650-327-0830</span>;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: <span class="value">18</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: <span class="value">19</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: <span class="value">15</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="value" title="2">$$</abbr>...</a></li>
</ul>
<div class="description"><p>
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</p></div>
Review (<a href="http://microformats.org/wiki/hreview">
hReview v<span class="version">0.3</span></a>)
by <span class="reviewer vcard"><span class="fn">anonymous</span></span>,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre>

With an accompanying CSS style sheet like:

<pre><nowiki>
a.url { display:block }
ul { margin:1em 0; padding:0 }
ul li { display:inline }
</nowiki></pre>

This hReview could be presented similar to the original text:

Cafe Borrone<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
[http://cafeborrone.com/ cafeborrone.com]<br />
<br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...]<br />

This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.

Review ([http://microformats.org/wiki/hreview hReview v0.3]) by anonymous, April 28th, 2005.

=== Product review ===
Here is an example of a product review:

<pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(*****)
</div>
</nowiki></pre>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<pre><nowiki>
<div class="hreview"><span class="item">
<a class="url fn" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
The Postal Service: Give Up</a></span>
<div class="description"><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></div>
(<abbr class="rating" title="5">*****</abbr>)
<p class="reviewer vcard">Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>
</p>
</div>
</nowiki></pre>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...

(*****)

Review by Adam Rifkin, February 2005.

=== Movie Review ===
Finally, here is an example of a movie review.

<pre><nowiki>
<div>
<span>anonymous, April 18th, 2005</span>
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote><p>
This movie has great visuals and music.
</p></blockquote>
</div>
</nowiki></pre>

With hReview:

<pre><nowiki>
<div class="hreview">
<span class="reviewer vcard">
<span class="fn">anonymous</span>,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>
</span>
<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: <span class="rating">4</span> out of 5</div>
<div class="description"><p>
This movie has great music and visuals.
</p></div>
</div>
</nowiki></pre>

Which could be presented like this:

anonymous, April 18th, 2005<br />
Ying Xiong (HERO)<br />
Rating: 4 out of 5<br />

This movie has great music and visuals.

== Examples in the wild ==
This section is '''informative'''. The number of hReview examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hreview-examples-in-wild|separate page]].

See [[hreview-examples-in-wild|hReview Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hReview implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hreview-implementations|separate page]].

See [[hreview-implementations|hReview Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[rel-tag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== 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.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* [http://local.yahoo.com/details?id=21359628 Crepes on Cole reviews on Yahoo! Local]
* Other reviews efforts. See [[reviews-formats]].
* Contributed from http://developers.technorati.com/wiki/hReview.

==== Similar Work ====
* [[hlisting-proposal|hListing]]
* [[xoxo|XOXO]]

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

=== Patents ===
{{MicroFormatPatentStatement}}

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

=== Changes from v0.2 ===
The following changes have been made in hReview v0.3 over [[hreview-v0.2|hReview v0.2]]:

Normative changes:
# MUST (instead of SHOULD) use [[hcard|hCard]] for the item description of a business or person
# "reviewer" changes
## Made reviewer *optional* per feedback from Ryan King and Mark Nottingham
## If reviewer is absent from the hReview, then look outside the hReview, in the context of the page, for the reviewer. If there is no "reviewer" outside either, then use the author information according to the containing document language (e.g. <code><nowiki><address></nowiki></code> for (X)HTML pages) as the reviewer.
## MUST (instead of SHOULD) use [[hcard|hCard]] to represent reviewer information
# "dtreviewed" changes
## Made dtreviewed *optional* per feedback from Ryan King and Mark Nottingham
## If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime).
# SHOULD use [[hcalendar|hCalendar]] to represent an item of 'type' 'event'
# Added one decimal digit of precision to ratings' numerical values based on publisher experience.
# Use [http://microformats.org/wiki/hcard#Value_excerpting the "value" construct from hCard] (as it is used in "tel" properties for example) to more explicitly markup the rating value when also providing (marking up) the best/worst of a rating.
# Added [[rel-license]] to indicate the license of the hReview as a whole.
# Permit tags inside ratings to denote rated tags, the same as ratings inside tags per suggestion from Eran Globen.
# Add [[include-pattern]] support to allow multiple reviews for the same item to not repeat the item info.

Informative changes (several, but in particular):
# Note that scalar/rated tags would ideally use a tag space that explain the ratings for that tag. E.g. to explain what Food:18/30 means.
# Updated examples accordingly.

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

== Related Pages ==
{{hreview-related-pages}}

[[Category:Drafts]]

hresume

2007-11-10T21:30:22Z

VanGore: Category:Drafts

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an hResume? Use the [http://hresume.weblogswork.com/hresumecreator/ hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog.

<h2> Microformats Draft Specification </h2>

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

{{rfc-2119-intro}}

__TOC__

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. {{must}} use [[hcard|hCard]]; {{should}} use <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hResume schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info in an [[hCard]]; {{should}} use <code class="element"><address></code> with [[hCard]] when possible.
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''<code class="class-name">publications</code>''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== XMDP Profile ===
* [[hresume-profile]] (@TODO)

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
<span class="fn">Pedro Sanchez</span>
<span class="adr">
<span class="street-address">123 Fake St.</span>
<span class="locality">Preston</span>, <span class="region">Idaho</span> <span class="postal-code">83263</span>
</span>
<span>Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a></span>
<span>Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a></span>
<span>Phone: <span class="tel">+01.208.555.4567</span></span>
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
<span class="summary">President</span>,
<span class="location">Preston High School</span>,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use one or more [[hcard|hCard]]s. hCard requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't customary to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

Currently, the recommended way to reference includes within microformats is to use a hyperlink with class="include". See [[include-pattern|include-pattern]] for details.

For example, this hCard refers to another hCard:

Using <code><a></code>:
<pre>
<span class="vcard">
<a href="#pedro-name" class="include" title="Pedro Sanchez"></a>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

Using <code><object></code>:
<pre>
<span class="vcard">
<object data="#pedro-name" class="include"></object>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

Where "<code class="attr-value">pedro-name</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):

<pre><nowiki>
<address class="vcard">
<span class="fn n" id="pedro-name">
<span class="given-name">Pedro</span>
<span class="family-name">Sanchez</span>
</span>
</address>
</nowiki></pre>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.

Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
<span class="affiliation vcard"><span class="fn org">National Honor Society</span></span>
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
See [[hresume-examples-in-wild]]

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

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

* [http://linkedin.com LinkedIn] generates hResume for all Public Profiles. [http://www.linkedin.com/in/steveganz LinkedIn Public Profile Example].

* [http://www.antix.co.uk Anthony Johnston] has implemented hResume (Creation and Import) in the [http://cv.antix.co.uk Antix CV Builder], an example resume using this site can be found [http://cv.antix.co.uk/ant here]
** The example resume is ''invalid''; job titles are marked with an hCard that is missing a "fn" (either directly or via object). --[[User:Gazza|Gazza]] 04:23, 1 May 2007 (PDT)

* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin]. See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here]. Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...

* The [http://www.ssdesigninteractive.com/ssdesign Sajid Saiyed] has created an hResume WordPress plugin located at [http://www.ssdesigninteractive.com/ssdesign/?p=96 Microformat Resume Plugin]. See an example of the hResume markup [http://www.ssdesigninteractive.com/ssdesign/?page_id=95 here].

* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator]. The creator will generate hResume markup ready to cut and paste into your webpage.

== Copyright ==
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
* [[RyanKing]]: I release all of my contributions to the public domain.

Per the above, and the public domain release on the author, [[User:RyanKing|RyanKing]]'s, user page this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[include-pattern|include pattern]]
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* [[rfc-2119]]
* @TODO

=== Informative References ===
* @TODO

== Acknowledgements ==
=== Concept ===
* [http://theryanking.com/ Ryan King] ([http://technorati.com Technorati])
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati])
* James Levine ([http://simplyhired.com Simply Hired])
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati])

== Related Pages ==
{{hresume-related-pages}}

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

[[Category:Drafts]]

hatom

2007-11-10T21:30:08Z

VanGore: Category:Drafts

<h1> hAtom 0.1 </h1>

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

__TOC__
== Draft Specification ==

;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

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

=== Patents ===
{{MicroFormatPatentStatement}}

== Introduction ==

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

{{rfc-2119-intro}}

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

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

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

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

The hAtom schema consists of the following:

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

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

=== Field and Element Details ===

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

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

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

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

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

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

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

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

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

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

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

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hfeed</dt>
<dd>
The concept of atom:feed from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>hentry</dt>
<dd>
The concept of atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-title</dt>
<dd>
The concept of atom:title inside of an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-content</dt>
<dd>
The concept of atom:content from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-summary</dt>
<dd>
The concept of atom:summary from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>bookmark</dt>
<dd>
The concept of atom:link (without any "rel") with an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>published</dt>
<dd>
The concept of atom:published from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>updated</dt>
<dd>
The concept of atom:updated from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>author</dt>
<dd>
The concept of atom:author from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
</dl>
</dd>
</dl>
</pre>

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

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

== Implementations ==

This section is '''informative'''.

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

* [http://spinn3r.com/opensource.php Spinn3r Open Source] - implemented in Spinn3r and part of [http://code.tailrank.com/feedparser FeedParser]
* [http://dichotomize.com/uf/hatom/creator.html hAtom Creator] modified from the other creators by BenWest.
** appears to have broken as of 14 Oct 2007. returns 404, as does each parent directory. site returns default Apache install home page.
* the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://tools.blogmatrix.com/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&microformat=hatom&submit=Submit example])
* the [http://www.trinityanne.com/tools/greasemonkey/microformat-action.user.js microformat-action] [[greasemonkey|Greasemonkey]] script detects hAtom content on webpages and will call the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser]
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format


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

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

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

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

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

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

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

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

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

[[Category:Drafts]]

geo

2007-11-10T21:29:43Z

VanGore: Category:Drafts

<h1> geo </h1>
*http://rbach.priv.at/2006/buttons/geo.png
'''geo''' (pronounced "gee-oh") is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

;Editor/Author
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF]. Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].

== Introduction and Background ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information. The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.

This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.

Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher {{must}} use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.

If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher {{should}} use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.

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

== Format ==
=== Singular Properties ===

Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is the value of the property. See [[hcard|hCard]] for details on this.

=== Root Class Name ===

The root class name for an geo location is <code>geo</code>.

=== Property List ===

This is the list of properties in geo, taken from [[hcard|hCard]]:

* latitude
* longitude

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:

<pre><nowiki>
<div class="geo">GEO:
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</div>
</nowiki></pre>

this geo could be displayed as: 

<div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>

Note that this is a '''live''' geo microformat, which will be found on this page by parsers.

=== Real world geo example ===

Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):

<pre><nowiki>
N 37° 24.491 W 122° 08.313
</nowiki></pre>

With geo markup:

<pre><nowiki>
<div class="geo">
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr>
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>
</nowiki></pre>

This geo might be displayed as: 

<div class="geo"><abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>

Again, this is a '''live''' example.

Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.

== Examples in the wild ==

This section is '''informative'''. The number of Geo examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a separate page, [[geo-examples-in-wild|Geo examples in the wild]].

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

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

*I've added Geo mark-up to the output of Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has Geo mark-up in the "[http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.686_N_2.193_W_region:GB_type:landmark#Mark-up Mark-up]" section. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Jul 2007 (PDT)
*GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
*[http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
**For UK, the British Isles and China, Google returns an error.
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
**GPX export is done, but needs some tweaking and testing. Just change &type=(kml|georss|gpx). Not quite ready for primetime yet. Feel free to test and send feedback.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.openstreetmap.org OpenStreetMap] uses the geo microformat on its wiki for place pages (added by [http://wiki.openstreetmap.org/index.php/User:Pigsonthewing Andy Mabbett]) and also on the GPS trace pages and diary entry pages ([http://www.dankarran.com/blog/archives/2007/09/04/pinpoint_your_openstreetmap_diary_entries.php added] by [http://www.dankarran.com Dan Karran]).

== References ==
=== Normative References ===
* [[hcard|hCard]]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

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

* Proposals for changes, additions and other thoughts about [[geo]] may be found at [[geo-brainstorming]].

== Related Work ==
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies

== Similar Work ==
* [[adr]]
* [[hcalendar|hCalendar]]
* [[XOXO]]

== See Also ==
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page]
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]

== Related Pages ==
{{geo-related-pages}}

[[Category:Drafts]]

adr

2007-11-10T21:27:42Z

VanGore: Category:Drafts

= adr =
http://rbach.priv.at/2006/buttons/adr.png

'''adr''' (pronounced "adder"; FAQ: [[hcard-faq#Should_I_use_ADDRESS_for_hCards|"why 'adr'?"]]) is a simple format for marking up address information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''adr''' is a 1:1 representation of the ''adr'' property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards. It is also a property of [[hCard]].

__TOC__

== Draft Specification ==
; Editor/Author
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF].

== Introduction and Background ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, address information on the Web, given how often bloggers, and numerous other sites publish address information. The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''adr'' from vCard/hCard.

This specification introduces the '''adr''' microformat, which is a 1:1 representation of the aforementioned ''adr'' property from the vCard standard, by simply reusing the ''adr'' property and sub-properties as-is from the [[hcard|hCard]] microformat.

Publishers can both embed '''adr''' addresses directly in their web pages and feeds, as well as markup existing addresses in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the ''name'' of the location in addition to its address, then the publisher MUST use [[hcard|hCard]] instead of just '''adr''' to publish the name and address of the location.

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

== Format ==
=== Singular Properties ===

Note that all the properties in '''adr''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

Similarly, if an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the <code>PHOTO</code> property and any other property that takes a <abbr title="Uniform Resource Locator">URL</abbr> 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.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is the value of the property. See [[hcard|hCard]] for details on this.

=== Root Class Name ===

The root class name for an '''adr''' address is <code>adr</code>.

=== Property List ===

This is the list of properties in '''adr''', taken from [[hcard|hCard]]:

* <code>post-office-box</code>
* <code>extended-address</code>
* <code>street-address</code>
* <code>locality</code>
* <code>region</code>
* <code>postal-code</code>
* <code>country-name</code>

The <code>type</code> sub-property is omitted because without the context of a type of address for ''whom'', it doesn't make much sense.

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===
See [[hcard-parsing|hCard parsing]], with the only difference being that "adr" is the root class name, rather than "vcard".

== Examples ==
This section is informative.

=== Sample adr ===

Here is a sample <code>adr</code>:

<pre><nowiki>
<div class="adr">
<div class="street-address">665 3rd St.</div>
<div class="extended-address">Suite 207</div>
<span class="locality">San Francisco</span>,
<span class="region">CA</span>
<span class="postal-code">94107</span>
<div class="country-name">U.S.A.</div>
</div>
</nowiki></pre>

which might be displayed as:

<div class="adr">
<div class="street-address">'''665 3rd St.'''</div>
<div class="extended-address">'''Suite 207'''</div>
<span class="locality">'''San Francisco'''</span>,
<span class="region">'''CA'''</span>
<span class="postal-code">'''94107'''</span>
<div class="country-name">'''U.S.A.'''</div>
</div>

Note that this is a '''live''' <code>adr</code> microformat, which will be found on this page by parsers.

=== More Examples ===

See [http://microformats.org/wiki/hcard-examples#3.2.1_ADR_Type_Definition hCard example ADR] for more examples.

See [http://microformats.org/wiki/adr-examples adr examples] for additional uses of ADR.

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

The following sites have published adrs, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc., in addition to [[hcard|hCard]] examples in the wild. If you find adrs outside of hCards anywhere else, feel free to add them to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://www.stems-florist.co.uk/ Stems Florist] uses the microformat on the front page to markup up the two store addresses
* ...

(See also [[hcard-examples-in-wild]])

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

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

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the location, or route to, an [[adr]] using a MapQuest map. The route is displayed from the starting location based on the viewer's IP-Address as determined by the [http://hostip.info HostIP] geolocation service.

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRouteEmbed] is another GreaseMonkey user script that will actually embed a route image in the webpage when the user clicks the "route" link.

* [http://georss.org/geopress GeoPress] is a [http://wordpress.org WordPress] plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and [http://georss.org GeoRSS] feeds.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding adrs and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* The [http://tantek.com/microformats/hcard-creator.html hCard creator], though it creates complete hCards, can also be used simply to create adrs by filling out the address portion and simply copy and pasting the <div class="adr"> element and its contents.

== References ==
=== Normative References ===
* [[hcard|hCard]]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

=== Similar Work ===
* [[geo]]
* [[hcalendar|hCalendar]]
* [[XOXO]]

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

== Discussions ==

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

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]] first, and if you don't find answers, add your questions! (Odds are that any '''adr''' question will apply to [[hCard]] as well).
* See also [http://microformats.org/discuss/ for other methods of feedback].

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document. Ditto.

== Related Pages ==
{{adr}}

[[Category:Drafts]]

User:VanGore

2007-11-09T11:41:43Z

VanGore:

Don't create new taxos. Use the existing.

== Todo ==
info.xml

shopinfo.xml