Microformats Wiki - User contributions [en]

photo-note-examples

2017-01-16T05:25:02Z

Bravenewgame: /* Examples */

= Photo Note Examples =

This is a concrete discussion of what exists right now in the specific problem area of annotating areas of photos with notes.

This is a very specific type of [[media-info]] that is not as generic as [[media-info-examples]] in general.

== Contributors ==

* Tantek Çelik
* Greg Elin

== Examples ==

* http://fotonotes.net
** http://fotonotes.net
** ordered list of notes, each note has unique ID
** each note has:
*** rectangle / boundingbox
*** unique id
*** title (thought of as human readable alias for unique id)
*** content - plain text
*** author of the note
*** date of annotation

* http://www.frankmanno.com/ideas/css-imagemap/
** CSS based image maps

* http://evan.nixsys.bz/note
** CSS based image maps

* https://www.google.com/maps/d/viewer?mid=1mO0Yz0rZm5iQKLfXek7xrvi-eP4&hl=en_US&ll=35.137878938941405%2C-92.41699249999999&z=4
** uses standard text formatting
** imagemaps with onmouseover events to load the text to display

* http://conflix.soe.umich.edu/photos/collections/KyleHelson/9/annotation/
** divs containing spans of plain text, very unexciting.

* http://flickr.com
** http://flickr.com/photos/tantek/64877881/
** ordered list of notes (there is an order because if they overlap, the latter one "wins" in terms of hover)
** each note has:
*** rectangle
*** content - hypertext markup
*** author of the note (left blank and implied for first-person notes)

* fotobuzz (has based their stuff on fotonotes, without attribution.)
** http://2entwine.com/screenshots/pic5.html (haven't found an editable one yet)
** http://fotobuzz.org/ displays an example containing multiple comments within one "note"
** plain text, although they display their data in flash
** rectangles.

photo-note-examples

2017-01-16T05:21:39Z

Bravenewgame: /* Examples */

= Photo Note Examples =

This is a concrete discussion of what exists right now in the specific problem area of annotating areas of photos with notes.

This is a very specific type of [[media-info]] that is not as generic as [[media-info-examples]] in general.

== Contributors ==

* Tantek Çelik
* Greg Elin

== Examples ==

* http://fotonotes.net
** http://fotonotes.net
** ordered list of notes, each note has unique ID
** each note has:
*** rectangle / boundingbox
*** unique id
*** title (thought of as human readable alias for unique id)
*** content - plain text
*** author of the note
*** date of annotation

* http://www.frankmanno.com/ideas/css-imagemap/
** CSS based image maps

* http://evan.nixsys.bz/note
** CSS based image maps

* https://drive.google.com/open?id=1mO0Yz0rZm5iQKLfXek7xrvi-eP4&usp=sharing
** uses standard text formatting
** imagemaps with onmouseover events to load the text to display

* http://conflix.soe.umich.edu/photos/collections/KyleHelson/9/annotation/
** divs containing spans of plain text, very unexciting.

* http://flickr.com
** http://flickr.com/photos/tantek/64877881/
** ordered list of notes (there is an order because if they overlap, the latter one "wins" in terms of hover)
** each note has:
*** rectangle
*** content - hypertext markup
*** author of the note (left blank and implied for first-person notes)

* fotobuzz (has based their stuff on fotonotes, without attribution.)
** http://2entwine.com/screenshots/pic5.html (haven't found an editable one yet)
** http://fotobuzz.org/ displays an example containing multiple comments within one "note"
** plain text, although they display their data in flash
** rectangles.

social-network-portability

2017-01-16T05:07:56Z

Bravenewgame: /* Open Source */

<h1> Social Network Portability </h1>
{{TOC-right}}
Social network portability is one of several [[user-interface]] ideas and suggestions for working with microformats in the area of [[data-portability]].

== The Problem ==
Why is it that every single social network community site makes you:
* re-enter all your [[hcard-supporting-user-profiles|personal profile info]] (name, email, birthday, URL etc.)?
* re-add all your [[hcard-xfn-supporting-friends-lists|friends]]?

In addition, why do you have to:
* re-turn off notifications?
* re-specify privacy preferences?
* re-[[block]] [http://headrush.typepad.com/creating_passionate_users/2006/04/angrynegative_p.html negative people]?

AKA "social network fatigue problem" and "social network update/maintenance problem".

== The Goals ==
When you join a new site, you should be able to ''import'' or preferably ''subscribe'' to
* your profile information
* your social network
from any existing profile of yours.

In addition it would be nice if preferences around:
* notifications
* [[privacy]]
also transferred between profiles.

AKA a social internetwork, a network of social networks.

== Design Patterns and Recipes ==

The "How To" for social network profile sites that want to solve the above problems and achieve the above goals.

# Publish microformats in your user profiles and contacts.
## implement [[hcard|hCard]] on user profile pages, including [[xfn]] rel="me" on hyperlinks to users' blogs or home pages that they specify. See [[hcard-supporting-profiles]] for sites that have already done this. See [[how-to-publish-user-profiles]] for more details (See [[hcard-authoring]] until that previous link is created and filled in.)
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of contacts on your user profile pages. Use [[xfn]] rel="me" to link to contacts list pages and contacts list pagination links too. See [[hcard-xfn-supporting-friends-lists]] for sites that already do this. (e.g. [[http://twitter.com/ Twitter]]) and [[how-to-markup-contact-lists]] for more details.
## implement [[hcard|hCard]] wherever a user's name is mentioned in lists, in comments, in messages or wherever else it would help to identity that a "person" or "organization" is being referred to.
# Subscribe to microformats for your user profiles and contacts:
## when signing up a new user and importing contacts
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> from one of their existing [[hcard-supporting-profiles]], their name, their icon etc. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Satisfaction Inc already supports this] ([http://staging.getsatisfaction.com/people/new sign up page]). See [[how-to-import-user-profiles]] for more details.
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> their list of contacts from one of their existing [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]]. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Dopplr.com already supports this] ([http://www.flickr.com/photo_zoom.gne?id=576635008&size=o screenshot]). See [[how-to-import-contacts]] for more details (e.g. first implement direct XFN friends list import/subscribe by using the SGAPI to important contacts *across the web*, much faster than importing from one service at a time.)

== Resources ==
=== Groups ===
* [http://ma.gnolia.com/groups/PSN Ma.gnolia Portable Social Networks group] for aggregated bookmarks around the subject and join the group to share links.
* [http://upcoming.yahoo.com/group/3601/ Upcoming Social Network Portability group] for events to discuss and implement social network portability.

=== Open Source ===
* "[http://code.google.com/apis/opensocial/ OpenSocial] defines a common API for social applications across multiple websites.
* [[hKit]] - web service and open source PHP for parsing/importing/subscribing to [[hcard-supporting-profiles|hCard open user profiles]].
* "[http://opensocialgraph.plaxo.com/ Online Identity Consolidator]" rel="me" web parser/crawler web service and open source Python. (source code link now broken; Google code has a copy at [http://code.google.com/p/google-sgnodemapper/source/browse/trunk/plaxo-rel_me_crawler.py rel_me_crawler.py])
* "[http://django-psn.googlecode.com/svn/trunk/readme.html Django-PSN (portable social networks)]" open source for a user interface to create links on a social network profile to "other profiles" marked up with rel="me" naturally. The code can be seen in action on the [https://itsmyurls.com/ ItsMyUrls] website, e.g. on [https://itsmyurls.com/wholehouse a ItsMyUrls profile page that links to other profiles of the same user]. This is a great complement to the above Plaxo Online Identity Consolidator. What Django-PSN publishes, Plaxo Online Identity Consolidator parses.
* [http://code.google.com/p/identity-matcher/ identity-matcher] - Rails plugin to match identities and social network information from sites such as GMail, Twitter, Flickr, Facebook and any site supporting appropriate microformats. This code was extracted and contributed from Dopplr.
* [http://redmonk.net/projects/portable-social-network-lib/ Portable Social Network Lib] is a Ruby library for consuming/providing Portable Social Network services in social web apps, written by Steve Ivy. ([http://redmonk.net/archives/2007/11/07/if-you-love-your-users-set-them-free-portable-social-networks/ More])
* [http://code.google.com/p/diso/ DiSo] - ''distributed social networking'' components, [[User:Chris_Messina|Chris Messina]] and [[User:SteveIvy|Steve Ivy]]

=== User Interfaces ===
* "[http://gerardramos.com/mf/ Social Network Portability with Microformats]" - a user interface that lets you check how portable your social network is across various sites.
* "[http://lab.backnetwork.com/ufXtract-psn/ ufXtract - Portable social network profile parser]" - A public API which can extract both hCard-XFN patterns and XFN rel=me links from social networks. The API can spider multiple pages following rel=me links. It also tries to find the representative hCard and provides output as JSON or XML.

== Social Network Portability FAQ ==
See [[social-network-portability-faq]].

== Events ==
*[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 portable social networks initial meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francisco, CA. Discussed portable social networks, simplified and crystalized problem statement (with progressive problems to solve), goals, design patterns, recipes. Created [[social-network-portability]] page.
* [[events/2007-08-19-social-network-portability-today|2007-08-19 BarCampBlock session on social network portability TODAY]] at Princeton Review offices, High Street, Palo Alto, CA. Reviewed problem statement, how sites can use the [[hcard|hCard]] and [[xfn|XFN]] microformats *today* to become a node on the "open social web" (phrase introduced).
* [[events/2007-08-28-social-network-portability-today|2007-08-28 Social Network Portability Today]] lunchtime meetup
* [[events/2007-09-05-dconstruct-microformats-workshop|2007-09-05 d.Construct workshop on microformats]] which covered both [[data-portability]] and [[social-network-portability]].
* [[events/2007-09-08-social-network-portability|2007-09-08 BarCampBrighton session on social network portability]] at Madgex offices, North Street, Brighton, England.
* [[events/2007-09-25-social-network-portability|2007-09-25 Portable Social Network Micro Meetup]] at Citizen Space, San Francisco, CA, USA.
*[[events/2007-09-28-portable-social-networks-meetup-amsterdam|2007-09-28 Portable Social Network Panel]] at PICNIC in Amsterdam, Netherlands
* <span class="vevent"><span class="dtstart">2007-10-04</span> <span class="summary">[[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web: Social Network Portability]]</span> by Tantek Çelik — <span class="location adr"><span class="locality">Gijón</span>, <span class="country-name">Spain</span></span></span>
* <span class="vevent"><span class="dtstart">2008-09-05</span>: <span class="summary">[[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008: Social Network Portability]]</span> (<span class="url">http://2008.dconstruct.org/schedule/TantekCelik.php#talk</span>) at [http://2008.dconstruct.org/ dConstruct 2008] in <span class="location">Brighton, England</span>.</span> ([http://tantek.com/presentations/2008/09/social-network-portability presentation])
* ...

See the microformats [[events]] page for upcoming events related to social network portability.

== Articles and blog posts ==
Note: if you know of or can find earlier mentions on the web of the phrases "portable social network" or "social network portability", please add the earliest reference elsewhere on the web to this chronology. [[User:Tantek|Tantek]] 08:25, 22 Aug 2007 (PDT).

* 2006-11-15 Jon Hicks: [http://www.flickr.com/photos/hicksdesign/298271647/ The straw that broke this camels back]: <blockquote><p>Thats the last social service that involves me adding all my friends in all over again. Life is too chuffing short.</p><p>Please, can someone come up with some way of avoiding this repetition of 'buddies'?!</p></blockquote>
* <strong>2006-11-15</strong> [http://twitter.com/drewm/statuses/68199 Drew McLellan on Twitter]: (Perhaps the earliest mention of the concept of social network portability.) <blockquote><p>Thinking that we really need to join the dots with XFN and make social networks portable.</p></blockquote>
* <strong>2006-11-15</strong> [http://twitter.com/adactio/statuses/68412 Jeremy Keith on Twitter]: (first known reference to "<strong>portable social networks</strong>") <blockquote><p> Agreeing with Drew about using XFN to create portable social networks. If we don't, Jon is going to go postal.</p></blockquote> The mention of Jon is likely a reference to the [http://www.flickr.com/photos/hicksdesign/298271647/ above-mentioned Flickr photo].
* 2006-11-19 Phil Gyford: [http://www.gyford.com/phil/writing/2006/11/19/your_single_soci.php Your single social network] <blockquote><p>I really, really want a single service where I can say “these people are my friends” and then when I sign up to any new website I can sync it with my previously-defined social network.</p></blockquote>
* 2006-11-21 Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* 2006-11-21 Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* 2006-11-22 Thomas Vander Wal: [http://www.personalinfocloud.com/2006/11/following_frien.html Following Friends Across Walled Gardens] - first mention of "portable social network" but in reference to quoting Jeremy Keith
* 2006-11-23 Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks] - describes the process of portability
* 2006-11-23 Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network] - talks about portable social networks in the backnetwork
* 2006-11-23 Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts. See [[social-network-portability-interfaces]] for more.
* <strong>2006-11-24</strong> [http://microformats.org/wiki?title=user-interface&diff=10524&oldid=10523 "<strong>social network portability</strong>" phrase and problem statement introduced to microformats wiki] by [[User:Tantek|Tantek Çelik]]
* 2007-03-11 Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* 2007-05-16 [http://2007.xtech.org/public/schedule/paper/69 What is your provenance?] by Gavin Bell for Xtech 2007. Also available on [http://video.google.com/videoplay?docid=-8663100900373306094 Google Video]
* 2007-06-20 Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]
* 2007-07-17 Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
*[http://www.plaxo.com/about/releases/release-20070718 2007-07-17 Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats]
* 2007-07-18 Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote><p>What if we could port all our friends and family from one social network to another. Why do we have to continue to add people = annoying</p></blockquote>
* 2007-07-18 Brian Oberkirch: [http://www.brianoberkirch.com/2007/07/18/highrise-microformats-and-portable-social-networks/ Highrise, microformats and portable social networks]
* 2007-07-24 Thomas Vander Wal: [http://vanderwal.net/random/entrysel.php?blog=1937 Sharing and Following/Listening in the Social Web]
* See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].
* 2007-08-01 Jeffrey Zeldman: [http://www.zeldman.com/2007/08/01/social-network-portability/ "InterNetwork" regarding social network portability]
* 2007-08-02
** [http://www.brosbeforeblogs.com/2007/08/identity-crisis.html Identity Crisis part 1] <blockquote><p>We need to put the ownership of how we define relationships online in the hands of the individual, not the services that utilize them.</p><p>My theory on how this should be accomplished is based on a marriage of OpenID and an open standard for defining relationships such as the [[XFN]] [http://microformats.org/ Microformat]. </p></blockquote>
** [http://www.brianoberkirch.com/2007/08/02/deeelightful-making-profile-import-a-snap/ Deeelightful: Making Profile Import a Snap] <blockquote><p>Why not make it simple for them to jumpstart a profile by reusing information they already have on the [[hcard|Web? Some forward thinking Web services are marking up user profile data with hCard, a microformat that]] signifies a person, place or organization is being described.</p></blockquote>
* 2007-08-08 Brian Oberkirch: [http://www.brianoberkirch.com/2007/08/08/building-blocks-for-portable-social-networks/ Building Blocks for Portable Social Networks]
* 2007-08-15 [http://news.bbc.co.uk/1/hi/technology/6944653.stm Pull down the walled gardens] Internet law professor Michael Geist says the walled gardens of social networks should be pulled down.
* 2007-08-16 Stephanie Booth: [http://climbtothestars.org/archives/2007/08/16/we-need-structured-portable-social-networks-spsn/ We Need Structured Portable Social Networks (SPSN)] (links to two more posts on the subject, but not certain they're relevant enough for a separate listing; edit as you see fit)
* 2007-08-17 [http://bradfitz.com/social-graph-problem/ Thoughts on the Social Graph] by Brad Fitzpatrick.
* 2007-08-25 [http://www.ignitesocialmedia.com/linking-it-all-%e2%80%93-social-network-portability/ Linking It All-Social Network Portability] by Mike Lotz for Ignite Social Media
* 2007-09-03 [http://themaninblue.com/writing/perspective/2007/09/03/ There are no social networks] by Cameron Adams
<blockquote><p>If you can't see my friends and let my friends be seen, you'll be washed up and hung out to dry.</p></blockquote>
* 2007-09-07 [[User:LynX|Carlo v. Loesch]]: [http://about.psyc.eu/Social_network#But.._why_microformats.3F Privacy and the web? Notification and HTTP? Are you looking at the right technologies!?]
* 2007-11-21 Sitepoint article [http://www.sitepoint.com/article/social-networks-take-friends Portable Social Networks: Take Your Friends with You]
* 2007-12-03 [http://www.glennjones.net/Post/833/Makingyoursocialnetworkingdataportable-Markingupprofilesandfriendswith.htm Making your social networking data portable - Marking up profiles and friends with mircoformats] by Glenn Jones
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability

See [http://ma.gnolia.com/groups/PSN ma.gnolia Portable Social Network Group] for aggregated bookmarks around the subject and join the group to share links.

[http://technorati.com/search/microformats.org/wiki/social-network-portability View blog reactions] to this page.

== Issues ==
* Beware of and avoid [[social-network-anti-patterns]]!
* See and add to [[social-network-portability-issues]].

== Alternative Approaches ==
Non-web based:
* [http://about.psyc.eu psyc] and [http://www.psyced.org psyced], a decentralized multi-protocol chat and event notification system with [http://about.psyc.eu/Social_Network friendship] and [http://about.psyc.eu/Trust trust] modeling.

== See also ==
* [[social-network-portability-interfaces]]
* [[social-network-portability-faq]]
* [[social-network-portability-issues]]
* [[social-network-anti-patterns]]
* [[hcard|hCard]]
* [[xfn]]
* [[user-interface]]
* [[data-portability]]

rel-nofollow

2017-01-16T04:22:18Z

Bravenewgame: /* exceptions */

<entry-title>rel="nofollow"</entry-title>
__TOC__
== Specification 2005-01-10 ==

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

=== Concept ===
* [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}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
* [[User:Kevin Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

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

== Abstract ==
<p class="entry-summary">RelNoFollow is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards. By adding <code>rel="nofollow"</code> to a hyperlink, a page indicates that the destination of that hyperlink {{should not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). Typical use cases include links created by 3rd party commenters on blogs, or links the author wishes to point to, but avoid endorsing. For more specific endorsement (or lack thereof) semantics, see [[vote-links|VoteLinks]].</p>

== XMDP profile ==
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[rel-nofollow]] specification.

=== URLs ===
This profile is hosted as a separate XMDP file on microformats.org:
* http://microformats.org/profile/rel-nofollow
* shortURL: http://ufs.cc/x/rel-nofollow

=== Usage ===
Profiles are referenced in (X)HTML files in the <HEAD> tag, e.g.:
<source lang=html4strict>
<head profile='http://microformats.org/profile/rel-nofollow'>
</source>

=== Profile ===
<source lang=html4strict>
<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 as defined in the
<a rel="help start" href="http://microformats.org/wiki/rel-nofollow">
rel-nofollow specification</a>
.</p>
<dl>
<dt id="nofollow">nofollow</dt>
<dd>Indicates that the referred resource was not necessarily linked to
by the author of the page, and thus said reference should not afford
the referred resource any additional weight or ranking by user agents.
</dd>
</dl>
</dd>
</dl>
</source>

== examples in the wild ==
This section is informative.
Note: There are numerous uses of rel-nofollow in the wild, this is very much an incomplete list. If your site marked up with rel-nofollow, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page ([[rel-nofollow-examples-in-wild]]).
* [http://www.netd.it/sviluppo/ Netdesign Developers Network] uses the rel-nofollow attribute to make search engines don't follow the "off-topic" links.
* [http://funadvice.com FunAdvice] supports using the rel-nofollow tag to prevent users posting content simply for the search engine benefit, to improve the quality of the advice giving community.
* [http://petfoodtalk.com/dogfoodcoupons/ Dog Food Coupons] provides a dog food coupon collection service for dog owners. rel-nofollow is used to instruct search engine agents to '''not''' further execute link analysis and avoid endorsement of the actual merchant coupon links.
* [http://petmoz.com/dogfoodcoupons Pet Food Coupons] While listing coupons in our Dog Food Coupons section why use the rel-nofollow tag to make sure that search engines specifically Google do not follow any links we believe have no value to the visitor.

== bad examples in the wild ==
This section is informative.
There are now numerous abuses of rel-nofollow, in particular, where it is used on *2nd party* links, rather than the original intention of *3rd party* links such as in blog comments. The primary abusers of rel-nofollow are content hosting / social network sites.
* [http://flickr.com/ Flickr] puts "nofollow" on comments by the content publisher themselves (should only be on 3rd party comments), e.g. http://www.flickr.com/photos/tantek/2344425887/ as well as on profile links e.g. website: http://www.flickr.com/people/microformats/
* [http://twitter.com/ Twitter] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://twitter.com/indiewebcamp (links in posts do not have "nofollow" yet are wrapped with "t.co" URLs).
* [https://www.instagram.com/ Instagram] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://www.instagram.com/wholehousecarpetcleaning
* [http://flavors.me/ Flavors] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://wholehousecarpetcleaning.flavors.me
* [https://soundcloud.com/ Soundcloud] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://soundcloud.com/whole-house-carpet-cleaning
* [https://audioboom.com/ Audioboom] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://audioboom.com/wholehousecarpet
* [http://knowem.com/ Knowem] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://knowem.com/business/wholehousecarpetcleaning
* ... nearly every other content hosting / publishing site - please add more specific examples with direct URLs to pages abusing "nofollow".

=== exceptions ===
It may seem odd to explicitly list *non* examples in an examples in the wild section, but such non-examples may be useful to help convince the bad examples in the wild to change their behavior:
* [http://blogspot.com/ Blogspot] does NOT put "nofollow" on content publisher links, e.g. http://epeus.blogspot.com/2012/03/when-youre-merchandise-not-customer.html
* [http://tumblr.com/ Tumblr] does NOT put "nofollow" on content publisher links, e.g. http://adactio.tumblr.com/post/27135731578/the-web-unusually-came-with-a-view-source
* [https://www.behance.net/ Behance] does NOT put "nofollow" on content publisher links, e.g. https://www.behance.net/wholehouse739b
* [https://myspace.com/ Myspace] does NOT put "nofollow" on content publisher links, e.g. https://myspace.com/wholehousecarpet
* [https://about.me/ About.me] does NOT put "nofollow" on content publisher links, e.g. https://about.me/tony-cox-rochester-ny
* [http://weebly.com/ Weebly] does NOT put "nofollow" on content publisher links, e.g. http://rochestercarpetcleaning.weebly.com
* ... (let's hope we find more such non-examples)

== normative references ==
* [http://gmpg.org/xmdp/ XMDP]
* http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

== informative references ==
* VoteLinks can be used by an author to explicitly state their support for or against, or neutrality toward the destination of a link. Implementers implementing rel="nofollow" and VoteLinks should similarly not afford any additional weight or ranking to links with either <code>rev="vote-abstain"</code> or <code>rev="vote-against"</code>.
* Contributed from http://developers.technorati.com/wiki/RelNoFollow

== open issues ==
These are open issues that have been raised about rel="nofollow" that have been raised in various forums, in particular, on the public [http://lists.w3.org/Archives/Public/www-html W3C www-html mailing list]. Once the list grows too big, we'll make a separate wiki page ([[rel-nofollow-issues]]). The issues have been grouped into four areas.

* '''Definition'''. nofollow indicates a behavior rather than a relationship from which the behavior should be inferred as appropriate for the useragent. rel values should be nouns that indicates what the resource being referenced is in relation to the source.
* '''Name'''. nofollow is a bad name.
** overloading. does not mean the same as robots exclusion standards (robots.txt, meta robots) nofollow.
** does not mean what it says. does not mean "do not follow this link", rather it means " do not add weight from this link". [http://www.w3.org/mid/opsk3cccj9lo81gp@quark Asbjørn Ulsberg]
** not a noun. see above.
** suggested alternatives:
*** 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]
*** notally - [http://www.eenmanierom.nl/google-penalty/ Patrick Mackaaij]
* '''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.

=== additional lists of issues ===
Additional lists of issues raised against rel="nofollow" can be found at the following site(s):
* http://www.nonofollow.net/
Matt Cutts Says No to Nofollow On Internal Links:
* http://www.techzene.com/seo/rel-nofollow-seo-disadvantages/

[[Category:Specifications]]
[[Category:rel-nofollow]]

== articles ==
When this section gets too big, we can move it to [[rel-nofollow-articles]].
* [http://searchenginewatch.com/3633972 2009-06-03 Search Engine Watch: Google Changes Course on Nofollow]
* [http://reference.sitepoint.com/html/rel-mf#rel__nofollow SitePoint reference: rel- Microformats / nofollow] by Ian Lloyd

rel-nofollow

2017-01-16T04:05:37Z

Bravenewgame: /* bad examples in the wild */

<entry-title>rel="nofollow"</entry-title>
__TOC__
== Specification 2005-01-10 ==

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

=== Concept ===
* [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}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
* [[User:Kevin Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

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

== Abstract ==
<p class="entry-summary">RelNoFollow is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards. By adding <code>rel="nofollow"</code> to a hyperlink, a page indicates that the destination of that hyperlink {{should not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). Typical use cases include links created by 3rd party commenters on blogs, or links the author wishes to point to, but avoid endorsing. For more specific endorsement (or lack thereof) semantics, see [[vote-links|VoteLinks]].</p>

== XMDP profile ==
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[rel-nofollow]] specification.

=== URLs ===
This profile is hosted as a separate XMDP file on microformats.org:
* http://microformats.org/profile/rel-nofollow
* shortURL: http://ufs.cc/x/rel-nofollow

=== Usage ===
Profiles are referenced in (X)HTML files in the <HEAD> tag, e.g.:
<source lang=html4strict>
<head profile='http://microformats.org/profile/rel-nofollow'>
</source>

=== Profile ===
<source lang=html4strict>
<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 as defined in the
<a rel="help start" href="http://microformats.org/wiki/rel-nofollow">
rel-nofollow specification</a>
.</p>
<dl>
<dt id="nofollow">nofollow</dt>
<dd>Indicates that the referred resource was not necessarily linked to
by the author of the page, and thus said reference should not afford
the referred resource any additional weight or ranking by user agents.
</dd>
</dl>
</dd>
</dl>
</source>

== examples in the wild ==
This section is informative.
Note: There are numerous uses of rel-nofollow in the wild, this is very much an incomplete list. If your site marked up with rel-nofollow, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page ([[rel-nofollow-examples-in-wild]]).
* [http://www.netd.it/sviluppo/ Netdesign Developers Network] uses the rel-nofollow attribute to make search engines don't follow the "off-topic" links.
* [http://funadvice.com FunAdvice] supports using the rel-nofollow tag to prevent users posting content simply for the search engine benefit, to improve the quality of the advice giving community.
* [http://petfoodtalk.com/dogfoodcoupons/ Dog Food Coupons] provides a dog food coupon collection service for dog owners. rel-nofollow is used to instruct search engine agents to '''not''' further execute link analysis and avoid endorsement of the actual merchant coupon links.
* [http://petmoz.com/dogfoodcoupons Pet Food Coupons] While listing coupons in our Dog Food Coupons section why use the rel-nofollow tag to make sure that search engines specifically Google do not follow any links we believe have no value to the visitor.

== bad examples in the wild ==
This section is informative.
There are now numerous abuses of rel-nofollow, in particular, where it is used on *2nd party* links, rather than the original intention of *3rd party* links such as in blog comments. The primary abusers of rel-nofollow are content hosting / social network sites.
* [http://flickr.com/ Flickr] puts "nofollow" on comments by the content publisher themselves (should only be on 3rd party comments), e.g. http://www.flickr.com/photos/tantek/2344425887/ as well as on profile links e.g. website: http://www.flickr.com/people/microformats/
* [http://twitter.com/ Twitter] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://twitter.com/indiewebcamp (links in posts do not have "nofollow" yet are wrapped with "t.co" URLs).
* [https://www.instagram.com/ Instagram] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://www.instagram.com/wholehousecarpetcleaning
* [http://flavors.me/ Flavors] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://wholehousecarpetcleaning.flavors.me
* [https://soundcloud.com/ Soundcloud] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://soundcloud.com/whole-house-carpet-cleaning
* [https://audioboom.com/ Audioboom] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. https://audioboom.com/wholehousecarpet
* [http://knowem.com/ Knowem] puts "nofollow" on account holders' profile links, in the "description" and "web site" fields, e.g. http://knowem.com/business/wholehousecarpetcleaning
* ... nearly every other content hosting / publishing site - please add more specific examples with direct URLs to pages abusing "nofollow".

=== exceptions ===
It may seem odd to explicitly list *non* examples in an examples in the wild section, but such non-examples may be useful to help convince the bad examples in the wild to change their behavior:
* [http://blogspot.com/ Blogspot] does NOT put "nofollow" on content publisher links, e.g. http://epeus.blogspot.com/2012/03/when-youre-merchandise-not-customer.html
* [http://tumblr.com/ Tumblr] does NOT put "nofollow" on content publisher links, e.g. http://adactio.tumblr.com/post/27135731578/the-web-unusually-came-with-a-view-source
* ... (let's hope we find more such non-examples)

== normative references ==
* [http://gmpg.org/xmdp/ XMDP]
* http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

== informative references ==
* VoteLinks can be used by an author to explicitly state their support for or against, or neutrality toward the destination of a link. Implementers implementing rel="nofollow" and VoteLinks should similarly not afford any additional weight or ranking to links with either <code>rev="vote-abstain"</code> or <code>rev="vote-against"</code>.
* Contributed from http://developers.technorati.com/wiki/RelNoFollow

== open issues ==
These are open issues that have been raised about rel="nofollow" that have been raised in various forums, in particular, on the public [http://lists.w3.org/Archives/Public/www-html W3C www-html mailing list]. Once the list grows too big, we'll make a separate wiki page ([[rel-nofollow-issues]]). The issues have been grouped into four areas.

* '''Definition'''. nofollow indicates a behavior rather than a relationship from which the behavior should be inferred as appropriate for the useragent. rel values should be nouns that indicates what the resource being referenced is in relation to the source.
* '''Name'''. nofollow is a bad name.
** overloading. does not mean the same as robots exclusion standards (robots.txt, meta robots) nofollow.
** does not mean what it says. does not mean "do not follow this link", rather it means " do not add weight from this link". [http://www.w3.org/mid/opsk3cccj9lo81gp@quark Asbjørn Ulsberg]
** not a noun. see above.
** suggested alternatives:
*** 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]
*** notally - [http://www.eenmanierom.nl/google-penalty/ Patrick Mackaaij]
* '''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.

=== additional lists of issues ===
Additional lists of issues raised against rel="nofollow" can be found at the following site(s):
* http://www.nonofollow.net/
Matt Cutts Says No to Nofollow On Internal Links:
* http://www.techzene.com/seo/rel-nofollow-seo-disadvantages/

[[Category:Specifications]]
[[Category:rel-nofollow]]

== articles ==
When this section gets too big, we can move it to [[rel-nofollow-articles]].
* [http://searchenginewatch.com/3633972 2009-06-03 Search Engine Watch: Google Changes Course on Nofollow]
* [http://reference.sitepoint.com/html/rel-mf#rel__nofollow SitePoint reference: rel- Microformats / nofollow] by Ian Lloyd

species-examples

2017-01-15T13:32:43Z

Bravenewgame: /* Types of publishers */

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

:'''Note: the original name of the proposed microformat, "species", is likely to change, probably to "biota" or "taxon". The former has been retained here, to avoid having to make many repetitive and perhaps redundant edits'''

'''If you find a link which is not working, please replace it with a suitable alternative, rather than simply deleting it. Thank you.'''

__TOC__

==Types of publishers==

There are, perhaps, three types of publisher of taxonomic information (with all the usual overlaps and exceptions one finds when generalising so much!):

#Those which publish a full or partial hierarchy, like [http://names.ubio.org/browser/classifications.php?conceptID=2463046 UBIO].
#Those which publish a binominal, or a binominal with a qualifier, like a subspecies, variety, breed, hybridisation - but still referring to a single type of living thing, with no higher- level taxonomy. e.g [http://terrorbirdmedia.tumblr.com/ Terror Bird Media of Rochester NY]
#These which publish common (or "vernacular") names, but who would be interested in "aliasing" those to the scientific equivalent. e.g [http://terrorbirdmedia.tumblr.com/ Terror Bird Media]

Interestingly, some sites (Wikipedia, for example) have pages which fall into each of the three categories!
#[http://en.wikipedia.org/wiki/Bar-tailed_Godwit Bar tailed Godwit]
#[http://en.wikipedia.org/wiki/Genetics_of_humans Genetics of humans]
#[http://en.wikipedia.org/wiki/Ladywalk Ladywalk]

[[User:AndyMabbett|AndyMabbett]] 12:05, 23 Oct 2006 (PDT)

==Binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki><b class="bird">Black-tailed Godwit</b></nowiki></pre>

'''''Limosa limosa'''''
[http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club county lists]

<pre><nowiki>
<th scope="col">Common Name</th><th scope="col">Scientific Name</th>
[...]
<th scope="row" class="bird">Black-tailed Godwit</th><td class="sci">Limosa limosa</td>
</nowiki></pre>

'''''Eurasian Bittern'''''
[http://www.westmidlandbirdclub.com/ladywalk/BITTE.htm Bitterns at LAdywalk]

<pre><nowiki>
<b class="bird">Eurasian Bitterns</b>, (<i class="sci">Botaurus stellaris</i>)
</nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

'''''Canis_lupus''''' on [http://animaldiversity.ummz.umich.edu/site/accounts/information/Canis_lupus.html Animal Diversity Web]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''Rose Trantula''' on [http://www.practical-pet-care.com/spider_question.php?ID=1.2006100416232172 Pet Care Forum]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre] (this is a duplicate. [[User:BenWest|BenWest]] 21:56, 21 Oct 2006 (PDT))

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

'''''Galeopsis tetrahit s.s.'''''
[http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm West Midland Bird Club]
<pre><nowiki>
<i class="sci">Galeopsis tetrahit 
<abbr lang="la" title="sensu stricto">s.s.</abbr>
</i>
(<b class="plant">Common Hemp-nettle</b>)
</nowiki></pre>

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

'''''Anarhynchus frontalis'' Quoy and Gaimard, 1830''' on [http://en.wikipedia.org/wiki/Wrybill Wikipedia: Wrybill]
:note two-person authority

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki><i>Podiceps</i> sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki><b>Pisum sativum</b> L. subsp. <b>sativum</b></nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd><i>Chamaecyparis lawsoniana</i> 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

===Synonyms===
[http://en.wikipedia.org/wiki/Tarpan The Tarpan], '''''Equus ferus ferus''''':
<blockquote>The Tarpan was first described by Johann Friedrich Gmelin in 1774; he had seen the animals in 1769 in the region of Bobrovsk, near Voronezh. In 1784 Pieter Boddaert named the species '''''Equus ferus''''', referring to Gmelin's description. Unaware of Boddaert's name, Otto Antonius published the name '''''Equus gmelini''''' in 1912, again referring to Gmelin's description. Since Antonius' name refers to the same description as Boddaert's it is a junior objective synonym.</blockquote>

on http://www.westmidlandbirdclub.com/biblio/bb/71-338.htm:
<blockquote>some authors still refer to Scandinavian Herring Gulls as '''''L. a. omissus'''''; others regard '''''omissus''''' as no longer valid (a synonym of '''''argentatus''''')</blockquote>

On http://en.wikipedia.org/wiki/Devario_chrysotaeniatus:

:'''''Devario chrysotaeniatus''''' [...] former Names and Synonyms
::* '''''Danio chrysotaeniatus'''''

On http://en.wikipedia.org/wiki/Tetracanthus:

:'''''Echinocactus tetracanthus''''' synonym of '''''Parodia erinacea''''' - cactus

On http://en.wikipedia.org/wiki/Jostia_teaguei (using a "taxobox")

:Binomial name
:'''''Jostia teaguei'''''
:(Luer) Luer
:Synonyms
:'''''Masdevallia teaguei''''' Luer, 1978

On http://www.coleopterist.org.uk/haliplidae-list.htm

:'''HALIPLUS''' Latreille, 1802
:Subgenus HALIPLUS Latreille, 1802
:''confinis'' Stephens, 1828
::''pallens'' Fowler, 1887
::''halberti'' Bullock, 1928

i.e. ''Haliplus pallens'' and ''H. halberti'' are synonyms of ''H. confinis''.

See also [http://en.wikipedia.org/wiki/Special:Search?search=species+synonym&fulltext=Search Wkipedia search for "species synonym"]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki><p>The <b>Black-tailed Godwit</b>, <i>Limosa limosa</i></nowiki></pre>

====Linking====
Wikipedia uses the standard convention of having species italicised. Internal links to species may be to the common name or scientific name depending on which is used as the article's title (usually common for animals, scientific for plants, although there are exceptions). Links to scientific names work regardless:

<pre><nowiki>''[[Limosa limosa]]''</nowiki></pre>

Link to common name:

<pre><nowiki>[[Black-tailed Godwit]]</nowiki></pre>

Link to common name, but displaying scientific name:

<pre><nowiki>''[[Black-tailed Godwit|Limosa limosa]]''</nowiki></pre>

These types of links are not used in the Black-tailed Godwit article itself, but in others related to it. e.g. [http://en.wikipedia.org/wiki/British_avifauna British avifauna]

====Taxobox====

Wiki markup for the taxobox (taxonomy infobox) on the English Wikipedia, as used on the Black-tailed Godwit article, with irrelevant fields removed:

<pre><nowiki>
{{Taxobox
| name = Black-tailed Godwit
| regnum = [[Animal]]ia
| phylum = [[Chordate|Chordata]]
| classis = [[bird|Aves]]
| ordo = [[Charadriiformes]]
| familia = [[Scolopacidae]]
| genus = ''[[Godwit|Limosa]]''
| species = '''''L. limosa'''''
| binomial = ''Limosa limosa''
| binomial_authority = ([[Carolus Linnaeus|Linnaeus]], 1758)
}}
</nowiki></pre>

Above is vaguely displayed in an HTML table as (with formatting and links removed):

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa</i>
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

Also allows for other levels of taxonomy (e.g. genus or subspecies), and synonyms.

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [[species-examples-quantitative]]

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*The Internet Movie Database
**[http://www.imdb.com/title/tt0029443/ Private Life of the Gannets]
***[http://www.imdb.com/title/tt0029443/trivia Private Life of the Gannets trivia page with binominal]
**[http://www.imdb.com/title/tt0133318/ The Trials of Life]
**[http://www.imdb.com/title/tt0227812/ Whooping Crane]
***[http://www.imdb.com/title/tt0227812/trivia Whooping Crane trivia page with binominal]
**[http://www.imdb.com/title/tt0301727/ Winged Migration]

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Sky News
**[http://news.sky.com/skynews/article/0,,15410-1249430,00.html Homo floresiensis]
**[http://news.sky.com/skynews/article/0,,30200-13546024,00.html Atlapetes latinuchus yariguierum]
**[http://news.sky.com/skynews/picture_gallery/picture_gallery/0,,15410-1244699,00.html Polypedates chlorophthalmus]
**[http://search.sky.com/search/skynews/results/1,,,00.html?CID=30000&QUERY=species&SITEREF=skynews&SECTION=&TYPE_REF=&radiodate=&dayFrom=dd&monthFrom=mm&yearFrom=yyyy&dayTo=dd&monthTo=mm&yearTo=yyyy&Submit.x=0&Submit.y=0 Sky News search for "species"]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United Nations
** [http://www.oceansatlas.org/ Atlas of the Oceans] e.g. [http://www.oceansatlas.org/world_fisheries_and_aquaculture/html/resources/capture/mainspec/species/sp2605.htm Chilean nylon shrimp ''Heterocarpus reedi'']

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

*YouTube
**[http://www.youtube.com/results?search_query=starling&search=Search YouTube search for 'starling']]

==Breaking news==
In under two weeks, the BBC News website carried the following stories, all including the scientific names of species:
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]
*[http://newsbou.blogspot.com/ British Ornithologists' Union news]
*[http://fieldmarking.reger.com/ FieldMarking] - An experiment to see how people can collaborate to record wildlife observations in blogs.

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)
*[[User:PeNGo|Peter Halasz]], Wikipedia Admin.

==See also==
{{species}}

to-do

2017-01-14T21:34:21Z

Bravenewgame: /* Wiki improvements */

<entry-title>To Do</entry-title>
__TOC__
This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

== microformats2 updates ==
The following pages need to be updated to for microformats2 (typically code, examples, and any specific format advice)
* [[introduction]]
* [[get-started]]
* [[faq]]
* [[hcard-authoring]] -> [[h-card-authoring]]
* [[hcard-examples]] -> [[h-card-examples]]
* [[advocacy]]
* ...

== wiki gardening ==

=== trim fixups ===
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.

* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]

In particular, let's document old tr.im links and (unlinked) and where they used to link to so that if someone *searches* for tr.im URLs to figure out what happened to them, there's a chance they'll find the equivalent.

* [[tr.im]]

=== simplify pages ===
Review pages, from the [[Main Page]] on down and:

* Simplify/minimize the content in the pages with direct writing, assuming an eager(impatient,positive) reader in the primary reading flow.
* Move (keep) clarifications/details/documentation for edge case people (i.e. deliberate misinterpreters, sarcastic skeptics, pedants etc.) to details further down in a page (or on subpages) rather than in the primary reading flow.

Examples of simplified pages:
* [[Main Page]] - simplified quite a bit (2012-04-02), but could probably use additional simplification
* ...

Pages to simplify:
* [[how-to-play]] (should probably be done by an admin, but left here in case someone wants to try drafting a revision on another page and have an admin review it)
* pages listed in [[stable-pages]] (simplifying these first will help with better translations)
** for specifications, please work with their editor(s) on non-trivial content copy edits.

=== remove broken URLs ===

There's lots of links to sites that are now gone (see [http://indiewebcamp.com/site-deaths site-deaths] on IWC for a full list).

It'd be useful if we replaced them where possible with links to archive.org or equivalent.

TODO (mark as done when done):

* [[Upcoming]]
* code.google.com

=== incorporate things expected to break ===
==== shortlink spec ====
The rel=shortlink spec:
* https://code.google.com/p/shortlink/wiki/Specification
is going to die soon as part of Google Code's shutdown.

1. We should copy that spec (along with FAQ for the first few valid questions/comments) to [[rel-shortlink]], moving existing contents there to supplementary pages or purely historical record.

2. Get http://purl.org/net/shortlink to redirect to [[rel-shortlink]] instead.

== more documentation and research ==
=== extract from 1989 timbl proposal ===
* extra all specific problems and use-cases mentioned in http://www.w3.org/History/1989/proposal.html
* write them up as their own wiki pages, one per specific problem/use-case
* see if they're solvable with modern [[microformats2]]

== microformats specific ==

Just some nice things, feel free to do any of these.

=== for all microformats ===
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].

=== hCalendar ===
==== Add support to open source calendar projects ====
These are open source projects that could be potentially enhanced to support hCalendar.

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

=== hReview ===
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
* an [[hreview|hReview]] validator.
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.

=== hCalendar/hCard/hReview editor ===
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

=== hAtom ===
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].

=== WordPress patches for microformats ===
* submit patches for WordPress code/templates for microformats improvement
** <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
* Wordpress plugin for microformats, specifically hReview and hCalendar
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
* [http://www.yuiblog.com Yahoo! User Interface Blog]

=== Drupal patches for microformats ===
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal. Currently looking to support hAtom, hCard and hCalendar to start with. Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.

=== Adding Microformats to Existing Pages ===
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

===Glossary===
Add to the [[glossary]].

===hAtom tutorial===
Finish the [[hatom-tutorial]].

=== wiki gardening ===
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
* Use [[templates]] for boilerplate text and repeated lists of links
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.

====Spelling====
Per [[how-to-play]]: for English-language pages only: Find British spellings of common words and replace them with the US spellings per [[en-US]]. Mark such edits as "minor" with the comment: <nowiki>[[en-US]]</nowiki>. Please be careful to use and maintain proper native spelling of proper nouns (see [[how-to-play]] for details).

Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.

{| border="1"
|+
! [[en-GB]] !! [[en-US]]
|-
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
|-
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
|-
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
|-
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
|-
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
|-
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
|-
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
|-
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
|-
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
|-
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
|-
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
|-
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
|-
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
|-
|}

[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]

== Admins ==
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.

Admins check this "inbox" periodically and process and move items to [[admin-to-do]].

Please check [[admin-to-do]] to see if there is already an ongoing task item relating to your request. Otherwise add the item below.

=== Website Improvements ===
* [http://robot-independente.tumblr.com/#microformats@irc.freenode.net Tony Cox Rochester]
* [http://sir-clean-a-lot.com/#microformats@irc.freenode.net Bowie Cleaners]

=== Wiki improvements ===

* Something broken with the new MediaWiki microformats templates for date modified on delta/version pages? see: https://twitter.com/tonycoxny

* Want: Right-to-left (RTL) support in the theme for better translating to RTL languages. Per [https://www.facebook.com/permalink.php?story_fbid=10150109554926465&id=214611 this comment on the microformats page on Facebook 2011-02-13]: <blockquote><cite>Sina Cheraghi</cite> > Microformats <br> "I want to contribute in Microformats wiki by translating it into Persian. But lack of RTL (right-to-left) languages (Persian, Arabic, Hebrew and ...) theme causes some problems for me and other contributors."</blockquote>

* New link styles for links to mailing list archive
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Add proper styling to phrase elements
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

== Tantek ==
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].

=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Wiki cleanup/gardening for existing established microformats
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
# New microformat requests
# Document microformats [[history]].
# Other

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** move exploratory discussions which are failing to follow the process to a separate page from that
** repair damage done to the wiki
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
**** [[hcalendar-examples-in-wild]]
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
****** http://adactio.com/extras/schedules/barcampbrighton3/
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
**** [[to-do]]

=== help publishers ===
==== solve problems blocking publishers ====
* [[value-class-pattern]]
** <del>drafted</del>
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
** <del>put out call for review, implementation,</del> and value-title tests

===== minor update current specifications =====
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** close remaining [[hcard-issues-resolved|hCard resolved issues]] by writing necessary [[hcard-faq|FAQ]] entries, updating [[hCard]], and adding to [[hcard-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
** incorporate [[hcard-feedback]]
** continue updating the spec per the inline comment about property references
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcard-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
** Update [[hcard-brainstorming]] on element specific parsing rules
** Update X2V, hKit, Operator accordingly
** Write test cases accordingly
** Update [[hcard-parsing]] accordingly
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
** close remaining [[hcalendar-issues-resolved|hCalendar resolved issues]] by writing necessary [[hcalendar-faq|FAQ]] entries, updating [[hCalendar]], and adding to [[hcalendar-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
** incorporate [[hcalendar-feedback]]
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list. Separate common properties up front.
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcalendar-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcalendar-examples]]
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
* draft hReview 0.4
* resolve hAtom issues
* co-edit hAtom per permission from David Janes
* draft [[hAtom]] 0.2
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
* add sections for comments/opinion from community as well as issues subsection
* solicit feedback
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.

==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

Brainstorm updates to the [[pocket-cheat-sheet]] to better enable [[social-network-portability]], or perhaps design a new '''social network portability pocket cheat sheet''' that specifically documents:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
* update cheatsheet to include new [[value-class-pattern]] uses
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

==== advocacy for obvious sites ====
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
*** open data > open source
*** "open information" vs "open source"
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
*** if the data is open you can always export it and consume it in any number of open source systems
*** that's why open data is MUCH more important than open source
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
*** if the data was open, anyone could rebuild an accessible version
*** faqs / misconceptions:
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard. Rather, if you think something is hard, then assume others may know easier methods, and ''ask'' the community how one can do it more easily. parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** look for hCards and parse them

* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.

* Conference Schedule Creator
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

=== iterate on current microformats ===
==== in general ====
===== plain language intros =====
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
* followed by links to more plain-language resources, e.g. *-intro pages.
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
* As well as a syntactic example, examples of use would be useful.
* when I might want to use XOXO.
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
These suggestions could be incorporated into the other specs as well.
===== exploratory discussions =====
* update [[exploratory-discussions]] with critical microformats as "active"
===== CSS enhancements for =====
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
* brainstorm additional possibilities for better presentation of content using existing microformats.
===== update affiliations =====
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
===== profile URLs =====
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-profile]] '''next-actions''':
** update property definitions with more detail using semantics from [[RFC2426]]
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* update [[hcalendar-examples]]
** add examples like [[hcard-examples]]
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
*** rrule
*** duration
*** ... etc.
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* have folks verify [[hcalendar-profile]]. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hreview|hReview]] ====
'''Next-actions''':
* reconcile [[hreview-profile|hReview 0.4 XMDP profile]] with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.

==== [[rel-tag]] ====
'''Next-actions''':
* send [[rel-tag]] XMDP profile ([[rel-tag-profile]]) to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== [[rel-me]] ====
'''Next-actions''':
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
** and put redirects in place, notes about contribution
* update rel-me examples and document with examples the rel-me implict subdir rule

==== [[hatom|hAtom]] ====
'''Next-actions''':

==== summary Examples in the Wild page ====
* need to create a summary / overall [[examples-in-the-wild]] page
** parallel the summary/overall [[implementations]] page.
** use newly reorganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

=== wiki cleanup ===
==== for all microformat specs ====
'''Next-actions''':
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
'''Goal''': greater approachability/readability of microformats specs by a broader audience.

Reference:
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.
* [[hreview|hReview]] has some similar improvements, but different.
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview

'''Next-actions''':
# contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|hResume]] is an improvement, and if it could be better. Document reasoning/requirements for intro/header and other sections.
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
# Write up methodology behind the section organization and note editors lessons learned into an [[editors-guide]] page (what other variants were done before, in which specs, and note problems/complaints with other variants).

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

'''Next-actions''':
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].

==== reorg Examples in the Wild sections ====
Work with community to:
* include more *key* details per example, e.g. precise or estimates of counts for services
* collate/sort examples in the wild by
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
** individiual companies/organizations contact info pages
** individual people's contact info pages
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.

=== site usability ===
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
** ideally use the from address of the author of the blog post
** maybe photomatt knows how to do this.

=== introduction / community ===
* microformats-discuss *
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.

==== posh improvement ====
* Create a page to answer the question "[[how-should-i-markup]]"
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.

==== principles and process ====
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general
* resolve [[process-issues]]

==== profiles ====
* update [[XMDP]] with new required features:
** ability for one profile to include/import another (rel="import" ?)
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
*** add rel="profile" to the [[xmdp-profile]].
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

==== community mark ====
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?

==== document issue resolutions ====
* Prefixing has already been considered and rejected for microformats in general. Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.

=== emerging microformats ===
* [[directions]]
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]
'''Next-actions''' for each emerging microformat (one at a time)
* review all microformats-email on the new microformat
* determine where new microformats is "stuck" in the process
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary

=== new microformat requests ===
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].

=== document microformats history ===
Document microformats [[history]], including:
* dates and origins of microformats, names, terms
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]

=== other ===
* Add XPath equivalents where appropriate in [[hcard-parsing]]

==Ryan==
=== wiki cleanup ===
* <s>possibly move dead proposals off of homepage?</s>

=== hCalendar/hCard/hReview creator improvements ===
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3

=== other ===
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml

=== rel-payment ===
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]

=== hcalendar ===
* make sure we explicitly disallow 'vjournal'

== Dimitri Glazkov ==

* Figure out REST/Microformats thing
* Work on result set idea
* Implement h-creators using Web Forms 2.0

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
* <strike>Read GTD (at least the first two chapters)</strike>.

=== Campaigns ===

* <strike>Get Blogger to support hAtom and hCard</strike>
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get <strike>Digg to support microformats</strike> (still need XFN).

=== Wishlist ===

* Microformat for "buyable items" (see [[listing-examples]] and related documents)
* Location MF -- right click "map this" (see [[geo]] and [[adr]])
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/ Flocktails])
* Better hCal support -- support many views of same hCal data on one page using XSLT
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
* invoicing microformat
* better microformats wiki theme
* Define flow for OpenID + XFN + hcard (see [http://diso-project.org DiSo Project])

Hey Chris.
Congrats on Microsyntax
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?

== Robert Bachmann ==
[[User:RobertBachmann|Robert Bachmann]]

=== XSLTs ===
<ul>
<li><strong>Test scripts</strong>
<ul>
<li>Do some refactoring, split Perl code into smaller modules</li>
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
<li>Provide some documentation for using the test scripts</li>
</ul>
</li>
<li><strong>hAtom2Atom</strong>
<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
</li>
</ul>

== Brian Suda ==
=== Citation Microformats ===
* Add all my notes to the Wiki
* Start the process of naming the properties using existing names

=== X2V ===
Make changes and update site (almost stable)
Get ATTENDEE and other strange attributes working
==== WARNINGS and ERROR ====
work on the warnings and error output for the pre-check in X2V

=== FAQ ===
* clean-up the MF FAQs
* clean-up FAQs from the major microformats
* pull Questions from the mailing list and document them to the FAQs and example

=== Microformats History ===
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== Ernest Prabhakar ==
=== Wiki-Thon Proposal ===
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# Tackle larger projects (~1-2 hours) than people usually have time for
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

* Clean up this todo list (meta!)
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
*** Ping anyone with specific tasks / nag
* Proposal for page simplifications - notes, to expand to tasks later:
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
** Process updates to blog?
** Activity overview updates on main site somewhere?
*** Code and Tools page on site: Currently it's mostly only tools. Need to add a list of actual specifications on the wiki.
** In general: less clutter, more structure, more focus.

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki
* documentation of semantic authoring techniques
* researching the social problems relating to authorship and publishing on the web
* development of new microformats in response to failing to meet the needs of the second with the first.

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)

=== Creators ===
_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model. This is a nice feature, so maybe I should be branching instead.
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
** how to author semantic html
** choosing class names
** using HTML's general extension mechanisms
** advocating use
** collaborating/reusing HTML
** debugging HTML: use pastebin, separate out the relevant bits.
** getting help from the community
** applying Microformats.

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

* Microformat
** Specification
** Tutorial
** Examples
** Use cases
** Reference
** Discussion
** Brainstorming (might be combined w/Discussion)
** Implementations
** Related Pages
** Further Reading
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)

These pages would be located respectively at

* http://microformats.org/wiki/hcard/
** http://microformats.org/wiki/hcard/Specification
** http://microformats.org/wiki/hcard/Tutorial
** http://microformats.org/wiki/hcard/Examples
** http://microformats.org/wiki/hcard/Use_cases
** http://microformats.org/wiki/hcard/Reference
** http://microformats.org/wiki/hcard/Discussion
** http://microformats.org/wiki/hcard/Brainstorming
** http://microformats.org/wiki/hcard/Implementations
** http://microformats.org/wiki/hcard/Related_Pages
** http://microformats.org/wiki/hcard/Further_Reading
** http://microformats.org/wiki/hcard/All

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

=== hAtom2Atom ===
<ul>
<li>Support for other XSLT engines:
* hAtom2Atom written using XSL 2.0
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

=== Microformats Proposals ===

* rel="disclaimer":
** Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.
* rel="external":
** Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
* Implement Tail scripts for adding things into Midgard

== Justin Thorp ==
* Start researching examples for a To-do microformat

== [[User:MarkLentczner|Mark Lentczner]] ==

* Get Second Life's event web pages to have proper event microformats data
** Add [[hcard|hCard]] to profile pages
** Add [[hcalendar|hCalendar]] to events listings
* Start pinging pingerati.net/ping/$url when pages are updated
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].

== [[User:DerrickPallas|Derrick Pallas]] ==
=== microformat proposal: dependancy ===
* looking for examples of directed graphs on the web
* applications in
** software engineering
*** automatically build library dependency trees
*** distribute security alerts to people that link to your code
** any directed, acyclic graph
*** getting dressed in the morning
*** cooking
* orthogonal to xfn
** people don't have versions
*** libfoo requires libbar-2.0 or later
** people don't have optional relationships
*** ex: at build time, compile in SSL support if present
** people don't have exclusive-or relationships
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick

== [[User:PaulDowney|Paul Downey]] ==
* building a generic Javascript parser
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

== [[User:BenWard | Ben Ward]] ==

=== Recurring ===

* Delete Wiki Spam

=== Currently ===

* Gardening/updating key wiki pages.
** [[how-to-play]]
** XHTML Design Principals
* embed brainstorming
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.

=== Next Actions ===

* Conclude new hCalendar proposals from Yahoo TV Listings experience
* Resume work on hListing microformat
* Re-org the Microformats.org front-page content
** Work with [[User:Phae]] on refreshing the microformats frontpage content
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
** Build new wiki edits module for the blog
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
* Build a microformats activity stream
** Replace front page blog with activity flow
*** Wiki Edits/New Pages
*** New Mailing List Threads
*** Interesting µf links
*** Blog posts
*** Upcoming events/event reminders
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)

== [[User:Spiritquest|Ketan Majmudar]] ==
=== Activites ===
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
** Provide real world examples and apply this to the proposed specifications
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
* see where I can help the community
* look at using x2v or writing php parser classes for hcard -> vcard
* open source hCard class (php) used to format db fields

blog-post-examples

2017-01-14T18:48:35Z

Bravenewgame: /* No Entry Permalink */

= Blog Post Examples =

This page is for documenting real world examples of what people publish in blog posts, what markup they use, and what implied schemas can be inferred from their behaviors. See also: [[blog-post-formats]], [[blog-post-brainstorming]], [[hatom|hAtom]].

__TOC__

= Introduction =
== Discussion Participants ==

hallu

=== Authors ===
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix BlogMatrix, Inc.]
* [[MichalMigurski]]

=== Contributors ===
* [http://rbach.priv.at/ Robert Bachmann]
* [http://tantek.com/ Tantek Çelik]
* [http://maetl.coretxt.net.nz Mark Rickerby]
* [http://bs-markup.de Björn Seibert]

=== Interested Folks ===

= Specific Examples from the Wild =

== EntryGroup ==

=== Entries are within an EntryGroup block ===
All entries are within an enclosing 'div' -- the EntryGroup. This is common with weblog home pages ([http://microformats.org/ example]) or archive with multiple entries.

<pre><nowiki>
<div id="content">
<h2 id="home-title">
Latest microformats news
<a href="http://www.microformats.org/feed/" title="link to RSS feed" id="feed-link">
<img src="/img/xml.gif" width="23" height="13" alt="XML" />
</a>
</h2>

<div class="entry">
<h3 id="post-60">
<a href="http://www.microformats.org/blog/2005/...">Wiki Attack</a>
</h3>
...
</div>

<div class="entry">
<h3 id="post-59">
<a href="http://www.microformats.org/blog/2005/...">Web Essentials Audio</a>
</h3>
...
</div>

<div class="entry">
<h3 id="post-57">
<a href="http://www.microformats.org/blog/2005/...">WebZine FollowUp</a>
</h3>
...
</div>
</div>
</nowiki></pre>

Note also the header at the top explaining what this feed is. We may want to exploit this also.

=== Entries are within an explicit EntryGroup ===
There are multiple entries on a single page but there is no explicit block element for the entries themselves -- though of course, there is at least one block that has the entries: <code><body></code>. This is also a common use case for weblogs and archives also.

=== Multiple EntryGroups on a page ===
There may be multiple groups of entries on a single page that are tenously connected ([http://news.google.ca/nwshp?hl=en&tab=wn&q= example-2]). Also, many weblogs have 'miniblogs' on the side that act much inthe same way.

* [http://www.truthlaidbear.com/topics.php example]

<pre><nowiki>
<div id="fullcol">
<div id="sumcol">

<b>
<a href="http://www.truthlaidbear.com/topicpage.php?topic=harrietmiers" class="linktitle">Harriet Miers</a>
</b>
</div>
<div id="commcol">
<img src="http://www.truthlaidbear.com/topics/topic_harrietmiers_sm.png" >
</div>
<div id="commcol">

<b>
<a href="http://polipundit.com/index.php?p=10420" class="linktitle">Harriet Miers Must...</a>
</b>
<br>
...
</div>
<div id="commcol">

<b>
<a href="http://instapundit.com/archives/026104.php" class="linktitle">A MIERS MELTDOWN? </a>
</b>
<br>
...
</div>
</div>

<div id="fullcol">
<div id="sumcol">

<b>
<a href="http://www.truthlaidbear.com/topicpage.php?topic=iraq" class="linktitle">Iraq</a>
</b>
</div>
<div id="commcol">
<img src="http://www.truthlaidbear.com/topics/topic_iraq_sm.png" >
</div>
<div id="commcol">

...
</div>
<div id="commcol">

...
</div>
</div>
</nowiki></pre>

=== Single entry on a page ===
This is common with weblogs that archive on a per entry basis ([http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ example]).

<pre><nowiki>
<div id="content">
<h2 id="home-title">
Latest microformats news
<a href="http://www.microformats.org/feed/" title="link to RSS feed" id="feed-link">
<img src="/img/xml.gif" width="23" height="13" alt="XML" />
</a>
</h2>
</div>
</nowiki></pre>

Note that's no guarentee that a block (as shown above as the <code>id=content</code> div) will be around the singleton entry.

== EntryGroup Title ==
== EntryGroup Permalink ==
== Individual Entry ==

=== Individual entries are within a container ===
Common.

* [http://microformats.org/ example]

<pre><nowiki>
<div class="entry">
<h3 id="post-60">
<a href="http://www.microformats.org/blog/2005/...">Wiki Attack</a>
</h3>
...
</div>
</nowiki></pre>

=== Individual entries are not within a container ===
Common.

* [http://nataliesolent.blogspot.com/ example]

<pre>
<a name="112877372228959075"> </a>
<br>
<strong>Just one problem, Minister.</strong> Last week, Bill Rammell,
<br>
</pre>

=== Disjointed entries ===
That is, not all sub-elements of an individual entry are in the container (for example, the author and date may follow in a separate block)

== Entry Titles ==
=== Entry Title enclosed in <code><h#></code> block element ===
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ example]

<pre>
<div class="entry single">
<h2 id="post-59">Web Essentials Audio</h2>
...
</div>
</pre>

=== Entry Title enclosed in a <code><div></code> block element ===
''I've seen this but I can't find an example, hopefully implying this is somewhat rare''.

=== Entry Title enclosed in an inline presentation element, such as <code><b></code> ===
* [http://nataliesolent.blogspot.com/ example]

<pre>
<a name="112877372228959075"> </a>
<br>
<strong>Just one problem, Minister.</strong> Last week, Bill Rammell,
<br>
</pre>

=== Entry Title enclosed in a <code><span></code> (inline element) ===
* [http://www.andrewsullivan.com/ example]

<pre>
<a name="112897777851715476"> </a>
<br>
<SPAN CLASS="inc_subtitle">EMAIL OF THE DAY II: </SPAN>"After years ...
</pre>

=== No Entry Title ===
* [http://www.instapundit.com/ example]

== Entry Content ==

=== Entry without content ===
That is, the entry has just a link and the title pointing to a different URI (which may actually have content). This is something frequently seen on news sites (which after all, can generate feeds)

* [http://www.cbc.ca/news/ example]

<pre><nowiki>
<ul>
<li>
<a href="/story/.../ndp-libs051016.html">NDP sets conditions for backing Liberals</a>
</li>
<li>
<a href="/story/.../teachers-bc051016.html">Go back to work, B.C. ...</a>
</li>
<li>
<a href="/story/.../alberta-strike2_051015.html">Plant managers charged ...</a>
</li>
<li>
<a href="/story/.../bc-mystery-illness051015.html">B.C. seniors' home reports...</a>
</li>
</ul>
</nowiki></pre>

=== Entry contains summary content only ===
This is common on media sites. MovableType also provides this as a default option, so it's often seen on MT blogs,

* [http://thecommunityengine.com/home/ example]

<pre><nowiki>
<div class="inlineBlog">
<h3 id="a003068">
<a href="http://thecommunityengine.com/h.../xfolk_vegomatic.html" class="taggedlink">xFolk Veg-o-matic Alpha</a>
</h3>
<p class="abstract extended">
We provide a way to surf the web and slice and dice information you find there into your own custom output stream.
</p>
<p class="categorylist">
Sections:
<a href="http://thecommunityengine.com/home/archives/tools_and_analytics" rel="tag">Tools and Analytics</a>
</p>
<p class="taglist">Topics:
<a href="http://thecommunityengine.com/home/archives/tags/greasemonkey" rel="tag">greasemonkey</a>
<a href="http://thecommunityengine.com/home/archives/tags/microformats" rel="tag">microformats</a>
<a href="http://thecommunityengine.com/home/archives/tags/xfolk" rel="tag">xFolk</a>
</p>
<p>
The folks at ... the rest of the content
</p>
<p class="extended">
<a href="http://thecommunityengine.com/.../xfolk_vegomatic.html#more">Continue reading "xFolk Veg-o-matic Alpha"</a>
</p>
...
</div>
</nowiki></pre>

Notes:
* there's a lot of things going on in this example
* there's an "abstract" at the top
* there's sections for "categories" and "tags"
* there's a summary section "The folks at ... the rest of the content"
* there's a link to the full content at the bottom

=== Entry contains complete content ===

* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ example]

<pre><nowiki>
<div class="entry single">
<h2 id="post-61">Class attributes are about more than styling</h2>

<p>When people talk about microformats, ... </p>

<blockquote cite="http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2">
... quoted text from elsewhere
</blockquote>

<p>There’s a couple of points I’d like to highlight here:</p>

... more content ...

<h4 class="tags">Technorati Tags:</h4>
<ul class="tags">
<li><a href="http://www.technorati.com/tag/css" rel="tag">css</a></li>
...
</ul>

<ul class="post-info">
... footer stuff ...
</ul>
</div>
</nowiki></pre>

=== Entry breaks content into multiple sections ===
* [http://www.samizdata.net/blog/ example]
* we also identify this as 'Split Content'

<pre><nowiki>
<div class="blogbody">
<a name="008148"></a>

<div class="title">
Face to face: why places will continue to exist
</div>

<div class="posted">
<strong>Brian Micklethwait (London)</strong>
  
<a href="...">Science & Technology</a>
</div>

<p>It is not just that I dislike filling in forms....</p>
... the first section of the content ...

... this link makes the extended section show ...
<span id="varP8148">
<img src="http://www.samizdata.net/blog/img/bullet_tri.gif" width="16" height="10" alt="" />
<a href="..." onclick="showMore(8148,'...');return false;">
Read more.
</a>
</span>

<div id="varXYZ8148" style="display: none">
<p>The very gadgets – computers linked...</p>
... the rest of the extended content ...

... this link makes the extended section hide ...
<img src="..." width="16" height="10" alt="" />
<a href="#008148" onclick="showMore(8148,0);return true;">
Read less.
</a>
</div>
</div>
</div>
</nowiki></pre>

== Entry Datetimes ==
Datetimes are rarely expressed in consistent formats on weblogs. Weblogs generally express the creation date of the posting, not the modified time.

=== Dates between weblog entries ===
This is a common pattern but by no means universal pattern seen on weblogs -- a header or div inserted between weblog entries indicating that the date has changed. I cannot find an example where this header is systematically linked to the entries using that data (i.e. a common enclosing div)

* [http://dannyayers.com/ example]

<pre><nowiki>
<div class="post">
<h3 class="storytitle" id="post-3151"><a href="http://dannyayers.com/...">...</a></h3>
...
</div>

<div class="date">2005-10-07</div>

<div class="post">
<h3 class="storytitle" id="post-3150"><a href="http://dannyayers.com/...">...</a></h3>
...
</div>
</nowiki></pre>

=== Entry Date or Datetime in entry footer ===
Most weblogs follow this pattern. Dates or datetimes are in human readable format in varying fashions. Often only the time is indicated, as the date is implied. The date or datetime is sometimes also used an indication of the 'permalink' for a post.

* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ example]

<pre><nowiki>
<div class="entry single">
<h2 id="post-59">Web Essentials Audio</h2>

<p>...</p>
<ul class="post-info">
<li><a href="...">Friday, September 30th, 2005 at 12:31 pm</a></li>
</ul>
</div>
</nowiki></pre>

== Entry Permalinks ==
Note that not only do some examples fit multiple categories, sometimes weblog posts place the multiple links to the permalink within a single post (for example, in the header and footer).

=== Entry Permalink is around or inside title ===
see immediate following example
=== Entry Permalink is in header of post ===
see immediate following example
=== Entry Permalink uses absolute URI ===
* [http://microformats.org/ example]

<pre><nowiki>
<div class="entry">
<h3 id="post-45">
<a
href="http://www.microformats.org/blog/2005/08/21/foobar-microformats/"
rel="bookmark"
title="Permanent Link to FooBar Microformats">FooBar Microformats</a>
</h3>
...
</div>
</nowiki></pre>

=== Entry Permalink is in footer of post ===
* [http://blogs.herald.com/dave_barrys_blog/2005/10/yet_another_ins.html example]

<pre><nowiki>
<h3>YET ANOTHER INSTANCE OF THE WORLD FINALLY CATCHING UP TO THE BLOG</h3>
<p>Today's news: Neuticles win ... award.</p>
<p class="posted">
Posted by judi on October 7, 2005 at 05:00 PM |
<a href="http://blogs.herald.com/dave_barrys_blog/2005/10/yet_another_ins.html">Permalink</a>
</p>
</nowiki></pre>

=== Entry Permalink uses relative URI ===
see immediate following example
=== Entry Permalink includes fragment ===
This is used when a weblog archives posts as a group (say, by month or week) rather than as individual posts. This is very common on older blogspot weblogs.

* [http://nataliesolent.blogspot.com/2005_10_02_nataliesolent_archive.html#112876103554732697 example]

<pre><nowiki>
<a name="112876103554732697"> </a><br>
<strong>The ceremony of Explaining the Joke</strong>
<br>
<span class="byline">posted by Natalie at
<a href="2005_10_02_nataliesolent_archive.html#112876103554732697">8:18 AM</a></span>
<br>
</nowiki></pre>

=== No Entry Permalink ===
This is common on single article archive pages, some social weblogs ([http://anthony-cox-rochester-ny.blogspot.com/ example]) and most big media webpages (i.e. non-blogs)
* [http://instapundit.com/archives/026056.php example]

<pre><nowiki>
<a name="026056"></a>
<p>ACCORDING TO THE WHITE HOUSE, ... hadn't we?</p>
<div class="footer">posted at 11:35 PM by <b>Glenn Reynolds</b></div>
</nowiki></pre>

== Entry Author ==

= Other Stock Examples =
Example of blog posts in unmodified weblog software installations.

=== Stock Wordpress 1.5 Installation ===
<pre><nowiki>
<div class="post">
<h2 id="post-237">
<a href="http://192.168.1.113/~migurski/wordpress/?p=237"
rel="bookmark" title="Permanent Link to More election maps">More
election maps</a>
</h2>
<small>November 9th, 2004 </small>

<div class="entry">
<p>via <a href="http://www.markme.com/jd/archives/006288.cfm">John Dowdell of JD on MX:</a></p>
<blockquote>
<p>More election maps: Ben Metcalfe, a software engineer at
the BBC, has his own list here… includes some not in
that “Flash the only winner” item from The
Inquirer, which Kevin also elaborated upon. Additionally,
Andrew Lucking pointed to the…</p>
</blockquote>
</div>

<p class="postmetadata">
Posted in <a
href="http://192.168.1.113/~migurski/wordpress/index.php?cat=1"
title="View all posts in General" rel="category tag">General</a>
<strong>|</strong> <a
href="http://192.168.1.113/~migurski/wordpress/?p=237#comments">
No Comments »</a>
</p>


</div>
</nowiki></pre>

=== Stock MoveableType 3.15 Installation ===
<pre><nowiki>
<h3 id="a000002">Example Entry</h3>
<p>This is the entry body.</p>
<p class="extended"><a href="http://localhost/archives/2005/08/example_entry_1.html#more">Continue reading "Example Entry"</a></p>
<p class="posted">Posted by migurski at <a href="http://localhost/archives/2005/08/example_entry_1.html">03:49 </a> | <a href="http://localhost/archives/2005/08/example_entry_1.html#comments">Comments (0)</a></p>
</nowiki></pre>

=== Stock Blosxom Installation, with [http://blosxom.com/downloads.html "Blosxom Flavor Sampler"] ===
<pre><nowiki>
<p>
<a name="post-identifier"><b>Post Title</b></a>
<br />
Post body text.
</p>
<p align="right">
<i>[<a href="/permalink/post-identifier">post-identifier</a>]
<a href="/permalink/2005/08/15#post-identifier">permanent link</a></i>
</p>
</nowiki></pre>

=== Stock Textpattern 4.0.3 Installation ===
<pre><nowiki>
<div id="content">

<h3><a href="http://txpdefault/article/2/second-post" title="Permanent link to this article">Second Post</a> · a few seconds ago by chris</h3>
<p>This is a short second post for illistration.</p>

<p class="comments_invite"><a href="http://txpdefault/article/2/second-post#comment" class="comments_invite">Comment</a></p>
<div align="center"><img src="http://txpdefault/images/1.gif" style="height:1px;width:400px" class="divider" alt="" /></div><h3><a href="http://txpdefault/article/1/first-post" title="Permanent link to this article">First Post</a> · 4 minutes ago by textpattern</h3>
<p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec rutrum est eu mauris. In volutpat blandit felis. Suspendisse eget pede. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos hymenaeos. Quisque sed arcu. Aenean purus nulla, condimentum ac, pretium at, commodo sit amet, turpis. Aenean lacus. Ut in justo. Ut viverra dui vel ante. Duis imperdiet porttitor mi. Maecenas at lectus eu justo porta tempus. Cras fermentum ligula non purus. Duis id orci non magna rutrum bibendum. Mauris tincidunt, massa in rhoncus consectetuer, lectus dui ornare enim, ut egestas ipsum purus id urna. Vestibulum volutpat porttitor metus. Donec congue vehicula ante.</p>

<p class="comments_invite"><a href="http://txpdefault/article/1/first-post#comment" class="comments_invite">Comment</a> [1]</p>

<div align="center"><img src="http://txpdefault/images/1.gif" style="height:1px;width:400px" class="divider" alt="" /></div>

</div>
</nowiki></pre>

= Rough Examples =

Moved here from [[blog-description-format]] for documentation purposes.

== Existing practice ==

=== Entry Wrappers ===

<pre><nowiki><div class="entry"></div></nowiki></pre>

The entry wrapper format has widespread usage, but seems to show up in slightly different contexts.

Some blogs (ala Wordpress) use the entry div as a wrapper to the actual post body, and wrap the whole thing in an additional div:

<pre><nowiki><div class="post">
<div class="entry">
</div>
</div></nowiki></pre>

A vast number of sites, including many blogs contain the main page content within a id="content" div:

<pre><nowiki><div id="content"></div></nowiki></pre>

=== Metadata ===

Wordpress uses class="postmetadata" to contain meta information, date, others use their own syntax - class="topics", class="description".

=== Basic Elements ===

Titles are usually denoted with an H2 or H3 heading. Use of class="title" seems rare, but some sites do use this explicit markup.

class="summary" is used to denote an item summary, usually in a paragraph element.

=== Permalinks ===

rel="bookmark" and rel="permalink" are both used in various places to denote a permalink to the specified entry.

=See Also=
* [[blog-post-examples]]
* [[blog-post-formats]]
* [[blog-post-brainstorming]]
* [[hatom|hAtom]] - the draft proposal based on this information
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)

hatom-ja

2017-01-14T07:46:33Z

Bravenewgame: /* Implementations */

<entry-title>hAtom-ja</entry-title>

<h1>hAtom 0.1</h1>
{{Template:DraftSpecification-ja}}

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

<div class="vcard">
;<span class="role">Editor/Author</span>
:<span class="fn">[http://blogmatrix.blogmatrix.com/ David Janes]</span> <span class="org">([http://www.blogmatrix.com BlogMatrix, Inc.])</span>
</div>

;Contributors
:<span class="vcard"><span class="fn">[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]</span></span>
:<span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span> and before at [http://technorati.com Technorati, Inc.])</span>

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

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

{{rfc-2119-intro-ja}}

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

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

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

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

The hAtom schema consists of the following:

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

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

=== Field and Element Details ===

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

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

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

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

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

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

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

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

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

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

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

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

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

== Implementations ==

This section is '''informative'''.

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

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here], and there is another [http://tonycoxrochesterny.strikingly.com/ demo here]


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

== 特許 ==
{{MicroFormatPatentStatement-ja}}

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

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

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

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

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

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

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

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

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

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

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional <span id="languages">languages</span>:
* [[hatom-fr|français]]

to-do

2017-01-14T07:19:49Z

Bravenewgame: /* Website Improvements */

<entry-title>To Do</entry-title>
__TOC__
This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

== microformats2 updates ==
The following pages need to be updated to for microformats2 (typically code, examples, and any specific format advice)
* [[introduction]]
* [[get-started]]
* [[faq]]
* [[hcard-authoring]] -> [[h-card-authoring]]
* [[hcard-examples]] -> [[h-card-examples]]
* [[advocacy]]
* ...

== wiki gardening ==

=== trim fixups ===
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.

* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]

In particular, let's document old tr.im links and (unlinked) and where they used to link to so that if someone *searches* for tr.im URLs to figure out what happened to them, there's a chance they'll find the equivalent.

* [[tr.im]]

=== simplify pages ===
Review pages, from the [[Main Page]] on down and:

* Simplify/minimize the content in the pages with direct writing, assuming an eager(impatient,positive) reader in the primary reading flow.
* Move (keep) clarifications/details/documentation for edge case people (i.e. deliberate misinterpreters, sarcastic skeptics, pedants etc.) to details further down in a page (or on subpages) rather than in the primary reading flow.

Examples of simplified pages:
* [[Main Page]] - simplified quite a bit (2012-04-02), but could probably use additional simplification
* ...

Pages to simplify:
* [[how-to-play]] (should probably be done by an admin, but left here in case someone wants to try drafting a revision on another page and have an admin review it)
* pages listed in [[stable-pages]] (simplifying these first will help with better translations)
** for specifications, please work with their editor(s) on non-trivial content copy edits.

=== remove broken URLs ===

There's lots of links to sites that are now gone (see [http://indiewebcamp.com/site-deaths site-deaths] on IWC for a full list).

It'd be useful if we replaced them where possible with links to archive.org or equivalent.

TODO (mark as done when done):

* [[Upcoming]]
* code.google.com

=== incorporate things expected to break ===
==== shortlink spec ====
The rel=shortlink spec:
* https://code.google.com/p/shortlink/wiki/Specification
is going to die soon as part of Google Code's shutdown.

1. We should copy that spec (along with FAQ for the first few valid questions/comments) to [[rel-shortlink]], moving existing contents there to supplementary pages or purely historical record.

2. Get http://purl.org/net/shortlink to redirect to [[rel-shortlink]] instead.

== more documentation and research ==
=== extract from 1989 timbl proposal ===
* extra all specific problems and use-cases mentioned in http://www.w3.org/History/1989/proposal.html
* write them up as their own wiki pages, one per specific problem/use-case
* see if they're solvable with modern [[microformats2]]

== microformats specific ==

Just some nice things, feel free to do any of these.

=== for all microformats ===
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].

=== hCalendar ===
==== Add support to open source calendar projects ====
These are open source projects that could be potentially enhanced to support hCalendar.

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

=== hReview ===
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
* an [[hreview|hReview]] validator.
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.

=== hCalendar/hCard/hReview editor ===
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

=== hAtom ===
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].

=== WordPress patches for microformats ===
* submit patches for WordPress code/templates for microformats improvement
** <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
* Wordpress plugin for microformats, specifically hReview and hCalendar
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
* [http://www.yuiblog.com Yahoo! User Interface Blog]

=== Drupal patches for microformats ===
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal. Currently looking to support hAtom, hCard and hCalendar to start with. Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.

=== Adding Microformats to Existing Pages ===
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

===Glossary===
Add to the [[glossary]].

===hAtom tutorial===
Finish the [[hatom-tutorial]].

=== wiki gardening ===
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
* Use [[templates]] for boilerplate text and repeated lists of links
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.

====Spelling====
Per [[how-to-play]]: for English-language pages only: Find British spellings of common words and replace them with the US spellings per [[en-US]]. Mark such edits as "minor" with the comment: <nowiki>[[en-US]]</nowiki>. Please be careful to use and maintain proper native spelling of proper nouns (see [[how-to-play]] for details).

Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.

{| border="1"
|+
! [[en-GB]] !! [[en-US]]
|-
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
|-
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
|-
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
|-
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
|-
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
|-
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
|-
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
|-
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
|-
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
|-
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
|-
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
|-
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
|-
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
|-
|}

[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]

== Admins ==
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.

Admins check this "inbox" periodically and process and move items to [[admin-to-do]].

Please check [[admin-to-do]] to see if there is already an ongoing task item relating to your request. Otherwise add the item below.

=== Website Improvements ===
* [http://robot-independente.tumblr.com/#microformats@irc.freenode.net Tony Cox Rochester]
* [http://sir-clean-a-lot.com/#microformats@irc.freenode.net Bowie Cleaners]

=== Wiki improvements ===

* Something broken with the new MediaWiki microformats templates for date modified on delta/version pages? see: https://twitter.com/CogitoStudios/status/32227146466332672

* Want: Right-to-left (RTL) support in the theme for better translating to RTL languages. Per [https://www.facebook.com/permalink.php?story_fbid=10150109554926465&id=214611 this comment on the microformats page on Facebook 2011-02-13]: <blockquote><cite>Sina Cheraghi</cite> > Microformats <br> "I want to contribute in Microformats wiki by translating it into Persian. But lack of RTL (right-to-left) languages (Persian, Arabic, Hebrew and ...) theme causes some problems for me and other contributors."</blockquote>

* New link styles for links to mailing list archive
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Add proper styling to phrase elements
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

== Tantek ==
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].

=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Wiki cleanup/gardening for existing established microformats
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
# New microformat requests
# Document microformats [[history]].
# Other

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** move exploratory discussions which are failing to follow the process to a separate page from that
** repair damage done to the wiki
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
**** [[hcalendar-examples-in-wild]]
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
****** http://adactio.com/extras/schedules/barcampbrighton3/
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
**** [[to-do]]

=== help publishers ===
==== solve problems blocking publishers ====
* [[value-class-pattern]]
** <del>drafted</del>
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
** <del>put out call for review, implementation,</del> and value-title tests

===== minor update current specifications =====
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** close remaining [[hcard-issues-resolved|hCard resolved issues]] by writing necessary [[hcard-faq|FAQ]] entries, updating [[hCard]], and adding to [[hcard-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
** incorporate [[hcard-feedback]]
** continue updating the spec per the inline comment about property references
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcard-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
** Update [[hcard-brainstorming]] on element specific parsing rules
** Update X2V, hKit, Operator accordingly
** Write test cases accordingly
** Update [[hcard-parsing]] accordingly
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
** close remaining [[hcalendar-issues-resolved|hCalendar resolved issues]] by writing necessary [[hcalendar-faq|FAQ]] entries, updating [[hCalendar]], and adding to [[hcalendar-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
** incorporate [[hcalendar-feedback]]
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list. Separate common properties up front.
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcalendar-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcalendar-examples]]
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
* draft hReview 0.4
* resolve hAtom issues
* co-edit hAtom per permission from David Janes
* draft [[hAtom]] 0.2
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
* add sections for comments/opinion from community as well as issues subsection
* solicit feedback
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.

==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

Brainstorm updates to the [[pocket-cheat-sheet]] to better enable [[social-network-portability]], or perhaps design a new '''social network portability pocket cheat sheet''' that specifically documents:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
* update cheatsheet to include new [[value-class-pattern]] uses
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

==== advocacy for obvious sites ====
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
*** open data > open source
*** "open information" vs "open source"
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
*** if the data is open you can always export it and consume it in any number of open source systems
*** that's why open data is MUCH more important than open source
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
*** if the data was open, anyone could rebuild an accessible version
*** faqs / misconceptions:
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard. Rather, if you think something is hard, then assume others may know easier methods, and ''ask'' the community how one can do it more easily. parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** look for hCards and parse them

* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.

* Conference Schedule Creator
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

=== iterate on current microformats ===
==== in general ====
===== plain language intros =====
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
* followed by links to more plain-language resources, e.g. *-intro pages.
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
* As well as a syntactic example, examples of use would be useful.
* when I might want to use XOXO.
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
These suggestions could be incorporated into the other specs as well.
===== exploratory discussions =====
* update [[exploratory-discussions]] with critical microformats as "active"
===== CSS enhancements for =====
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
* brainstorm additional possibilities for better presentation of content using existing microformats.
===== update affiliations =====
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
===== profile URLs =====
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-profile]] '''next-actions''':
** update property definitions with more detail using semantics from [[RFC2426]]
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* update [[hcalendar-examples]]
** add examples like [[hcard-examples]]
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
*** rrule
*** duration
*** ... etc.
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* have folks verify [[hcalendar-profile]]. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hreview|hReview]] ====
'''Next-actions''':
* reconcile [[hreview-profile|hReview 0.4 XMDP profile]] with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.

==== [[rel-tag]] ====
'''Next-actions''':
* send [[rel-tag]] XMDP profile ([[rel-tag-profile]]) to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== [[rel-me]] ====
'''Next-actions''':
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
** and put redirects in place, notes about contribution
* update rel-me examples and document with examples the rel-me implict subdir rule

==== [[hatom|hAtom]] ====
'''Next-actions''':

==== summary Examples in the Wild page ====
* need to create a summary / overall [[examples-in-the-wild]] page
** parallel the summary/overall [[implementations]] page.
** use newly reorganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

=== wiki cleanup ===
==== for all microformat specs ====
'''Next-actions''':
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
'''Goal''': greater approachability/readability of microformats specs by a broader audience.

Reference:
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.
* [[hreview|hReview]] has some similar improvements, but different.
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview

'''Next-actions''':
# contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|hResume]] is an improvement, and if it could be better. Document reasoning/requirements for intro/header and other sections.
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
# Write up methodology behind the section organization and note editors lessons learned into an [[editors-guide]] page (what other variants were done before, in which specs, and note problems/complaints with other variants).

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

'''Next-actions''':
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].

==== reorg Examples in the Wild sections ====
Work with community to:
* include more *key* details per example, e.g. precise or estimates of counts for services
* collate/sort examples in the wild by
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
** individiual companies/organizations contact info pages
** individual people's contact info pages
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.

=== site usability ===
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
** ideally use the from address of the author of the blog post
** maybe photomatt knows how to do this.

=== introduction / community ===
* microformats-discuss *
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.

==== posh improvement ====
* Create a page to answer the question "[[how-should-i-markup]]"
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.

==== principles and process ====
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general
* resolve [[process-issues]]

==== profiles ====
* update [[XMDP]] with new required features:
** ability for one profile to include/import another (rel="import" ?)
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
*** add rel="profile" to the [[xmdp-profile]].
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

==== community mark ====
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?

==== document issue resolutions ====
* Prefixing has already been considered and rejected for microformats in general. Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.

=== emerging microformats ===
* [[directions]]
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]
'''Next-actions''' for each emerging microformat (one at a time)
* review all microformats-email on the new microformat
* determine where new microformats is "stuck" in the process
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary

=== new microformat requests ===
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].

=== document microformats history ===
Document microformats [[history]], including:
* dates and origins of microformats, names, terms
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]

=== other ===
* Add XPath equivalents where appropriate in [[hcard-parsing]]

==Ryan==
=== wiki cleanup ===
* <s>possibly move dead proposals off of homepage?</s>

=== hCalendar/hCard/hReview creator improvements ===
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3

=== other ===
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml

=== rel-payment ===
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]

=== hcalendar ===
* make sure we explicitly disallow 'vjournal'

== Dimitri Glazkov ==

* Figure out REST/Microformats thing
* Work on result set idea
* Implement h-creators using Web Forms 2.0

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
* <strike>Read GTD (at least the first two chapters)</strike>.

=== Campaigns ===

* <strike>Get Blogger to support hAtom and hCard</strike>
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get <strike>Digg to support microformats</strike> (still need XFN).

=== Wishlist ===

* Microformat for "buyable items" (see [[listing-examples]] and related documents)
* Location MF -- right click "map this" (see [[geo]] and [[adr]])
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/ Flocktails])
* Better hCal support -- support many views of same hCal data on one page using XSLT
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
* invoicing microformat
* better microformats wiki theme
* Define flow for OpenID + XFN + hcard (see [http://diso-project.org DiSo Project])

Hey Chris.
Congrats on Microsyntax
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?

== Robert Bachmann ==
[[User:RobertBachmann|Robert Bachmann]]

=== XSLTs ===
<ul>
<li><strong>Test scripts</strong>
<ul>
<li>Do some refactoring, split Perl code into smaller modules</li>
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
<li>Provide some documentation for using the test scripts</li>
</ul>
</li>
<li><strong>hAtom2Atom</strong>
<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
</li>
</ul>

== Brian Suda ==
=== Citation Microformats ===
* Add all my notes to the Wiki
* Start the process of naming the properties using existing names

=== X2V ===
Make changes and update site (almost stable)
Get ATTENDEE and other strange attributes working
==== WARNINGS and ERROR ====
work on the warnings and error output for the pre-check in X2V

=== FAQ ===
* clean-up the MF FAQs
* clean-up FAQs from the major microformats
* pull Questions from the mailing list and document them to the FAQs and example

=== Microformats History ===
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== Ernest Prabhakar ==
=== Wiki-Thon Proposal ===
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# Tackle larger projects (~1-2 hours) than people usually have time for
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

* Clean up this todo list (meta!)
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
*** Ping anyone with specific tasks / nag
* Proposal for page simplifications - notes, to expand to tasks later:
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
** Process updates to blog?
** Activity overview updates on main site somewhere?
*** Code and Tools page on site: Currently it's mostly only tools. Need to add a list of actual specifications on the wiki.
** In general: less clutter, more structure, more focus.

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki
* documentation of semantic authoring techniques
* researching the social problems relating to authorship and publishing on the web
* development of new microformats in response to failing to meet the needs of the second with the first.

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)

=== Creators ===
_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model. This is a nice feature, so maybe I should be branching instead.
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
** how to author semantic html
** choosing class names
** using HTML's general extension mechanisms
** advocating use
** collaborating/reusing HTML
** debugging HTML: use pastebin, separate out the relevant bits.
** getting help from the community
** applying Microformats.

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

* Microformat
** Specification
** Tutorial
** Examples
** Use cases
** Reference
** Discussion
** Brainstorming (might be combined w/Discussion)
** Implementations
** Related Pages
** Further Reading
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)

These pages would be located respectively at

* http://microformats.org/wiki/hcard/
** http://microformats.org/wiki/hcard/Specification
** http://microformats.org/wiki/hcard/Tutorial
** http://microformats.org/wiki/hcard/Examples
** http://microformats.org/wiki/hcard/Use_cases
** http://microformats.org/wiki/hcard/Reference
** http://microformats.org/wiki/hcard/Discussion
** http://microformats.org/wiki/hcard/Brainstorming
** http://microformats.org/wiki/hcard/Implementations
** http://microformats.org/wiki/hcard/Related_Pages
** http://microformats.org/wiki/hcard/Further_Reading
** http://microformats.org/wiki/hcard/All

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

=== hAtom2Atom ===
<ul>
<li>Support for other XSLT engines:
* hAtom2Atom written using XSL 2.0
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

=== Microformats Proposals ===

* rel="disclaimer":
** Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.
* rel="external":
** Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
* Implement Tail scripts for adding things into Midgard

== Justin Thorp ==
* Start researching examples for a To-do microformat

== [[User:MarkLentczner|Mark Lentczner]] ==

* Get Second Life's event web pages to have proper event microformats data
** Add [[hcard|hCard]] to profile pages
** Add [[hcalendar|hCalendar]] to events listings
* Start pinging pingerati.net/ping/$url when pages are updated
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].

== [[User:DerrickPallas|Derrick Pallas]] ==
=== microformat proposal: dependancy ===
* looking for examples of directed graphs on the web
* applications in
** software engineering
*** automatically build library dependency trees
*** distribute security alerts to people that link to your code
** any directed, acyclic graph
*** getting dressed in the morning
*** cooking
* orthogonal to xfn
** people don't have versions
*** libfoo requires libbar-2.0 or later
** people don't have optional relationships
*** ex: at build time, compile in SSL support if present
** people don't have exclusive-or relationships
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick

== [[User:PaulDowney|Paul Downey]] ==
* building a generic Javascript parser
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

== [[User:BenWard | Ben Ward]] ==

=== Recurring ===

* Delete Wiki Spam

=== Currently ===

* Gardening/updating key wiki pages.
** [[how-to-play]]
** XHTML Design Principals
* embed brainstorming
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.

=== Next Actions ===

* Conclude new hCalendar proposals from Yahoo TV Listings experience
* Resume work on hListing microformat
* Re-org the Microformats.org front-page content
** Work with [[User:Phae]] on refreshing the microformats frontpage content
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
** Build new wiki edits module for the blog
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
* Build a microformats activity stream
** Replace front page blog with activity flow
*** Wiki Edits/New Pages
*** New Mailing List Threads
*** Interesting µf links
*** Blog posts
*** Upcoming events/event reminders
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)

== [[User:Spiritquest|Ketan Majmudar]] ==
=== Activites ===
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
** Provide real world examples and apply this to the proposed specifications
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
* see where I can help the community
* look at using x2v or writing php parser classes for hcard -> vcard
* open source hCard class (php) used to format db fields

irc

2017-01-14T07:02:25Z

Bravenewgame: /* Web */

<entry-title>#microformats on freenode</entry-title>
{{TOC-right}}
;shortURL
:http://ufs.cc/w/irc

== Quick Start ==
You may use a IRC client application such as [http://colloquy.info/ Colloquy] (Mac or iOS) or [https://market.android.com/details?id=org.yaaic&feature=search_result Yaaic on Android] to join:
* irc://irc.freenode.net/microformats

Alternatively you may use a browser to quickly join and chat:
* http://webchat.freenode.net/?channels=microformats&nick=uf-wiki-visitor
* Firefox users: install [https://addons.mozilla.org/en-US/firefox/addon/chatzilla/ Chatzilla] IRC plugin.


The microformats IRC channel is hosted on the freenode.net server. See [[irc#Joining_a_server_and_channel|Joining a server and channel]] help for further information and use of client applications which provide additional services (authenticated nicknames, logging, etc.).

== Logs ==
Recent logs of the Freenode #microformats IRC channel can be found at:
* https://chat.indieweb.org/microformats/
* [http://logbot.glob.com.au/?c=freenode%23microformats&s=today logbot.glob.com.au microformats IRC Logs]

Older logs can be found at the following locations for the following periods:
* [https://chat.indieweb.org/microformats/2011-02-12 2011-02-12]–[https://chat.indieweb.org/microformats current] at https://chat.indieweb.org/microformats
* [http://logbot.glob.com.au/?c=freenode%23microformats&s=20090220&e=20090220 2009-02-20] - [http://logbot.glob.com.au/?c=freenode%23microformats&s=today current] at [http://logbot.glob.com.au/?c=freenode%23microformats&s=today logbot.glob.com.au microformats IRC Logs]
* [http://krijnhoetmer.nl/irc-logs/microformats/20131028 2013-10-28] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/ current] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
----
* [http://krijnhoetmer.nl/irc-logs/microformats/20130811 2013-08-11] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/20130917 2013-09-17] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
* [http://krijnhoetmer.nl/irc-logs/microformats/20120726 2012-10-09] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/20130807 2013-08-07] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
* [http://krijnhoetmer.nl/irc-logs/microformats/20120726 2012-07-26] - [http://krijnhoetmer.nl/irc-logs/microformats/20120916 2012-09-16] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
* [http://krijnhoetmer.nl/irc-logs/microformats/20090220 2009-02-20] - [http://krijnhoetmer.nl/irc-logs/microformats/20120621 2012-06-21] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
* [http://rbach.priv.at/Microformats/IRC/2011-04-05 2011-04-05] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]
* [http://rbach.priv.at/Microformats/IRC/2011-02-24 2011-02-24] - [http://rbach.priv.at/Microformats/IRC/2011-03-03 2011-03-03] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]
* [http://rbach.priv.at/Microformats/IRC/2009-08-28 2009-08-28] - [http://rbach.priv.at/Microformats/IRC/2010-09-27 2010-09-27] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]
* [http://rbach.priv.at/Microformats/IRC/2009-03-26 2009-03-26] - [http://rbach.priv.at/Microformats/IRC/2009-06-29 2009-06-29] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]
* 2009-02-09 - 2009-02-20 '''missing'''. if anyone has any logs for this time period, please upload them and add links here.
* [http://rbach.priv.at/Microformats/IRC/2009-01-14 2009-01-14] - [http://rbach.priv.at/Microformats/IRC/2009-02-09 2009-02-09] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]
* [http://krijnhoetmer.nl/irc-logs/microformats/20080825 2008-08-25] - [http://krijnhoetmer.nl/irc-logs/microformats/20090114 2009-01-14] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]
* 2008-08-16 - 2008-08-24 '''missing'''. if anyone has any logs for this time period, please upload them and add links here.
* [http://rbach.priv.at/Microformats/IRC/2005-11-16 2005-11-16] - [http://rbach.priv.at/Microformats/IRC/2008-08-16 2008-08-16] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]

Until sometime on 2007-07-16, there was an [http://microformat.makedatamakesense.com/log_feed/ atom feed] provided for the [http://rbach.priv.at/Microformats-IRC/ rbach IRC Logs].

=== logs status ===
* [http://logbot.glob.com.au/?c=freenode%23microformats logbot.glob.com.au microformats IRC Logs] are current and live
* [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs] appears to have stopped logging as of 2016-01.
** I emailed and heard back from Krijn on 2016-03-19 "Yeah, sorry, I know, server resources are very low for that (old) machine. I think it's sort of EOL.." [http://logs.glob.uno/?c=freenode%23microformats&s=21+Mar+2016&e=21+Mar+2016&h=Krijn#c86411] -- gRegor
* [http://rbach.priv.at/Microformats-IRC/ rbach IRC Logs] appear to have stopped logging as of 2009-06-29.

== People on IRC ==
See our [[irc-people|list of IRC regulars]] and their normal timezones.

Our channel has regular admins, who are also mailing list and wiki admins. If you want to get their attention, just say "adminhelp".

==Bots on IRC==
The IRC channel uses these bots:

* [[mfbot]] - logs all edits to this wiki. (Contact: [[User:RyanKing|Ryan King]])
* [[mflogbot]] - logs the irc channel itself to archives on the web. (Contact: [[User:RobertBachmann|Robert Bachmann]])
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

=== Greeting Bot ===
To display a brief description of who you are each time you join the channel, you can use “JiBot” to create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.example.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

== Getting started with IRC ==
'''Please note:''' These directions relate specifically to the services that [http://freenode.net/ Freenode] offers. Other IRC servers may differ with the services they offer and how to operate them.

===Joining a server and channel===
Most clients will offer you a connection dialogue showing the required fields for connection. The details to connect to the server are:

*Server: <code>irc.freenode.net</code>
*Port: <code>6667</code> (usually default)

You should also fill in any fields to set your alias, real name and email address. If available, save these settings for later to speed up connecting in future.

More on setting a password protected alias can be [[irc#Creating_a_registered_nickname|read here]].

Once connected, you will most likely be presented with the "MOTD" (message of the day). For the first visit, it is advisable to read this to find out about the server's policies and other important pieces of news and help, otherwise it can be ignored and you can either [[irc#Creating_a_registered_nickname|authenticate your alias]] or join a channel.

Your client may display to you a listing of all available channels. Locate <code>#microformats</code> and select to join, or type <code>'''/join #microformats'''</code> into the command line available to you in your client (where you've just been shown your connection).

Assuming you've connected correctly, you should now find youself in the microformats channel!

More detailed, but general, advice can be [http://www.irchelp.org/irchelp/irctutorial.html#intro read here].

===Creating a registered nickname===
Registration means that a password becomes associated with your alias/nickname/sign-in name and from the point of registration authorisation is required to communicate using that alias.

Registration of a nickname is required for some channels, and should be done to protect your identity.

To register with [http://freenode.net Freenode], you must communicate with their service known as NickServ. The two basic command you will need to get started are:

For registration: <code>/msg nickserv register ''password''</code>

For authentication (login): <code>/msg nickserv identify ''password''</code>

With <code>''password''</code> being a value of your choice. You can also associate an email address with your nickname, which is optional, but advisable, should you want to request a password retrieval:

To add your email address: <code>/msg nickserv set email ''email''</code>

Where <code>''email''</code> is your email address.

Your client may offer you an option to set your alias and password, so that you will not have to manually enter this information on each join. Refer to your client's help files for more on this.

These commands can be typed directly into the server window upon join, or whilst in a channel, just as you would normally send a message.

More detailed user registration command information can be found in [http://freenode.net/faq.shtml#userregistration Freenode's FAQ]

===Communicating===
Sending a message to a channel may be as simple as joining the channel and typing into the window, just as you would with an Instant Messenger. You can refer to your client's help files for quicker/alternative methods of doing the following. For all clients the following commands are available (the parts in bold must be used, but are not seen by others):

'''Sending a message to the entire channel you are currently in:'''

Command: <kbd>'''/msg''' Hello world!</kbd>

Result: <samp><Bill> Hello world!</samp>

'''Sending an action/emotive/3rd person statement:'''

Command: <kbd>'''/me''' dances a code jig</kbd>

Result: <samp>Bill dances a code jig</samp>

'''Sending a message to one person only (private chat):'''

Command: <kbd>'''/msg Bob''' Hi, would you like to code jig?</kbd>

Result (for Bob only): <samp><Bill> Hi, would you like to code jig?</samp>

==Clients==
The following clients are recommended by #microformats participants:

=== Web ===
* [http://leafychat.com/#microformats@irc.freenode.net Leafy Chat]

* [http://www.wholehousecc.com/#microformats@irc.freenode.net Carpet Cleaning]

===Windows===
* [http://www.mirc.com/ mIRC] — Popular Windows client. Trial version only.
* [http://xchat.org/ X-Chat] — Popular cross-platform client. [http://www.silverex.org/download/ Free Windows version] available.
* [http://www.adiirc.com/ AdiIRC] — Simple C# based IRC client.
* [http://www.miranda-im.org/ Miranda] — Lightweight, muti-protocol instant messenger.

=== Mac ===
* [http://colloquy.info Colloquy] — open source, free
* [http://homepage.mac.com/philrobin/conversation/ Conversation]
* [http://sourceforge.net/projects/fire Fire] — open source, free
* [http://www.conceitedsoftware.com/products/linkinus Linkinus]
* [http://www.chipersoft.com/minerva/ Minerva]
* [http://www.snak.com/ Snak]
* [http://xchataqua.sourceforge.net/twiki/bin/view/Main/WebHome X-Chat Aqua]
** now has [http://www.portableapps.org PortableApps] version — [http://www.macupdate.com/info.php/id/21685/portable-x-chat-aqua MacUpdate link]
* [http://www.aquaticx.com/ Xirc]

===Cross-platform===
* [https://addons.mozilla.org/en-US/firefox/addon/chatzilla/ Chatzilla] — Cross-platform IRC extension for Firefox
* [http://pidgin.im/ Pidgin] — Popular open-source multi-protocol windows client, using libpurple
* [http://irssi.org/ Irssi] — Unix client, often run from a shell, sometimes [http://f0rked.com/articles/irssi in conjunction with 'screen'].
* [http://jirc.hick.org/jirc/ jIRCii]

== meetups ==
The idea of having IRC meetups (a set time for a meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups.

==IRC and microformats==
=== hCard ===
<div class="discussion">
* ''How do we maintain info about ircing in our hCards (nick, network, fav-channels?)?''
** presumably this would be done with a URL. - [[User:Tantek|Tantek]] 18:42, 30 July 2009 (UTC)
</div>

== Related discussions ==
* [[chat]] [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]

==See also==
*[[irc-meetups]]
*[[discuss|Other discussion fora]]