Microformats Wiki - User contributions [en]

adr

2006-01-16T14:08:16Z

ManoMano:

= adr =

'''adr''' (working name, pronounced "adder") is a simple format for marking up address information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''adr''' is a 1:1 representation of the ''adr'' property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

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

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

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

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

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

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

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

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

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

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

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

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

=== Human vs. Machine readable ===

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

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

=== Value excerpting ===

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

=== Root Class Name ===

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

=== Property List ===

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

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

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

=== XMDP Profile ===

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

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

== Examples ==
This section is informative.

=== Sample adr ===

Here is a sample adr:

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

This adr might be displayed as:

<pre>665 3rd St.
Suite 207
San Francisco, CA 94107
U.S.A.</pre>

=== More Examples ===

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

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

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

* ...
* ...

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

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

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

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

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

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

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

== Discussions ==

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

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

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

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

naming-conventions

2006-01-16T14:07:51Z

ManoMano:

All pages on this wiki should follow these naming conventions:

# All lowercase.
# Dashes between words.
# XMDP profile pages for microformat specs should be named with the name of the spec, followed by "-profile"

Any violations will be deleted.

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

process

2006-01-16T14:07:20Z

ManoMano:

=So you wanna develop a new microformat?=

__TOC__

==Why?==
There must be a problem to be solved. No problem, no microformat.

Once you've found your 'problem,' ask yourself: 'is there a simpler problem here?' If so, let's solve that problem first. We want to deal with the simplest problems first and only then build up to more complex problems.

Also, search around on the web. Chances are that someone else has encountered the same problem as you. If you still believe that you have an unsolved problem, post something to the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] mailing list or any other public channel (see http://microformats.org/discuss/) We want to involve all interested parties in the discussion. Start the discussion '''BEFORE''' you start creating any pages on the wiki. We're not using the wiki as a general "scratch pad". If you can't summarize the problem you are trying to solve in a short email, and feel like you need a long document, you're probably trying to solve too big of a problem - see previous paragraph.

==Document Current Behavior==
Document current human behavior. Remember, we're [http://ifindkarma.typepad.com/relax/2004/12/microformats.html paving the cowpaths]- before you do that you have to ''find'' the cowpaths. Your [[examples]] should be a collection of real world sites and pages which are publishing the kind of data you wish to structure with a microformat. From those pages and sites, you should extract markup examples and the schemas implied therein, and provide analysis.

This collection of examples should be public, preferably on a wiki because there's no way you can do it by yourself (no matter how many of you there are). The [[reviews-formats]] page is a good example of research done before the creation of a microformat. Before developing [[hreview]], the collaborators went out, documented current practices around reviews on web sites, and provided some analysis of the schemas implied therein.

It's quite possible during this step that you'll find someone else who has dealt with the problem you're addressing. Perhaps even solved it. Do your best to open a dialog with others who have encountered the same problem. We don't want to build walls between competing communities - we want people to work together to develop a good solution which will cover the majority of cases.

==Propose a Microformat==
Actually, '''DON'T!!!'''

There are other things to try before developing a microformat. First, ask yourself these questions:

# Is there a standard element in XHTML that would work?
# Is there a compound of XHTML elements that would work?
# Ok, if the answer to the above two is 'no,' we can talk about a microformat.

For more details on semantic XHTML, examples of using XHTML elements, and constructing XHTML compounds, see [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML].

First you should observe [[microformats#the_microformats_principles|the microformats principles]]

After you understand the principes, ask yourself: "are there any well established, interoperably implemented standards we can look at which address this problem?" For example, hCard and hCalendar were built on top of the IETF standards for vCard and iCal, respectively, both of which are widely interoperably implemented. The developers of those standards had already spent many years in standards committees arguing about and developing the schemas. Better to leverage all the hard work that others have done before you, than to go off as a solo cowboy inventor, and waste time repeating all their mistakes. It's also much easier to start from a well established schema, and map into into XHTML than to develop a new schema.

Remember, microformats should be designed for humans first and machines second. Here are few questions that may help you decide if you really need a microformat for the problem you are trying to solve:

# If I looked at this microformat in a browser that didn't support CSS or had CSS turned off, would it still be human readable?
# Are this format's elements stylable with CSS?

If the proposed format doesn't pass these two things, it's not likely to gain much acceptance. Remember: ''humans first, machines second''.

== Iterate ==
After proposing a microformat, you'll likely get a lot of feedback from others interested in microformats. The proposal needs to be iterated and adapted. Microformat development should be collaborative and communtiy based.

Here's an ASCII-art flow diagram:
<pre>
DIAGRAM:
problem statement---->research/discussion---->proposal/draft---->standard
^________________V ^___________________V ^______________V
</pre>

Note that each stage involves iteration. That iteration consists of discussion and feedback and may result in major changes. Do not be afraid to make major changes and please don't get too attached to any particular solutions.

=== Pages to consider creating ===

A pattern has emerged from successful microformat development efforts of several specific kinds of wiki pages being created, in a particular order (though not always).

After a specific problem area (*) has been determined (principle 1), consider creating and filling out the following pages for it. If your'e unable to come up with material for the pages, then you should probably reconsider whether or not the problem is worth (or ready for) solving.

# *-examples. Find examples on today's web of the the type of content you think needs a microformat. Document them with URLs. Document the implicit schemas that the content examples imply. This is the action that helps follow principle 3, design for humans first, machines second ... adapt to current behaviors and usage patterns.
# *-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. There will likely be common questions about the new microformat which can/should be answered in an FAQ page.
# **-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.

=== Moving from Stage to Stage ===

These stages of development are mirrored on the main page where microformats are divided into "Exploratory Discussions", "Drafts", and "Specifications". How do microformats move from one stage to the other? To help answer this question, it's probably useful to write up a set of desiderata for each stage.

==== Exploratory Discussions ====

You need a problem, and you need to attempt to state it. You should do it on this wiki using current items under exploratory discussion as a guide. Then send a note to the microformats-discuss list to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.

Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.

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.

==== Drafts ====

Here, you need to write what is essentially a specification, but with the idea that it could change a lot. Again, this needs to go in the wiki, and you should send a note to microformats-discuss to alert people that something new has happened. Don't hesitate to continue trying to pull in feedback from relevant resources outside the community. Drafts need to include at least the following:

* Statements regarding the fact that you will not patent and are adopting appropriate copyright as illustrated by current drafts.
* 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]].
* Examples from current practice that show how the microformat would be used. Keep an eye out for how the microformat is actually improving things. If it's not, that might be an indication that you either need to abandon or change a lot.
* References that back up your design decisions for the microformat. To the extent possible, you do not want to invent things from whole cloth.
* A list of implementations (if any).
* An issues section for people to feed back to you with detailed objections.

==== Specifications ====

You will usually need at least one iteration to get past the draft stage. By the time something becomes a specification, it should be stable so that developers can pick it up and write to it. This in turn implies that there are at least a couple of implementations.

Before moving to the specifications section, drop a note to microformats-discuss and wait a day or two for major objections. If none are forthcoming, move the microformat to the specifications area. This move will wake up any sleeping editors, and they may raise an objection and move you back to draft. If you have followed the process, now is the time to pin them down. At this juncture, any remaining issues should be easy to resolve.
[http://northwestairlines.bravehost.com Northwest Airlines]
[http://northwestairlines.bravehost.com Northwest Airlines]

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

introduction

2006-01-16T14:07:09Z

ManoMano:

__NOTOC__

= Introduction to Microformats =

Related: [[press]], [[presentations]], [[suggested-reading]], [[testimonials]]

== What are Microformats? ==

Microformats are the "dictionaries" of XHTML semantic content. They are for codifying commonly used information-rich HTML content in such a way that semantic meaning can be machine extracted. In short, they are the easiest-possible way to design data (or data formats) intended for reuse on the web.

== Stub note ==

This page is a stub and could certainly use some contributions, especially from folks new to [[microformats]], and what key points and details from their perspective helped explain to them what microformats are, why they matter, what benefits they provide to web designers, information architects, web developers, web programmers etc. - [http://tantek.com/log/ Tantek]

== Why Microformats ==

Why did we come up with microformats?

In short, microformats are the convergence of a number of trends:
# a logical next step in the evolution of web design and information architecture
# a way for self-publishers to publish richer information themselves, without having to rely upon centralized services
# an acknowledgment that "traditional" metadata efforts have either failed or taken so long to garner any adoption, that a new approach was necessary
# a way to use (X)HTML for data.

__TOC__

=== Evolution of Web Design ===

In the beginning (1990), there was [http://www.w3.org/MarkUp/ HTML] and it was good. It was simple, minimal, and used to semantically markup user visible data (text) and share it on the World Wide Web.

Then came the [http://en.wikipedia.org/wiki/Browser_wars browser wars] (1994-1999) where dominant browser manufacturers took their turns introducing "innovative" presentational tags, giving the typical web author/designer what they wanted: a semblance of control over the presentation of their webpages. The result: [http://www.w3.org/TR/REC-html32 HTML 3.2] "standardized" these defacto presentational innovations.

The introduction of [http://www.w3.org/TR/REC-CSS1 CSS1] (1996) and the semantically richer [http://www.w3.org/TR/REC-html40/ HTML4] (1998) brought a glimmer of hope, but it wasn't until years later (2000-2001), with the introduction of fully compliant (or almost) implementations of CSS1/HTML4 (IE5/Mac, IE6/Windows, Netscape 6) that it became practical for web designers to depend on CSS in their web pages. Leaders in the community began to furiously adopt and promote CSS (even if it took [http://www.tantek.com/log/2004/07.html#ie5macbandpass a] [http://tantek.com/CSS/Examples/boxmodelhack.html hack] [http://www.tantek.com/CSS/Examples/midpass.html or] [http://tantek.com/CSS/Examples/highpass.html two]) and the efficiencies and enhanced productivity that separating presentation from markup brought them, yet remained a small vocal minority.

The introduction of the Wired News redesign in 100% CSS, and the beautiful [http://csszengarden.com/ CSS Zen Garden] (2002-2003) was CSS's tipping point. With the clear and obvious presentation of visual beauty and broad creativity, designers world-wide "got it" and realized that this was the future of web design. The presentational markup of <code><FONT></code>, <code><TABLE></code>, and <code>spacer.gif</code> were tossed aside by any and all self-respecting web designers, who discovered the near infinite flexibility of <code><div></code>, <code><span></code>, and the 'class' attribute. A few in the community even began adopting some of the more semantic elements in HTML: <code><p></code>, <code><h1></code>...<code><h6></code>, <code><ol></code>, <code><ul></code>, <code><li></code>, <code><em></code>, <code><strong></code>. Leaders in the community exercised the semantic limits of strict HTML4 (experimented with XHTML) and documented [http://www.simplebits.com/publications/solutions/ best practices].

As the community followed rapidly in the footpaths they had worn, the leaders began to run into the limits of semantic (X)HTML. Other subcultures were attempting to rewrite the world in their own language(s) (<abbr title="Resource Description Framework">[http://www.w3.org/RDF/ RDF]</abbr>, "plain" <abbr title="eXtensible Markup Language">[http://www.w3.org/XML/ XML]</abbr> (<abbr title="David Janes on the failure of *plain XML* approaches">[http://blog.davidjanes.com/mtarchives/2005_10.html#003410 2]</abbr>), <abbr title="Scalable Vector Graphics">[http://www.w3.org/TR/SVG/ SVG]</abbr>), yet not having much of an impact on the World Wide Web, which required human presentable data, compatible with the browsers people already used. [http://en.wikipedia.org/wiki/Social_software Social Software] and [http://en.wikipedia.org/wiki/Blogs Blogs], written by this new generation of web designers and programmers, began to take off.

Natural patterns emerged from the way people used blogging systems, putting things into lists, for example lists of other bloggers (known as blogrolls), and annotating them with information representing relationships such has having met, friends, family, etc. The first microformat, <abbr title="XHTML Friends Network">[http://gmpg.org/xfn/ XFN]</abbr>, was designed to match these behaviors, and [http://tantek.com/log/2003/12.html#L20031215t0830 introduced to the blogging community] (2003-2004), who adopted it within weeks. The [http://gmpg.org GMPG] was formed as a home for XFN, and documented a few key [http://gmpg.org/principles design principles] later adopted for microformats. The key notion, that semantic (X)HTML could be extended, had been introduced and accepted by the community.

By understanding, using, and combining semantic (X)HTML building blocks, as well as determining that semantic (X)HTML could be validly extended via new rel, meta name, and class values, defined in (X)HTML profiles in the [http://gmpg.org/xmdp XMDP format], the community began to design and develop many more microformats (2004-2005). More patterns emerged from the blogging community, and each aggregate human behavior drove the design of simple, adaptive microformats to meet its needs. Creative Commons licensing became popular and [[rel-license]] was proposed. Outlines and lists: [[xoxo|XOXO]]. Contact info: [[hcard|hCard]]. Calendars and events [[hcalendar|hCalendar]].

Using these new found building blocks, the web design and information architecture communities were no longer limited by the predefined semantics of HTML4 (nor did they have to compromise human presentation and ease of authoring which other attempts sorely lacked). 2005 may well be the year that microformats became the next step in the evolution of the web.

=== The Appeal to Simplicity ===

* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world, i.e. see this [http://www.windley.com/archives/2005/07/microformats.shtml comparison of microformats and REST]. See the [http://rest.blueoxen.net REST wiki] for more about REST. Related [http://patricklogan.blogspot.com/2006/01/microformat-microprotocol.html microformats and microprotocols].
* See also: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley

== See Also ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer]
* [http://thedredge.org/ Andrew D. Hume] has written a blog post [http://thedredge.org/2005/07/introducing-microformats/ introducing microformats] and another one on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats].
* See microformat [[presentations]] for more background and introductory material on [[microformats]].
* Recent [[press]] interviews and articles are also a good introduction.
* [[suggested-reading]]
* [[implement|So you wanna implement microformats?]]
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan

== Miscellaneous Reference ==

These are various intro-related links/articles which I haven't figured out yet how to incorporate. You may find them of interest. - [http://tantek.com/log/ Tantek]

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

press

2006-01-16T14:06:57Z

ManoMano:

= Press =

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

This page documents the press that [[microformats]] has received.

== 2006 ==
=== January ===
* [http://www.philoneist.com/50226711/interview_with_technorati_marketing_director_derek_gordon.php Philoneist: Interview With Technorati Marketing Director Derek Gordon by Jonathan G. Cohen, January 11]
* [http://www.kbcafe.com/iBLOGthere4iM/?guid=20060101232742 #2 on the list of Best Web 2.0 Blogs, January 2]

== 2005 ==
=== December ===
* [http://www.publish.com/article2/0,1759,1904359,00.asp Publish: Year in Review: CSS, Standards, Microformats and Flash, By Stephen Bryant, December 21]
* [http://www.primezone.com/newsroom/news.html?d=91118 Newswire: Structured Blogging to support microformats, December 13th]
* [http://www.linuxjournal.com/article/8731 Linux Journal: Syndication and the Live Web Economy, By Doc Searls, December 9]

=== November ===
* [http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=349&page=4 ACM Queue: A Conversation with Ray Ozzie, ACM Queue vol. 3, no. 9 - November 2005]
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer by Garrett Dimon, November 14, 2005]

=== October ===
* [http://www.xml.com/pub/a/2005/10/19/microformats-and-web-2.0.html XML.com: Microformats and Web 2.0 by Micah Dubinko, October 19, 2005]
=== September ===
* [http://channel9.msdn.com/Showpost.aspx?postid=118325 Channel 9: Interview at PDC] - Robert Scoble interviews Tantek Çelik briefly on web standards, IE, and microformats.
=== July ===
* [http://www.acm.org/technews/articles/2005-7/0722f.html#item12 ACM News Service - Volume 7, Issue 819: Friday, July 22, 2005]
* [http://lists.ssc.com/pipermail/suitwatch/2005-July/000090.html Linux Journal: SuitWatch -- July 21 -- by Doc Searls, Senior Editor of Linux Journal: Making More Sense of the Web]
* [http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1247&specialId=38 Knowledge at Wharton: Supernova 2005: It's a Whole New, Connected World: What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats]
** Simplified Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=4>
** Traditional Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&l=4&languageid=5>
** Original english version: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=1>

=== June ===
* [http://news.com.com/2030-12-5745034.html#microformats CNET News.com: Supernova 2005 blogcast] - David Weinberger interviews Tantek Çelik and Rohit Khare about microformats and [http://microformats.org/ microformats.org].
** [http://blog.blogcast2005.silkclips.com/clipView?http://silkblogs.com/FindResource/EC139870-22E5-F208-70FA-BC437BD64420/celik-khave-full.mov Watch the full interview with Rohit Khare & Tantek Çelik (22:21 minutes)]
* Golem: [http://www.golem.de/0506/38831.html microformats.org - Formate für Menschen und Maschinen] (German: microformats.org - Formats for humans and machines)

=== March ===
* [http://www.xml.com/pub/a/2005/03/23/deviant.html XML.com: What Are Microformats?]

presentations

2006-01-16T14:06:50Z

ManoMano:

= microformats presentations =

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

This page lists various presentations and sessions which have provided explanations and discusions of both [[microformats]] in general, and specific [[microformats]].

== most recent first ==

Most recent presentations/sessions listed first.

=== this year ===
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA
** [[presentation-think-2005-11-12]]
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]
* September 30, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] ([http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3 MP3 - incomplete])
* September 29, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] ([http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3 MP3])
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]
* September 21, Web Intelligence Conference, Compiegne, France
** [http://moloko.itc.it/paoloblog/presentations/presentation_wi05/presentation_wi05.html Page-reRank: using trusted links to re-rank authority] ([http://sra.itc.it/people/massa/publications/wi05_page_rerank_massa_hayes.pdf paper]) - A discussion of using [[vote-links]] to improve [http://www-db.stanford.edu/~backrub/google.html PageRank]
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"

* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]"
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]"
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]"
** "Distributed Social Networks (XFN Implementations)"
*** Demonstrations of [http://wordpress.org WordPress] & [http://metafilter.com Metafilter]'s builtin XFN support, and XFN search engines [http://rubhub.com/ RubHub] & [http://xhtmlfriends.net/ xhtmlfriends.net].
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]"
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]"
** "Bibliographies ([[hbib]])"
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"
** "Semantic Web and Microformats" panel, Room 201

* March 15: "[http://tantek.com/presentations/2005/03/decentralizednetworks/ Decentralized Social Networks]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 17AB, Austin TX

* March 14: "[http://2005.sxsw.com/interactive/conference/panels/?action=show&id=IAP0060 How to Trick-Out Your Blog]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* March 13
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX
** "[http://tantek.com/presentations/2005/03/leveragingtags.html Leveraging Tags]", as part of the "How to Leverage Solipsism" panel, South by South West Conference (SXSW) 2005, Austin Convention Center Room 18A, Austin TX
** "[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA

=== 2004 ===

* September 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]", SD Forum Web Services SIG, eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131

* September 12: "[http://wiki.oreillynet.com/foocamp04/index.cgi?MVCeqXHTMLCSSJS Model+View+Controller = XHTML+CSS+JS]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Wallcreeper room, Sebastopol CA

* September 11: "[http://wiki.oreillynet.com/foocamp04/index.cgi?AttentionXML Attention.XML]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Appaloosa room, Sebastopol CA

* September 10: "[http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Camel room, Sebastopol CA

* March 15: "[http://tantek.com/presentations/2004sxsw/xfn.html Ridiculously Easy Social Software]", South by South West Conference (SXSW) 2004, Austin Convention Center Room 17B, Austin TX

* February 11th: "[http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics]", O'Reilly Emerging Technology Conference (ETech) 2004 Westin Horton Plaza, San Diego, CA. This presentation was the first public discussion and introduction of the terms "microformat" and "lowercase semantic web". Reprised as a five-minute lightning talk at [http://wiki.oreillynet.com/etech/index.cgi?ConCon ConCon], Rx Gallery, San Francisco CA (16 February 2004).

This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the technorati developers wiki].

faq

2006-01-16T14:06:43Z

ManoMano:

= Microformats wiki FAQ =
<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >
== wiki specific questions ==

Q: ''How do I create a username? Why won't it let me use my preferred username?''

A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to caplitalize the first letter of the user name.

== Basic Microformat Questions ==

Q: ''Are microformats dependent upon (X)HTML?''

A: Microformats are made to be embeddable. They can be embedded in (X)HTML, RSS, Atom or anywhere (X)HTML is allowed.

Q: ''Microformats sound great. How can I help?''

A: First of all, take a look at http://microformats.org/discuss to see some ways to join the conversations about microformats.

Q: ''I'd like to make a donation to the microformat cause. How can I do this?''

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

Q: ''Which microformats have been implemented?''

See the [[implementations]] page.

Q: ''Which microformats should I implement?''

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard]].

Q: ''Do you have any link badges I can add to my website/blog?''

A: Not yet, but we'll post them when we do...

Q. ''Are there any tools that support microformats?''

A. Yes... [[implementations]].

Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''

A. In general, it is more work, and less content-publisher friendly, to ask them to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

== Class interactions ==

Q. ''Are there issues with page styling when specific class values are used?''

A. There might be. However, any such issues can be easily (trivially) worked around by using contextual selectors.

Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code> and <code><span></code> semantics ==

Q. Is it semantically meaningless to use divs?

A. Yes, both <code><div></code> and <code><span></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code><span></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code><span></code>.

Q. Does the use of <code><div></code> and <code><span></code> elements add any semantics to web pages?

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 spec], <code><div></code> and <code><span></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

== Class semantics ==

Q. ''Do (X)HTML class names have semantics?''

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

== Microformats and Spam ==

Q. Given that Google now looks at hidden content as potential spam, will microformats be considered spam?

A. Microformats aren't meant to disguise semantics -- only provide a mechanism for marking up the content you intend to make visible on a page, typically no more and no less. Where we embed semantic equivalents in the tags themselves (i.e. GMT times in abbr tags for times), it doesn't seem logic that such data could be considered spam.

how-to-play

2006-01-16T14:06:04Z

ManoMano:

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.
# 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.
# If its not a document that should be collaboratively written, this is probably not the right place for it.
# Don't use talk pages. If you're tempted to use one, use the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list instead.
# Please try to ensure that you produce valid XHTML.
<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >

Main Page

2006-01-16T14:05:49Z

ManoMano:

__NOTOC__
= Microformats Wiki =
Welcome to the [http://microformats.org microformats] wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.

But First:

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

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

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]].

One popular definition from our mailing list 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]

== 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]]
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}
* [[hatom|hAtom]] ({{NewMarker}})

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[datetime-design-pattern]]
* [[class-design-pattern]]
* [[rel-design-pattern]]
* [[abbr-design-pattern]]
* [[existing-classes|class names defined across all microformats]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[blog-description-format]]
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]]
*[[cite-examples]], [[citation-brainstorming]], [[cite|Planning pages for a citation microformat]]
*[[comments-formats]]
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[forms-examples]]
*[[genealogy-formats]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[mfo-examples]]
*[[media-metadata-examples]]
*[[other-formats]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[rest-examples]]
*[[search-results-example]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])
*[[show-brainstorming]]
*[[showroll-brainstorming]]

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

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

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

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

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{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])

<div style="overflow:auto; height: 1px;">

[http://www.hornyblog.org/bigtitpatrol/ BigTitPatrol]
[http://www.hornyblog.org/asstraffic/ Asstraffic]
[http://www.hornyblog.org/allinternal/ Allinternal]
[http://www.hornyblog.org/creampiesurprise/ CreampieSurprise]
[http://www.hornyblog.org/spermswap/ Spermswap]
[http://www.hornyblog.org/givemepink/ GiveMePink ]
[http://www.torrie-wilson.org/torrie-wilson/ Torrie Wilson ]

</div >