Microformats Wiki - User contributions [en]

tagspeak-examples

2005-11-13T20:48:12Z

SSriram: /* gada.be formulation */

= tagspeak examples =
tagspeak is the way in which ordinary people construct tags.

== The Problem ==
As tags have grown in popularity and usage they are increasingly
called upon to undertake additional tasks besides categorization such as-

*As directives to route content, associate tags to a group tag or associate with a broader consensus tag
*Provide additional attributes such as username, genre etc. for a tag

Currently, these additional tag attributes are being marked up in an ad-hoc
fashion as decided by individuals, consensus groups and/or tag services.

Formulating a standard for tagspeak would
*assist taggers - who could use the same formulation across multiple services
*assist tagservices - who could build support for the range of tagspeak instead of one-of and ad-hoc development.
*assist tag processors - who could build parsers for tagspeak

== Participants ==
* [http://sriram.wordpress.com S. Sriram]

== Real-World Examples ==
Everyday users construct tags in two ways
*with links: using the rel-tag formulation
*in plain text: on taggable services such as flickr, delcious etc.

=== Link examples ===
The primary example of this is the rel-tag formulation, which although
works quite well, could be broadened to assist everyday bloggers
as this [http://napsterization.org/stories/archives/000569.html study] indicates.

==== Technorati and rel-tag formulations ====
<pre><nowiki>
<a href="http://technorati.com/<tag>" rel="tag">any text</a>
</nowiki></pre>

==== gada.be formulation ====
Uses the first word in the url as the tag. This has the benefit of making it very easy
to remember, and is especially useful for mobile customers.
<pre><nowiki>
<a href="http://<tag>.gada.be">any text</a>
</nowiki></pre>

==== Proposed formulations - blogspeak.org & inames ====
These are not currently in real-world implementations but are examples
of some thinking that in effect combines the above two approaches
[http://blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
<pre><nowiki>
<a href="http://TAGSPACE.someservice.com/../PAR/AME/TERS/<tag>" rel="tag">any text</a>
</nowiki></pre>
[http://www.seedwiki.com/wiki/itag/power_i-tags.cfm itags]
<pre><nowiki>
<a href='http://xri.itags.net/=mary/(+blog)/napsterization*
(=mary/(+tag)/(+dog))*(=mary/(+blog.post)/41)/dog'>dog</a>
</nowiki></pre>

=== Plain text examples ===
==== delicious :colon ====
The use of colon : as a separator
<pre><nowiki>
for:username - when a bookmark is tagged thus it is routed to the specified users's space
within delicious
groupname:tag - This type formulation is rumored+ to be released soon.
</nowiki></pre>
+[http://www.hyperorg.com/blogger/mtarchive/berkman_joshua_schachter.html source of rumor]
==== shadows.com & jots.com :& ====
The use of @ to denote a group
<pre><nowiki>
@tag denotes a group tag
</nowiki></pre>

==== delicious & technorati :+ ====
The use of + to denote an intersection
<pre><nowiki>
tag1+tag2 denotes an intersection of tags when used to search
</nowiki></pre>

==== inames ====
inames use an 'equal to' = sign to prepend the iname

==== HonorTags & Tagback(1) - The use of a standard prefix ====
[http://honortags.com/ HonorTags]
<pre><nowiki>
HonorTagJournalism
HonorTagProfessional
HonorTagAdvocate
HonorTagPersonal
HonorTagFiction
HonorTagUnTag
</nowiki></pre>
[http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ Tagback(1)]
<pre><nowiki>
Strip spaces from the title and add a prefix such as bb to the begining
Title: Introducing tagback
tag: bbintroducingtagback
</nowiki></pre>

==== Proposed formulations ====
These are not in real world use but are proposed
and use a combination of : & =iname
* [http://tagspaces.org/index.php?title=WorkingDraft tagspaces.org]
tag attributes separated by colons appended with an optional iname
* Open Tags & Tagback (2) - The use of a fragment
[http://www.corante.com/getreal/archives/2005/11/01/itags_open_tags.php Open Tags & Tagback(2)]
Instead of the last segment of the url being the tag, having the fragment be the tag
and this fragment points to a position on the page which would show a list of
trackback like tagback pings from the various tag-processors who have picked
the tag up.
<pre><nowiki>
<a href=
"http://www.corante.com/getreal/archives/2005/07/24/name_of_post.php#tag_thai" rel="tag">thai</a>
</nowiki></pre>

== Existing Practices ==
Here are a couple of thoughts on existing practices
*plain-text: The punctuations in use are either used as a separator or as a qualifier. The separator currently in use is the colon as adopted by delicious. @ and = are used as qualifiers for a group and iname respectively. This nuanced distinction is useful as it could allow for constructs such as @group:tag or =iname:tag
*links: Explicit tagging wherein bloggers place rel="tag" attributes has ramped up from 0% in 2005 January 1 (before [[rel-tag]] was introduced) to 35% as of 2005 November 1. This rapid ramp has demonstrated that visible rel-tags are quickly being adopted, both by individual bloggers and blogging tools, and also displacing invisible RSS Category or invisible DC:Subject keywords.

== Proposal ==
*Link: Allow tags to be any one of the following
**The last fragment in a url
**The first word in a url where no words exist beyond the TLD
**The last word in a url if no fragment is present (This is the current rel-tag standard)
***Where the last word or last fragment is the tag, the optional use of the first word as a tagspace
<pre><nowiki>
Last fragment: <a href="http://bla-bla.com/../xyz.html#thetag" rel="tag">
First word: <a href="http://thetag.bla-bla.com/" rel="tag">
Last word: <a href="http://bla-bla.com/../thetag" rel="tag">
First & Last fragment: <a href="http://tagspace.bla-bla.com/../xyz.html#thetag" rel="tag">
First & Last word: <a href="http://tagspace.bla-bla.com/../thetag" rel="tag">
</nowiki></pre>
*Plain text: Allow the use of special punctuations as ''separators'' and ''qualifiers''
**The use of a : as a separator
***Establish a reserved set of tag directives such as 'for', 'domain names' etc.
**The use of a + for more than one tag
**The use of @ and = as qualifiers for an group & iname respectively.
tagdirective:tag
<pre><nowiki>
tagdirective:tag
Where tagdirectives is either one of a reserved set of directives or
is a tag for a broader group classification
So if 'for' is a reserved directive but 'plumbers' is not a reserved directive
for:john would be interpreted based on the reserved directive 'for'
plumbers:john would tag the item with the tag john in the broader group/cluster of plumbers

Standard domain conventions could be used in the reserved directives such as
amazon.com:tag
wine.com:tag
etc.
</nowiki></pre>
qualifiers and separators
<pre><nowiki>
plumbers:john

could be written as

@plumbers:john - to explicitly denote plumbers to be a group/cluster

and/or as

@plumbers:=john - to note that john is an iname
</nowiki></pre>

tag1+tag2+tag3
<pre><nowiki>
tag1+tag2+tag3: Would tag an item with all three tags
</nowiki></pre>

== See Also ==
* [http://www.blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
* [http://gada.be/about gada.be/about]
* [http://sriram.wordpress.com/2005/11/04/tagspeak-models-tagback-shelley-tagback-stowe-itags-mary-tagspaces-chris/ overview of some tagspeak models]
* [http://www.tagspaces.org tagspaces.org]
* [http://www.seedwiki.com/wiki/itag/itag.cfm itags]
* [http://www.corante.com/getreal/archives/2005/07/24/open_tags_made_for_a_distributed_world.php open tags tagback(2)]
* [http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ tagback(1)]

tagspeak-examples

2005-11-13T19:26:31Z

SSriram: noted distinction between qualifiers & separators in plain-text

= tagspeak examples =
tagspeak is the way in which ordinary people construct tags.

== The Problem ==
As tags have grown in popularity and usage they are increasingly
called upon to undertake additional tasks besides categorization such as-

*As directives to route content, associate tags to a group tag or associate with a broader consensus tag
*Provide additional attributes such as username, genre etc. for a tag

Currently, these additional tag attributes are being marked up in an ad-hoc
fashion as decided by individuals, consensus groups and/or tag services.

Formulating a standard for tagspeak would
*assist taggers - who could use the same formulation across multiple services
*assist tagservices - who could build support for the range of tagspeak instead of one-of and ad-hoc development.
*assist tag processors - who could build parsers for tagspeak

== Participants ==
* [http://sriram.wordpress.com S. Sriram]

== Real-World Examples ==
Everyday users construct tags in two ways
*with links: using the rel-tag formulation
*in plain text: on taggable services such as flickr, delcious etc.

=== Link examples ===
The primary example of this is the rel-tag formulation, which although
works quite well, could be broadened to assist everyday bloggers
as this [http://napsterization.org/stories/archives/000569.html study] indicates.

==== Technorati and rel-tag formulations ====
<pre><nowiki>
<a href="http://technorati.com/<tag>" rel="tag">any text</a>
</nowiki></pre>

==== gada.be formulation ====
Uses the first word in the url as the tag. This has the benefit of making it very easy
to remember, and is especially useful for mobile customers.
<pre><nowiki>
<a href="http://<tag>.gada.be>any text</a>
</nowiki></pre>

==== Proposed formulations - blogspeak.org & inames ====
These are not currently in real-world implementations but are examples
of some thinking that in effect combines the above two approaches
[http://blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
<pre><nowiki>
<a href="http://TAGSPACE.someservice.com/../PAR/AME/TERS/<tag>" rel="tag">any text</a>
</nowiki></pre>
[http://www.seedwiki.com/wiki/itag/power_i-tags.cfm itags]
<pre><nowiki>
<a href='http://xri.itags.net/=mary/(+blog)/napsterization*
(=mary/(+tag)/(+dog))*(=mary/(+blog.post)/41)/dog'>dog</a>
</nowiki></pre>

=== Plain text examples ===
==== delicious :colon ====
The use of colon : as a separator
<pre><nowiki>
for:username - when a bookmark is tagged thus it is routed to the specified users's space
within delicious
groupname:tag - This type formulation is rumored+ to be released soon.
</nowiki></pre>
+[http://www.hyperorg.com/blogger/mtarchive/berkman_joshua_schachter.html source of rumor]
==== shadows.com & jots.com :& ====
The use of @ to denote a group
<pre><nowiki>
@tag denotes a group tag
</nowiki></pre>

==== delicious & technorati :+ ====
The use of + to denote an intersection
<pre><nowiki>
tag1+tag2 denotes an intersection of tags when used to search
</nowiki></pre>

==== inames ====
inames use an 'equal to' = sign to prepend the iname

==== HonorTags & Tagback(1) - The use of a standard prefix ====
[http://honortags.com/ HonorTags]
<pre><nowiki>
HonorTagJournalism
HonorTagProfessional
HonorTagAdvocate
HonorTagPersonal
HonorTagFiction
HonorTagUnTag
</nowiki></pre>
[http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ Tagback(1)]
<pre><nowiki>
Strip spaces from the title and add a prefix such as bb to the begining
Title: Introducing tagback
tag: bbintroducingtagback
</nowiki></pre>

==== Proposed formulations ====
These are not in real world use but are proposed
and use a combination of : & =iname
* [http://tagspaces.org/index.php?title=WorkingDraft tagspaces.org]
tag attributes separated by colons appended with an optional iname
* Open Tags & Tagback (2) - The use of a fragment
[http://www.corante.com/getreal/archives/2005/11/01/itags_open_tags.php Open Tags & Tagback(2)]
Instead of the last segment of the url being the tag, having the fragment be the tag
and this fragment points to a position on the page which would show a list of
trackback like tagback pings from the various tag-processors who have picked
the tag up.
<pre><nowiki>
<a href=
"http://www.corante.com/getreal/archives/2005/07/24/name_of_post.php#tag_thai" rel="tag">thai</a>
</nowiki></pre>

== Existing Practices ==
Here are a couple of thoughts on existing practices
*plain-text: The punctuations in use are either used as a separator or as a qualifier. The separator currently in use is the colon as adopted by delicious. @ and = are used as qualifiers for a group and iname respectively. This nuanced distinction is useful as it could allow for constructs such as @group:tag or =iname:tag
*links: Explicit tagging wherein bloggers place rel="tag" attributes has ramped up from 0% in 2005 January 1 (before [[rel-tag]] was introduced) to 35% as of 2005 November 1. This rapid ramp has demonstrated that visible rel-tags are quickly being adopted, both by individual bloggers and blogging tools, and also displacing invisible RSS Category or invisible DC:Subject keywords.

== Proposal ==
*Link: Allow tags to be any one of the following
**The last fragment in a url
**The first word in a url where no words exist beyond the TLD
**The last word in a url if no fragment is present (This is the current rel-tag standard)
***Where the last word or last fragment is the tag, the optional use of the first word as a tagspace
<pre><nowiki>
Last fragment: <a href="http://bla-bla.com/../xyz.html#thetag" rel="tag">
First word: <a href="http://thetag.bla-bla.com/" rel="tag">
Last word: <a href="http://bla-bla.com/../thetag" rel="tag">
First & Last fragment: <a href="http://tagspace.bla-bla.com/../xyz.html#thetag" rel="tag">
First & Last word: <a href="http://tagspace.bla-bla.com/../thetag" rel="tag">
</nowiki></pre>
*Plain text: Allow the use of special punctuations as ''separators'' and ''qualifiers''
**The use of a : as a separator
***Establish a reserved set of tag directives such as 'for', 'domain names' etc.
**The use of a + for more than one tag
**The use of @ and = as qualifiers for an group & iname respectively.
tagdirective:tag
<pre><nowiki>
tagdirective:tag
Where tagdirectives is either one of a reserved set of directives or
is a tag for a broader group classification
So if 'for' is a reserved directive but 'plumbers' is not a reserved directive
for:john would be interpreted based on the reserved directive 'for'
plumbers:john would tag the item with the tag john in the broader group/cluster of plumbers

Standard domain conventions could be used in the reserved directives such as
amazon.com:tag
wine.com:tag
etc.
</nowiki></pre>
qualifiers and separators
<pre><nowiki>
plumbers:john

could be written as

@plumbers:john - to explicitly denote plumbers to be a group/cluster

and/or as

@plumbers:=john - to note that john is an iname
</nowiki></pre>

tag1+tag2+tag3
<pre><nowiki>
tag1+tag2+tag3: Would tag an item with all three tags
</nowiki></pre>

== See Also ==
* [http://www.blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
* [http://gada.be/about gada.be/about]
* [http://sriram.wordpress.com/2005/11/04/tagspeak-models-tagback-shelley-tagback-stowe-itags-mary-tagspaces-chris/ overview of some tagspeak models]
* [http://www.tagspaces.org tagspaces.org]
* [http://www.seedwiki.com/wiki/itag/itag.cfm itags]
* [http://www.corante.com/getreal/archives/2005/07/24/open_tags_made_for_a_distributed_world.php open tags tagback(2)]
* [http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ tagback(1)]

User:SSriram

2005-11-13T05:50:30Z

SSriram: seeded page

http://sriram.wordpress.com

tagspeak-examples

2005-11-13T05:49:57Z

SSriram: seeded page

= tagspeak examples =
tagspeak is the way in which ordinary people construct tags.

== The Problem ==
As tags have grown in popularity and usage they are increasingly
called upon to undertake additional tasks besides categorization such as-

*As directives to route content, associate tags to a group tag or associate with a broader consensus tag
*Provide additional attributes such as username, genre etc. for a tag

Currently, these additional tag attributes are being marked up in an ad-hoc
fashion as decided by individuals, consensus groups and/or tag services.

Formulating a standard for tagspeak would
*assist taggers - who could use the same formulation across multiple services
*assist tagservices - who could build support for the range of tagspeak instead of one-of and ad-hoc development.
*assist tag processors - who could build parsers for tagspeak

== Participants ==
* [http://sriram.wordpress.com S. Sriram]

== Real-World Examples ==
Everyday users construct tags in two ways
*with links: using the rel-tag formulation
*in plain text: on taggable services such as flickr, delcious etc.

=== Link examples ===
The primary example of this is the rel-tag formulation, which although
works quite well, could be broadened to assist everyday bloggers
as this [http://napsterization.org/stories/archives/000569.html study] indicates.

==== Technorati and rel-tag formulations ====
<pre><nowiki>
<a href="http://technorati.com/<tag>" rel="tag">any text</a>
</nowiki></pre>

==== gada.be formulation ====
Uses the first word in the url as the tag. This has the benefit of making it very easy
to remember, and is especially useful for mobile customers.
<pre><nowiki>
<a href="http://<tag>.gada.be>any text</a>
</nowiki></pre>

==== Proposed formulations - blogspeak.org & inames ====
These are not currently in real-world implementations but are examples
of some thinking that in effect combines the above two approaches
[http://blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
<pre><nowiki>
<a href="http://TAGSPACE.someservice.com/../PAR/AME/TERS/<tag>" rel="tag">any text</a>
</nowiki></pre>
[http://www.seedwiki.com/wiki/itag/power_i-tags.cfm itags]
<pre><nowiki>
<a href='http://xri.itags.net/=mary/(+blog)/napsterization*
(=mary/(+tag)/(+dog))*(=mary/(+blog.post)/41)/dog'>dog</a>
</nowiki></pre>

=== Plain text examples ===
==== delicious :colon ====
The use of colon : as a separator
<pre><nowiki>
for:username - when a bookmark is tagged thus it is routed to the specified users's space
within delicious
groupname:tag - This type formulation is rumored+ to be released soon.
</nowiki></pre>
+[http://www.hyperorg.com/blogger/mtarchive/berkman_joshua_schachter.html source of rumor]
==== shadows.com & jots.com :& ====
The use of @ to denote a group
<pre><nowiki>
@tag denotes a group tag
</nowiki></pre>

==== delicious & technorati :+ ====
The use of + to denote an intersection
<pre><nowiki>
tag1+tag2 denotes an intersection of tags when used to search
</nowiki></pre>

==== inames ====
inames use an 'equal to' = sign to prepend the iname

==== HonorTags & Tagback(1) - The use of a standard prefix ====
[http://honortags.com/ HonorTags]
<pre><nowiki>
HonorTagJournalism
HonorTagProfessional
HonorTagAdvocate
HonorTagPersonal
HonorTagFiction
HonorTagUnTag
</nowiki></pre>
[http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ Tagback(1)]
<pre><nowiki>
Strip spaces from the title and add a prefix such as bb to the begining
Title: Introducing tagback
tag: bbintroducingtagback
</nowiki></pre>

==== Proposed formulations ====
These are not in real world use but are proposed
and use a combination of : & =iname
* [http://tagspaces.org/index.php?title=WorkingDraft tagspaces.org]
tag attributes separated by colons appended with an optional iname
* Open Tags & Tagback (2) - The use of a fragment
[http://www.corante.com/getreal/archives/2005/11/01/itags_open_tags.php Open Tags & Tagback(2)]
Instead of the last segment of the url being the tag, having the fragment be the tag
and this fragment points to a position on the page which would show a list of
trackback like tagback pings from the various tag-processors who have picked
the tag up.
<pre><nowiki>
<a href=
"http://www.corante.com/getreal/archives/2005/07/24/name_of_post.php#tag_thai" rel="tag">thai</a>
</nowiki></pre>

== Existing Practices ==
Here are a couple of thoughts on existing practices
*plain-text: The use of a colon as a separator as delicious has chosen to
implement is seemingly the defacto standard, however the use of other
punctuation marks are prevalent notably the @ and the =
*links: Explicit tagging wherein bloggers place rel="tag" attributes
according to Mary Hodder occur only 5% of the time. Her study as well as
Stowe Boyd's comments indicate that more flexibility is needed
to allow for hidden tags and tags which have different link formulations.

== Proposal ==
*Link: Allow tags to be any one of the following
**The last fragment in a url
**The first word in a url where no words exist beyond the TLD
**The last word in a url if no fragment is present (This is the current rel-tag standard)
***Where the last word or last fragment is the tag, the optional use of the first word as a tagspace
<pre><nowiki>
Last fragment: <a href="http://bla-bla.com/../xyz.html#thetag" rel="tag">
First word: <a href="http://thetag.bla-bla.com/" rel="tag">
Last word: <a href="http://bla-bla.com/../thetag" rel="tag">
First & Last fragment: <a href="http://tagspace.bla-bla.com/../xyz.html#thetag" rel="tag">
First & Last word: <a href="http://tagspace.bla-bla.com/../thetag" rel="tag">
</nowiki></pre>
*Plain text: Allow the use of special punctuations
**The use of a : as a separator
***Establish a reserved set of tag directives such as 'for' 'domain names' etc.
**The use of a + for more than one tag
**The use of = for an iname
tagdirective:tag
<pre><nowiki>
tagdirective:tag
Where tagdirectives is either one of a reserved set of directives or
is a tag for a broader group classification
So if 'for' is a reserved directive but 'plumbers' is not a reserved directive
for:john would be interpreted based on the reserved directive 'for'
plumbers:john would tag the item with the tag john in the broader group/cluster of plumbers

Standard domain conventions could be used in the reserved directives such as
amazon.com:tag
wine.com:tag
etc.
</nowiki></pre>
tag1+tag2+tag3
<pre><nowiki>
tag1+tag2+tag3: Would tag an item with all three tags
</nowiki></pre>
=iname
<pre><nowiki>
=john: would interpret the tag as an iname
</nowiki></pre>

== See Also ==
* [http://www.blogspeak.org/tagspeak.html blogspeak.org/tagspeak.html]
* [http://gada.be/about gada.be/about]
* [http://sriram.wordpress.com/2005/11/04/tagspeak-models-tagback-shelley-tagback-stowe-itags-mary-tagspaces-chris/ overview of some tagspeak models]
* [http://www.tagspaces.org tagspaces.org]
* [http://www.seedwiki.com/wiki/itag/itag.cfm itags]
* [http://www.corante.com/getreal/archives/2005/07/24/open_tags_made_for_a_distributed_world.php open tags tagback(2)]
* [http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/ tagback(1)]

Main Page

2005-11-13T05:38:54Z

SSriram: Added tagspeak-examples

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

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|RelLicense]]
* [[rel-nofollow|RelNoFollow]]
* [[rel-tag|RelTag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

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

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

== Exploratory discussions ==
Focused on real-world [[examples]] to motivate the microformat.
*[[hatom|hAtom]] ({{NewMarker}}) is based on: [[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]]
*[[blog-description-format]]
*[[chat-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]])
*[[media-metadata-examples]]
*[[other-formats]]
*[[requirements-testing]]
*[[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]])

== 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]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]

== 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 languages</del> at least one more language:

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

* [[Main_Page-fr|Français (French)]] (Thanks to neuro`!)
* ...

=== help add more languages ===

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