Microformats Wiki - User contributions [en]

rel-payment

2007-01-02T00:36:46Z

Token: /* Amazon Associates */

== Authors ==
[http://solitude.dk Andreas Haugstrup Pedersen]

[http://joshkinberg.com Joshua Kinberg]

[http://momentshowing.net Jay Dedman]

[http://poorbuthappy.com/ease Peter Van Dijk]

== Abstract ==
RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page.

One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content).

== RelPayment ==
RelPayment is meant as a general way to facilitate acts of support, and thus this specification makes no assumptions on the type of support.

A page may contain any number of hyperlinks marked with rel="payment". This allows authors to give readers more than one possible way to show support (a DropCash link, a PayPal link, a link to a page with an address to mail a check and so on). It also allows authors to add payment links that only relate to a certain section of a page. E.g. a book review website may have several book reviews on one page with each review having their own Amazon Affiliate link marked with rel="payment". Aggregators should implement support for multiple payment hyperlinks.

Authors should use the "title" attribute to provide a human readable description of the type of support pointed to by the hyperlink. Aggregators may use the contents of the "title" attribute to provide additional information about the support link to their users. E.g. <a href="[url]" rel="payment" title="Donate Money Via PayPal">.

If the hyperlink contains an image (e.g. <a href="[url] rel="payment"><img src="[url]" alt="Support Badge" /></a>) aggregators may display that image instead of the aggregator's standard link.

== Visible Metadata ==
Links marked with rel="payment" are meant to be visible on the page, and because of that the <a> element is encouraged over the <link> element. This gives readers the easiest access to show support and it discourages link fraud. Authors should not use empty hyperlinks such as <a href="[url]" rel="payment" /> and parsers may ignore empty links.

== XMDP profile ==
<pre><nowiki><dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="payment">payment</dt>
<dd>Indicates that the referred resource provides a way to show support for the referring page.</dd>
</dl>
</dd>
</dl></nowiki>
</pre>

== Application for addition to Atom registry of link relations ==

The following is an application for a link relation value, as
specified in the Atom Syndication Format.
[https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&filename=draft-ietf-atompub-format]

thank you,

Joshua Kinberg, jkinberg AT gmail DOT com

Robert Sayre, sayrer AT gmail DOT com

=== Registry ===

http://www.iana.org/assignments/link-relations

=== Attribute Value ===

"payment"

=== Description ===

rel="payment" indicates a URI where payment is accepted. It is meant
as a general way to facilitate acts of payment, and thus this
specification makes no assumptions on the type of payment or
transaction protocol. Examples may include a WWW page where donations
are accepted or where goods and services are available for purchase.
rel="payment" is not intended to initiate an automated transaction.

A link element with a rel="payment" attribute may exist at the
feed/channel level and/or the entry/item level. For example, a
rel="payment" link at the feed/channel level may point to a "tip jar"
URI, whereas an entry/item containing a book review may include a
rel="payment" link that points to the location where the book may be
purchased through an online retailer.

=== Display Characteristics ===

End-user software could support rel="payment" by displaying a "payment
button" along with the content. Alternatively, content aggregators may
display a payment hyperlink containing the text specified in a
corresponding title attribute within the <link> element, for example:
<pre>
<link rel="payment"
href="http://example.com/c.r.e.a.m"
title="give me the loot" />
</pre>
May display either a payment button or a hyperlink containing the
text, "give me the loot."

=== Security Considerations ===

The link element is subject to tampering and observation, as is the
linked resource. For that reason, implementations should clearly
signal the level trust and privacy a linked resource provides. If
present, digital signatures provide authentication, message integrity,
and non-repudiation with proof of origin. Encryption provides data
confidentiality. Implementations should also consider the level of
confidentiality and message integrity provided by the transport used
to reach the payment resource.

== Prior Art ==

=== Anil Dash's proposal, 2002 ===

* http://www.dashes.com/anil/2002/12/10/payment_link_ta

Anil Dash's proposal in 2002 to use XHTML <link> element to define payment URLs:

<blockquote>
<b>payment LINK tags</b>
<br/>
There are already a lot of defined (if not quite standardized) possible values for the LINK element in XHTML. We're using them for RSS Auto-Discovery and, of course, for stylesheets already. But what about something like:
<br/>
<link rel="appendix" type="text/html" title="payment" href="URL of Wishlist or Paypal Page" />
<br/>
A standardized way of linking to the page where you pay for your patronage of a site. Granted, calling the payment page an "Apppendix" of the site you're visiting is fudging things a bit. Maybe there's a more elegant way?
</blockquote>

Although this is similar to rel="payment" as we are proposing, it is not as flexible as it can only be used to define one payment location for an entire page (likely a tip jar or wishlist page). Perhaps rel="payment" could be used within the link element as well as within standard anchor tags?

== Examples from the wild ==

=== Amazon Associates ===
'''Product with image'''

This is the code generated by Amazon for a single product endorsement with photo. Everything is generated automatically. The form can be replaced with another regular HTML link.

<pre><nowiki>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<body>
<table cellSpacing=0 cellPadding=1 width=120 height=240 bgColor=#000000 border=0>
<tr>
<td>
<table cellSpacing=0 cellPadding=0 width=118 height=238 align=center bgColor=#ffffff border=0>
<tr>
<td>
<table width=100% height=238 border=0 cellSpacing=0 cellPadding=0>
<tr align=center>
<td>
<a href=http://www.amazon.com/exec/obidos/ASIN/B00022AH6I/solitudedk-20?creative=327641&camp=14573&link_code=as1 target=_blank><img src=http://rcm-images.amazon.com/images/P/B00022AH6I.01._SCTZZZZZZZ_.jpg vspace=3 border=0></a>
</td>
</tr>
<tr>
<td vAlign=center height=15%><center>
<a href=http://www.amazon.com/exec/obidos/ASIN/B00022AH6I/solitudedk-20?creative=327641&camp=14573&link_code=as1 target=_blank><font face=Arial color=#0000ff size=1>Kodak EasyShare DX7440 4MP Digital C...</font></a>
</td>
</tr>
<tr height=15%>
<td>
<center>
<font face=Arial color=#000000 size=-2>Kodak Digital </font>
</center>
</td>
</tr>
<tr>
<td height=15%>
<center><a href="http://www.amazon.com/exec/obidos/redirect?tag=solitudedk-20&camp=14573&creative=327641&link_code=am1&path=tg/stores/offering/list/-/B00022AH6I/all/ASIN/B00022AH6I&camp=14573&creative=327641" target=_blank><font face=Arial color=#0000ff size=1>Best Price <font face=Arial color=#990000 size=1>$157.70</font></font></a></center>
</td>
</tr>
<tr height=15%>
<td>
<center><font face=Arial color=#000000 size=1>or Buy New <font color=#990000></font></font></center>
</td>
</tr>
<tr>
<td height=15%><center>
<table>
<form method="GET" action="http://www.amazon.com/gp/aws/cart/add.html" target="_blank">
<tr>
<td>
<input type="hidden" name="SubscriptionId" value="D68HUNXKLHS4J" />
<input type="hidden" name="AssociateTag" value="solitudedk-20" />
<input type="hidden" name="ASIN.1" value="B00022AH6I" />
<input type="hidden" name="Quantity.1" value="1" />
<input type="hidden" name="linkCode" value="as1" />
<input type="image" name="submit.add" value="Buy from Amazon.com" border="0" alt="Buy from Amazon.com" src="http://rcm-images.amazon.com/images/G/01/buttons/buy-from-tan.gif" />
</center>
</td>
</tr>
</form>
</table>
</center></td>
</tr>
<tr>
<td height=5% align=absbottom>
<center><a href=http://rcm.amazon.com/e/cm/privacy-policy.html?o=1 target=_blank>
<font face=Arial color=#a1a1a1 size=1>Privacy Information</font></a></center>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>
</nowiki></pre>

'''Text links'''

This is the code for a text link to a product category. The visible link text is chosen by the user.
<pre><nowiki>
<a href="http://www.amazon.com/exec/obidos/redirect?link_code=ur2&camp=1789&
tag=solitudedk-20&creative=9325&path=tg/browse/-/1">
Get Photography Books at Amazon
</a>
<img src="http://www.assoc-amazon.com/e/ir?t=solitudedk-20&l=ur2&o=1"
width="1" height="1" border="0" alt="" style="border:none !important;
margin:0px !important;" />
</nowiki></pre>

'''Banners'''

The following is the code generated by Amazon for generic Amazone banners. Note use of imagemap to create "privacy policy link".

<pre><nowiki>
<html>
<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0>
<table width=468 height=60 border=0 cellspacing=0 cellpadding=0>
<tr valign=middle align=center>
<td>
<MAP NAME='boxmap'><AREA SHAPE='RECT' COORDS='379, 50, 469, 61'
HREF=http://rcm.amazon.com/e/cm/privacy-policy.html?o=1 target=_top>
<AREA COORDS='0,0,10000,10000' HREF=http://www.amazon.com/exec/obidos/redirect?
tag=solitudedk-20&creative=333489&camp=15553&link_code=ez&path=
/tg/browse/-/171280 target=_top>
</MAP>
<img src=http://rcm-images.amazon.com/images/G/01/
associates/2005/served-banners/us_banner_imag_468x60.gif
width='468' height='60' border='0' usemap='#boxmap'>
</td>
</tr>
</table>
</body>
</html>
</nowiki></pre>

'''Search Boxes'''

Amazon offers search boxes:

<pre><nowiki>
<form action="http://www.amazon.com/exec/obidos/external-search">
<table class="normal" border="0" cellpadding="0" cellspacing="0">
<tr>
<td style="background-color:#fff;">
<table border="0" cellpadding="0" cellspacing="0" align="top"
height="90" width="120" style="border: 1px solid #000000 !important;">
<tr>
<td style="background-color:#fff;" height="20" valign="bottom" align="center">
<span style="font-family: verdana,arial,helvetica,sans-serif;
font-size:10px !important; font-weight:bold !important;">Search Now:</span>
</td>
<td style="background-color:#fff;"> </td>
</tr>
<tr>
<td style="background-color:#fff;" align="center" height="30" valign="top">
<input type="text" name="keyword" size="10" value="" />
</td>
<td style="background-color:#fff;" height="20" valign="top" align="left">

<input type="hidden" name="mode" value="blended" />
<input type="hidden" name="tag" value="solitudedk-20" />
<input type="image" border="0" value="Go" name="Submit"
src="http://g-images.amazon.com/images/G/01/associates/build-links/
ap-search-go-btn.gif" alt="[ Go ]" align="absmiddle" />
</td>
</tr>
<tr>
<td colspan="2" style="background-color:#000;" height="40">
<a href="http://www.amazon.com/exec/obidos/redirect-home/solitudedk-20">
<img src="http://g-images.amazon.com/images/G/01/associates/build-links/
searchbox-logo-126x32.gif" height="36" border="0" width="126"
alt="Amazon Logo" /></a></td>
</tr>
</table>
</td>
</tr>
</table>
</form>
</nowiki></pre>

<dl><dt>Comments to author of article: </dt>
<dd>This is a bad example for semantic, microformats, w3c and rel="payment"
<ul><li>It's using table/td/tr for layout</li>
<li>attributes without quotation marks (bgColor=120)</li>
<li>uppercase to markup</li>
<li>markups depreceated</li>
<li>the example isn't have rel="payment" attribute</li></dd>
<dl>

=== Practical examples of rel="payment" ===

* http://www.joshkinberg.com/blog/archives/2005/07/channel_102_int.php

Blog entry containing video interview with founders of a theater group. rel="payment" link points to the theater group's fundraising page where the reader is encourage to donate via PayPal.

* http://www.joshkinberg.com/blog/archives/2005/08/e_e_meet_bullwi.php

Blog entry containing home video that uses music by a popular recording artist. rel="payment" link encourages reader to purchase the artist's CD at Amazon (could have used Amazon affilliate link as noted above).

* http://www.joshkinberg.com/blog/archives/2005/08/vlogs_on_npr_sc.php

Blog entry containing audio segment from an NPR interview. rel="payment" link encourages the reader to support NPR by purchasing something from the NPR Online Shop.

== Tools that currently support RelPayment ==

* http://GetFireAnt.com

FireAnt is an RSS video aggregator and media player. Subscribe to any RSS 2.0 channel and automatically download fresh media content to watch and listen to.

* http://blip.tv

blip.tv lets you share and watch video for free. We will host your video, make it available for your friends, family and blog readers and help you find video that others have shared.

* http://MeFeedia.com

Mefeedia is a video aggregator, like Bloglines for video. You can subscribe to channels and watch thousands of videos. This site is about not about movies, television shows or video made by big companies, it's about the thousands of people are creating video and putting it online. Movies made by real people.

* http://rssbazaar.com

* http://49media.com

==See also==
* [[rel-faq]]

hcard-pt-br

2006-12-01T14:04:09Z

Token:

=hCard=
hCard é um simples, aberto formato distribuído para represetar pessoas, companias, organizações e lugares usando uma representação 1:1 de propriedades e valores de padrão vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) em [[semantic-xhtml|semântica XHTML]]. hCard é um dos muitos padrões abertos de [[microformats|microformato]] apropriado para ser inserido em (X)HTML, Atom, RSS, e o arbitrário XML.

Quer começar a escrever em [[hcard|hCard]]? Use o [http://microformats.org/code/hcard/creator criador de hCard]

para detalhar algumas informações de contato e publicá-la, ou seguir [[hcard-authoring|hCard authoring tips]] para adicionar marcação hCard em sua página atual de contato.

__TOC__

== Especificação ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Autores ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

=== Inspiração e Reconhecimentos ===
Agradecimento à: meu amigo [http://vadim.com/ Vadim] que me introduziu ao vCard ''vários'' anos atrás, e se eu tivesse prestado mais atenção talvez então poderia ter ajudado muitas pessoas a evitar desperdiçar tempo reinventando várias rodas de padrões ''wheels''.

== Introdução ==
O padrão vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), tem largamente implementado interoperabilidade (e.g. Apple's "Address Book" application built into MacOSX).

Em adição, muitos bloggers se identificam pelo nome e discutem a seus amigos e família. Com só um pouco de estrutura, bloggers podem discutir as pessoas em seus blog(s) de tal um modo que spiders e outros agregadores podem receber essa informação, automaticamente convertê-las para vCard e usá-las então e qualquer aplicativo vCard ou serviços.

Essa especificação introduz o formato '''hCard''' , que usa uma representação 1:1 de propriedades e valores de mencioado no padrão vCard acima, em elemento XHTML.
podem ambos embutir diretamente hCards em suas páginas, e estilizá-las com CSS tornando-as parecido como desejado.

Em adição, hCard ativa aplicações para receber informação diretamente de páginas web sem ter que referenciar um arquivo separado

Use o [http://microformats.org/code/hcard/creator criador de hCard] para copiar o código HTML e gerar para seu blog ou website e publicá-lo em sua informação de contato.

== Semântica XHTML Princípios de Design ==
{{semantic-xhtml-design-principles}}

== Formato ==
=== Em geral===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forma a base do hCard.

O formato básico de hCard é usar nomes vCard objeto/propriedade em caixa-baixa para nomes de classes, e mapear aninhando objetos vCard diretamente para elementos XHTML aninhado.

=== Mais Equivalente Semântico ===
Para algumas propriedades há o elemento HTML que é mais combinado e conduz suas semanticas.
A seguinte propriedade DEVE ser codificada com o seguinte (X)HTML:
* <code>URL</code> um vCard que se torna <code><a class="url" href="...">...</a></code> dentro do elemento com <code>class="vcard"</code> em hCard.
* Similarmente, <code>EMAIL</code> um vCard que se torna <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> um vCard que se torna <code><img class="photo" src="..." alt="Foto de ..." /></code> ou <code><object class="photo" data="..." type="...">Foto de ...</object></code>
* <code>UID</code> um vCard simply que se torna outro semantica aplicada a uma especifico URL (ou EMAIL) para um hCard.

=== Propriedades Singular vs. Plural ===

Para propriedades que estão no singular (ex. "N" e "FN"), o primeiro elemento descendente com aquela class deve ter efeito, qualquer outros serão ignorados.

Para propriedades que podem estar no plural (ex. "TEL"), each class instance should create a instance of that property.

==== Propriedades no Singular ====

Propriedades no Singular: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

Todas as outras propriedades são plural. Essa lista foi derivada de uma analize de semantica de propriedades individuais em vCard RFC2426 e determinando logicamente que eles DEVEM ser singular pela sua semantica. Ver [[hcard-singular-properties]] para explicação.

==== Propriedades plurais Singularizadas ====

Desde que nomes de propriedades plurais tornam-se seus equivalente em singular, mesmo se propriedade no plural original permitiu só um único valor com componentes múltiplos, esses múltiplos componentes são representados cada um com suas próprios propriedade nomeada singularidade e a propriedade é efetivamente polivalente e submetido ao tratamento acima de propriedades polivalente.

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

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

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

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

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with rel-tag. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

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

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]<br />
Technorati
</div>

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

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

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], "A. I. Cuza" University Iaşi, Romania uses hCard for each staff member.
* [http://www.finds.org.uk/ The Portable Antiquities Scheme at the British Museum] hCards added to footer of every page and to contacts section. Working on adding more and getting it right.
* In [http://www.ideasfornet.com/ IdeasForNet.com - the ideas repository] hCards were implemented partially in the footer of each page, and more comprehnsively in the contact and about pages.
* The [http://www.cst.ed.ac.uk/ Centre of Canadian Studies] at the University of Edinburgh use hCards for contact information in the footer of their site.
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh use hCards for contact information on their home page
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club] in the English Midlands uses hCard on its [http://www.westmidlandbirdclub.com/ home page], [http://www.westmidlandbirdclub.com/diary/ events diary], [http://www.westmidlandbirdclub.com/club/contact.htm contact pages] and [http://www.westmidlandbirdclub.com/site/links.htm links page]. The former is a page footer which is gradually being rolled out across the whole site.
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard
* [http://www.fischsolutions.com/ Fisch Internet Solutions] uses an embedded hCard and a vCard download to provide customers an easy way to contact them on their [http://fischsolutions.com/contactus.html Contact Us] section of the website.
* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK governement agency, formed 2006-10-01). No "fn" - which makes it invalid.
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [http://www.creative-ways.nl/ Ron Kok] uses hCards to mark-up the names and URLs of commentors on his blog. He also uses hCards in combination with XFN in his blogposts to refer to friends, and has an hCard for himself in the footer of his blog.
* [http://tagg.no Tagg Media] uses hCard for [http://heine.tagg.no/contact.php contact information] and provide link to vCard download in the contact section.
* [http://en.wikipedia.org/wiki/Neo_%28The_Matrix%29 Thomas A Anderson in Wikipedia] is now marked up with hCard.
* [http://dconstruct06.madgex.com/ d.Construct 2006 Backnetwork] uses hCards for conference delegates (and provides the markup so that delegates can copy and paste cards into their own sites).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address "Find"] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hcards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).
* [http://www.webdirections.org Web Directions ]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [http://www.markthisdate.com/contactform.html MarkThisDate.com ]. An hCard is implemented on our contactform. For our calendars hCalendars will follow as soon as possible.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] and his [http://rasterweb.net/portfolio/ Portfolio]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf Kåre Lefdal] uses hCard in the markup of his contact information
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.

=== Examples ===
* [http://www.nfwebsolutions.com/ New Frontier Web Solutions] uses hCard on their frontpage along with a link pointing to Brian Suda's [http://suda.co.uk/projects/X2V/get-vcard?uri=http://www.nfwebsolutions.com/ X2V].
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'><defs id='defs3959' /><path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < with %3C (etc., eg Brian Suda's vcard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/ Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [http://www.child-care-index.net.au/ The Australian Child Care Index] has over 3000 entries listing child care services across Australia - and every single one is marked up with an hcard!
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard
==== UTF8 Examples in the Wild ====
These examples all contain one or more characters in UTF8 that are outside the ASCII7 range and make for excellent test cases to make sure you are handling UTF8 properly throughout your hCard parsing and transforming. And especially if you are generating vCards, these test cases will help you make sure you are generating UTF8 vCards in such a way that can be recognized by UTF8 supporting vCard applications.
* [http://tantek.com/ Tantek's Thoughts] encodes Çelik as inline UTF8.

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
** <strike>WARNING - uses class="cell" instead of <span class="type">cell</span></strike> Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://elbewerk.com/2006/09/vcardexplorer-02.shtml vCardExplorer 0.2] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by Daniel Kagemann.
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Related Pages ==
* [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|feedback]]) - create your own hCard.
* [[hcard-authoring|hCard authoring]] - learn how to add hCard markup to your existing contact info.
* [[hcard-examples|hCard examples]] - Example usage of various classes within hCard,
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.
* [[hcard-issues|hCard issues]] - Please add any specific issues with the specification to the issues page.
* [[hcard-feedback|hCard feedback]] - General feedback (as opposed to specific issues) should be added to the hCard feedback page.
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]

rel-nofollow-pt-br

2006-11-25T22:33:20Z

Token:

= rel="nofollow" =
__TOC__

== Especificação 2005-01-10 ==

=== Editores ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc.]

=== Conceito ===
* [http://www.google.com/googleblog/ Matt Cutts], [http://google.com Google, Inc]
* [http://www.shellen.com/ Jason Shellen], [http://www.blogger.com Blogger]/[http://www.google.com Google]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==
RelNoFollow é um [[elemental-microformat-pt-br|microformato elementar]], um dos diversos [[microformats|microformatos]] de padrões aberto. Ao adicionar <code>rel="nofollow"</code> a um hyperlink, uma página indica que aquele destino do hyperlink NÃO DEVE ser permitida qualquer importancia ou ranking por agentes de usuário que oferecem análise de link pelas páginas web (como máquinas de busca). Tipicamente usa casos incluído links criado pela comentários de 3rd party em blogs ou links que o autor gostaria de apontar, porém contra uma aprovação. Para mais informações contra aprovações (ou falta de) semântica, veja VoteLinks.

== Perfil XMDP ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
Definição HTML4 do atríbuto 'rel'.</a>
Aqui está um valor adicional.</p>
<dl>
<dt id="nofollow">nofollow</dt>
<dd>Indica que o recurso referido não foi necessariamente linkado pelo
autor da página, e tal referencia dita não deve oferecer qualquer recurso
adicional de importancia ou ranking por agentes de usuário.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== referencia normativa ==
* [http://gmpg.org/xmdp/ XMDP]
* http://www.google.com/googleblog/2005/01/preventing-comment-spam.html
* http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

== referencias informativa ==
* VoteLinks pode ser usado pelo autor para estágio explicitamente apoiar ou contrariar, ou neutralidade para destino de um link. Implementadores implementam rel="nofollow" e VoteLinks não deve permitir paralelamente dar importância ou ranking para links com <code>rev="vote-abstain"</code> ou <code>rev="vote-against"</code>.
* Contribuído de http://developers.technorati.com/wiki/RelNoFollow

== assuntos aberto ==
Há assuntos aberto que tem sido levantados sobre rel="nofollow" que foi levantado em vários fórums, em particular, em público [http://lists.w3.org/Archives/Public/www-html W3C www-html mailing list]. Eles foram agrupados para quatro areas.

* '''Definition'''. nofollow indica um ambiente em vez de um relacionamento do qual o ambiente deve ser inferido como apropriado por useragent. Valores rel deve ser nome que indica o recurso referido é uma relação da origem.

* '''Name'''. nofollow é um nome ruim.
** overloading. não significa o mesmo que padrões de exclusão robots (robots.txt, meta robots) nofollow.
** does not mean what it says. não significa o que isso diz "não siga esse link", em vez de " não adicione importancia a esse link". [http://www.w3.org/mid/opsk3cccj9lo81gp@quark Asbjørn Ulsberg]
** not a noun. veja acima.
** alternativas sugerida:
*** noendorse - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0046.html Micah Dubinko]
*** none
*** noweight
*** unendorsed - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0057.html Lachlan Hunt]
*** unrelated - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0049.html Jens Meiert]
*** untrusted
*** nonauth - [http://www.mnot.net/blog/2003/12/29/comment_spam_and_google Mark Baker]
*** norank - [http://www.digitalburg.com/ Ben Pierce]
* '''Efficacy'''. nofollow will not affect spamming behavior.
* '''Collateral Damage'''. If tools automatically add nofollow to all 3rd party links, then many legitimate non-spam links will be ignored or given reduced weight, and thus the destination of such links will be unfortunate casualties.

=== listas adicional de assuntos ===
Listas adicional de assuntos levantados contra rel="nofollow" pode ser encontrado nos sites seguido:
* http://www.nonofollow.net/

hcard-pt-br

2006-11-20T14:49:20Z

Token:

=hCard=
hCard é um simples, aberto formato distribuído para represetar pessoas, companias, organizações e lugares usando uma representação 1:1 de propriedades e valores de padrão vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) em [[semantic-xhtml|semântica XHTML]]. hCard é um dos muitos padrões abertos de [[microformats|microformato]] apropriado para ser inserido em (X)HTML, Atom, RSS, e o arbitrário XML.

Quer começar a escrever em [[hcard|hCard]]? Use o [http://microformats.org/code/hcard/creator criador de hCard]

para detalhar algumas informações de contato e publicá-la, ou seguir [[hcard-authoring|hCard authoring tips]] para adicionar marcação hCard em sua página atual de contato.

__TOC__

== Especificação ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Autores ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

=== Inspiração e Reconhecimentos ===
Agradecimento à: meu amigo [http://vadim.com/ Vadim] que me introduziu ao vCard ''vários'' anos atrás, e se eu tivesse prestado mais atenção talvez então poderia ter ajudado muitas pessoas a evitar desperdiçar tempo reinventando várias rodas de padrões ''wheels''.

== Introdução ==
O padrão vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), tem largamente implementado interoperabilidade (e.g. Apple's "Address Book" application built into MacOSX).

Em adição, muitos bloggers se identificam pelo nome e discutem a seus amigos e família. Com só um pouco de estrutura, bloggers podem discutir as pessoas em seus blog(s) de tal um modo que spiders e outros agregadores podem receber essa informação, automaticamente convertê-las para vCard e usá-las então e qualquer aplicativo vCard ou serviços.

Essa especificação introduz o formato '''hCard''' , que usa uma representação 1:1 de propriedades e valores de mencioado no padrão vCard acima, em elemento XHTML.
podem ambos embutir diretamente hCards em suas páginas, e estilizá-las com CSS tornando-as parecido como desejado.

Em adição, hCard ativa aplicações para receber informação diretamente de páginas web sem ter que referenciar um arquivo separado

Use o [http://microformats.org/code/hcard/creator criador de hCard] para copiar o código HTML e gerar para seu blog ou website e publicá-lo em sua informação de contato.

== Semântica XHTML Princípios de Design ==
{{semantic-xhtml-design-principles}}

== Formato ==
=== Em geral===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forma a base do hCard.

O formato básico de hCard é usar nomes vCard objeto/propriedade em caixa-baixa para nomes de classes, e mapear aninhando objetos vCard diretamente para elementos XHTML aninhado.

=== Mais Equivalente Semântico ===
Para algumas propriedades há o elemento HTML que é mais combinado e conduz suas semanticas.
A seguinte propriedade DEVE ser codificada com o seguinte (X)HTML:
* <code>URL</code> um vCard que se torna <code><a class="url" href="...">...</a></code> dentro do elemento com <code>class="vcard"</code> em hCard.
* Similarmente, <code>EMAIL</code> um vCard que se torna <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> um vCard que se torna <code><img class="photo" src="..." alt="Foto de ..." /></code> ou <code><object class="photo" data="..." type="...">Foto de ...</object></code>
* <code>UID</code> um vCard simply que se torna outro semantica aplicada a uma especifico URL (ou EMAIL) para um hCard.

=== Propriedades Singular vs. Plural ===

Para propriedades que estão no singular (ex. "N" e "FN"), o primeiro elemento descendente com aquela class deve ter efeito, qualquer outros serão ignorados.

Para propriedades que podem estar no plural (ex. "TEL"), each class instance should create a instance of that property.

==== Propriedades no Singular ====

Propriedades no Singular: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

Todas as outras propriedades são plural. Essa lista foi derivada de uma analize de semantica de propriedades individuais em vCard RFC2426 e determinando logicamente que eles DEVEM ser singular pela sua semantica. Ver [[hcard-singular-properties]] para explicação.

==== Propriedades plurais Singularizadas ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

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

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

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

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

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with rel-tag. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

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

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]<br />
Technorati
</div>

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

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

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], "A. I. Cuza" University Iaşi, Romania uses hCard for each staff member.
* [http://www.finds.org.uk/ The Portable Antiquities Scheme at the British Museum] hCards added to footer of every page and to contacts section. Working on adding more and getting it right.
* In [http://www.ideasfornet.com/ IdeasForNet.com - the ideas repository] hCards were implemented partially in the footer of each page, and more comprehnsively in the contact and about pages.
* The [http://www.cst.ed.ac.uk/ Centre of Canadian Studies] at the University of Edinburgh use hCards for contact information in the footer of their site.
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh use hCards for contact information on their home page
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club] in the English Midlands uses hCard on its [http://www.westmidlandbirdclub.com/ home page], [http://www.westmidlandbirdclub.com/diary/ events diary], [http://www.westmidlandbirdclub.com/club/contact.htm contact pages] and [http://www.westmidlandbirdclub.com/site/links.htm links page]. The former is a page footer which is gradually being rolled out across the whole site.
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard
* [http://www.fischsolutions.com/ Fisch Internet Solutions] uses an embedded hCard and a vCard download to provide customers an easy way to contact them on their [http://fischsolutions.com/contactus.html Contact Us] section of the website.
* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK governement agency, formed 2006-10-01). No "fn" - which makes it invalid.
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [http://www.creative-ways.nl/ Ron Kok] uses hCards to mark-up the names and URLs of commentors on his blog. He also uses hCards in combination with XFN in his blogposts to refer to friends, and has an hCard for himself in the footer of his blog.
* [http://tagg.no Tagg Media] uses hCard for [http://heine.tagg.no/contact.php contact information] and provide link to vCard download in the contact section.
* [http://en.wikipedia.org/wiki/Neo_%28The_Matrix%29 Thomas A Anderson in Wikipedia] is now marked up with hCard.
* [http://dconstruct06.madgex.com/ d.Construct 2006 Backnetwork] uses hCards for conference delegates (and provides the markup so that delegates can copy and paste cards into their own sites).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address "Find"] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hcards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).
* [http://www.webdirections.org Web Directions ]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [http://www.markthisdate.com/contactform.html MarkThisDate.com ]. An hCard is implemented on our contactform. For our calendars hCalendars will follow as soon as possible.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] and his [http://rasterweb.net/portfolio/ Portfolio]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf Kåre Lefdal] uses hCard in the markup of his contact information
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.

=== Examples ===
* [http://www.nfwebsolutions.com/ New Frontier Web Solutions] uses hCard on their frontpage along with a link pointing to Brian Suda's [http://suda.co.uk/projects/X2V/get-vcard?uri=http://www.nfwebsolutions.com/ X2V].
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'><defs id='defs3959' /><path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < with %3C (etc., eg Brian Suda's vcard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/ Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [http://www.child-care-index.net.au/ The Australian Child Care Index] has over 3000 entries listing child care services across Australia - and every single one is marked up with an hcard!
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard
==== UTF8 Examples in the Wild ====
These examples all contain one or more characters in UTF8 that are outside the ASCII7 range and make for excellent test cases to make sure you are handling UTF8 properly throughout your hCard parsing and transforming. And especially if you are generating vCards, these test cases will help you make sure you are generating UTF8 vCards in such a way that can be recognized by UTF8 supporting vCard applications.
* [http://tantek.com/ Tantek's Thoughts] encodes Çelik as inline UTF8.

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
** <strike>WARNING - uses class="cell" instead of <span class="type">cell</span></strike> Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://elbewerk.com/2006/09/vcardexplorer-02.shtml vCardExplorer 0.2] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by Daniel Kagemann.
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Related Pages ==
* [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|feedback]]) - create your own hCard.
* [[hcard-authoring|hCard authoring]] - learn how to add hCard markup to your existing contact info.
* [[hcard-examples|hCard examples]] - Example usage of various classes within hCard,
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.
* [[hcard-issues|hCard issues]] - Please add any specific issues with the specification to the issues page.
* [[hcard-feedback|hCard feedback]] - General feedback (as opposed to specific issues) should be added to the hCard feedback page.
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]

Main Page-pt-br

2006-11-19T09:02:42Z

Token: watchlist review

__NOTOC__

= Microformatos Wiki =

'''Olá!''' Bem vindo ao microformatos wiki. Se esta é sua primeira visita, por favor veja a página de [[introduction-pt-br|introdução]].

Por favor, leia [[how-to-play-pt-br|o que fazer]] antes de fazer qualquer edição.

Por favor, leia o [[process-pt-br|procedimento]] antes de propor qualquer novo microformato.

__TOC__

==Guia Rápido==

[[what-are-microformats|O que são microformatos]]? [[what-can-you-do-with-microformats|O que você pode fazer com eles]]?

A [http://microformats.org/about/ página about], e mais recente [[press]], [[presentations]], [[podcasts]], and [[screencasts]] são bom locais para informações a fundo.

As perguntas feitas com mais frequência sobre o wiki e microformatos em geral são respondidas no [[faq]].

Quer aprender mais pessoalmente? Verifique os [[events|eventos]].

==Definição==

Uma definição popular da nossa [http://microformats.org/discuss/ lista de discussão] (ver também: [[mailing-lists]]) é "convenções simples para combinar semântica em HTML para permitir o desenvolvimento decentralizado." Mais precisamente, microformatos podem ser definidos como:
:convenções simples
:para combinar com marcação semântica
::for a specific problem domain
:para ser legível aos humanos, documentos (X)HTML/XML, feeds Atom/RSS, e XML "plano"
::que padroniza existente conteúdo com uso de padrões.
::usando brief, descritivas nomes de classes
::baseada frequentemente nos existentes padrões de interoperabilidade
:para permitir desenvolvimento decentralizado
::de recursos, ferramentas, e serviços

Simplesmente coloque: "Microformatos são uma codificação de convenção." -- [http://easy-reader.net Aaron Gustafson]

"Ou você só usa seu browser para navegar? Então isto é o século 20." -- [http://diveintomark.org Mark Pilgrim]

== Como contribuir ==

Você quer ajudar a levar microformatos ao próximo nível? Você pode:

*Verificar as coisas em aberto [[to-do-pt-br|lista do que fazer]] para ajudar a concluir.
*Ingressar na [http://microformats.org/discuss lista de emails] e [[irc|Canal de IRC]] para aprender como ajudar a responder perguntas sobre microformatos.
*[[advocacy|Advocacia]] o uso de microformatos.
*Ajudar a [[Main_Page#microformats_wiki_in_other_languages|traduza o microformatos wiki para outras linguagens]] e tornar microformatos globalmente acessível.

== Especificações ==
[[microformats-pt-br|Microformatos]] especificações de padrões abertos (ver também: [[implementations-pt-br|implementações]])
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag-pt-br]]
* [[vote-links-pt-br|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (ver também: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-pt-br|XOXO]]

== Esboços ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker-pt-br}}
* [[hresume|hResume]] {{NewMarker-pt-br}}
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Padrões do projeto ==

{{design_patterns}} 

== Discussões exploratória ==
Pesquisa e análises do mundo real [[examples|exemplos]], formatos existentes e idéias para motivar o microformatos.
*alternates [[alternates-brainstorming]], [[alternates-examples]]
*[[attention]]
* blog description [[blog-description-examples|examplos]]
* blog info [[blog-info-examples|exemplos]]
* blog post [[blog-post-examples|exemplos]], [[blog-post-formats|formatos]], e [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|exemplos]], [[book-formats|formatos]], e [[book-brainstorming|brainstorming]]
* chat [[chat-examples|exemplos]], [[chat-formats|formatos]], e [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formatos]], [[citation-brainstorming|brainstorming]], e [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], e [[comments-formats|formatos]] (Alguma coisa precisa ser extraída de [[comments-formats]])
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}
* directions [[directions-examples|examplos]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formatos]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examplos]], and [[distributed-conversation-formats|formatos]]
* forms [[forms-examples|exemplos]]
* genealogy [[genealogy-formats|exemplos]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examplos]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|exemplos]] e [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|exemplos]], [[last-modified-formats|formatos]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], e [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|exemplos]], [[listing-formats|formatos]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formatos]]. (ver também [[adr]] e [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|exemplos]], [[media-info-formats|formatos]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|exemplos]], [[meeting-minutes-formats|formatos]], e [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|exemplos]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|brainstorming]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|exemplos]]
* photo note [[photo-note-examples|exemplos]]
* recipe [[recipe-examples|exemplos]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], e [[requirements-testing-examples|examplos]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], e [[resume-formats|formatos]]
* review [[review-examples|examples]], e [[review-formats|formatosformatos]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|exemplos]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - para a remarcação de nomes científicos de coisas vivas: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}
* table [[table-examples|exemplos]]
* tagspeak [[tagspeak-examples|exemplos]]
* tagcloud [[tagcloud-examples|exemplos]], e [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|exemplos]]
* [[uid]]
* widget [[widget-examples|exemplos]], e [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formatos]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formatos]], e [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (ver também [[xmdp-faq]])

== Exemplos ==
* [[examples]]
* [[zen-garden]]

== Ferramentas & Casos Prova & Pesquisa Adicional ==

O primeira lugar a procurar por exemplos, códigos, e casos é nas páginas de cada microformato indivídual. Há poucas ferramentas de atalho e serviços que precisam processar mais que um microformato. Esta sessão é destinada a editores, analisadores, validadores, testadores de casos e a outras informações relevantes através de microformatos multíplos.

*[[accessibility|acessibilidade]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== Areas de trabalho compartilhado ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker-pt-br}}
* [[demo]] - uma página com links para rapidamente demostrar microformatos funcionando na prática.
* [[events|eventos]] {{NewMarker-pt-br}}
* [[to-do-pt-br|o que fazer]]
* [[user-interface]]
* [[marked-for-deletion]]

== wiki em outras linguagens==

Você pode ler e editar artigos microformatos em qualquer língua:

* linguagens com mais de 50 artigos
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* linguagens com mais de 20 artigos
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
* linguagens com mais de 2 artgos
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* linguagens com 2 artigos
** [[Main_Page-de|Deutsch (German)]]

==== tradução de microformatos dos outros ====
Há outras páginas/sites externas com traduções sobre microformatos. Se você está trabalhando em uma dessas, por favor, considere como tradução o principal site de microformatos!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Iniciar um microformatos wiki em outras línguas ===

Não vê a tradução que gostaria? Ajuda a traduzir a wiki para sua língua!

Estamos trabalhando na melhoria das páginas em outra linguagem.

Enquanto isso, veja [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Página em coordenadas Multi-língua], e [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia Como iniciar um novo Wikipedia] para algumas dicas, conselhos, e convenções de comunidade.

Para começar, você pode acessar as [[stable-pages|páginas estáveis]], que são páginas que são relativamente estáveis e tem apenas pequenas mudanças editoriais, que as tornam muito fácil mantê-las em sincronia com a versão em inglês, pelo uso do recurso [[Special:Watchlist|my watchlist]] (use-o para monitorar as páginas que você traduziu).

Nome do artigo: a versão traduzida de uma página, coloque o mesmo nome para a página e simplesmente adicione o código de identificador de linguagem RFC 3066 como um traço no sulfixo do nome original.
Ex. para a versão em Francês, [[Main_Page]] torna-se [[Main_Page-fr]], e [[how-to-play]] torna-se [[how-to-play-fr]].

vote-links-pt-br

2006-11-19T08:38:52Z

Token:

= Vote Links =
__TOC__
== Especificação 2005 ==
=== Editor ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (formalmente da [http://microsoft.com/ Microsoft Corporation])

=== Conceito ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com, Technorati,Inc.]

=== Autores ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

=== Inspiração e Reconhecimentos ===
Obrigado a todos que deram retorno ao VoteLinks. Especialmente ao EtanWexler,
que fez a primeira realmente boa documentação para que VoteLinks deveria usar 'rev' em vez de 'rel' (confira [[vote-links-faq]]) e ao John Allsopp
que semelhantemente contestou o uso do 'rel',
e ajudou co-autores a explorar questões [[RelFAQ]] e assuntos sobre o uso de HTML4 'rel', atributos 'rev' e linktypes em geral.

== Introdução ==
Indexando e rastreando aplicações que tratam todos os links como confirmação e expressões de apoio. Este é um problema, ao precisarmos links aqueles que discordamos também, para discutir porque.

== Especificação ==

VoteLinks é um [[elemental-microformat|elemental microformat]], e um dos diversos [[microformats|microformat]] de padrão aberto.
Propomos um conjunto de três novos valores para o atributo rev em uma tag <a> (hyperlink) em HTML

Os novos valores são "vote-for" "vote-abstain" or "vote-against", que são mutualmente exclusivos e respectivamente representam, acordo, abstenção/indiferença e desacordo

Um link sem um valor explícito do voto em 'rev' é considerado um "vote-for" (acordo) ou mesmo "vote-abstain" (abstenção), dependendo do caso.

Comentário adicional humano-legível pode ser adicionado usando um existente atributo 'title', em que a maioria dos browser mostram como um ''rollover''.

Exemplos:
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="pura paródia">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="bebida com xarope de milho sujo">Raging Cow</a>
</nowiki></pre>

=== Desaprovado: Uso de 'rel' em VoteLinks ===
No antigo esboço da especificação usada para valor 'rel' em vez do atributo 'rev'. Analise e retorno demostraram que é inapropriado usar 'rel', enquanto 'rev' foi muito mais importante. Veja o [[RelFAQ]] para mais detalhes.

Implementações PODEM suportar links com valores VoteLinks em atributos 'rel' para fins de compatibilidade retroativa com qualquer conteúdo atual de VoteLinks

Autores NÃO DEVEM usar 'rel' para valores VoteLinks.

== Perfil XMDP ==
<pre><nowiki>
<dl class="profile">
<dt id="rev">rev</dt>
<dd><p><a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
Definição HTML4 para o atributo 'rev'.</a>
Aqui estão alguns valores adicionais.</p>
<dl>
<dt id="vote-for">vote-for</dt>
<dd>Indica concordância ou recomendação do recurso indicado.</dd>
<dt id="vote-abstain">vote-abstain</dt>
<dd>Indica abstenção ou indiferença do recurso indicado.</dd>
<dt id="vote-against">vote-against</dt>
<dd>Indica desacordo ou recomendação contra ao recurso indicado.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Implementação ==
Essa seção é '''informativa'''.

* [http://moloko.itc.it/paoloblog/ Paolo Massa] criou [http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks], uma leve extensão do Firefox que mostra informações vote-for, vote-against. (Note que links para download do SemanticLinks foram removidos pelo autor.)

== Referências de Normativa ==
* [http://gmpg.org/xmdp/ XMDP]

== Trabalho Relacionado ==
* [[xoxo]]
* [http://gmpg.org/xfn/ XFN]
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[rellicense]]
* [[reltag]]
* [[relnofollow]]

== FAQ ==
* Ver [[votelinks-faq]] e o largo [[rel-faq]].
* Ver também [[votelinks-issues]] para temas que foram levantados com votelinks [[microformat]].

rel-tag-pt-br

2006-11-11T04:56:37Z

Token: /* Encoding issues */

<h1> rel-tag </h1>

__TOC__

== Especificação do Esboço 2005-01-10 ==
=== Editores/Autores ===
[http://tantek.com/ Tantek Çelik]

[http://epeus.blogspot.com/ Kevin Marks]

=== Concepção ===
[http://powazek.com/ Derek Powazek]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==
[[Rel-Tag]] é um dos muitos [[microformats-pt-br|microformatos]]. Para inclusão <code>rel="tag"</code> a um hyperlink, uma página indica que o destino daquele hyperlink é destinado a "tag" (ou palavra-chave/assunto) para a página atual. Note que a tag pode apenas referir a porção maior da página atual (como. uma postagem de blog). ex: por colocar este link em uma página,

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

o autor indica que a página (ou alguma parte da página) tem uma tag "tech".

A link da página DEVE existir e é a página linkada, em vez do texto do link que define a tag. O último caminho do componente da URL é o texto da tag, então

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

deveria indicar a tag "tech" em vez de "fish".

== Escopo ==
rel="tag" é especialmente designado para conteúdo "tagging", tipicamente páginas da web (ou porções dela, como blog-postagens)

rel="tag" NÃO é destinada para estiquetar/por tag ("tagging") em URL's proprietárias ou para conteúdo externo.
Há demanda por uma sintaxe decentralizada maior pela etiquetagem de URL's externa para a página atual, mas isso não é significativo. Veja [[xfolk|xFolk]] e [[hreview|hReview]] para formas de por tag em URLs arbitrárias.

Se você precisa definir tags como parte de um formato mais especializado. rel="tag"
é uma forma recomendada de fazer isso, e [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]] e [[hcalendar|hCalendar]] todos esses.
== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="tag">tag</dt>
<dd>Indicates that the referred resource serves as a "tag",
or keyword/subject, for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Espaços em Tag ==
Tags são embutidas em HTTP URIs em uma bem-definida maneira de modo que tags embutidas em um HTML URI pode ser extraido mecaniamente da URI.
Especialmente, o último segmento da porção do caminho da URL (depois do caracter final "/") contém o valor da tag.
Por exemplo, a URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contém a tag "foo".

Assim, para propósitos de comparação duas HTTP URIs como tags, o último segmento do caminho da porção deve ser extraídoe somente aquele valor (aquele valor da tag) deve ser comparado.

''Precisa-se de mais linguagens formais sobre comparações e sobre processo de extração.''

O destino de um hyperlink rel="tag" é necessário para ser um espaço de tag (um local que confere ou define tags), onde o último segmento do caminho de uma URL é a tag, ex:

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

é uma URL para a tag "tech".
Tags podem apenas ser localizadas em um caminho URL, e apenas o último segmento do caminho. Tags podem não estar localizadas no paramentro solicitado ou fragmento identificador. ex:

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

ainda é uma URL para a tag "tech", e não "fish" e não "emu".

Como a última parte do espaço da tag da URL da qual qualquer estrutura é requirida é o último caminho do segmento, um espaço de tag da URL pode estar localizada em qualquer domínio. Autores podem escolher um link para uma tag em uma tag particupar para oferecer um significado especifico. Ex: uma tag para a tecnologia pode linkar para:

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

Barras posterior na tag da URL são ignoradas, como:

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
a URL rel-tag é tratada como:
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>

== Assuntos de Encodificação ==
Espaços podem ser convertidos por <code>+</code> ou <code>%20</code>. Como os caracteres unicode são convertidos, por favor veja a lista em [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. Por exemplo:

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>
Note que se usar Wikipedia como um tagspace, como descrito acima, você deve usar <code>%20</code> como eles convertem '+' por <code>%2B</code>, causando uma página com mais sinais no título (que geralmente não existe) para aparecer.

== Tags São Vísiveis a Metadata ==
Hyperlinks <code>rel="tag"</code> são destinados a ser vísiveis a links na páginas e postagens.
Esse é um contraste perfeito para meta keywords (que está invísivel e tipicamente nunca relevado a leitores),
e assim é ao menos um tanto mais resiliente a problemas que atormentam meta keywords.

Tornando tag hyperlinks vísiveis têm um benefício adicional ao fazer isso mais óbvio al eitores se uma página está abusando de links com tag, e assim oferecer mais pontos precisos para melhor ambiente
Isso também torna mais óbvio a autores, que podem nem sempre estar ciente de que metadata invísivel estar sendo gerada em seu benefício

Como um resultado da variante da sintaxe de tag invísivel: <code><link rel="tag" href="..." /></code> NÃO DEVEM ser suportada pela implementação.

== Implementações ==
Essa seção é '''informativa'''.

As seguintes implementações tem sido desenvolvidas na qual ou gera ou analisa link rel-tag
Se você tem uma implementação rel-tag, sinta-se livre para adicioná-la ao topo dessa lista.

[[rel-tag#Implementations]]

== Referência ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

=== Informative References ===
* [[hreview|hReview]] uses rel-tag for tags and scalar tags
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds
* [[hcard|hCard]] can use rel-tag for categories
* [[hcalendar|hCalendar]] can use rel-tag for categories
* [http://technorati.com/help/tags.html Using Technorati Tags]
* Contributed from http://developers.technorati.com/wiki/RelTag

== Discussions ==
* Feedback is encouraged on the [[rel-tag-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]

=== Q&A ===
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.

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

rel-tag-pt-br

2006-11-11T04:54:03Z

Token: /* Tag Spaces */

<h1> rel-tag </h1>

__TOC__

== Especificação do Esboço 2005-01-10 ==
=== Editores/Autores ===
[http://tantek.com/ Tantek Çelik]

[http://epeus.blogspot.com/ Kevin Marks]

=== Concepção ===
[http://powazek.com/ Derek Powazek]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==
[[Rel-Tag]] é um dos muitos [[microformats-pt-br|microformatos]]. Para inclusão <code>rel="tag"</code> a um hyperlink, uma página indica que o destino daquele hyperlink é destinado a "tag" (ou palavra-chave/assunto) para a página atual. Note que a tag pode apenas referir a porção maior da página atual (como. uma postagem de blog). ex: por colocar este link em uma página,

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

o autor indica que a página (ou alguma parte da página) tem uma tag "tech".

A link da página DEVE existir e é a página linkada, em vez do texto do link que define a tag. O último caminho do componente da URL é o texto da tag, então

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

deveria indicar a tag "tech" em vez de "fish".

== Escopo ==
rel="tag" é especialmente designado para conteúdo "tagging", tipicamente páginas da web (ou porções dela, como blog-postagens)

rel="tag" NÃO é destinada para estiquetar/por tag ("tagging") em URL's proprietárias ou para conteúdo externo.
Há demanda por uma sintaxe decentralizada maior pela etiquetagem de URL's externa para a página atual, mas isso não é significativo. Veja [[xfolk|xFolk]] e [[hreview|hReview]] para formas de por tag em URLs arbitrárias.

Se você precisa definir tags como parte de um formato mais especializado. rel="tag"
é uma forma recomendada de fazer isso, e [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]] e [[hcalendar|hCalendar]] todos esses.
== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="tag">tag</dt>
<dd>Indicates that the referred resource serves as a "tag",
or keyword/subject, for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Espaços em Tag ==
Tags são embutidas em HTTP URIs em uma bem-definida maneira de modo que tags embutidas em um HTML URI pode ser extraido mecaniamente da URI.
Especialmente, o último segmento da porção do caminho da URL (depois do caracter final "/") contém o valor da tag.
Por exemplo, a URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contém a tag "foo".

Assim, para propósitos de comparação duas HTTP URIs como tags, o último segmento do caminho da porção deve ser extraídoe somente aquele valor (aquele valor da tag) deve ser comparado.

''Precisa-se de mais linguagens formais sobre comparações e sobre processo de extração.''

O destino de um hyperlink rel="tag" é necessário para ser um espaço de tag (um local que confere ou define tags), onde o último segmento do caminho de uma URL é a tag, ex:

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

é uma URL para a tag "tech".
Tags podem apenas ser localizadas em um caminho URL, e apenas o último segmento do caminho. Tags podem não estar localizadas no paramentro solicitado ou fragmento identificador. ex:

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

ainda é uma URL para a tag "tech", e não "fish" e não "emu".

Como a última parte do espaço da tag da URL da qual qualquer estrutura é requirida é o último caminho do segmento, um espaço de tag da URL pode estar localizada em qualquer domínio. Autores podem escolher um link para uma tag em uma tag particupar para oferecer um significado especifico. Ex: uma tag para a tecnologia pode linkar para:

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

Barras posterior na tag da URL são ignoradas, como:

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
a URL rel-tag é tratada como:
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>

== Encoding issues ==
Espaços podem ser convertidos como <code>+</code> ou <code>%20</code>. Como caracters unicode são codificados, veja em [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. Por exemplo:

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>
Note que se usar Wikipedia como um tagspace, como discutido acima, você deve usar <code>%20</code> as they remap '+' to <code>%2B</code>, causing a page with a plus sign in the title (which usually does not exist) to appear.

== Tags São Vísiveis a Metadata ==
Hyperlinks <code>rel="tag"</code> são destinados a ser vísiveis a links na páginas e postagens.
Esse é um contraste perfeito para meta keywords (que está invísivel e tipicamente nunca relevado a leitores),
e assim é ao menos um tanto mais resiliente a problemas que atormentam meta keywords.

Tornando tag hyperlinks vísiveis têm um benefício adicional ao fazer isso mais óbvio al eitores se uma página está abusando de links com tag, e assim oferecer mais pontos precisos para melhor ambiente
Isso também torna mais óbvio a autores, que podem nem sempre estar ciente de que metadata invísivel estar sendo gerada em seu benefício

Como um resultado da variante da sintaxe de tag invísivel: <code><link rel="tag" href="..." /></code> NÃO DEVEM ser suportada pela implementação.

== Implementações ==
Essa seção é '''informativa'''.

As seguintes implementações tem sido desenvolvidas na qual ou gera ou analisa link rel-tag
Se você tem uma implementação rel-tag, sinta-se livre para adicioná-la ao topo dessa lista.

[[rel-tag#Implementations]]

== Referência ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

=== Informative References ===
* [[hreview|hReview]] uses rel-tag for tags and scalar tags
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds
* [[hcard|hCard]] can use rel-tag for categories
* [[hcalendar|hCalendar]] can use rel-tag for categories
* [http://technorati.com/help/tags.html Using Technorati Tags]
* Contributed from http://developers.technorati.com/wiki/RelTag

== Discussions ==
* Feedback is encouraged on the [[rel-tag-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]

=== Q&A ===
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.

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

rel-tag-pt-br

2006-11-11T02:15:28Z

Token: First step of translation

<h1> rel-tag </h1>

__TOC__

== Especificação do Esboço 2005-01-10 ==
=== Editores/Autores ===
[http://tantek.com/ Tantek Çelik]

[http://epeus.blogspot.com/ Kevin Marks]

=== Concepção ===
[http://powazek.com/ Derek Powazek]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==
[[Rel-Tag]] é um dos muitos [[microformats-pt-br|microformatos]]. Para inclusão <code>rel="tag"</code> a um hyperlink, uma página indica que o destino daquele hyperlink é destinado a "tag" (ou palavra-chave/assunto) para a página atual. Note que a tag pode apenas referir a porção maior da página atual (como. uma postagem de blog). ex: por colocar este link em uma página,

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

o autor indica que a página (ou alguma parte da página) tem uma tag "tech".

A link da página DEVE existir e é a página linkada, em vez do texto do link que define a tag. O último caminho do componente da URL é o texto da tag, então

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

deveria indicar a tag "tech" em vez de "fish".

== Escopo ==
rel="tag" é especialmente designado para conteúdo "tagging", tipicamente páginas da web (ou porções dela, como blog-postagens)

rel="tag" NÃO é destinada para estiquetar/por tag ("tagging") em URL's proprietárias ou para conteúdo externo.
Há demanda por uma sintaxe decentralizada maior pela etiquetagem de URL's externa para a página atual, mas isso não é significativo. Veja [[xfolk|xFolk]] e [[hreview|hReview]] para formas de por tag em URLs arbitrárias.

Se você precisa definir tags como parte de um formato mais especializado. rel="tag"
é uma forma recomendada de fazer isso, e [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]] e [[hcalendar|hCalendar]] todos esses.
== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="tag">tag</dt>
<dd>Indicates that the referred resource serves as a "tag",
or keyword/subject, for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Tag Spaces ==
Tags são embutidas em HTTP URIs em uma bem-definida maneira de modo que tags embutidas em um HTML URI pode ser extraido mecaniamente da URI.
Especialmente, o último segmento da porção do caminho da URL (depois do caracter final "/") contém o valor da tag.
Por exemplo, a URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contém a tag "foo".

Assim, para propósitos de comparação duas HTTP URIs como tags, o último segmento do caminho da porção deve ser extraídoe somente aquele valor (aquele valor da tag) deve ser comparado.

''Precisam mais linguagem formal sobre comparação e processo de extração.''

O destino de um hyperlink rel="tag" é necessário para ser um espaço de tag (um local que confere ou define tags), onde o último segmento do caminho de uma URL é a tag, ex:

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

é uma URL para a tag "tech".
Tags podem apenas ser localizadas em um caminho URL, e apenas o último segmento do caminho. Tags podem não estar localizadas no paramentro solicitado ou fragmento identificador. ex:

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

ainda é uma URL para a tag "tech", e não "fish" e não "emu".

Como a última parte do espaço da tag da URL da qual qualquer estrutura é requirida é o último caminho do segmento, um espaço de tag da URL pode estar localizada em qualquer domínio. Autores podem escolher um link para uma tag em uma tag particupar para oferecer um significado especifico. Ex: uma tag para a tecnologia pode linkar para:

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

Barras posterior na tag da URL são ignoradas, como:

Trailing slashes in tag URLs are ignored, that is:

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
a URL rel-tag é tratada como:
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>

== Encoding issues ==
Espaços podem ser convertidos como <code>+</code> ou <code>%20</code>. Como caracters unicode são codificados, veja em [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. Por exemplo:

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>
Note que se usar Wikipedia como um tagspace, como discutido acima, você deve usar <code>%20</code> as they remap '+' to <code>%2B</code>, causing a page with a plus sign in the title (which usually does not exist) to appear.

== Tags São Vísiveis a Metadata ==
Hyperlinks <code>rel="tag"</code> são destinados a ser vísiveis a links na páginas e postagens.
Esse é um contraste perfeito para meta keywords (que está invísivel e tipicamente nunca relevado a leitores),
e assim é ao menos um tanto mais resiliente a problemas que atormentam meta keywords.

Tornando tag hyperlinks vísiveis têm um benefício adicional ao fazer isso mais óbvio al eitores se uma página está abusando de links com tag, e assim oferecer mais pontos precisos para melhor ambiente
Isso também torna mais óbvio a autores, que podem nem sempre estar ciente de que metadata invísivel estar sendo gerada em seu benefício

Como um resultado da variante da sintaxe de tag invísivel: <code><link rel="tag" href="..." /></code> NÃO DEVEM ser suportada pela implementação.

== Implementações ==
Essa seção é '''informativa'''.

As seguintes implementações tem sido desenvolvidas na qual ou gera ou analisa link rel-tag
Se você tem uma implementação rel-tag, sinta-se livre para adicioná-la ao topo dessa lista.

[[rel-tag#Implementations]]

== Referência ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

=== Informative References ===
* [[hreview|hReview]] uses rel-tag for tags and scalar tags
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds
* [[hcard|hCard]] can use rel-tag for categories
* [[hcalendar|hCalendar]] can use rel-tag for categories
* [http://technorati.com/help/tags.html Using Technorati Tags]
* Contributed from http://developers.technorati.com/wiki/RelTag

== Discussions ==
* Feedback is encouraged on the [[rel-tag-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]

=== Q&A ===
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.

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

xoxo-pt-br

2006-11-09T02:51:46Z

Token:

<h1> XOXO 1.0: Extensible Open XHTML Outlines </h1>

XOXO é um formato de esboço simples, aberto escrito em padrão XHTML e adequado para ser embutido em (X)HTML, Atom, RSS, e XML arbitrário. XOXO é um dos muitos [[microformats-pt-br|microformatos]] de padrões aberto.

__TOC__

== Draft Specification 2004-10-01 ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== Autores ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc] (formerly of [http://microsoft.com/ Microsoft Corporation])
* [http://diveintomark.org/ Mark Pilgrim], [http://ibm.com IBM]
* [http://www.blogologue.com/ Morten W. Petersen]

=== Copyright ===
{{MicroFormatCopyrightStatement2003}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Prefácio ==
Quando estávamos discutindo [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek apontou que XHTML tem tudo de necessário para expressar semanticamente esboços e subscrição em blogroll-derivados em um formato XML que são ambos renderizável interativamente por navegadores e analisável por motores XML rígidas (strict). Esta página está aqui para discutir essa idéia.

=== Nome ===
XOXO significa eXtensible Open XHTML Outlines, e é pronunciado variadamente como 'ecks oh ecks oh', 'zho-zho' ou 'sho-sho'.

== Sumário ==
Essa especificação define um novo tipo de documento XHTML que é baseada sob o módulo de estrutura e módulos definido em Modularização de XHTML

XOXO é um dos muitos [[microformats-pt-br|microformatos]]. Essa especificação define um novo tipo de documento XHTML que é baseada sob o módulo de estrutura e módulos definido em Modularização de XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). O propósito do tipo de documento XOXO é para servir como base para esboço de XHTML amigável para processamento por motores XML e para fácil renderização interativa por browsers.

== O Tipo de Documento XOXO ==
O tipo de documento XOXO é composto dos seguintes módulos XHTML. Os elementos, atributos e modelos de conteúdo mínimos associado com estes módulos são definidos pela "Modularização de XHTML"
([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). Os elementos que estão listados aqui são para propósitos de informação, mas as definições de "Modularização de XHTML" devem ser consideradas definitivas. Na versão online desse documento, os módulos online na lista abaixo fazem ligação para definição dos módulos dentro da atual versão de "Modularização de XHTML"

[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]
body, head, html, title
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]
a
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]
dl, dt, dd, ol, ul, li
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]
meta
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]
style element
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]
style attribute
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]
link
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]
Attribute compact on ol and ul

=== O Perfil XOXO ===

Veja [[xoxo-profile]] para o perfil [http://gmpg.org/xmdp XMDP] de XOXO que define os valores XOXO para o atributo class.

== Simples Fragmento XOXO ==

=== Marcação ===

<pre><nowiki><ol class='xoxo'>
<li>Assunto 1
<ol>
<li>subponto a</li>
<li>subponto b</li>
</ol>
</li>
<li>Assunto 2
<ol compact="compact">
<li>subponto c</li>
<li>subponto d</li>
</ol>
</li>
<li>Assunto 3
<ol>
<li>subponto e</li>
</ol>
</li>
</ol>
</nowiki></pre>

=== Exemplo de Renderização ===
<pre><nowiki>
1. Assunto 1
a. subponto a
b. subponto b
2. Assunto 2
3. Assunto 3
a. subponto e
</nowiki></pre>
=== Uso do atributo 'compact' ===

Note que o uso do atributo 'compact' indica que os subpontos de título de "Assunto 2" não estão em um estágio expandido. A ausência do atributo 'compact' indica que outros títulos estão em um estágio expandido.

=== Regras de Estilo Padrão para o Exemplo da Renderização ===

<pre><nowiki>
ol.xoxo { list-style:decimal; }
ol.xoxo ol { list-style:lower-latin; }
ol[compact="compact"] { display:none; }
</nowiki></pre>

== Mais Exemplos Simples ==

MarkP fez um conjunto de exemplos que demostra ambos a simplicidade de marcação e a riquesa de apresentação que é possível:

* [http://diveintomark.org/public/2004/01/xo-flat.xo simple arquivo XO que pode ser embutido diretamente em uma página XHTML]
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.
** na tentativa de cumprir com príncipios semanticos o atributo "compact" para os elementos ol e ul é o que conduzem o estágio de exibição. Por scripting, estou definindo classes pertercentes ao elemento li para adicionar flexibilidade de estilização, através do CSS Gurus devee estar apto a substitur "li.expanded" no outlines.css com algum outro seletor CSS que diz "selecione um nó li que contém um nó ol com um atributo 'compact'"

== Propriedades de Itens Esboço ==
Esboços tipicamente consiste de uma hiearquia de pontos e subpontos. Cada um desses pontos (item do esboço) si próprio pode ter algumas propriedades (como atributos ou metadata) que são necessários para ser representado. Talvez a mais comum propriedade adicional em itens de esboço na prática é a URL como demostrado nos exemplos de Mark Pilgrim acima

Até mesmo o texto label/title de um item de esboço pode ser considerado uma propriedade comum. Algumas tais propriedades comum:

* text /texto
* description /descrição
* url (frequentemente chamado de xmlurl ou htmlurl; as veses de permalink)
* title /título
* type /tipo (hint of the MIME type of the resource indicated by the URL)

Em geral, propriedades em um item de esboço <code><nowiki><li></nowiki></code>
são representado por um lista de definição alojado. A rigor, é o primeiro <code><nowiki><dl></nowiki></code> dentro do <code><nowiki><li></nowiki></code> e antes de qualquer seguinte <code><nowiki><ol></nowiki></code>, <code><nowiki><ul></nowiki></code>, ou <code><li></code>, exemplo. aqui é um item "item 1" com uma propriedades descrição (os subpontos existem puramente como um ponto de referencia para um exemplo recente).

<pre><nowiki>
<ol class='xoxo'>
<li>item 1
<dl>
<dt>description</dt>
<dd>This item represents the main point we're trying to make.</dd>
</dl>
<ol>
<li>subpoint a</li>
<li>subpoint b</li>
</ol>
</li>
</nowiki></pre>

=== Propriedades Especiais ===
Há um punhado de propriedades especial que estamos apto a representar mais diretamente e convenientemente com o XHTML semântico construíndo blocos que temos incluíndo, em vez de termos de uma lista de definição. Predominantemente levada da lista abaoxp de propriedades comum, são esses:
* text, url, title, type, e rel (abreviação de relationship/relação)

Se fossemos representá-los de forma simples como termos de definição (incluindo a propriedade "description" do exemplo anterior), eles poderiam se parecer com algo como isso:

Exemplo de causa de discussão apenas / não um exemplo XOXO canônico:

<pre><nowiki>
<ol class='xoxo'>
<li>
<dl>
<dt>texto</dt>
<dd>item 1</dd>
<dt>description</dt>
<dd> Esse item representa o ponto principal que tentamos fazer.</dd>
<dt>url</dt>
<dd>http://example.com/more.xoxo</dd>
<dt>title</dt>
<dd>title of item 1</dd>
<dt>type</dt>
<dd>text/xml</dd>
<dt>rel</dt>
<dd>help</dd>
</dl>
</li>
</nowiki></pre>

Embora, levando vantagem na semântica o elemento <code><a href></code>, estamos apto a simplificar dramaticamente os casos comum que utilizamos nessas propriedades. Da perspectiva de analisadores, isto aplica-se primeiro ao elemento <code><a href></code> diretamente dentro do <code><nowiki><li></nowiki></code>.

Exemplo XOXO Atual:

<pre><nowiki>
<ol class='xoxo'>
<li><a href="http://example.com/more.xoxo"
title="titulo do item 1"
type="text/xml"
rel="help">item 1</a>

<dl>
<dt>descrição</dt>
<dd>Esse item representa o ponto principal do que estamos fazendo.</dd>
</dl>
</li>
</nowiki></pre>
Qualquer outras propriedades são simplesmente adicionadas para a lista de definição na mesma forma como a propriedades "description"

== Publicação XOXO ==

XOXO pode ser publicado de duas formas, XHTML válido, e simples XML bem-formado.

=== XHTML Válido XOXO ===

Uma página XHTML válido XOXO é um documento XHTML completo.

<pre><nowiki>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Página XOXO</title>
</head>
<body>
<ol class="xoxo">
<li><a href="URL-one">TEXTO-um</a></li>
<li><a href="URL-two">TEXTO-dois</a></li>
...
</ol>
</body>
</html>
</nowiki></pre>

==== Content-Type ====

XHTML Válido XOXO DEVE ser servidor com esse cabeçalho Content-Type para a máxima compatibilidade de navegação.

<pre><nowiki>
Content-Type: text/html; charset=utf-8
</nowiki></pre>

Isso DEVE ser servidor com um desses cabeçalhos Content-Type

<pre><nowiki>
Content-Type: text/html; charset=utf-8
Content-Type: application/xhtml+xml
</nowiki></pre>

=== XML bem-formado XOXO ===

O elemento raiz da uma simples página XML bem-formado XOXO é ou um <code>ol</code> ou <code>ul</code> com nome de classes de "xoxo". Essa variante é ideal para distribuição e transclusion em páginas (X)HTML com [[rest/ahah|AHAH]].

<pre><nowiki>
<ol class="xoxo">
<li><a href="URL-one">TEXTO-um</a</li>
<li><a href="URL-two">TEXTO-dois</a></li>
...
</ol>
</nowiki></pre>

==== Content-Type ====

Simples XML bem-formado XOXO DEVE ser servidor com este cabeçalho Content-Type:
<pre><nowiki>
Content-Type: text/xml; charset=utf-8
</nowiki></pre>

Ele deve ser servido com um desses cabeçalhos Content-Type:

<pre><nowiki>
Content-Type: text/xml; charset=utf-8
Content-Type: application/xml
Content-Type: application/xml; charset=utf-8
</nowiki></pre>

== Exemplos ==
Esta seção é '''informativa'''.

Grande múmeros para documentar completamente. Quase cada blogroll na Web pode ser analisável como XOXO,
desde que eles são tipicamente uma lista não ordenada de lista de items de hyperlinks, que estão dentro do perfil XOXO.

== Implementações ==
Esta seção é '''informativa'''.

* [http://chneukirchen.org/blog/ Christian Neukirchen] foi [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html escrito um xoxo.rb, um analisador XOXO e gerado por Ruby]
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.
* http://tool-man.org/examples/sorting.html é uma ótima demostração de ''arrastar e soltar'' de apresentação de listas XOXO com javascript e CSS.
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]

=== Exemplo de Código ===

* Veja a página [[xoxo-sample-code]] por exemplos de código aberto para ler e escrever arquivos XOXO.
* Veja também a página [[xoxo-compact-sample]] com fontes de CSS e JS que modificam a aparencia e sensação de algumas muitos XOXO planos ter virado triângulos para alojar lista que respeitam o atributo compact como dito.

== Esquemas XOXO ==
Esta seção é '''informativa'''.

Nota: estes podem estar desatualizados e requerer atualização para refletir o uso do <dl> para explicar itens XOXO com propriedades arbitrárias.
* [[DTDs]]
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]

== Referencias ==
=== Normative References ===
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]
* [http://gmpg.org/xmdp/ XMDP]
* [http://gmpg.org/xfn/ XFN]

=== Referencias Informativa ===
This section is '''informative'''.
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[VoteLinks]]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://opml.scripting.com/spec OPML 1.0]
* Contributed from http://developers.technorati.com/wiki/XOXO

=== Trabalho Similar ===
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)

=== Leitura Vinculado ===
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].
* [http://raybenchen.blogspot.com/2005/11/is-crappy-format-worth-saving.html Dr. Tao Chen on why it is better to use XOXO than OPML going forward]

=== Leitura Desvinculado ===
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.

=== Materiais Promocionais ===
* Há uma completa linha de roupas e acessórios XOXO em. [http://www.xoxo.com/home.php Compre materiais XOXO online].

== Discussões ==
Essa especificação é um trabalho em progresso. Como aspectos adicionais estão discutidos, compreendidos e escritos, eles serão adicionados. Há um documento separado que estamos mantendo nossas idéias eoutras relações exploratórias em XOXO:

* Veja [[xoxo-brainstorming]] para pensamentos adicionais de como usar XOXO para usos especificos.
* Veja também [http://www.technorati.com/cosmos/referer.html os blogs de discussão nessa página].
** [http://blogxoxo.blogspot.com/ XOXO Blog]

=== Perguntas&Respostas ===
* Se você tem qualquer dúvida sobre XOXO, verifique nosso [[xoxo-faq]], e se você não encontrar respostas, adicione-a.!

=== Assuntos ===
* Por favor, adicione qualquer assunto com a especificação no documento separado [[xoxo-issues]] (em inglês).

User talk:ChristopheDucamp

2006-11-07T02:07:22Z

Token: /* Translation */

==Beau travail!==

Je tiens à te féliciter pour ton travail remarquable de traduction des pages du wiki! C'est du beau boulot! :-) [[User:Remi|Remi]] 09:52, 27 Jun 2006 (PDT)

''Merci Rémi. Je tente encore de comprendre et aimerais bien pouvoir mettre quelques microformats en application notamment avec le développement d'un site francophone en dur avec un blog... qui pourrait héberger les traductions de quelques billets du blog http://microformats.org/, s'inspirer du design original, et aussi pointer les efforts de quelques francophones ;-) -- [[xtof]] | <small>[[User talk:ChristopheDucamp|talk]]</small> 23:13, 27 Jun 2006 (PDT)

<div style="display:none">
[id_5]
[http://freeonlinecasinoslots.blogspot.com/ free online casino slots]
[http://vip-freeonlineslots.blogspot.com/ free online slots]
[http://vip-bestonlinecasinos.blogspot.com/ best online casinos]
[http://atlanticcitycasinos.blogspot.com/ atlantic city casinos]
</div>

== Translation ==

Are you using automatic translator to translate the pages?
[[User:Token|Token]] 18:07, 6 Nov 2006 (PST)

User talk:ChristopheDucamp

2006-11-07T02:06:54Z

Token: Translation

design-patterns-pt-br

2006-11-05T05:34:58Z

Token:

= Projetos Padrões =

{{design_patterns-pt-br}}

Template:design patterns-pt-br

2006-11-05T05:34:11Z

Token:

Os '''Padrões do Projeto''' ou ''Design patterns'' dá aos autores de microformato um vocabulário para expressar suas idéias consistentemente com o que já tem sido feito. ''Se você está tentando experiementar com suas mãos ao escrever um microformato '''[[process|leia isso primeiro]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|nomes de class definidos por todo od microformatos]]
* [[include-pattern]], [[include-pattern-feedback]] {{NewMarker-pt-br}}
* [[rel-design-pattern]]

rel-license-pt-br

2006-11-05T04:03:32Z

Token:

= rel="license" =

'''Rel-License''' é um simples e aberto microformato para indicação de conteúdo de licença que estiver embutido em um (X)HTML, Atom, RSS e o arbitrário XML.

Rel-License é um dos muitos [[microformats-pt-br|microformatos]] de padrão aberto.

__TOC__

== Especificação 2005-02-06 ==
=== Autor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (anteriormente da [http://microsoft.com/ Microsoft Corporation])

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==

Rel-License é um dos muitos MicroFormatos. Por inclusão <code>rel="license"</code> é para um hyperlink, uma página indica que o destino daquele hyperlink é licenciado para a página atual. Ex. com o seguite hyperlink:

<pre><nowiki>
<a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
</nowiki></pre>

o autor indica que a página está licenciada sob Creative Commons 2.0 Attribution Required license.

== Multiplas Licenças ==
Multiple such rel="license" hyperlinks indica que a página está disponível sobre alguma licença referida. Ex:. a seguinte licença poderia ser usada para declarar que a página está disponível sob Commons 2.0 Attribution Required ou licença Apache 2.0:

<pre><nowiki><a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
<a href="http://www.apache.org/licenses/LICENSE-2.0" rel="license">Apache 2.0</a></nowiki></pre>

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="license">license</dt>
<dd>Indicates that the referred resource is a license for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Implementações ==
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of rel-license links from within Dreamweaver 8. Includes (cc) defaults.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel license and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://creativecommons.org/license/ Creative Commons (cc) license chooser]
* [http://search.yahoo.com/cc Yahoo! (cc) search]
* [http://www.google.com/support/bin/answer.py?answer=29508 Google "Usage Rights" search]

== Referencias ==
=== Referencias Normativa ===
* [http://gmpg.org/xmdp/ XMDP]

=== Referencias Informativas ===
* 20040211 rel="license" primeira proposta na apresentação [http://tantek.com/presentations/2004etech/realworldsemanticspres.html semantica no mundo real] em 2004 O'Reilly Emerging Technologies Conference, San Diego, CA, USA.
* 20040225 [http://tantek.com/log/2004/02.html#d25t1805 Completa discussão de rel="license"] incluindo vantagens e apresentação de possibilidades.
* [http://creativecommons.org/licenses/by/2.0/ Creative Commons 2.0 By (Attribution Required) license]
* [http://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]
* Contribuido de http://developers.technorati.com/wiki/RelLicense

== ver também ==
* Veja [[rellicense-issues]] para assuntos o qual tem sido levantado com esse [[microformats|microformato]].

Main Page-pt-br

2006-11-05T02:18:05Z

Token:

__NOTOC__

<h1> Microformatos Wiki </h1>

'''Olá!''' Bem vindo ao microformatos wiki. Se esta é sua primeira visita, por favor veja a página de [[introduction-pt-br|introdução]].

Por favor, leia [[how-to-play-pt-br|o que fazer]] antes de fazer qualquer edição.

Por favor, leia o [[process-pt-br|processo]] antes de propor qualquer novo microformatos.

__TOC__

==Guia Rápido==

[[what-are-microformats|O que são microformatos]]? [[what-can-you-do-with-microformats|O que você pode fazer com eles]]?

A [http://microformats.org/about/ página about], e mais recente [[press]], [[presentations]], [[podcasts]], and [[screencasts]] são bom locais para informações a fundo.

As perguntas feitas cm mais frequencia sobre o wiki e microformatos são em geral respondidas no [[faq|FAQ]].

Quer aprender mais pessoalmente? Verifique [[events|microformats events]].

==Definição==

Uma definição popular da nossa [http://microformats.org/discuss/ lista de discussão] (ver também: [[mailing-lists]]) é "convenções simples para combinar semântica em HTML para permitir o desenvolvimento decentralizado." Mais precisamente, microformatos podem ser definidos como:
:convenções simples
:para combinar com marcação semântica
::for a specific problem domain
:para ser legível aos humanos, documentos (X)HTML/XML, feeds Atom/RSS, e XML "plano"
::que padroniza existente conteúdo com uso de padrões.
::usando brief, descritivas nomes de classes
::baseada frequentemente nos existentes padrões de interoperabilidade
:para permitir desenvolvimento decentralizado
::de recursos, ferramentas, e serviços

"Ou você só usa seu browser para navegar? Então isto é o século 20." -- [http://diveintomark.org Mark Pilgrim]

== Como contribuir ==

Você quer ajudar a levar microformatos ao próximo nível? Você pode:

*Verificar as coisas em aberto [[to-do-pt-br|lista do que fazer]] para ajudar a concluir.
*Ingressar na [http://microformats.org/discuss lista de emails] e [[irc|Canal de IRC]] para aprender como ajudar a responder perguntas sobre microformatos.
*[[advocacy|Advocacia]] o uso de microformatos.
*Ajudar a [[Main_Page#microformats_wiki_in_other_languages|traduza o microformatos wiki para outras linguagens]] e tornar microformatos globalmente acessível.

== Especificações ==
[[microformats-pt-br|Microformatos]] especificações de padrões abertos (ver também: [[implementations-pt-br|implementações]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (ver também: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Esboços ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Padrões do projeto ==

{{design_patterns}} 

== Discussões exploratória ==
Pesquisa e análises do mundo real [[examples|exemplos]], formatos existentes e idéias para motivar o microformatos.
*alternates [[alternates-brainstorming|brainstorming]], [[alternates-examples|examplos]]
*[[attention]]
* blog description [[blog-description-examples|examplos]]
* blog info [[blog-info-examples|exemplos]]
* blog post [[blog-post-examples|exemplos]], [[blog-post-formats|formatos]], e [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|exemplos]], [[book-formats|formatos]], e [[book-brainstorming|brainstorming]]
* chat [[chat-examples|exemplos]], [[chat-formats|formatos]], e [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formatos]], [[citation-brainstorming|brainstorming]], e [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], e [[comments-formats|formatos]] (Alguma coisa precisa ser extraída de [[comments-formats]])
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}
* directions [[directions-examples|examplos]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formatos]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examplos]], and [[distributed-conversation-formats|formatos]]
* forms [[forms-examples|exemplos]]
* genealogy [[genealogy-formats|exemplos]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examplos]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|exemplos]] e [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|exemplos]], [[last-modified-formats|formatos]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], e [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|exemplos]], [[listing-formats|formatos]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formatos]]. (ver também [[adr]] e [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|exemplos]], [[media-info-formats|formatos]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|exemplos]], [[meeting-minutes-formats|formatos]], e [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|exemplos]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|brainstorming]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|exemplos]]
* photo note [[photo-note-examples|exemplos]]
* recipe [[recipe-examples|exemplos]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], e [[requirements-testing-examples|examplos]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], e [[resume-formats|formatos]]
* review [[review-examples|examples]], e [[review-formats|formatosformatos]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|exemplos]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - para a remarcação de nomes científicos de coisas vivas: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}
* table [[table-examples|exemplos]]
* tagspeak [[tagspeak-examples|exemplos]]
* tagcloud [[tagcloud-examples|exemplos]], e [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|exemplos]]
* [[uid]]
* widget [[widget-examples|exemplos]], e [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formatos]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formatos]], e [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (ver também [[xmdp-faq]])

== Exemplos ==
* [[examples]]
* [[zen-garden]]

== Ferramentas & Casos Prova & Pesquisa Adicional ==

O primeira lugar a procurar por exemplos, códigos, e casos é nas páginas de cada microformato indivídual. Há poucas ferramentas de atalho e serviços que precisam processar mais que um microformato. Esta sessão é destinada a editores, analisadores, validadores, testadores de casos e a outras informações relevantes através de microformatos multíplos.

*[[accessibility|acessibilidade]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== Areas de trabalho compartilhado ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - uma página com links para rapidamente demostrar microformatos funcionando na prática.
* [[events|eventos]] {{NewMarker}}
* [[to-do-pt-br|o que fazer]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki em outras linguagens==

You may read and edit microformats articles in many other languages:

* linguagens com mais de 50 artigos
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* linguagens com mais de 10 artigos
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
* linguagens com mais de 2 artgos
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* linguagens com 2 artigos
** [[Main_Page-de|Deutsch (German)]]

==== tradução de microformatos dos outros ====
Há outras páginas/sites externas com traduções sobre microformatos. Se você está trabalhando em uma dessas, por favor, considere como tradução o principal site de microformatos!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Iniciar um microformatos wiki em outras linguagem ===

Não vê a língua que gostaria? Ajuda a traduzir o microformatos wiki para outra língua!

We're still figuring this out.

Por enquanto, veja [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], e [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] para algumas dicas, conselhos, e community conventions.

Você pode começar com a lista [[stable-pages|páginas estáveis]], que são as páginas que são relativamente estáveis e tem só míninas mudanças editoriais, que as fazem muito fácil mantê-las em sincronia com a versão em inglês, pelo uso do recurso [[Special:Watchlist|my watchlist]] (use-o para monitorar as páginas que você traduziu para alterações).

Nome da página: para a versão traduzida de uma página, use o mesmo nome para a página e simplesmente adicione um código de identificador de linguagem RFC 3066 como um traço no sulfixo. Ex. para a versão em Francês, [[Main_Page]] torna-se [[Main_Page-fr]], e [[how-to-play]] torna-se [[how-to-play-fr]].

==== mais linguagens familiar que quer ver ====

* Chinese: 微格式 (Microformatos) (ver [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

spread-microformats-pt-br

2006-11-04T23:22:00Z

Token:

<h1>Propague os Microformatos</h1>

Inspirado no [http://spreadfirefox.com/ Spread Firefox], esta página é para compartilhar recursos da comunidade e comercializar produtos microformatos como [[buttons|botões]], banners, papel de parede / imagens de tela, logotipos gráficos, etc.

__TOC__
== Papel de parede ==
=== Papel de parede e imagens de tela. ===
* Um [http://remiprevost.com/weblog/2006/06/25/microformats-le-fond-decran/ papel de parede] criado por [[User:Remi|Rémi Prévost]]

== Logo ==
* Um [http://remiprevost.com/images/wallpapers/microformats/mf-vector.svg SVG] e [http://remiprevost.com/images/wallpapers/microformats/mf-vector.png PNG] (pelo Fireworks) do logo do microformatos, por [[User:Remi|Rémi Prévost]] (Lançado sob licença [http://creativecommons.org/licenses/by-nc-sa/2.5/ Creative Commons BY-NC-SA] license)

== Camisetas ==

* [http://www.goodstorm.com/item/factorycity/microformats_shirt_we_do_it_with_class Compre camisetas do microformatos em Goodstorm]
* Veja [http://flickr.com/photos/tags/microformatstshirt fotos das camisetas microformatos em Flickr] (the [http://flickr.com/photos/tags/microformatstshirt/clusters/ clusters] are especially fun)
* Note also [http://pixelsebi.com/2006-10-26/microformats-t-shirt-in-second-life/ microformats t-shirt in Second Life]

== Recursos de comunidade online externo ==
=== wiki-communities ===
* [http://www.usemod.com/cgi-bin/mb.pl?MicroFormats meatball:microformats] -- uma página primeiro (esboço para ser revisado) dedicado para ter qualquer revisão/opinião de almondegas especialmente nos wiki-formats.
* [http://communitywiki.org/fr/MicroFormats communitywiki:microformats] -- uma página multilingual antiga com uma proposta ''blockcodemachine''.

== Veja também ==
* [[advocacy]]
* [[buttons]]
* [[podcasts]]
* [[presentations]]
* [[press]]

stable-pages-pt-br

2006-11-04T23:03:57Z

Token:

= Páginas Estáveis =

Há uma lista de páginas que são relativamente estáveis e tem só alterações mínimas editoriais, que fazem-as muito mais fácil de se manterem em sincronia com a versão em inglês quando forem feitas traduções.

Isto é um pouco de prioridade ordenada, então se está fazendo uma tradução, examine as páginas recentes de tradução na primeira linha.

== Introdutório / Sobre ==
# [[Main_Page-pt-br]]
# [[introduction-pt-br]]
# [[press]]
# [[presentations]]

== Estáveis e especificações amplamente implementada ==

# [[xoxo]]
# [[rel-tag]]
# [[rel-license]]
# [[hcard]]
# [[hcalendar]]
# [[hreview]]

== Comunidade ==

# [[how-to-play-pt-br]]
# [[process-pt-br]]

Main Page

2006-11-04T22:56:05Z

Token:

__NOTOC__

<h1> Microformats Wiki </h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

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

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*alternates [[alternates-brainstorming|brainstorming]], [[alternates-examples|examples]]
*[[attention]]
* blog description [[blog-description-examples|examples]]
* blog info [[blog-info-examples|examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|formats]], and [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|examples]], [[book-formats|formats]], and [[book-brainstorming|brainstorming]]
* chat [[chat-examples|examples]], [[chat-formats|formats]], and [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examples]], and [[distributed-conversation-formats|formats]]
* forms [[forms-examples|examples]]
* genealogy [[genealogy-formats|examples]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examples]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|examples]] and [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|examples]], [[last-modified-formats|formats]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], and [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|examples]], [[media-info-formats|formats]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|examples]], [[meeting-minutes-formats|formats]], and [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|brainstorming]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|examples]]
* photo note [[photo-note-examples|examples]]
* recipe [[recipe-examples|examples]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], and [[requirements-testing-examples|examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], and [[resume-formats|formats]]
* review [[review-examples|examples]], and [[review-formats|formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|example]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|examples]]
* tagcloud [[tagcloud-examples|examples]], and [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|examples]]
* [[uid]]
* widget [[widget-examples|examples]], and [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formats]], and [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]]

== Tools & Test Cases & Additional Research ==

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

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}
* languages with over 2 articles
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* languages with 2 articles
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

Template:NewMarker-pt-br

2006-11-04T22:53:50Z

Token:

how-to-play

2006-11-04T22:41:38Z

Token:

If this is your first visit, please see the [[introduction]] page.

= How to Play =

Before contributing please observe these guidelines:

# You have to create an account (see [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines]) before editing/creating pages.
# Try one of the [http://microformats.org/discuss mailing lists] first (and read the [[mailing-lists]] page before doing so).
# If you write something opinionated, sign it with your username.
# Please only create pages directly relating to microformats on this wiki. Other pages will likely be deleted.
# Please obey the [[naming-conventions| naming conventions]] for pages.
# Don't use talk pages. See #2.
# Please try to ensure that you produce valid XHTML.
# When you paste code, add some line breaks at a reasonable width.

how-to-play-pt-br

2006-11-04T22:41:11Z

Token:

Se essa é sua primeira visita, por favor veja o página de [[introduction-pt-br|introdução]]

= Como começar =

Antes de contribuir, por favor, observe esse pontos:

# Você criou uma conta (veja [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines]) antes de editar/criar páginas.
# Tente uma [http://microformats.org/discuss lista de discussão] primeiro (e leia a página [[mailing-lists]] antes de fazer algo).
# Se você escrever opinioso, atribua-o com seu username.
# Por favor, apenas crie páginas diretamente relacionadas com microformatos neste wiki. Outras páginas serão deletadas.
# Por favor, obedece a [[naming-conventions| convenção de nomes]] para páginas.
# Não use páginas para conversar. Ver item #2.
# Por favor, tente assegurar-se que você produziu um XHTML válido.
# Quando você colar código, adicione algumas quebra de linhas por motivos de largura.

how-to-play-pt-br

2006-11-04T22:40:37Z

Token:

Se essa é sua primeira visita, por favor veja o página de [[introduction-pt-br|introdução]]

Antes de contribuir, por favor, observe esse pontos:

# Você criou uma conta (veja [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines]) antes de editar/criar páginas.
# Tente uma [http://microformats.org/discuss lista de discussão] primeiro (e leia a página [[mailing-lists]] antes de fazer algo).
# Se você escrever opinioso, atribua-o com seu username.
# Por favor, apenas crie páginas diretamente relacionadas com microformatos neste wiki. Outras páginas serão deletadas.
# Por favor, obedece a [[naming-conventions| convenção de nomes]] para páginas.
# Não use páginas para conversar. Ver item #2.
# Por favor, tente assegurar-se que você produziu um XHTML válido.
# Quando você colar código, adicione algumas quebra de linhas por motivos de largura.

accessibility-pt-br

2006-11-04T21:37:00Z

Token:

=Accessibilidade=

Essa página é para manter um caminho de discussão de microformatos com acessibilidade, esperamos que qualquer potencial do tema acessibilidade seja resolvido rapidamente, e para técnicas de documentação tornar os microformatos mais acessível.

== Lista de discussão ==

* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006OctDec/0022.html Microformatos e Estrutura Semântica (parte 2)] - 2006-10-11 in w3c-wai-ig.
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig.

==Fórum==
*[http://www.accessifyforum.com/viewtopic.php?t=6167&postdays=0&postorder=asc&start=0 Uso do 'abbr' em microformatos] - 2006-09-20. Assunto: uso do 'abbr'

dtstart-pt-br

2006-11-04T21:27:09Z

Token:

'''dtstart''' (start-date) ou data-inicial é uma propridade do [[hcalendar|hCalendar]].

adr-examples-pt-br

2006-11-04T20:55:54Z

Token:

=<h1>Mais exemplos ADR</h1>=

<h2>LOCALITY e outros fragmentos ADR</h2>

Usar o microformato <strong>adr</strong> não deve apenas ficar limitado a um conjunto de dados de informações.
Em alguns casos, regiões de referência de pessoas ou localidades sem informações adicional.

Para marcação desses casos acima, use os microformatos, (particularmente <strong>adr</strong>) será usado.

Por exemplo - com a informação abaixo, faremos referência a cidade e nada mais.
Porque eu fiz marcação do nome da cidade com propriedade <em>locality</em>, E adicionei propriedade <em>adr</em>
para o block-level do elemento pai que contém a relevante <em>locality</em> propriedade.

<h3>Exemplo:</h3>

<pre><nowiki>
<p class="adr">Unbelievable. Yesterday's high temperature in <span
class="locality">Salem</span> it was 57 degrees out. </p>
</nowiki></pre>

<h2>Usar o elemento <code><abbr></code></h2>

Semanticamente correto a marcação <strong>adr</strong> deve ser usada com o elemento <code><abbr></code> enquanto usar o <em>region</em>, <em>country-name</em> e talvez outra propriedade <strong>adr</strong>.

<h3>Exemplo:</h3>

<pre><nowiki>
<abbr class="region" title="California">CA</abbr>,
<abbr class="country-name" title="United States">US</abbr>
</nowiki></pre>

Para o nome completo do país use o atributo <code>title</code> do elemento <code><abbr></code> quando for usar a propriedade <em>country-name</em>,
use [http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html ISO 3166-1].

glossary-pt-br

2006-11-04T20:23:46Z

Token:

Microformatos - Glossário

;microformato
:Ver http://microformats.org/about/.

;XHTML
:HTML reformulado em XML. (See http://www.w3.org/TR/xhtml1/ para mais informações.)

;microformato elementar
:See [[elemental-microformat]]

;microformato combinado
:See [[compound-microformat]]

;microformatador
: Uma pessoa envolvida com microformatos.

Sinta-se livre para adicionar um termo nessa lista que você gostaria de ver definido.

semantic-xhtml-pt-br

2006-11-04T20:09:49Z

Token:

=<h1>XHTML Semântico</h1>=

(Esse arquivo é um esboço, sinta-se livre para expandi-lo!)

'''XHTML semântico refere-se a:'''
# Os elementos semânticos e atributos de (X)HTML (em oposição aos elementos e atributos do [[presentational-html|presentational HTML]])
# Documentos (X)HTML que são escritos usando XHTML semânticos.
# A prática de escrever XHTML semânticos.

__TOC__

== Colaboradores ==
* [http://tantek.com/ Tantek]

== Elementos Semânticos ==

(Esta lista está incompleta, por favor adicione!)

* a
* abbr
* acronym
* address
* blockquote
* cite
* dt, dd
* dfn
* em
* ...
* h1,h2,h3,h4,h5,h6
* ...
* label
* legend
* ...
* p
* q
* ...
* samp
* strong
* sub
* sup
* table
* tr
* var

== Atributos Semânticos ==

(Esta lista está incompleta, por favor adicione!)

* class
* data
* href
* hreflang
* id
* rel
* rev
* type

== Apresentação ==

As seguintes apresentação oferecem teor adicional, explicações, e tecnicas para criação de (X)HTML semântico.

* 2005-09-29 [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* 2004-09-28 [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean]
* 2004-02-11 [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics]
* 2003-03-?? [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets] in particular slide 9, titled ''CSS & the Semantic Spectrum'', provides an overview of the semantic spectrum of (X)HTML tags.
* More microformats [[presentations]] in general

== Veja também ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== Referências ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

process-pt-br

2006-11-04T19:51:49Z

Token:

:Se essa é sua primeira visita, por favor veja a página de [[introduction-pt-br|introdução]].

=Então você quer desenvolver um novo microformato?=

__TOC__

==Por que?==
Deve haver um problema a ser resolvido. Sem problemas, sem microformatos.

Uma vez que você encontrou seu 'problema', pergunte-se: 'há um problema mais simples aqui?' Nesse caso, vamos resolver aquele problema primeiro. Queremos tratar com mais simplicidade o primeiro problema e só então aumentar para problemas complexos.

Também, procure na internet. Há chances são que alguém mais tenha encontrado o mesmo problema que você. Se você ainda acredita que tem um problema não resolvido, poste algo em [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] na lista de discussão ou qualquer outro canal público (ver http://microformats.org/discuss/) Nós queremos envolver todos as partes interessadas na discussão. Inicie uma discussão '''ANTES''' de criar qualquer página no wiki. Não estamos usando o wiki como "bloco de anotações" gerais. Se você não pode resumir o problema que está tentando resolver em um curto email, e sente-se como se precisasse de uma longa documentação, você está provavelmente tentando resolver um gigantesco de um problema - veja paragráfo anterior.

==Comportamento Atual do Documento==
Documento atual do comportamento humano. Lembre-se, estamos [http://ifindkarma.typepad.com/relax/2004/12/microformats.html pavimentando o caminho da vaca] - antes de fazer você tem que ''encontrar'' o caminho-da-vaca. Seus [[examples|exemplos]] devem ser uma coleção dos sites do mundo
e páginas que são publicadas do tipo de informação que gostaria de estruturar com um microformato. Dessas páginas e sites, você deve extrair exemplos de marcação e de temas internamente implicitos e fazer análises.

Essa coleção de exemplos deve ser pública, preferencialmente em uma wiki pois não há forma de fazer tudo isso sozinho (não importa quantos de vocês são). A página [[reviews-formats]] é um bom exemplos de pesquisa feita antes da criação de um microformato. Antes de desenvolver [[hreview]], os colaboradores sairam, documentaram práticas atuais ao redor das revisões em web sites, e forneceram algumas análises de temas internamente implicito.

É bastante possível durante este passo que você encontrará mais outra pessoa que tem tratado desse problema discursado. Talvez até mesmo o resolvido. Faça seu melhor para abrir um dialogo com os outros que tem o encontrado o mesmo problema. Nós não queremos construir paredes entre comunidade competitivas - nós queremos pessoas trabalhando juntas para desenvolver uma boa solução que cobrirá a maioria dos casos.

==Proponha um Microformato==
Atualmente, '''NÃO!!!'''

Há outras coisas para tentar antes de desenvolver um microformato. Primeiro, faça-se essas perguntas:

# Há um elemento padrão em XHTML que trabalharia?
# Há uma combinação de elementos XHTML que trabalhariam?
# Ok, se a resposta para as duas acima é 'não,' nós podemos conversas sobre um microformato.

Para mais detalhes em XHTML semântico, exemplos de uso de elementos XHTML, e construção de combinações XHTML, veja
[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML].

Primeiro você deve observar [[microformats#the_microformats_principles|the microformats principles]].

Antes de você entender os principios, pergunte-se: "há alguma bem estabelecida, padrões implementado de interoperabilidade que podemos examinar em que tratam desse problema?" Por exemplo, hCard e hCalendar foram contruídos sobre o topo dos padrões IETF para vCard e iCal, respectivamente, ambos que são largamente implementação de interoperabilidade. Os desenvolvedores desses padrões já tem gasto muitos anos nos comitês de padrões debatendo e desenvolvendo os esquemas. Melhor influenciar todo o trabalho duro que outros fizeram antes de você, do que isolar-se como um caubói, e perder tempo repetindo todos seus enganos.

Também é mais fácil para começar de um esquema bem estabelecido e mapear para XHTML do que desenvolver um esquema novo.

Lembre-se, microformatos devem ser designados para humanos em primeiro lugar e máquinas em segundo. aqui há poucas perguntas que podem ajudar a você se realmente precisa de microformato para o problema que você está tentando resolver:

Se eu olhar para esse microformato em um navegador que não suporta CSS ou tem CSS desligado, ainda seria humano-legível?
# os estilos dos elementos desse formato estão com CSS?

Se o formato proposto não passou nessas duas coisas, não é provável que ganhe muita aceitação. Lembre-se: ''humanos primeiro, máquinas segundo''.

== Iterate ==
Depois de propor um microformato, você obterá muito retorno de outros interessados no microformato. A proposta precisa ser reiterada e adaptada. Desenvolvimento de microformato deve ser colaborativo e baseado em comunidade.

Aqui está uma arte ASCII em fluxograma:
<pre>
DIAGRAMA:
indicação do problema---->pesquisa/discussão---->proposta/esboço---->padrão
^___________________V ^__________________V ^_______________V
</pre>

Note que cada estágio envolve iteração. A iteração consiste de discussão e retorno e deve resultar em maiores mudanças. Não tenha medo de fazer maiores mudanças e por favor não fique ligado demais a qualquer situação particular.

=== Páginas para considerar criação ===

Um padrão emergiu de esforços de desenvolvimento de microformatos bem sucedido de diversos tipos especificos de páginas wiki sendo criada, em ordem particular (embora nem sempre).

Depois de uma área de problema especifico (*) tem sido determinado (princípio1), considerar criando e preenchendo as seguintes páginas para isso. Se você está inapto a produzir material para páginas, então você deve provavelmente reconsiderar se ou não o problema é importante (ou pronto para) resolver.

# *-examples. Encontrar exemplos de hoje na web de tipos de conteúdo que acha necessário um microformato. Documente-os com URLs. Documente os esquemas implicitos que contêm exemplos. Esta é a ação que ajuda a seguir o principio 3, designado a humanos em primeiro, máquinas em segundo... adapteo atual ambiente para usar padrões.
# *-formats. Find widely adopted interoperable current data formats and standards that attempt to or have attempted to solve the problem previously. Document their explicit schemas. This is necessary prerequisite for following through with principle 4, "reuse building blocks from widely adopted standards".
# *-brainstorming. Use the current real-world web examples and their implicit schemas to determine an 80/20 as-simple-as-possible (principle 2) generic schema to represent their data. Yes, this means you will explicitly ''omit'' some features of some use cases, or perhaps entire use cases which are more edge-cases than representative of larger, aggregate/macro behaviors. See which existing microformats can be reused as building blocks (principle 5, modularity). Use those existing data formats and schemas as a [[existing-classes|source of names]] for the fields (principle 4). Consider how would you embed this microformat in other formats (also principle 5, embeddability). With an 80/20 schema, and a source of field names, write up one or more straw proposals for a microformat. Make sure the straw proposals encourage the decentralized distribution of data (principle 6). At this point, you may want to also consider a naming section, where various names for the microformat can be considered.
# **. When it seems like there is some amount of consensus around one of the straw proposals for a microformat(**), write it up as a separate wiki page as a draft specification.
# **-faq. Haverá perguntas comum sobre novos microformatos que podem/devem ser respondidas na página FAQ.
# **-issues. Folks may also raise issues about the microformat which aren't immediately addressable. An issues document helps serves to capture these issues, who raised them, and when, so that folks working on the microformat can be sure to go through and thoroughly answer them.
# **-implementations. Eventually there may be too many implementations of a microformat to document them in an informative section at the end of the specification, thus the list deserves its own page.

=== Movendo de Estágio para Estágio ===

Esses estágios de desenvolvimento são espelhados na página principal onde microformatos são divididos para "Discussão Exploratória", "Esboços" e "Especificações". Como microformatos movem de um estágio para outro? Para ajudar a responder essa pergunta, é provavelmente útil elogiar uma definição de desiredato para cada estágio.

==== Discussão Exploratória ====

Você precisa de um problema e você precisa tentar declarar isto. Você deve fazer isso nessa wiki usando os itens atuais sob discussão exploratória como um guia. Então envie uma nota para a lista microformats-discuss para obter a atenção dos outros que você está interessado em microformatos. Esta é provavelmente uma boa chance de puxar pessoas de fora da comunidade de microformatos atuais que podem também ser experiência do mesmo assunto.

Retorno provavelmente irá alcançar a gama. Outros podem desafiar sua indicação do problema, o necessário para um microformato, concordar, ou adicionar. Todo retorno construtivo é bom.

As a result of feedback, you may decide to abort your microformat idea or substantially modify it. One thing you want to be sure to do at this stage is to avoid [[reinvented-wheels|reinventing the wheel]]. Are there elemental microformats you can reuse as building blocks? Doing this will save you effort and help you get implemented later because implementers will have less work to do.

However, do not be cowed from moving forward just because some people object. If you can find a group of people you respect who feel your idea has merit and, perhaps most importantly, are willing to continue working with you on getting it in shape, proceed.

==== Esboços ====

Aqui, você precisa escrever o que é essencialmente uma especificação, mas com a idéia que pode mudar bastante. Novamente, isto requer ir na wiki, e você deve enviar uma nota para o microformats-discuss para alertar pessoas que algo novo aconteceu. Não hesite em continuar tentando pegar uma resposta de recursos pertinentes fora da comunidade. Esboços precisam incluir ao menos o seguinte:

* Opiniões a respeito do fato que você não patenteará e serão adotadas o apropriado copyright como ilustrado pelo esboço atual.
* An XMDP stating attribute values. You may want to place this on a separate wiki page and link to it. In that case use the naming convention *-profile, e.g. [[hcard-profile]].
* Exemplos de práticas atuais que mostram como o microformato seria usado. Fique de olho pronto para como o microformato está atualmente melhorando as coisas. Se não está, talvez uma indicação que ou precisa abandonar ou mudar bastante.
* Referenciar que recuam suas decisões de projeto do microformato. Na medida do possível, você não quer inventar coisas de whole cloth.
* Uma lista de implementações (se houver).
* Uma sessão de assuntos para pessoas para retornar à você com objeções detalhadas.

==== Especificações ====

Você geralmente precisará ao menos de uma iteração para ir além do estágio de esboço. No momento algo torna-se uma especificação, deve ser estável então deve ser estável de modo que desenvolvedor possa colher e escrever. Isto implica que há ao menos um par de implementações.

Antes de mover-se para a sessão especificações, solte uma nota para o microformats-discuss e aguarde um dia ou dois para maiores objeções. Se nada está disponível, mova-se o microformato para a area de especificações. Isso despertará qualquer editor adormecido, e eles podem mostrar sua objeção e mover a você de volta para esboço. Se você tem seguido o processo, agora é hora de conseguir definação. Nesse conjuntura, qualquer assunto restante deve ser fácil de resolver.

== Outros Documentos ==

=== Padrões ===

Que tal outros tipos de páginas nesse wiki, como "padrões" (ex. [[include-pattern]])?

Como esses são criados?

A curta explicação disso:

Os padrões não são formados ao todo. Eles não se sustentam por si próprio. Eles são meramente documentos de partes de outros formatos que são esperados para (ou é) existinte do reuso pelos outros formatos. Os exemplos do mundo real para inclusão de um parcipar foram documentados no contexto do [[resume-examples]], [[resume-formats]], e [[resume-brainstorming]] (como notado [[include-pattern|o documento]]) "Inicialmente desenvolvido como parte do resume-brainstorming..." Mais tarde, os exemplos do mundo real por revisões que foram encontrada para precisar de incluir padrões igualmente.

== Relatado ==

* [[process-brainstorming]]

buttons-pt-br

2006-11-04T06:19:37Z

Token:

= Botões Microformatos =

Houveram pedidos para inclusão de vários botões microformatos. Seja sinais/distintivos ou botões que fazem algo com especificos microformatos. Esta página mantém uma lista de botões, e solicitações também. - [http://tantek.com/log/ Tantek]

Armazenado os botões para todos os microformatos, incluindo os de esboço, assim como instruções de como fazer seus próprios botões (14 Mai 2006) - [http://www.wackomenace.co.uk/ Ruben]

== Botões ==

=== Banner Microformato ===

Temos feito banner para os microformatos. Existem muitos e mais virão, just indicating support/ use of might be a good generic approach.

A imagem é livre para uso. Por favor, copie para seu próprio dominio, não faça link para esse.

http://www.crowley.nl/images/microformats.png

Eu já tenho um "Eu uso
http://www.crowley.nl/images/microformats.png" no meu blog: http://doncrowley.blogspot.com/

- Don Crowley

* http://www.boogdesign.com/images/buttons/microformat.png
* http://www.boogdesign.com/images/buttons/microformat_enabled.png
* http://www.boogdesign.com/images/buttons/emf_green.png
* http://www.boogdesign.com/images/buttons/mfe_green.png
* http://www.boogdesign.com/images/buttons/mwmf_green.png
* http://www.boogdesign.com/images/buttons/smf_green.png
* http://www.boogdesign.com/images/buttons/emf_white.png
* http://www.boogdesign.com/images/buttons/mfe_white.png
* http://www.boogdesign.com/images/buttons/mwmf_white.png
* http://www.boogdesign.com/images/buttons/smf_white.png

=== [[hcalendar|hCalendar]] ===
* http://rbach.priv.at/2006/buttons/hcal.png
* http://www.boogdesign.com/images/buttons/microformat_hcalendar.png
* CSS-powered button from [http://www.midgard-project.org/community/events/ Midgard CMS - Event calendar]:

<span class="badge" style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0; border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none; text-align: center;"><span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em; margin-right: 0.1em;">›››</span> hCalendar</span>

Code (white space added for readability):

<pre><nowiki>
<span class="badge"
style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0;
border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none;
text-align: center;">
<span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em;
margin-right: 0.1em;">
&#8250;&#8250;&#8250;
</span>
hCalendar
</span>
</nowiki></pre>

=== [[hcard|hCard]] ===
* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)
* http://rbach.priv.at/2006/buttons/hcard.png
* http://www.boogdesign.com/images/buttons/microformat_hcard.png
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]

=== [[rel-license]] ===
* http://rbach.priv.at/2006/buttons/license.png
* http://www.boogdesign.com/images/buttons/microformat_rellicense.png

=== [[rel-nofollow]] ===
* http://rbach.priv.at/2006/buttons/nofollow.png
* http://www.boogdesign.com/images/buttons/microformat_relnofollow.png

=== [[rel-tag]] ===
* http://rbach.priv.at/2006/buttons/rel-tag.png
* http://rbach.priv.at/2006/buttons/tag.png
* http://www.boogdesign.com/images/buttons/microformat_reltag.png

=== [[vote-links|VoteLinks]] ===
* http://rbach.priv.at/2006/buttons/votelinks.png
* http://www.boogdesign.com/images/buttons/microformat_votelinks.png

=== [http://gmpg.org/xfn/ XFN] ===
* http://rbach.priv.at/2006/buttons/xfn.png
* http://www.boogdesign.com/images/buttons/microformat_xfn.png

=== [http://gmpg.org/xmdp/ XMDP] ===
* http://rbach.priv.at/2006/buttons/xmdp.png
* http://www.boogdesign.com/images/buttons/microformat_xmdp.png

=== [[xoxo|XOXO]] ===
* http://rbach.priv.at/2006/buttons/xoxo.png
* http://www.boogdesign.com/images/buttons/microformat_xoxo.png

== Botões para formatos em esboços ==

Esses talvez estão sujeito a mudanças se o nome dos formatos mudarem quando eles forem lançados.

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

=== [[geo]] ===
* http://rbach.priv.at/2006/buttons/geo.png

=== [[hatom|hAtom]] ===
* http://rbach.priv.at/2006/buttons/hatom.png

=== [[hresume|hResume]] ===
* http://rbach.priv.at/2006/buttons/hresume.png
* http://www.boogdesign.com/images/buttons/microformat_hresume.png

=== [[hreview|hReview]] ===
* http://rbach.priv.at/2006/buttons/hreview.png

=== [[rel-directory]] ===
* http://rbach.priv.at/2006/buttons/directory.png

=== [[rel-enclosure]] ===
* http://rbach.priv.at/2006/buttons/enclosure.png

=== [[rel-home]] ===
* http://rbach.priv.at/2006/buttons/rel-home.png
* http://rbach.priv.at/2006/buttons/home.png

=== [[relpayment-research|rel-payment]] ===
* http://rbach.priv.at/2006/buttons/payment.png

=== [[robots-exclusion|Robots Exclusion]] ===
* http://rbach.priv.at/2006/buttons/robots.png

=== [[xfolk|xFolk]] ===
* http://rbach.priv.at/2006/buttons/xfolk.png

== Faça seus próprios botões ==
=== Estilo 1 ===

Examplo: http://www.crowley.nl/images/hcard.png

Use o [http://kalsey.com/tools/buttonmaker/ Kalsey Button Maker] com a seguinte configuração:
* Outer border: #666666
* Inner border: #ffffff
* Bar position: 25 pixels from the left
* Left box text: >>>
* Left box background: #000000
* Left box text colour: #ffffff
* Left box text start: 7 pixels from the left
* Right box text: (The name of the microformat goes here)
* Right box background: #31757b
* Right box text colour: #ffffff
* Right box text start: 3 pixels from the bar

=== Estilo 2 ===

Examplo: http://rbach.priv.at/2006/buttons/hcal.png

# Pegue a fonte [http://www.kottke.org/plus/type/silkscreen/ Silkscreen]
# Instale [http://www.imagemagick.org/ ImageMagick]
# Get the blank icon (http://rbach.priv.at/2006/buttons/blank.png)
# Digite:
<pre>convert blank.png
-fill white
-font Silkscreen
-pointsize 8
+antialias
-draw "text 28,10 'button label'"
output.png
</pre>

= Logos Microformatos =
Rohit é um muito pobre CSS hack, mas é dado a ele a melhor foto. Ele também [http://labs.commerce.net/~rohit/µf-logo.html renderizou em 72 e 18 pontos.]

http://microformats.org/img/logo.gif

<div style="position: relative; top:-46px; left:180px">
<div style="background-color:#679A06; width:30px; height: 30px; left:1px; top:10px; position:absolute; -moz-border-radius:5pt;"></div>

<div style="background-color:#85BC07; width:22px; height: 22px; left:11.5px; top:6px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white; -moz-border-radius:4pt;"></div>

<div style="background-color:#AEE219; width:14px; height: 14px; left:22.5px; top:4px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white;-moz-border-radius:2pt;"></div>

<div style="font-family:Arial Narrow,Arial,sans-serif;font-size:17.5pt;letter-spacing:0px;color:#676767; position: absolute; left:44px; top: -6px">
<span style="padding-left:9;color:#111111;vertical-align:40%">micro</span><span style="vertical-align:40%;padding-left:1pt">formatos</span>
</div>
</div>

= Requisições =

* Logos de todos os microformatos.
* Quando alguém tiver tempo, estes devem ser repetidos na página de cada respectivo formato.

downloads-brainstorming-pt-br

2006-11-04T05:44:20Z

Token:

==Propósito==
Muitos sites ([http://download.com/ Download.com], [http://tucows.com/ Tucows], [http://sourceforge.net/ SourceForge], etc.) oferecem downloads de softwares: shareware, freeware, open-source. Para criar um indice de pesquisa ou coisa assim por lá seria muito difícil, pois lá não há marcação padrão.

Muitos outros sites indexam tais downloads, seletivamente, sem os fornecer diretamente, por exemplo o site [http://www.pricelesswarehome.org/2004/PL2004nSYSTEMUTILITIES.php PricelessWare].

==Veja também==
* [[rel-license]] (rel=copyright para licenças com copyright? rel=license whatiscopyright.org?)
* [[hash-examples]]
* [http://usefulinc.com/doap DOAP]
* '''[http://dannyayers.com:88/xmlns/hdoap/profile/index.xhtml hDOAP]'''
& [http://www.google.com/codesearch Google Code Search] (não uma pesquisa por downloads, mas similar)

introduction-pt-br

2006-11-04T05:17:58Z

Token:

__NOTOC__

==Introdução ao Microformatos==

__TOC__

== O que são Microformatos? ==

Os microformatos são uma forma de adicionar marcação simples para legíveis a humanos, itens de informaçãos como um evento, detalhes de contato ou uma localização, em páginas da web de modo que a informação nela contida pode ser extraída pelo software e ser indexada, buscada, salva, ter referência-cruzada ou combinada.

Mais tecnicamente, eles são itens de marcação semântica, usando só o padrão (X)HTML e com uma definição de nomes-de-classes comum. Eles são abertos, disponíveis e livres para qualquer um usar.

== Por que Microformatos ==

Por que propusemos microformatos?

Em resumo, microformatos são uma convergência de um número de tendências:

# um próximo passo lógico na evolução de web design e arquitetura de informação.
# um número de pessoas e organizações que publicam informações ricas para si próprios, sem ter que confiar em serviços centralizados.
# um reconhecimento que (fora da areas de especialista) esforços de meta dados "tradicional" ou tem falhado ou levado longo tempo para adquirir qualquer adoção, que uma nova abordagem foi necessária.
# uma forma de usar (X)HTML para informação.

==O Apelo pela Simplicidade==

* Os microformatos são um esforço simples que tem atraido para muitos frustradas pelos esforços complexos anteriores. Um paralelo que pode ser desenhado é o RESTO dos serviços mundiais da web, exemplo, veja isto [http://www.windley.com/archives/2005/07/microformats.shtml comparação de microformatos e o RESTO]. Veja o [http://rest.blueoxen.net REST wiki] for more about REST. Related [http://patricklogan.blogspot.com/2006/01/microformat-microprotocol.html microformatos e microprotocolos].
* Veja também: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley

==Veja também==
*Recente [[press]] entrevista e [[articles|artigos]] também é uma boa introdução.
*Veja [[presentations|apresentação]] para ir mais a fundo e leia material introdutório em [[microformats|microformatos]].
*Escute o [[podcasts]] sobre microformatos.
*Leia o [[faq|FAQs]] para pesquisa geral sobre microformato.
*Mais [[suggested-reading|leitura sugerida]]
*[[implement|O que posso implementar com microformatos?]]
*[[presentations|apresentações]]
*[[podcasts]]
*[[suggested-reading]]
*[[testimonials]]

stable-pages-pt-br

2006-11-04T04:43:36Z

Token:

= Páginas Estáveis =

Há uma lista de páginas que são relativamente estáveis e tem só alterações mínimas editoriais, que fazem-as muito mais fácil de se manterem em sincronia com a versão em inglês quando forem feitas traduções.

Isto é um pouco de prioridade ordenada, então se está fazendo uma tradução, examine as páginas recentes de tradução na primeira linha.

== Introdutório / Sobre ==
# [[Main_Page]]
# [[introduction]]
# [[press]]
# [[presentations]]

== Estáveis e especificações amplamente implementada ==

# [[xoxo]]
# [[rel-tag]]
# [[rel-license]]
# [[hcard]]
# [[hcalendar]]
# [[hreview]]

== Comunidade ==

# [[how-to-play]]
# [[process]]

Main Page-pt-br

2006-11-04T04:22:05Z

Token:

__NOTOC__

<h1> Microformatos Wiki </h1>

'''Olá!''' Bem vindo ao microformatos wiki. Se esta é sua primeira visita, por favor veja a página de [[introduction|introdução]].

Por favor, leia [[how-to-play|o que fazer]] antes de fazer qualquer edição.

Por favor, leia o [[process|processo]] antes de propor qualquer novo microformatos.

__TOC__

==Guia Rápido==

[[what-are-microformats|O que são microformatos]]? [[what-can-you-do-with-microformats|O que você pode fazer com eles]]?

A [http://microformats.org/about/ página about], e mais recente [[press]], [[presentations]], [[podcasts]], and [[screencasts]] são bom locais para informações a fundo.

As perguntas feitas cm mais frequencia sobre o wiki e microformatos são em geral respondidas no [[faq|FAQ]].

Quer aprender mais pessoalmente? Verifique [[events|microformats events]].

==Definição==

Uma definição popular da nossa [http://microformats.org/discuss/ lista de discussão] (ver também: [[mailing-lists]]) é "convenções simples para combinar semântica em HTML para permitir o desenvolvimento decentralizado." Mais precisamente, microformatos podem ser definidos como:
:convenções simples
:para combinar com marcação semântica
::for a specific problem domain
:para ser legível aos humanos, documentos (X)HTML/XML, feeds Atom/RSS, e XML "plano"
::que padroniza existente conteúdo com uso de padrões.
::usando brief, descritivas nomes de classes
::baseada frequentemente nos existentes padrões de interoperabilidade
:para permitir desenvolvimento decentralizado
::de recursos, ferramentas, e serviços

"Ou você só usa seu browser para navegar? Então isto é o século 20." -- [http://diveintomark.org Mark Pilgrim]

== Como contribuir ==

Você quer ajudar a levar microformatos ao próximo nível? Você pode:

*Verificar as coisas em aberto [[to-do-pt-br|lista do que fazer]] para ajudar a concluir.
*Ingressar na [http://microformats.org/discuss lista de emails] e [[irc|Canal de IRC]] para aprender como ajudar a responder perguntas sobre microformatos.
*[[advocacy|Advocacia]] o uso de microformatos.
*Ajudar a [[Main_Page#microformats_wiki_in_other_languages|traduza o microformatos wiki para outras linguagens]] e tornar microformatos globalmente acessível.

== Especificações ==
[[microformats-pt-br|Microformatos]] especificações de padrões abertos (ver também: [[implementations-pt-br|implementações]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (ver também: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Rascunhos ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Padrões do projeto ==

{{design_patterns}} 

== Discussões exploratória ==
Pesquisa e análises do mundo real [[examples|exemplos]], formatos existentes e idéias para motivar o microformatos.
*alternates [[alternates-brainstorming|brainstorming]], [[alternates-examples|examplos]]
*[[attention]]
* blog description [[blog-description-examples|examplos]]
* blog info [[blog-info-examples|exemplos]]
* blog post [[blog-post-examples|exemplos]], [[blog-post-formats|formatos]], e [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|exemplos]], [[book-formats|formatos]], e [[book-brainstorming|brainstorming]]
* chat [[chat-examples|exemplos]], [[chat-formats|formatos]], e [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formatos]], [[citation-brainstorming|brainstorming]], e [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], e [[comments-formats|formatos]] (Alguma coisa precisa ser extraída de [[comments-formats]])
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}
* directions [[directions-examples|examplos]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formatos]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examplos]], and [[distributed-conversation-formats|formatos]]
* forms [[forms-examples|exemplos]]
* genealogy [[genealogy-formats|exemplos]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examplos]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|exemplos]] e [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|exemplos]], [[last-modified-formats|formatos]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], e [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|exemplos]], [[listing-formats|formatos]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formatos]]. (ver também [[adr]] e [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|exemplos]], [[media-info-formats|formatos]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|exemplos]], [[meeting-minutes-formats|formatos]], e [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|exemplos]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|brainstorming]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|exemplos]]
* photo note [[photo-note-examples|exemplos]]
* recipe [[recipe-examples|exemplos]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], e [[requirements-testing-examples|examplos]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], e [[resume-formats|formatos]]
* review [[review-examples|examples]], e [[review-formats|formatosformatos]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|exemplos]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - para a remarcação de nomes científicos de coisas vivas: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}
* table [[table-examples|exemplos]]
* tagspeak [[tagspeak-examples|exemplos]]
* tagcloud [[tagcloud-examples|exemplos]], e [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|exemplos]]
* [[uid]]
* widget [[widget-examples|exemplos]], e [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formatos]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formatos]], e [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (ver também [[xmdp-faq]])

== Exemplos ==
* [[examples]]
* [[zen-garden]]

== Ferramentas & Casos Prova & Pesquisa Adicional ==

O primeira lugar a procurar por exemplos, códigos, e casos é nas páginas de cada microformato indivídual. Há poucas ferramentas de atalho e serviços que precisam processar mais que um microformato. Esta sessão é destinada a editores, analisadores, validadores, testadores de casos e a outras informações relevantes através de microformatos multíplos.

*[[accessibility|acessibilidade]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== Areas de trabalho compartilhado ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - uma página com links para rapidamente demostrar microformatos funcionando na prática.
* [[events|eventos]] {{NewMarker}}
* [[to-do-pt-br|o que fazer]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki em outras linguagens==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* languages with over 2 articles
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* languages with 2 articles
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
Há outras páginas/sites externas com traduções sobre microformatos. Se você está trabalhando em uma dessas, por favor, considere como tradução o principal site de microformatos!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Iniciar um microformatos wiki em outras linguagem ===

Não vê a língua que gostaria? Ajuda a traduzir o microformatos wiki para outra língua!

We're still figuring this out.

Por enquanto, veja [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], e [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] para algumas dicas, conselhos, e community conventions.

Você pode começar com a lista [[stable-pages|páginas estáveis]], que são as páginas que são relativamente estáveis e tem só míninas mudanças editoriais, que as fazem muito fácil mantê-las em sincronia com a versão em inglês, pelo uso do recurso [[Special:Watchlist|my watchlist]] (use-o para monitorar as páginas que você traduziu para alterações).

Nome da página: para a versão traduzida de uma página, use o mesmo nome para a página e simplesmente adicione um código de identificador de linguagem RFC 3066 como um traço no sulfixo. Ex. para a versão em Francês, [[Main_Page]] torna-se [[Main_Page-fr]], e [[how-to-play]] torna-se [[how-to-play-fr]].

==== mais linguagens familiar que quer ver ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])