Microformats Wiki - User contributions [en]

feed-examples

2012-11-06T00:09:12Z

Singpolyma: /* real world examples */ add ossguy.com category example

{{stub}}

<entry-title>feed examples</entry-title>

Part of the [[feed]] microformat development effort per the [[process]].

This page is for documenting [[examples]] of real world web pages with one or more feeds that would benefit from additional explicit structural markup.

== The Problem ==
If a site has items from more than one feed, a [[feed-reader]] has no idea how to aggregate items from only one feed. Feed readers need a way to discover and choose which feed on a page they are aggregating.

== Use Cases ==
=== Read one feed of many ===
It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries in the case where there are multiple feeds on one page, and one wanted to read the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

=== Search and indexing ===
Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).

== previous effort ==
* [[blog-description-examples]] may have examples that could be incorporated here

== real world examples ==
''Links to public web pages, either popular or insightful'' that provide real world examples of the type of publishing that can be improved with a feed microformat.

Flat list of examples:
* http://ma.tt (blog feed + tweets feed on the same page)
* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)
* http://ossguy.com/?cat=8 (blog filtered by category + tweets feed on the same page)

Grouped examples:

=== hAtom ===
Most examples these days use hAtom already and thus check here for specific modern examples:
* [[hatom-examples-in-wild]]

== analysis of publishing practices ==
* ''Summary of common patterns discovered from above examples''
* ''Other attempts to solve The Problem'' (other actual [[formats]] belong in the [[feed-formats]] page)

== see also ==
* [[feed]]
* [[hAtom]]
* [[microformats2#h-entry|h-entry]]

== next steps ==
* [[feed-formats]]
* [[feed-brainstorming]]

media-info-examples

2011-08-22T23:05:56Z

Singpolyma: /* Service publishing of photos */ add yfrog example

= Media Info Examples =

{{TOC-right}}

== Contributors ==

* [[User:RodBegbie | RodBegbie]]
* [http://tantek.com/log/ Tantek Çelik]
* [http://napsterization.org/stories/ Mary Hodder]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:MikeJohnson | Mike Johnson]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:WebOrganics| Martin McEvoy]]

== Introduction ==

Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.

== Emphasis on Practical, Simple, and Minimal ==

Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.

Thus for now, this document is deliberately restricted to examples that are:
* ''Actual'' examples in practice on the Web '''with URLs''' to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.

Any examples added which do not conform to these requirements will be deleted.

Any generic analysis will also be deleted. Analysis before examples is premature. Once there are sufficient media-info-examples, and hopefully a simple/clean listing of [[media-info-formats]], we'll hopefully start a [[media-info-brainstorming]] page to do aggregate analysis of the examples.

===Note on proposals===

Because the hMedia became a task so big that it seems impossible to make it "simple and minimal" discussions started on splitting them by media type.

see: [[audio-info-brainstorming]]

== Real World Examples ==

=== Overall Notes About Examples ===
These examples are organized into a short list of top level media categories, in the hopes that it will be easier to determine if there are media specific publishing behaviors, in addition to common behaviors across multiple types of media. Some may be subcategorized and distinguished by whether it was published by an individual publisher or a service:
* [[media-info-examples#Audio|Audio]] (Speech, Music)
* [[media-info-examples#Video|Video]]
* [[media-info-examples#Photos|Photos]]

The numbers after some of the examples' descriptions are based on numbers found pulling in media records at Dabble. Others may have higher numbers and would be encouraged to restate them if that's true.

=== Audio ===

==== Speech ====
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing. Quotes of audio files are beginning to appear, and publishers are putting up files with links to other audio files they've quoted from. Most audio appears to often have the same base elements as video and photos, with the exception of quotes.

===== Individual Publishing of Speech =====

* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]
** Appears to be composed of:
*** title/summary of the recording
*** clickable hyperlink to the recording (MP3)
*** comments
** Contextual:
*** (primary) speaker is indicated in nearby text

* [http://www.thechrispirilloshow.com/help/20060119_chuck_cummins_on_windows_vista_interface_design.phtml Chris Pirillo podcast]
** This example has a Title, Html URL, media URL(s), description or summary, categories/tags underneath what is viewable, and date. +10k

* [http://yukelzon.blogspot.com/2006/01/podcasts.html Reflog's Random Thoughts podcast]
** This example has a Title, Html URL, description or summary, creator, tags and publish time and date. NOTE, record also contains an [http://images.apple.com/r/ipodstore/ipodviews/0.jpg image], comments +10k records.

* [http://www.evilgeniuschronicles.org/wordpress/2006/01/12/egc-clambake-for-january-12-2006/ Evil Genius Chronicles podcast]
** This example has a Title, Html URL, description or summary, quotes URLs and descriptions, licence, creator, comments, tags and publish time and date. +10k records.

* [http://www(dot)bizbyjake.com/2006/01/how-are-you-doing.html media published from a blog, Jake Steinfeld's Audio Blog] NOTE: this record had trouble because mediawiki blocks any DOTbiz domains and so while this domain coincidentally has a DOTbizbyjake.com name that is not a TLD, it was still blocked in the loading of the page with this example. So please adjust the URL manually and then visit the site.
** This example has a Title, Html URL, media URL, creator and publish time and date. +10k records.

* [http://podcast.rubyonrails.org/ Ruby on rails Podcast]
** Feed, title, published, description, author, contributor, download, format

* [http://www.cnet.com/8300-11455_1-10.html Buzz out loud]
** Feed, title, description, published, episode, download, author

===== Analysis of Individual Publishing of Speech Sites =====

7 examples, 6 available

* post-title 100%
* audio-title 100%
* download 100%
* author 100%
* contributor 100%
* description 100%
* published 83.33%
* feed 66.66%
* category 50%
* comments 50%
* format 33.33%
* episode 16.66%
* photo 16.66%

==== Music ====

===== Individual Publishing of Music =====

* [http://www.bradsucks.net/music/ Brad Sucks » music]
** Has album title, song title, separate link to more info, inline flash player, and play link (to mp3)

* [http://www.scottandrew.com/music/ Scott Andrew - lo-fi acoustic pop superhero! > music >]
** Has album title, song title, licensing info, remixing policy, multiple formats such as streaming link (to m3u), play links (to mp3, OGG, FLAC)
** Record contains album cover image.

* [http://www.hearingdouble.co.uk/dumb/index2.html Portishead Remixed]
** Whole page is for one album (a mash-up remix of a Portishead album). Has Album Track Number and Title (linked to mp3) and Remixer's name. Also a link to multiple formats such as the BitTorrent download of the whole album.
** Record contains album cover images.

* More examples here please....

===== Analysis of Individual Publishing of Music Sites =====

3 examples, 2 available

* post-title: 100%
* audio-title: 100%
* download: 100%
* contributor: 100%
* published: 100%
* duration: 100%
* photo: 100%
* payment: 100%
* album title: 100%
* category: 50%

===== Music Podcasting sites=====

* [http://www.coverville.com/archives/2008/10/coverville_517.html Coverville]
** description, title, published, contributor, position, download, comments

* [http://magnatune.com/podcasts/details/magnatune_middle-eastern_podcast_2006_12_14 Magnatune]
** Feed, title, section, genre, length, published, contributor, interval, download

* [http://www.mutantpop.net/radioclash/archives/2007/03/24/rc-113/ Mutantpop]
** Feed, description, title, photo, format, duration, size, published, contributor, download, category, comments

* [http://www.btpodshow.com/shows/?sId=21&mId=5332173 btpodshow]
** Feed, description, title, episode , category, published, contributor, position, comments

* [http://indiecastwp.podshow.com/?p=76 Indiecast]
** Feed, description, title, section, format, category, length, published, contributor, episode

* [http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/ Accidenthash]
** Feed, description, title, category, length, published, contributor, episode, download, comments

* [http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/ Strong words inc]
** Feed, description, title, duration, published, episode, download, author, comments

* [http://threehive.libsyn.com/index.php?post_id=111596 Three hive]
** Feed, description, title, photo, format, category, published, contributor[s] author, episode, download, comments

* [http://music.for-robots.com/archives/002495.html For Robots]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.fluxblog.org/2008/10/when-the-work-is-done fluxblog]
** Feed, title, published, description, contributor, download, comments

* [http://www.3hive.com/2008/10/photons.php 3hive]
** Feed, title, published, photo, description, author, contributor, download[s] , format, category, comments

* [http://www.saidthegramophone.com/archives/complete_coverage.php said the gramophone]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.archasung.com/playlist/playlist-cloudy-days Archasung]
** Feed, title, published, photo, description, contributor, download[s], comments

* [http://betterpropaganda.com/content.aspx?id=840 Better Propaganda]
** Feed, title, photo, description, contributor, download[s], episode

* [http://freakytrigger.co.uk/ft/2008/10/a-bite-of-stars-a-slug-of-time-and-thou-episode-14/ Freaky Trigger]
** Feed, title, published, description, author, contributor, download, episode, comments

* [http://www.catbirdseat.org/archives/001093.php Cat Bird Seat]
** Feed, title, published, description, contributor, download[s], format

* [http://the-big-ticket.blogspot.com/2007/09/all-in-game-indeed.html The Big Ticket]
** Feed, title, published, description, author, contributor, download, format, category, comments

* [http://sixeyes.blogspot.com/2008/10/sixeyes-saturday-mix-oct-4th.html Six Eyes]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.spoiltvictorianchild.co.uk/2007/11/no-vice-my-arse.html Spoilt Victorian Child]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.scissorkick.com/2008/09/midnight-lab-band/ Scissorkick]
** Feed, title, published, photo, description, author, contributor, download, format, category, comments

* [http://loki23.blogspot.com/2008/09/flower-electronics.html loki23]
** Feed, title, published, photo, description, author, contributor, download[s], format, category, comments

* [http://www.sweetthunder.org/tapes/weekonehundredandsix.html sweetthunder]
** Feed, title, published, photo, description, contributor, download, duration, comments

* [http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html Arjan writes]
** Feed, title, published, photo, description, contributor, download, duration, format, comments

===== Analysis of Podcasting Sites =====

23 examples

* feed 100%
* post-title 100%
* audio-title 100%
* contributor 95.65%
* description 95.65%
* download 95.65%
* published 95.65%
* comments 78.26%
* photo 56.52%
* author 52.17%
* category 39.13%
* format(eg: mp3) 39.13%
* episode(number) 30.43%
* duration 13.04%

properties occurring less than 10%

* interval

===== Service Publishing of Music =====

* [http://audiofind.ru/ AudioFind]
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Album Example]
*** Information displayed: artist (link), title, genre (link), style (link), release date, label, summary, web-based purchase (link), price, artist rating, album rating.
*** Record contains cover image
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Song Example]
*** Information displayed: track number, title, length, rating, price, sample (link), web-based purchase (link)
*** Record contains cover image

* [http://bigpondmusic.com Telstra BigPond]
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Album Example]
*** Information displayed: artist (link), title, genre, release date, label, summary, web-based purchase (link), subscriber price, non-subscriber price, cover image
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Song Example]
*** Information displayed: track number, title, artist, album, price, add to pop-list (link), sample (link), web-based purchase (link)

* [http://www.bitmunk.com/ Bitmunk]
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068744 Album Example]
*** Information displayed: artist, album title, publisher, release date, genre (link), summary, long description, payees, total price, sample (link), tracks, web-based purchase (link), p2p-based purchase (link)
*** Record contains cover image
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068746 Song Example]
*** Information displayed: artist, song title, composer, publisher, release date, genres, album, payees, total price, web-based purchase (link), p2p-based purchase (link)

* [http://downloadpunk.com Download Punk]
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Album Example]
*** Information displayed: title, artist (link), label (link), physical-based purchase (link), web-based purchase (link)
*** Record contains cover image
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Song Example]
*** Information displayed: title, sample (link), price, web-based purchase (link)

* [http://www.fye.com FYE]
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Album Example]
*** Information displayed: title, artist (link), format, release date, label (link), UPC, product id, genre, styles, regular price, store price, savings, physical-based purchase (link), tracks, description, reviews, production credits
*** Record contains cover image
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Song Example]
*** Information displayed: track number, title, artist

* [http://imusic.libero.it/ iMusic]
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Album Example]
*** Information displayed: title, artist (link), genre, release date, publisher, number of tracks, length, tracks, web-based purchase (link)
*** Record contains cover image
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Song Example]
*** Information displayed: track number, length, sample (link), release date, price, web-based purchase (link)

* [http://musicdownload.aon.at/v7/ AON Music ]
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Album Example]
*** Information displayed: artist (link), album, price, format, bitrate, label, genre, number of tracks, sample (link), add bookmark (link), web-based purchase (link), tracks
*** Record contains cover image
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Song Example]
*** Information displayed: track number, title, length, format, price, sample (link), add bookmark (link), web-based purchase (link)

* [http://music.msn.com MSN]
** [http://music.msn.com/album/?album=50538895 Album Example]
*** Information displayed: artist (link), title, release date, label, album rating.
*** Record contains cover image
** Song Example (store wasn't working correctly - no song info found)

* [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/Call?htmltemplate=./index.htm TDC Online]
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Album Example]
*** Information displayed: title, artist (link), length, release date, label, format, web-based purchase (link), price, tracks
*** Record contains cover image
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Song Example]
*** Information displayed: track number, title (link), price, sample (link), web-based purchase (link)

* [http://www.audiolunchbox.com Audio Lunchbox]
** [http://www.audiolunchbox.com/album?a=75751 Album Example]
*** Information displayed: title, artist (link), label (link), genre (link), release date (link), format, bitrate, price, price in credits, web-based purchase (link), add to wishlist (link), sample (flash applet), tracks
*** Record contains cover image
** [http://www.audiolunchbox.com/album?a=75751 Song Example]
*** Information displayed: track number, title, length, price, price in credits, web-based purchase (link), sample (flash applet)

* [http://www.chaosmusic.com/music/ Chaos Music]
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Album Example]
*** Information displayed: title, artist (link), genre, format, release date, price, physical-based purchase (link), add to wishlist (link), tracks, description, availability
*** Record contains cover image
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Song Example]
*** Information displayed: track number, title

* [http://www.connect-europe.com Sony Connect]
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, length, publisher, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Song Example]
*** Information displayed: title, artist, length, price, sample (link), web-based purchase (link)

* [http://www.digirama.co.nz/ Digirama]
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Album Example]
*** Information displayed: title, artist (link), genre (link), label, release date, price, web-based purchase (link), license, related albums, also bought, reviews, tracks
*** Record contains cover image
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Song Example]
*** Information displayed: track number, title, length, sample (link), price, web-based purchase (link)

* [http://www.emusic.com eMusic]
** [http://www-v3.emusic.com/album/10917/10917324.html Album Example]
*** Information displayed: title, artist (link), sample (link), save to playlist (link), genre (link), styles (link), label (link), album rating, reviews, length, tracks, web-based purchase (link)
** [http://www-v3.emusic.com/album/10917/10917324.html Song Example]
*** Information displayed: track number, sample (link), tracks, length, web-based purchase (link)

* [http://www.fnacmusic.com/ FNAC]
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Album Example]
*** Information displayed: title, artist (link), length, add to playlist (link), web-based purchase (link), tracks, price, genre
*** Record contains cover image
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Song Example]
*** Information displayed: sample (link), add to playlist (link), track number, title, length, web-based purchase (link), price

* [http://sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Album Example]
*** Information displayed: title, artist (link), release date, catalog ID, SKU, label, price, price in points, summary, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Song Example]
*** Information displayed: track number, title

* [http://www.misrolas.com/ MisRolas]
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Album Example]
*** Information displayed: title, artist (link), cover image, release date, number of tracks, album rating, price, web-based purchase (link), tracks, reviews
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Song Example]
*** Information displayed: track number, title, sample (link), artist, price, web-based purchase (link), add to wishlist (link)

* [http://www.mtv.com MTV]
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Album Example]
*** Information displayed: title (link), artist (link), release date, label, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Song Example]
*** Information displayed: track number, title, sample (link), video sample (link)

* [http://www.musica360.com/ Musica360]
** [http://musica360.com/store/product_info.php?products_id=232 Album Example]
*** Information displayed: title, artist, price, samples (flash), tracks, web-based purchase (link)
*** Record contains cover image
** [http://musica360.com/store/product_info.php?products_id=232 Song Example]
*** Information displayed: title, artist, price, web-based purchase (link)

* [http://www.musicload.de/ Musicload]
** [http://www.musicload.de/item.ml?releaseid=1884260_2 Album Example]
*** Information displayed: title, artist (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), tracks, comments
** [http://www.musicload.de/item.ml?releaseid=1884261_4 Song Example]
*** Information displayed: title, artist (link), album (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), comments

* [http://www.napster.com Napster]
** [http://www.napster.com/view/album/index.html?id=12376484 Album Example]
*** Information displayed: title, artist (link), release date, track count, label, sample (link), share (link), web-based purchase (link), review, tracks
** [http://www.napster.com/view/album/index.html?id=12376484 Song Example]
*** Information displayed: artist (link), title, track number, album title, length, web-based purchase (link)

* [http://www.partymob.com/edl/browse/?tab=music PartyMob]
** [http://www.partymob.com/edl/details/default.aspx?album=2089814 Album Example]
*** Information displayed: title, artist (link), total length, release date, format, quality, genre, sample (link), price, web-based purchase (link), tracks
** [http://www.partymob.com/edl/details/default.aspx?track=234418 Song Example]
*** Information displayed: title, artist, length, release date, format, quality, genre, sample (link), price, web-based purchase (link), DRM information

* [http://www.peerimpact.com Peer Impact]
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449 Album Example]
*** Information displayed: title, artist (link), price, purchase (application link), format, track count, genre, release date, label, tracks
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449# Song Example]
*** Information displayed: track number, sample (link), title, artist (link), length, price

* [http://www.puretracks.com Pure Tracks]
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Album Example]
*** Information displayed: artist, title, label, total length, disc count, release date, price, web-based purchase (link), DRM information, tracks
*** Record contains cover image
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Song Example] (in popup window)
*** Information displayed: track number, sample (link), title, artist, length, price, web-based purchase (link), label (popup)

* [http://www.reggaecountry.com Reggae Country]
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Album Example]
*** Information displayed: title, artist, release date, label, web-based purchse (link), price, tracks
*** Record contains cover image
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Song Example]
*** Information displayed: sample (link), track number, title, artist, length, web-based purchase (link), price

* [http://www.rhapsody.com Real/Rhapsody]
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Album Example]
*** Information displayed: artist, title, sample (link), label, release date, tracks
*** Record contains cover image
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Song Example]
*** Information displayed: sample (link), track number, title

* [http://www.ruckusnetwork.com Ruckus]
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Album Example]
*** Information displayed: title, artist, release date, genre, label, tracks
*** Record contains cover image
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Song Example]
*** Information displayed: track number, title, length

* [http://www.sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Album Example]
*** Information displayed: title, artist (link), release date, catalog id, label, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Song Example]
*** Information displayed: sample, track number, title

* [http://www.starzik.com/starzik.php Starzik SARL]
** Album Example (hidden url)
*** Information displayed: title, artist (link), genre, label, release date, length, format, bitrate, size, web-based purchase (link), tracks
*** Record contains cover image
** Song Example (hidden url, separate from album example)
*** Information displayed: title, artist (link), album title, genre, label, release date, length, creators, composer, performance artist, format, bitrate, size, web-based purchase (link)

* [http://www.thecellcity.com CellCity]
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=fuzzyquery&CDMdepartment=music&cdmalbum=What's%20The%20Word%20Vol.%201&CDMReturnURL=/music/albumdetails.shtml] Album Example]
*** Information displayed: artist, label, release date, genre, tracks
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=GetProductDetail&CDMProductID=A00001148172&CDMReturnURL=/music/product_detail.shtml Song Example]
*** Information displayed: title, price, web-based purchase (link)

* [http://www.top100.cn top100.cn]
** [http://www.top100.cn/product/specialall/S0027876000.htm Album Example]
*** Information displayed: title, artist (link), release date, sample (link), web-based purchase (link), label (link), genre (link), long description, tracks
** [http://www.top100.cn/product/SongFiles/0027876/M0027876001.htm Song Example]
*** Information displayed: title, artist (link), label (link), genre (link), price, sample (link), web-based purchase (link), description, comments

* [http://www.wippit.com/default.aspx Wippit]
** [http://www.wippit.com/AlbumDet.aspx?StrId=28724&StrCatType=S Album Example]
*** Information displayed: title, artist (link), price, genre (link), format, release date, tracks, web-based purchase (link)
** [http://www.wippit.com/DetailItem.aspx?StrItemID=28724&StrMediaID=724904&StrMediaType=S Song Example]
*** Information displayed: title, artist (link), album (link), genre, format, release date, size, track number, file type, price, web-based purchase link

* [http://www.yanga.ru Yanga]
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, price, web-based purchase (link), rating, tracks
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Song Example]
*** Information displayed: sample, track number, title, length, rating, price, web-based purchase (link)

* [http://www.somesongs.com/ somesongs]
** [Album Example]
*** Information displayed:
** [http://www.somesongs.com/song_info.php?select=4713 Song Example]
*** Information displayed: title, artist (link), rating, sample (link), summary, reviews, release date

* [http://magnatune.com/ Magnatune]
** [http://magnatune.com/artists/albums/ammonite-recon/ Album Example]
*** Information displayed: artist (link), title, cover image, total time, length, release date, artist location (link), web-based purchase (link), physical-based purchase (link), license (link), tracks, summary
** [http://magnatune.com/artists/albums/ammonite-recon/ Song Example]
*** Information displayed: track number, title, length, sample (link)

* [http://www.songfight.org/ SONG FIGHT!]
** [http://www.songfight.org/artistpage.php?key=15-16_puzzle&sortkey=date Album Example]
*** Information displayed: artist (link), cover image, artist location, summary, title,
** [ Song Example]
*** Information displayed: release date, sample (link), title

* [http://www.yes.com/ Yes.com]
** [http://www.yes.com/ Album Example]
*** Information displayed: cover image, artist (link)
*** Record contains cover image
** [http://www.yes.com/ Song Example]
*** Information displayed: cover image, artist (link), rank, web-based purchase (link), played-by radio station

* [http://www.myspace.com MySpace]
** [http://myspace.com/theradioknives Album Example]
*** Information displayed: artist, title, sample (link), cover image, number of plays, tracks
*** Record contains cover image
** [http://myspace.com/theradioknives Song Example]
*** Information displayed: artist, title, number of plays, sample (link), lyrics (link)

* [http://musicbrainz.org MusicBrainz.org]
** [http://musicbrainz.org/release/1138abc1-77f4-4ba9-900d-5cf52baaf4bf.html Album Example]
*** Information displayed: artist (link), title, cover image, tracks, disc id
*** Record contains cover image
** [http://musicbrainz.org/show/track/?trackid=435002 Song Example]
*** Information displayed: title, artist, length, id (link), length, album (link), album id (link), artist, artist id (link), relationship (link), track number

* [http://reactor-core.org/ogg-tagging.html Vorbis Comment Recommendations]
** [http://reactor-core.org/ogg-tagging.html Album Example]
*** Information displayed: artist, publisher, copyright, disc number, isrc, ean/upn, label, label catalog number, license, opus, source media, title, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment
** [http://reactor-core.org/ogg-tagging.html Song Example]
*** Information displayed: album, artist, publisher, copyright, disc number, isrc, ean/upn, label, label number, license, opus, source media, title, track number, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment

* [http://www.apple.com/itunes/podcasts/techspecs.html iTunes RSS extensions]
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Album Example]
*** Information displayed: title, website (link), language, licensing, summary, description, owner, owner e-mail, cover image, genre
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Song Example]
*** Information displayed: title, artist, summary, description, sample (link), length, format, id, release date, tags

* [http://www.discogs.com/ Discogs]
** [http://www.discogs.com/release/705805 Album Example]
*** Information displayed: artist, title, label (link), catalog id, format, country, release date, genre, style, notes, rating, tracks
** [http://www.discogs.com/release/705805 Song Example]
*** Information displayed: artist (link), title, track number

* [http://www.last.fm/ Last.fm]
** [http://www.last.fm/music/Muse/+albums Album Example]
*** Information displayed: cover image, artist, title, release date, label (link), number of tracks, sample (link), physical-based purchase (link), tracks
** [http://www.last.fm/music/Muse/Absolution Song Example]
*** Information displayed: track number, sample (link), title, length, number of plays

===== In-active Music Services =====

* [http://music.yahoo.com/ Yahoo! Music Unlimited]
* [http://www.musicmatch.com Musicmatch] (Merged with Yahoo! Jukebox)
* [http://www.musicnet.com MusicNet] (Service Provider)
* [http://www.musicnow.com AOL Music Now] (Merged with Napster)
* [http://www.nate.com Nate.com] (Appears to be Korean, cannot find album examples)
* [http://www.nextradiosolutions.com Next Radio] (Service Provider)
* [http://www.soundbuzz.com Soundbuzz] (Requires MS IE6)
* [http://www.starbucks.com Starbucks] (Requires Flash 8 player)
* [http://www.streetcds.com/ Street CDs] (parked domain name)
* [http://www.synacor.com/content/index.php Synacor] (Service provider)
* [http://www.telecomitalia.com/ Telecom Italia] (Service provider)
* [http://www.terra.es/pixbox/ Pixbox (Terra) ] (Windows application)
* [http://www.virgin.com/downloads Virgin Digital] (merged with Napster)
* [http://www.virginmega.fr/ Virgin] (Requires Windows)
* [http://www.yeahronimo.nl Yeahronimo (Commodoreworld)]

===== Analysis of Music Sites =====

Shown below is the most popular information listed for music albums. This includes analysis of over 85 online music sites.

'''Album Statistics'''
* 100%: artist
* 92%: title
* 85%: tracks
* 77%: release date
* 67%: label
* 62%: genre
* 62%: web-based purchase
* 59%: cover image
* 49%: price
* 26%: format
* 23%: sample
* 21%: length
* 18%: summary
* 15%: physical-based purchase
* 10%: publisher
* 10%: reviews

Shown below is the most popular information listed for songs. Keep in mind that along with the information listed below - for over 80% of the cases, album information was listed on the same page.

'''Song/Track Statistics'''
* 95%: title
* 69%: track number
* 67%: sample
* 62%: web-based purchase
* 59%: artist
* 54%: price
* 54%: length
* 26%: release date
* 15%: album
* 15%: genre
* 13%: format
* 10%: rating
* 10%: label

=== Video ===
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player. *Many videos include a thumbnail jpg which is clickable to the media object and player.* Some video includes links to those other source videos, photos and audio that have been quoted. Most videos have the same base elements as photos and audio, with the exception of quotes.

==== Individual publishing of video ====

* [http://FreeVlog.org FreeVlog]
** [http://www.freevlog.org/index.php/2007/01/24/new-vlog-moments-in-turkey/ Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments (link)

* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]
** [http://joshkinberg.com/popupmaker/ Video Example]
*** Information displayed: title, download (link), preview image

* [http://ryanedit.blogspot.com/ Ryanne's Video Blog]
** [http://ryanedit.blogspot.com/2006/01/light-water-music-2.html Video Example]
*** Information displayed: title, post date, preview image, download (link), tags, comments (link)

* [http://www.prototypen.com/blog/vjblog/ Artificial Eye]
** [http://www.prototypen.com/blog/vjblog/archives/001240.html Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, website (link), comments

* [http://www.itsjerrytime.com/ It's JerryTime!]
** [http://www.itsjerrytime.com/?p=89 Video Example]
*** Information displayed: title, preview image, video (link), comments, tags

* [http://www.bottomunion.com/blog/ Bottom Union]
** [http://bottomunion.com/blog/?p=403 Video Example]
*** Information displayed: title, preview image, video (link), video (embedded), post date, summary, website (link), comments, tags, feed subscription (link)

* [http://rocketboom.com/vlog/ Rocketboom]
** [http://www.rocketboom.com/stories/rb_07_mar_26 Video Example]
*** Information displayed: title, preview image, download (link), post date, video (embedded), comments (link), tags (link), feed subscription (link)

* [http://www.chesslodge.com/ Chess Lodge]
** [http://www.chesslodge.com/2007/03/chess-video-lesson-2/ Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, video (embedded), website (link), comments (link), tags, feed subscription (link)

* [http://pechesscast.blogspot.com/ PE Chesscast]
** [http://pechesscast.blogspot.com/2007_03_01_archive.html#4209870902184134583 Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, comments (link), tags (link), feed subscription (link), e-mail to friend (link)

* [http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html Steve Garfield]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv media]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv.jpg image]
*** Information displayed: title, preview image, download (link), post date, summary, commennts (link), tags, description, feed subscription, licensing.
*** Quoting / credits: music included.

==== Service publishing of video (there are 350+ so this is a short list) ====

* [http://blip.tv/ blip.tv]
** [http://thedailyreel.blip.tv/file/181901?filename=Thedailyreel-TheDailyReelMarch28629.flv Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, review rating, content rating (link), category, video (embedded), number of comments, comments (link), tags, e-mail forward (link), feed subscription (link)

* [http://youtube.com/ YouTube]
** [http://youtube.com/watch?v=KKTDRqQtPO8 Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link), e-mail to friend (link), save to favorites, add to groups, number of views, number of comments, number of honors, number of links, number of responses, permalink, related

* [http://mefeedia.com/ Mefeedia]
** [http://mefeedia.com/entry/2303506/ Video Example]
*** Information displayed: creator (link), title, preview image, download (link), post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link)

* [http://vimeo.com/ Vimeo]
** [http://vimeo.com/clip:162754 Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments

* [http://DailyMotion.com/ DailyMotion]
** [http://www.dailymotion.com/us/featured/video/x1l9qx_sad-kermit-hurt Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, content rating, category, summary, video (embedded), website (link), comments, tags, add to favorites (link), add to blog (link), e-mail to friend (link), length, filming location, permalink

* [http://www.nbc.com NBC]
** [http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/ Video Example]
*** Information displayed: title, summary, video(embeded), duration, tags, views, rating, comments, permalink(url)

* [http://abc.go.com ABC]
** [http://abc.go.com/primetime/watercooler/index?pn=index Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, season, episode, rating

* [http://video.google.com Google Video]
** [http://video.google.com/videoplay?docid=-5177576155567667810&hl=en Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.videosift.com Video Sift]
** [http://www.videosift.com/video/Idiot-Cop-never-heard-of-the-Constitution Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.footbag.org/gallery/video Footbag]
** [http://www.footbag.org/gallery/show/8830 Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, download(enclosure), size

* [http://www.break.com Break]
** [http://www.break.com/index/powerful-tornado-throws-cars.html Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.collegehumor.com College Humor]
** [http://www.collegehumor.com/video:1886239 Video Example]
*** Information displayed: title, creator, video(embeded), published, rating, tags, comments

* [http://www.ebaumsworld.com Ebaum's World]
** [http://www.ebaumsworld.com/video/watch/1044597/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, tags, views, share(link), comments

* [http://www.holylemon.com/ Holylemon]
** [http://www.holylemon.com/The-Animator--v818.html Video Example]
*** Information displayed: title, description, video(embeded), published, rating, views, share(link), comments

* [http://www.crooksandliars.com/ Crooks and Liars]
** [http://crooksandliars.com/david-neiwert/get-ready-rights-post-election-delig Video Example]
*** Information displayed: title, description, creator, video(embeded), published, tags, share(link), comments

* [http://video.yahoo.com Yahoo Video]
** [http://video.yahoo.com/watch/3786346/10380005 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://www.myspace.com MySpace Videos]
** [http://vids.myspace.com/index.cfm?fuseaction=vids.individual&VideoID=44857402 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://video.aol.com/ AOL Video]
** [http://uncutvideo.aol.com/tags/art-&-animation/adf34e0b55f492d0210491e9c4906362?index=7 Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, views, share(link), comments

* [http://www.heavy.com/ Heavy]
** [http://www.heavy.com/channel/1179 Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.ifilm.com/ iFilm] now [http://www.spike.com/ Spike]
** [http://www.spike.com/video/spider-man-3-trailer/2783985 Video Example]
*** Information displayed: title, description, creator/s, video(embeded), published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.metacafe.com/ Metacafe]
** [http://www.metacafe.com/watch/1932833/universe/ Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments

* [http://www.atomfilms.com/ Atom Films]
** [http://www.atom.com/funny_videos/border_vcast_interview/ Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, tags, views, share(link), comments, contributors

* [http://www.veoh.com/ Veoh]
** [http://www.veoh.com/videos/v16297680ZFN5cMXb Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments, permalink(url)

* [http://grouper.com/ Grouper] now [http://crackle.com/ Crackle]
** [http://crackle.com/c/Quantum_of_Solace/Quantum_Of_Solace/2327783#ml=o%3d12%26fpl%3d297691%26fx%3d Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, views, comments, permalink(url)

* [http://revver.com/ Revver]
** [http://revver.com/video/1281276/beer-goggles-commercial/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, download(enclosure), size, format, rating, share(link), comments, permalink(url)

==== Analysis of Video Sites ====

35 total examples Analysed

* title 100%
* video(embeded) 100%
* published 91.42%
* comments 88.57%
* tags 71.42%
* rating 65.71%
* summary 62.85%
* creator 60%
* share(link) 51.42%
* views 45.71%
* download(enclosure) 42.85%
* duration 31.42%
* permalink(url) 28.57%
* description 25.71%

other discovered elements less than 10%

* video size
* feed url
* preview image
* contributor/s

=== Photos ===
* A few photos online have region annotation and quoting. But as tools are developed that are usable for mass publishers, this will likely increase.
* Many videos have thumbnails that are jpgs, and are effectivly quotes of the video.
* Many videos use pictures and therefore the pictures themselves are quotes from the video.
* Most photos have the same elements as videos and audio, including quotes that are derived from the original photo.

==== Individual Publishing of Photos ====

* [http://blog.bouckenooghe.com/2005/09/01/em6-a-est-fache-avec-le-centimetre/ Blog A Brac » E=m6 a est fâché avec le centimètre - photo with annotated screen-caps]
** This example has a Title, Html URL, media URL, description or summary, creator, quotes and descriptions, tags/categories, and publish date and time. +200 across all individually blogged photos.

* [http://scribbling.net/projects/fotonotesrolloverviewer/fotonotesplugin.php?p=helicopterovernyc.jpg Scribbling.net implementation of Fotonotes Plugin demonstrating the fotonotes annotation tool for photos]
** This example has media url, quotes or "notes" and descriptions, creator. +200 across all individually blogged photos.

* [http://community.livejournal.com/boston_photos/ Boston photos]
** [http://www.bobspixels.com/view_album.php?album=2008/2008_10_31&photo=md_oct_31_2008_121452.jpg Photo Example]
*** Information displayed: title, summary, creator, photo, published, resolution, album

* [http://mute.rigent.com/ Mute]
** [http://mute.rigent.com/index.php?ladat=2008-11-03 Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://www.durhamtownship.com/ Durham township]
** [http://www.durhamtownship.com/blog-archives/002245.html Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://blog.magnumphotos.com/ Magnum Photos]
** [http://blog.magnumphotos.com/2008/11/surfing_the_archive_a_contest.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights

* [http://www.boston.com/bigpicture/ Boston Big picture]
** [http://www.boston.com/bigpicture/2008/11/conflict_in_congo_refugees_on.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights, share

* [http://amysteinphoto.blogspot.com/ Amy Stein Photo]
** [http://amysteinphoto.blogspot.com/2008/11/brand-new-funky-president.html Photo Example]
*** Information displayed: title, description, creator, photo, tag, published, comments, rights, share

* [http://blog.photoblogs.org/ Photoblogs Blog]
** [http://blog.photoblogs.org/2008/10/31/saturday-nights-alright-for-fighting-by-treeswing/ Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments

* [http://www.aminus3.com/ Aminus Photoblogs]
** [http://krikis.aminus3.com/image/2008-11-04.html Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments, rights, exif

* [http://johnsfoto.blogspot.com/ Johns Foto]
** [http://johnsfoto.blogspot.com/2008/11/my-world-drammen-norway.html Photo Example]
*** Information displayed: title, description, creator, photo/s, tag, published, comments, rights

* For more work along the lines of 2d annotations, please see (and add to) [[photo-note-examples]].

==== Service publishing of photos ====

* [http://www.flickr.com/photos/500hats/50282408/ Flickr - Photo Sharing instance of a photo.]
** This example has a Title, Html URL, media URL, description or summary, quotes URLs and descriptions, licence, tags, upload time, playlist (set), license, creator, and other capture data. +millions across all hosters. Many photos are also part of a "set" or "viewlist." So the photo can be considered a quote of the set, or a piece of it. +millions of records.

* [http://www.webshots.com/ Webshots.]
** [http://www.webshots.com/g/32/579-sh/25695.html Photo Example.]
*** Information displayed: title, description, creator, photo, published, tag, comments, download, share, album

* [http://zooomr.com/ Zooomr - Photo sharing site]
** [http://www.zooomr.com/photos/flwrgrl/6168222/ Photo Example.]
*** Information displayed: title, creator, photo, published, tag, comments, download, share, location, rating, exif

* [http://www.deviantart.com Deviant Art]
** [http://littlemewhatever.deviantart.com/art/Autumn-Morning-102650017 Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, views, comments, file-size, resolution, download-count, download

* [http://moblog.co.uk Moblog]
** [http://moblog.net/view/861286/voted-bitches Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share

* [http://www.tabblo.com/studio Tabblo]
** [http://www.tabblo.com/studio/stories/view/1653958/?nextnav=recent Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share, slides

* Twitpic
** [http://twitpic.com/6a4zlt Photo Example]

* [http://www.corbis.com Corbis Photograpy]
** [http://pro.corbis.com/popup/Enlargement.aspx?mediauids={59a81f5c-165d-4461-945c-702ecbf19f43} Photo Example]
*** Information displayed: title, summary, creator, photo, tag, file-size, slides, payment, rights, id

* [http://www.istockphoto.com istockphoto]
** [http://www.istockphoto.com/file_closeup.php?id=000004484543 Photo Example]
*** Information displayed: title, summary, creator, photo, tag, views, comments, file-size, resolution, slides, payment, rights, id

* [http://www.sxc.hu Stock.XCHNG]
** [http://www.sxc.hu/photo/478557 Photo Example]
*** Information displayed: title, creator, photo, tag, views, comments, file-size, print-size, resolution, slides, payment, rights, id, download-count, download, exif

* [http://www.photos.com/ Photos.com]
** [http://www.photos.com/en/search/close-up?oid=11525603&hoid=6cb716176348ec2870265408a3ac5d29 Photo Example]
*** Information displayed: title, description, photo, tag, resolution, slides, payment, rights, id

* [http://elfwood.lysator.liu.se/elfwood.pike Elfwood]
** [http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html Photo Example]
*** Information displayed: title, creator, description, photo, tag, comments, rights, technique, share

* [http://www.epilogue.net/cgi/database/art/editors.pl/ Epilogue]
** [http://www.epilogue.net/cgi/database/art/view.pl?id=117980&genre=2 Photo Example]
*** Information displayed: title, creator, description, photo, comments, rights, medium

* [http://ackegard.com/gallery/main.php Ackegard]
** [http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, resolution

* [http://www.caligari.com/Gallery/ImagesGallery/default.asp?Cate=GImages Caligari Images Gallery]
** [http://www.caligari.com/Gallery/ImagesGallery/2008/sep/winner.asp?img=3771&email=harri.pakarinen@gmail.com&name=Harri%20Pakarinen Photo Example]
*** Information displayed: creator, photo, contact

* [http://www.amateurillustrator.com/ Amateur Illustrator]
** [http://www.amateurillustrator.com/articles/?p=1191 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, comments, download, share

* [http://www.cgchannel.com/gallery/ CG channel]
** [http://www.cgchannel.com/gallery/viewimage.jsp?imgID=85 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, vote, rate, views, software

* [http://www.alrioart.com/ Alrioart]
** [http://alrioart.com/details.php?image_id=3246 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, views, file-size

* [http://www.freeart.org/ Freeart]
** [http://www.freeart.org/display.cgi?v=s&i=2 Photo Example]
*** Information displayed: title, creator, description, published, photo, rate, id

* [http://www.dreamstime.com/ Dreamstime]
** [http://www.dreamstime.com/family-image6933295 Photo Example]
*** Information displayed: title, description, creator, photo, tag, views, file-size, print-size, resolution, slides, payment, rights, id, download-count, download

* yFrog
** [http://yfrog.com/h0sadtej Photo Example]

==== Analysis of Photo Sites ====

30 total examples

* photo 100%
* creator 96.66%
* title 93.33%
* description 73.33%
* comments 70%
* tag 63.33%
* rights 43.33%
* resolution(screen) 23.33%
* slides(slide show) 23.33%
* download 20%
* file-size 20%
* views 20%
* file-size 20%
* summary 16.66%
* payment 16.66%
* id 13.33%

Other discovered properties occurring less than 10%

* download-count
* exif(extended information, camera, exposure time, etc)
* album(collection)
* print-size
* location(geo coordinates)
* rating
* technique(Artist style)
* software(Imaging application ie: photoshop)

=== Media comments ===

The following urls are examples of user/visitor comments about media items.

* http://ryanedit.blogspot.com/2006/01/light-water-music-2.html
** Information displayed: author, author-url, comment

* http://prototypen.com/blog/vjblog/archives/001318.html
** Information displayed: author, author-url, comment, published

* http://www.itsjerrytime.com/?p=89
** Information displayed: author, author-url, comment, published

* http://bottomunion.com/blog/?p=469
** Information displayed: author, author-url, comment, published

* http://www.rocketboom.com/rb_07_mar_26/
** Information displayed: author, author-url, comment, published, comments-link

* http://www.chesslodge.com/2007/03/chess-video-lesson-2/
** Information displayed: author, author-url, comment, published

* http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html
** Information displayed: author, author-url, comment, published

* http://blip.tv/file/1425655/
** Information displayed: author, author-url, comment, published

* http://uk.youtube.com/watch?v=KKTDRqQtPO8
** Information displayed: author, author-url, comment, published, reply-url, vote

* http://vimeo.com/162754
** Information displayed: author, author-url, comment, published

* http://www.dailymotion.com/commented-week/lang/en/video/x7a2my_lewis-hamilton-champion-f1-2008_sport
** Information displayed: author, author-url, comment, published

* http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/
** Information displayed: author, author-url, author-photo, comment, published

* http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/
** Information displayed: author, author-url, comment, published, comment-link

* http://freakytrigger.co.uk/ft/2008/11/blondie-call-me/
** Information displayed: author, author-url, comment, published, comment-link

* http://www.scissorkick.com/2008/09/midnight-lab-band/
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html
** Information displayed: author, author-url, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://loki23.blogspot.com/2008/09/flower-electronics.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://videogum.com/archives/the-hunt-for-the-worst-movie-of-all-time/the-hunt-for-the-worst-movie-o-30_032141.html
** Information displayed: author, author-url, author-photo, comment, published, comment-link, vote, reply-url

* http://www.haloscan.com/comments/empirestatehuman/7424868678376349884/
** Information displayed: author, author-url, comment, published, comment-link, reply-link

* http://www.3hive.com/2008/10/1000_robata.php#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://www.musicload.de/album/1884260_2/nik-p--dj-%C3%B6tzi/ein-stern-der-deinen-namen-tr%C3%A4gt/item.html
** Information displayed: author, comment, published, rating

* http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/#comments
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1
** Information displayed: author, comment, published

* http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html#addnewcmt
** Information displayed: author, author-url, comment, published

==== Analysis of Media comments ====

25 examples

* author 100%
* comment 100%
* published 100%
* author-url 92%
* comment-link 40%
* author-photo 16%
* reply-url 12%

Other properties occuring less than 10%

* vote

== Notes on Existing Practices ==

Mary Hodder:
* We are finding at Dabble as we look at millions of user generated media records, that almost all have html and/or media urls, titles, uploader or creator, and at least a default licensing of Copyright. Most have tags whose functionality is made available through the hosting service (the richer the media, the more likely tagging goes toward 100% of the items), thumbnail URL(s), publishing date, and about 25% have quoting information of some sort (quotes of video or audio, and region quotes of photos).
* Tags apparently appear at the upload point on 61% of photos in Flickr, and within a short period, 80+% have tags. 12% of users in Flickr apparently tag photos other than their own.

Manu Sporny (on music):
* There is an increasing number of sites that link to different methods of acquiring content displayed on a web page. These may include links to high-quality, or full versins of the media being described on the page. The various options include: free, streaming with ads, one-time purchase, and rental.
* Summaries, long descriptions and reviews are also prevalent in some of the content.

Manu Sporny (on video):
* We should attempt to support the basic information on sites that have been operational for years such as IMDB and Rotten Tomatoes among others. These sites tend to have very detailed information on all things related to video and TV - other sites will follow their lead because their meta-data seems to be the most complete on the web - thus making every other site contain a sub-set of their meta-data.

== Next Steps ==
# Add more real-world, simple, minimal examples.
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.
# Start [[media-info-brainstorming]] based on examples.

== See Also ==
* [[media-metadata-examples]] - previous attempt to catalog and organize top down metadata systems generated by engineers and committees, as examples of elements, and includes formats which should be in a separate page. Useful as a source of research but this microformat needs to embrace the bottomup ways users are publishing photos, video and audio online.

{{Template:hmedia-related-pages}}

media-info-examples

2011-08-22T23:02:14Z

Singpolyma: /* Service publishing of photos */ add twitpic example

= Media Info Examples =

{{TOC-right}}

== Contributors ==

* [[User:RodBegbie | RodBegbie]]
* [http://tantek.com/log/ Tantek Çelik]
* [http://napsterization.org/stories/ Mary Hodder]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [[User:ChrisMessina | ChrisMessina]]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:MikeJohnson | Mike Johnson]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:WebOrganics| Martin McEvoy]]

== Introduction ==

Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.

== Emphasis on Practical, Simple, and Minimal ==

Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.

Thus for now, this document is deliberately restricted to examples that are:
* ''Actual'' examples in practice on the Web '''with URLs''' to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.

Any examples added which do not conform to these requirements will be deleted.

Any generic analysis will also be deleted. Analysis before examples is premature. Once there are sufficient media-info-examples, and hopefully a simple/clean listing of [[media-info-formats]], we'll hopefully start a [[media-info-brainstorming]] page to do aggregate analysis of the examples.

===Note on proposals===

Because the hMedia became a task so big that it seems impossible to make it "simple and minimal" discussions started on splitting them by media type.

see: [[audio-info-brainstorming]]

== Real World Examples ==

=== Overall Notes About Examples ===
These examples are organized into a short list of top level media categories, in the hopes that it will be easier to determine if there are media specific publishing behaviors, in addition to common behaviors across multiple types of media. Some may be subcategorized and distinguished by whether it was published by an individual publisher or a service:
* [[media-info-examples#Audio|Audio]] (Speech, Music)
* [[media-info-examples#Video|Video]]
* [[media-info-examples#Photos|Photos]]

The numbers after some of the examples' descriptions are based on numbers found pulling in media records at Dabble. Others may have higher numbers and would be encouraged to restate them if that's true.

=== Audio ===

==== Speech ====
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing. Quotes of audio files are beginning to appear, and publishers are putting up files with links to other audio files they've quoted from. Most audio appears to often have the same base elements as video and photos, with the exception of quotes.

===== Individual Publishing of Speech =====

* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]
** Appears to be composed of:
*** title/summary of the recording
*** clickable hyperlink to the recording (MP3)
*** comments
** Contextual:
*** (primary) speaker is indicated in nearby text

* [http://www.thechrispirilloshow.com/help/20060119_chuck_cummins_on_windows_vista_interface_design.phtml Chris Pirillo podcast]
** This example has a Title, Html URL, media URL(s), description or summary, categories/tags underneath what is viewable, and date. +10k

* [http://yukelzon.blogspot.com/2006/01/podcasts.html Reflog's Random Thoughts podcast]
** This example has a Title, Html URL, description or summary, creator, tags and publish time and date. NOTE, record also contains an [http://images.apple.com/r/ipodstore/ipodviews/0.jpg image], comments +10k records.

* [http://www.evilgeniuschronicles.org/wordpress/2006/01/12/egc-clambake-for-january-12-2006/ Evil Genius Chronicles podcast]
** This example has a Title, Html URL, description or summary, quotes URLs and descriptions, licence, creator, comments, tags and publish time and date. +10k records.

* [http://www(dot)bizbyjake.com/2006/01/how-are-you-doing.html media published from a blog, Jake Steinfeld's Audio Blog] NOTE: this record had trouble because mediawiki blocks any DOTbiz domains and so while this domain coincidentally has a DOTbizbyjake.com name that is not a TLD, it was still blocked in the loading of the page with this example. So please adjust the URL manually and then visit the site.
** This example has a Title, Html URL, media URL, creator and publish time and date. +10k records.

* [http://podcast.rubyonrails.org/ Ruby on rails Podcast]
** Feed, title, published, description, author, contributor, download, format

* [http://www.cnet.com/8300-11455_1-10.html Buzz out loud]
** Feed, title, description, published, episode, download, author

===== Analysis of Individual Publishing of Speech Sites =====

7 examples, 6 available

* post-title 100%
* audio-title 100%
* download 100%
* author 100%
* contributor 100%
* description 100%
* published 83.33%
* feed 66.66%
* category 50%
* comments 50%
* format 33.33%
* episode 16.66%
* photo 16.66%

==== Music ====

===== Individual Publishing of Music =====

* [http://www.bradsucks.net/music/ Brad Sucks » music]
** Has album title, song title, separate link to more info, inline flash player, and play link (to mp3)

* [http://www.scottandrew.com/music/ Scott Andrew - lo-fi acoustic pop superhero! > music >]
** Has album title, song title, licensing info, remixing policy, multiple formats such as streaming link (to m3u), play links (to mp3, OGG, FLAC)
** Record contains album cover image.

* [http://www.hearingdouble.co.uk/dumb/index2.html Portishead Remixed]
** Whole page is for one album (a mash-up remix of a Portishead album). Has Album Track Number and Title (linked to mp3) and Remixer's name. Also a link to multiple formats such as the BitTorrent download of the whole album.
** Record contains album cover images.

* More examples here please....

===== Analysis of Individual Publishing of Music Sites =====

3 examples, 2 available

* post-title: 100%
* audio-title: 100%
* download: 100%
* contributor: 100%
* published: 100%
* duration: 100%
* photo: 100%
* payment: 100%
* album title: 100%
* category: 50%

===== Music Podcasting sites=====

* [http://www.coverville.com/archives/2008/10/coverville_517.html Coverville]
** description, title, published, contributor, position, download, comments

* [http://magnatune.com/podcasts/details/magnatune_middle-eastern_podcast_2006_12_14 Magnatune]
** Feed, title, section, genre, length, published, contributor, interval, download

* [http://www.mutantpop.net/radioclash/archives/2007/03/24/rc-113/ Mutantpop]
** Feed, description, title, photo, format, duration, size, published, contributor, download, category, comments

* [http://www.btpodshow.com/shows/?sId=21&mId=5332173 btpodshow]
** Feed, description, title, episode , category, published, contributor, position, comments

* [http://indiecastwp.podshow.com/?p=76 Indiecast]
** Feed, description, title, section, format, category, length, published, contributor, episode

* [http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/ Accidenthash]
** Feed, description, title, category, length, published, contributor, episode, download, comments

* [http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/ Strong words inc]
** Feed, description, title, duration, published, episode, download, author, comments

* [http://threehive.libsyn.com/index.php?post_id=111596 Three hive]
** Feed, description, title, photo, format, category, published, contributor[s] author, episode, download, comments

* [http://music.for-robots.com/archives/002495.html For Robots]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.fluxblog.org/2008/10/when-the-work-is-done fluxblog]
** Feed, title, published, description, contributor, download, comments

* [http://www.3hive.com/2008/10/photons.php 3hive]
** Feed, title, published, photo, description, author, contributor, download[s] , format, category, comments

* [http://www.saidthegramophone.com/archives/complete_coverage.php said the gramophone]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.archasung.com/playlist/playlist-cloudy-days Archasung]
** Feed, title, published, photo, description, contributor, download[s], comments

* [http://betterpropaganda.com/content.aspx?id=840 Better Propaganda]
** Feed, title, photo, description, contributor, download[s], episode

* [http://freakytrigger.co.uk/ft/2008/10/a-bite-of-stars-a-slug-of-time-and-thou-episode-14/ Freaky Trigger]
** Feed, title, published, description, author, contributor, download, episode, comments

* [http://www.catbirdseat.org/archives/001093.php Cat Bird Seat]
** Feed, title, published, description, contributor, download[s], format

* [http://the-big-ticket.blogspot.com/2007/09/all-in-game-indeed.html The Big Ticket]
** Feed, title, published, description, author, contributor, download, format, category, comments

* [http://sixeyes.blogspot.com/2008/10/sixeyes-saturday-mix-oct-4th.html Six Eyes]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.spoiltvictorianchild.co.uk/2007/11/no-vice-my-arse.html Spoilt Victorian Child]
** Feed, title, published, photo, description, author, contributor, download, comments

* [http://www.scissorkick.com/2008/09/midnight-lab-band/ Scissorkick]
** Feed, title, published, photo, description, author, contributor, download, format, category, comments

* [http://loki23.blogspot.com/2008/09/flower-electronics.html loki23]
** Feed, title, published, photo, description, author, contributor, download[s], format, category, comments

* [http://www.sweetthunder.org/tapes/weekonehundredandsix.html sweetthunder]
** Feed, title, published, photo, description, contributor, download, duration, comments

* [http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html Arjan writes]
** Feed, title, published, photo, description, contributor, download, duration, format, comments

===== Analysis of Podcasting Sites =====

23 examples

* feed 100%
* post-title 100%
* audio-title 100%
* contributor 95.65%
* description 95.65%
* download 95.65%
* published 95.65%
* comments 78.26%
* photo 56.52%
* author 52.17%
* category 39.13%
* format(eg: mp3) 39.13%
* episode(number) 30.43%
* duration 13.04%

properties occurring less than 10%

* interval

===== Service Publishing of Music =====

* [http://audiofind.ru/ AudioFind]
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Album Example]
*** Information displayed: artist (link), title, genre (link), style (link), release date, label, summary, web-based purchase (link), price, artist rating, album rating.
*** Record contains cover image
** [http://audiofind.ru/music/album/-/Lost%20Angel/Destination/?id=591 Song Example]
*** Information displayed: track number, title, length, rating, price, sample (link), web-based purchase (link)
*** Record contains cover image

* [http://bigpondmusic.com Telstra BigPond]
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Album Example]
*** Information displayed: artist (link), title, genre, release date, label, summary, web-based purchase (link), subscriber price, non-subscriber price, cover image
** [http://bigpondmusic.com/Album/The-Decemberists/The-Crane-Wife.aspx Song Example]
*** Information displayed: track number, title, artist, album, price, add to pop-list (link), sample (link), web-based purchase (link)

* [http://www.bitmunk.com/ Bitmunk]
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068744 Album Example]
*** Information displayed: artist, album title, publisher, release date, genre (link), summary, long description, payees, total price, sample (link), tracks, web-based purchase (link), p2p-based purchase (link)
*** Record contains cover image
** [http://www.bitmunk.com/showdetails?action=view&cwid=6068746 Song Example]
*** Information displayed: artist, song title, composer, publisher, release date, genres, album, payees, total price, web-based purchase (link), p2p-based purchase (link)

* [http://downloadpunk.com Download Punk]
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Album Example]
*** Information displayed: title, artist (link), label (link), physical-based purchase (link), web-based purchase (link)
*** Record contains cover image
** [http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202 Song Example]
*** Information displayed: title, sample (link), price, web-based purchase (link)

* [http://www.fye.com FYE]
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Album Example]
*** Information displayed: title, artist (link), format, release date, label (link), UPC, product id, genre, styles, regular price, store price, savings, physical-based purchase (link), tracks, description, reviews, production credits
*** Record contains cover image
** [http://www.fye.com/Not-Too-Late-Music_stcVVproductId7456462VVcatId458211VVviewprod.htm Song Example]
*** Information displayed: track number, title, artist

* [http://imusic.libero.it/ iMusic]
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Album Example]
*** Information displayed: title, artist (link), genre, release date, publisher, number of tracks, length, tracks, web-based purchase (link)
*** Record contains cover image
** [http://imusic.libero.it/compilation.php?icom_id=105902&ptipo=pus&pid=171437 Song Example]
*** Information displayed: track number, length, sample (link), release date, price, web-based purchase (link)

* [http://musicdownload.aon.at/v7/ AON Music ]
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Album Example]
*** Information displayed: artist (link), album, price, format, bitrate, label, genre, number of tracks, sample (link), add bookmark (link), web-based purchase (link), tracks
*** Record contains cover image
** [http://www.omds.de/servlets/2452685121527Dispatch/31/Call?htmltemplate=./album/viewalbum.htm&lmtype=ALBUM&albumid=2310333 Song Example]
*** Information displayed: track number, title, length, format, price, sample (link), add bookmark (link), web-based purchase (link)

* [http://music.msn.com MSN]
** [http://music.msn.com/album/?album=50538895 Album Example]
*** Information displayed: artist (link), title, release date, label, album rating.
*** Record contains cover image
** Song Example (store wasn't working correctly - no song info found)

* [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/Call?htmltemplate=./index.htm TDC Online]
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Album Example]
*** Information displayed: title, artist (link), length, release date, label, format, web-based purchase (link), price, tracks
*** Record contains cover image
** [http://musik.tdconline.dk/servlets/2452306090224Dispatch/19/call?htmltemplate=./album/viewalbum.htm&trackid=5010526 Song Example]
*** Information displayed: track number, title (link), price, sample (link), web-based purchase (link)

* [http://www.audiolunchbox.com Audio Lunchbox]
** [http://www.audiolunchbox.com/album?a=75751 Album Example]
*** Information displayed: title, artist (link), label (link), genre (link), release date (link), format, bitrate, price, price in credits, web-based purchase (link), add to wishlist (link), sample (flash applet), tracks
*** Record contains cover image
** [http://www.audiolunchbox.com/album?a=75751 Song Example]
*** Information displayed: track number, title, length, price, price in credits, web-based purchase (link), sample (flash applet)

* [http://www.chaosmusic.com/music/ Chaos Music]
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Album Example]
*** Information displayed: title, artist (link), genre, format, release date, price, physical-based purchase (link), add to wishlist (link), tracks, description, availability
*** Record contains cover image
** [http://chaos.com/product.asp?intProductID=739720&intArtistID=167488 Song Example]
*** Information displayed: track number, title

* [http://www.connect-europe.com Sony Connect]
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, length, publisher, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://store.connect-europe.com/albumDetailPage.do?albumId=3260785 Song Example]
*** Information displayed: title, artist, length, price, sample (link), web-based purchase (link)

* [http://www.digirama.co.nz/ Digirama]
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Album Example]
*** Information displayed: title, artist (link), genre (link), label, release date, price, web-based purchase (link), license, related albums, also bought, reviews, tracks
*** Record contains cover image
** [http://www.digirama.co.nz/AlbumDetails.aspx?MediaID=578456 Song Example]
*** Information displayed: track number, title, length, sample (link), price, web-based purchase (link)

* [http://www.emusic.com eMusic]
** [http://www-v3.emusic.com/album/10917/10917324.html Album Example]
*** Information displayed: title, artist (link), sample (link), save to playlist (link), genre (link), styles (link), label (link), album rating, reviews, length, tracks, web-based purchase (link)
** [http://www-v3.emusic.com/album/10917/10917324.html Song Example]
*** Information displayed: track number, sample (link), tracks, length, web-based purchase (link)

* [http://www.fnacmusic.com/ FNAC]
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Album Example]
*** Information displayed: title, artist (link), length, add to playlist (link), web-based purchase (link), tracks, price, genre
*** Record contains cover image
** [http://www.fnacmusic.com/album/7088f214-6187-4845-afdc-6391e103f67d.aspx Song Example]
*** Information displayed: sample (link), add to playlist (link), track number, title, length, web-based purchase (link), price

* [http://sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Album Example]
*** Information displayed: title, artist (link), release date, catalog ID, SKU, label, price, price in points, summary, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-942394 Song Example]
*** Information displayed: track number, title

* [http://www.misrolas.com/ MisRolas]
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Album Example]
*** Information displayed: title, artist (link), cover image, release date, number of tracks, album rating, price, web-based purchase (link), tracks, reviews
** [http://www.misrolas.com/downloadmusic/album.php?id=1316 Song Example]
*** Information displayed: track number, title, sample (link), artist, price, web-based purchase (link), add to wishlist (link)

* [http://www.mtv.com MTV]
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Album Example]
*** Information displayed: title (link), artist (link), release date, label, tracks, physical-based purchase (link)
*** Record contains cover image
** [http://www.mtv.com/#/music/artist/my_chemical_romance/albums.jhtml?albumId=1367908 Song Example]
*** Information displayed: track number, title, sample (link), video sample (link)

* [http://www.musica360.com/ Musica360]
** [http://musica360.com/store/product_info.php?products_id=232 Album Example]
*** Information displayed: title, artist, price, samples (flash), tracks, web-based purchase (link)
*** Record contains cover image
** [http://musica360.com/store/product_info.php?products_id=232 Song Example]
*** Information displayed: title, artist, price, web-based purchase (link)

* [http://www.musicload.de/ Musicload]
** [http://www.musicload.de/item.ml?releaseid=1884260_2 Album Example]
*** Information displayed: title, artist (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), tracks, comments
** [http://www.musicload.de/item.ml?releaseid=1884261_4 Song Example]
*** Information displayed: title, artist (link), album (link), price, rating, genre, length, quality, release date, label, sample (link), web-based purchase (link), comments

* [http://www.napster.com Napster]
** [http://www.napster.com/view/album/index.html?id=12376484 Album Example]
*** Information displayed: title, artist (link), release date, track count, label, sample (link), share (link), web-based purchase (link), review, tracks
** [http://www.napster.com/view/album/index.html?id=12376484 Song Example]
*** Information displayed: artist (link), title, track number, album title, length, web-based purchase (link)

* [http://www.partymob.com/edl/browse/?tab=music PartyMob]
** [http://www.partymob.com/edl/details/default.aspx?album=2089814 Album Example]
*** Information displayed: title, artist (link), total length, release date, format, quality, genre, sample (link), price, web-based purchase (link), tracks
** [http://www.partymob.com/edl/details/default.aspx?track=234418 Song Example]
*** Information displayed: title, artist, length, release date, format, quality, genre, sample (link), price, web-based purchase (link), DRM information

* [http://www.peerimpact.com Peer Impact]
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449 Album Example]
*** Information displayed: title, artist (link), price, purchase (application link), format, track count, genre, release date, label, tracks
** [http://www2.peerimpact.com/contentstorage-xml/album30.do?templateName=WEB-INF/conversion-templates/album30.vm&albumId=89449# Song Example]
*** Information displayed: track number, sample (link), title, artist (link), length, price

* [http://www.puretracks.com Pure Tracks]
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Album Example]
*** Information displayed: artist, title, label, total length, disc count, release date, price, web-based purchase (link), DRM information, tracks
*** Record contains cover image
** [http://us.puretracks.com/catalog/details.aspx?pid=emi_094638723653 Song Example] (in popup window)
*** Information displayed: track number, sample (link), title, artist, length, price, web-based purchase (link), label (popup)

* [http://www.reggaecountry.com Reggae Country]
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Album Example]
*** Information displayed: title, artist, release date, label, web-based purchse (link), price, tracks
*** Record contains cover image
** [http://www.reggaecountry.com/Shopping/Browse.aspx?mode=item&category=209&item=35745 Song Example]
*** Information displayed: sample (link), track number, title, artist, length, web-based purchase (link), price

* [http://www.rhapsody.com Real/Rhapsody]
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Album Example]
*** Information displayed: artist, title, sample (link), label, release date, tracks
*** Record contains cover image
** [http://www.rhapsody.com/harryconnickjr/chansonduvieuxcarrconnickonpiano3 Song Example]
*** Information displayed: sample (link), track number, title

* [http://www.ruckusnetwork.com Ruckus]
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Album Example]
*** Information displayed: title, artist, release date, genre, label, tracks
*** Record contains cover image
** [http://wapps.ruckus.com/cgi-bin/WebObjects/ruckus.woa/2/wo/bQ5EBCLVYbWMuHOuCRElwM/0.0.27.15.13.1.16.3.3 Song Example]
*** Information displayed: track number, title, length

* [http://www.sanity.com.au Sanity]
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Album Example]
*** Information displayed: title, artist (link), release date, catalog id, label, price, web-based purchase (link), tracks
*** Record contains cover image
** [http://www.sanity.com.au/product/rockpop.asp?sku=-943269 Song Example]
*** Information displayed: sample, track number, title

* [http://www.starzik.com/starzik.php Starzik SARL]
** Album Example (hidden url)
*** Information displayed: title, artist (link), genre, label, release date, length, format, bitrate, size, web-based purchase (link), tracks
*** Record contains cover image
** Song Example (hidden url, separate from album example)
*** Information displayed: title, artist (link), album title, genre, label, release date, length, creators, composer, performance artist, format, bitrate, size, web-based purchase (link)

* [http://www.thecellcity.com CellCity]
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=fuzzyquery&CDMdepartment=music&cdmalbum=What's%20The%20Word%20Vol.%201&CDMReturnURL=/music/albumdetails.shtml] Album Example]
*** Information displayed: artist, label, release date, genre, tracks
** [http://www.thecellcity.com/4DACTION/CDMProductQuery?CDMCommand=GetProductDetail&CDMProductID=A00001148172&CDMReturnURL=/music/product_detail.shtml Song Example]
*** Information displayed: title, price, web-based purchase (link)

* [http://www.top100.cn top100.cn]
** [http://www.top100.cn/product/specialall/S0027876000.htm Album Example]
*** Information displayed: title, artist (link), release date, sample (link), web-based purchase (link), label (link), genre (link), long description, tracks
** [http://www.top100.cn/product/SongFiles/0027876/M0027876001.htm Song Example]
*** Information displayed: title, artist (link), label (link), genre (link), price, sample (link), web-based purchase (link), description, comments

* [http://www.wippit.com/default.aspx Wippit]
** [http://www.wippit.com/AlbumDet.aspx?StrId=28724&StrCatType=S Album Example]
*** Information displayed: title, artist (link), price, genre (link), format, release date, tracks, web-based purchase (link)
** [http://www.wippit.com/DetailItem.aspx?StrItemID=28724&StrMediaID=724904&StrMediaType=S Song Example]
*** Information displayed: title, artist (link), album (link), genre, format, release date, size, track number, file type, price, web-based purchase link

* [http://www.yanga.ru Yanga]
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Album Example]
*** Information displayed: title, artist (link), genre (link), release date, label, price, web-based purchase (link), rating, tracks
** [http://yanga.ru/music/album/-/Duke%20Ellington/Jack%20The%20Bear/?id=28510 Song Example]
*** Information displayed: sample, track number, title, length, rating, price, web-based purchase (link)

* [http://www.somesongs.com/ somesongs]
** [Album Example]
*** Information displayed:
** [http://www.somesongs.com/song_info.php?select=4713 Song Example]
*** Information displayed: title, artist (link), rating, sample (link), summary, reviews, release date

* [http://magnatune.com/ Magnatune]
** [http://magnatune.com/artists/albums/ammonite-recon/ Album Example]
*** Information displayed: artist (link), title, cover image, total time, length, release date, artist location (link), web-based purchase (link), physical-based purchase (link), license (link), tracks, summary
** [http://magnatune.com/artists/albums/ammonite-recon/ Song Example]
*** Information displayed: track number, title, length, sample (link)

* [http://www.songfight.org/ SONG FIGHT!]
** [http://www.songfight.org/artistpage.php?key=15-16_puzzle&sortkey=date Album Example]
*** Information displayed: artist (link), cover image, artist location, summary, title,
** [ Song Example]
*** Information displayed: release date, sample (link), title

* [http://www.yes.com/ Yes.com]
** [http://www.yes.com/ Album Example]
*** Information displayed: cover image, artist (link)
*** Record contains cover image
** [http://www.yes.com/ Song Example]
*** Information displayed: cover image, artist (link), rank, web-based purchase (link), played-by radio station

* [http://www.myspace.com MySpace]
** [http://myspace.com/theradioknives Album Example]
*** Information displayed: artist, title, sample (link), cover image, number of plays, tracks
*** Record contains cover image
** [http://myspace.com/theradioknives Song Example]
*** Information displayed: artist, title, number of plays, sample (link), lyrics (link)

* [http://musicbrainz.org MusicBrainz.org]
** [http://musicbrainz.org/release/1138abc1-77f4-4ba9-900d-5cf52baaf4bf.html Album Example]
*** Information displayed: artist (link), title, cover image, tracks, disc id
*** Record contains cover image
** [http://musicbrainz.org/show/track/?trackid=435002 Song Example]
*** Information displayed: title, artist, length, id (link), length, album (link), album id (link), artist, artist id (link), relationship (link), track number

* [http://reactor-core.org/ogg-tagging.html Vorbis Comment Recommendations]
** [http://reactor-core.org/ogg-tagging.html Album Example]
*** Information displayed: artist, publisher, copyright, disc number, isrc, ean/upn, label, label catalog number, license, opus, source media, title, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment
** [http://reactor-core.org/ogg-tagging.html Song Example]
*** Information displayed: album, artist, publisher, copyright, disc number, isrc, ean/upn, label, label number, license, opus, source media, title, track number, version, encoded-by, encoding, composer, arranger, lyricist, author, conductor, performer, ensemble, part, part number, genre, release date, location, comment

* [http://www.apple.com/itunes/podcasts/techspecs.html iTunes RSS extensions]
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Album Example]
*** Information displayed: title, website (link), language, licensing, summary, description, owner, owner e-mail, cover image, genre
** [http://www.apple.com/itunes/store/podcaststechspecs.html#_Toc526931673 Song Example]
*** Information displayed: title, artist, summary, description, sample (link), length, format, id, release date, tags

* [http://www.discogs.com/ Discogs]
** [http://www.discogs.com/release/705805 Album Example]
*** Information displayed: artist, title, label (link), catalog id, format, country, release date, genre, style, notes, rating, tracks
** [http://www.discogs.com/release/705805 Song Example]
*** Information displayed: artist (link), title, track number

* [http://www.last.fm/ Last.fm]
** [http://www.last.fm/music/Muse/+albums Album Example]
*** Information displayed: cover image, artist, title, release date, label (link), number of tracks, sample (link), physical-based purchase (link), tracks
** [http://www.last.fm/music/Muse/Absolution Song Example]
*** Information displayed: track number, sample (link), title, length, number of plays

===== In-active Music Services =====

* [http://music.yahoo.com/ Yahoo! Music Unlimited]
* [http://www.musicmatch.com Musicmatch] (Merged with Yahoo! Jukebox)
* [http://www.musicnet.com MusicNet] (Service Provider)
* [http://www.musicnow.com AOL Music Now] (Merged with Napster)
* [http://www.nate.com Nate.com] (Appears to be Korean, cannot find album examples)
* [http://www.nextradiosolutions.com Next Radio] (Service Provider)
* [http://www.soundbuzz.com Soundbuzz] (Requires MS IE6)
* [http://www.starbucks.com Starbucks] (Requires Flash 8 player)
* [http://www.streetcds.com/ Street CDs] (parked domain name)
* [http://www.synacor.com/content/index.php Synacor] (Service provider)
* [http://www.telecomitalia.com/ Telecom Italia] (Service provider)
* [http://www.terra.es/pixbox/ Pixbox (Terra) ] (Windows application)
* [http://www.virgin.com/downloads Virgin Digital] (merged with Napster)
* [http://www.virginmega.fr/ Virgin] (Requires Windows)
* [http://www.yeahronimo.nl Yeahronimo (Commodoreworld)]

===== Analysis of Music Sites =====

Shown below is the most popular information listed for music albums. This includes analysis of over 85 online music sites.

'''Album Statistics'''
* 100%: artist
* 92%: title
* 85%: tracks
* 77%: release date
* 67%: label
* 62%: genre
* 62%: web-based purchase
* 59%: cover image
* 49%: price
* 26%: format
* 23%: sample
* 21%: length
* 18%: summary
* 15%: physical-based purchase
* 10%: publisher
* 10%: reviews

Shown below is the most popular information listed for songs. Keep in mind that along with the information listed below - for over 80% of the cases, album information was listed on the same page.

'''Song/Track Statistics'''
* 95%: title
* 69%: track number
* 67%: sample
* 62%: web-based purchase
* 59%: artist
* 54%: price
* 54%: length
* 26%: release date
* 15%: album
* 15%: genre
* 13%: format
* 10%: rating
* 10%: label

=== Video ===
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player. *Many videos include a thumbnail jpg which is clickable to the media object and player.* Some video includes links to those other source videos, photos and audio that have been quoted. Most videos have the same base elements as photos and audio, with the exception of quotes.

==== Individual publishing of video ====

* [http://FreeVlog.org FreeVlog]
** [http://www.freevlog.org/index.php/2007/01/24/new-vlog-moments-in-turkey/ Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments (link)

* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]
** [http://joshkinberg.com/popupmaker/ Video Example]
*** Information displayed: title, download (link), preview image

* [http://ryanedit.blogspot.com/ Ryanne's Video Blog]
** [http://ryanedit.blogspot.com/2006/01/light-water-music-2.html Video Example]
*** Information displayed: title, post date, preview image, download (link), tags, comments (link)

* [http://www.prototypen.com/blog/vjblog/ Artificial Eye]
** [http://www.prototypen.com/blog/vjblog/archives/001240.html Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, website (link), comments

* [http://www.itsjerrytime.com/ It's JerryTime!]
** [http://www.itsjerrytime.com/?p=89 Video Example]
*** Information displayed: title, preview image, video (link), comments, tags

* [http://www.bottomunion.com/blog/ Bottom Union]
** [http://bottomunion.com/blog/?p=403 Video Example]
*** Information displayed: title, preview image, video (link), video (embedded), post date, summary, website (link), comments, tags, feed subscription (link)

* [http://rocketboom.com/vlog/ Rocketboom]
** [http://www.rocketboom.com/stories/rb_07_mar_26 Video Example]
*** Information displayed: title, preview image, download (link), post date, video (embedded), comments (link), tags (link), feed subscription (link)

* [http://www.chesslodge.com/ Chess Lodge]
** [http://www.chesslodge.com/2007/03/chess-video-lesson-2/ Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, video (embedded), website (link), comments (link), tags, feed subscription (link)

* [http://pechesscast.blogspot.com/ PE Chesscast]
** [http://pechesscast.blogspot.com/2007_03_01_archive.html#4209870902184134583 Video Example]
*** Information displayed: title, preview image, download (link), post date, summary, comments (link), tags (link), feed subscription (link), e-mail to friend (link)

* [http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html Steve Garfield]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv media]
** [http://blip.tv/file/get/Stevegarfield-SXSWAllTogetherNow326.flv.jpg image]
*** Information displayed: title, preview image, download (link), post date, summary, commennts (link), tags, description, feed subscription, licensing.
*** Quoting / credits: music included.

==== Service publishing of video (there are 350+ so this is a short list) ====

* [http://blip.tv/ blip.tv]
** [http://thedailyreel.blip.tv/file/181901?filename=Thedailyreel-TheDailyReelMarch28629.flv Video Example]
*** Information displayed: creator, title, preview image, download (link), post date, summary, review rating, content rating (link), category, video (embedded), number of comments, comments (link), tags, e-mail forward (link), feed subscription (link)

* [http://youtube.com/ YouTube]
** [http://youtube.com/watch?v=KKTDRqQtPO8 Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link), e-mail to friend (link), save to favorites, add to groups, number of views, number of comments, number of honors, number of links, number of responses, permalink, related

* [http://mefeedia.com/ Mefeedia]
** [http://mefeedia.com/entry/2303506/ Video Example]
*** Information displayed: creator (link), title, preview image, download (link), post date, review rating, category, summary, video (embedded), website (link), comments, tags, feed subscription (link)

* [http://vimeo.com/ Vimeo]
** [http://vimeo.com/clip:162754 Video Example]
*** Information displayed: creator, title, preview image, post date, summary, video (embedded), website (link), comments

* [http://DailyMotion.com/ DailyMotion]
** [http://www.dailymotion.com/us/featured/video/x1l9qx_sad-kermit-hurt Video Example]
*** Information displayed: creator, title, preview image, post date, review rating, content rating, category, summary, video (embedded), website (link), comments, tags, add to favorites (link), add to blog (link), e-mail to friend (link), length, filming location, permalink

* [http://www.nbc.com NBC]
** [http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/ Video Example]
*** Information displayed: title, summary, video(embeded), duration, tags, views, rating, comments, permalink(url)

* [http://abc.go.com ABC]
** [http://abc.go.com/primetime/watercooler/index?pn=index Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, season, episode, rating

* [http://video.google.com Google Video]
** [http://video.google.com/videoplay?docid=-5177576155567667810&hl=en Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.videosift.com Video Sift]
** [http://www.videosift.com/video/Idiot-Cop-never-heard-of-the-Constitution Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, tags, views, rating, download(enclosure), share(link), comments

* [http://www.footbag.org/gallery/video Footbag]
** [http://www.footbag.org/gallery/show/8830 Video Example]
*** Information displayed: title, summary, video(embeded), duration, published, download(enclosure), size

* [http://www.break.com Break]
** [http://www.break.com/index/powerful-tornado-throws-cars.html Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.collegehumor.com College Humor]
** [http://www.collegehumor.com/video:1886239 Video Example]
*** Information displayed: title, creator, video(embeded), published, rating, tags, comments

* [http://www.ebaumsworld.com Ebaum's World]
** [http://www.ebaumsworld.com/video/watch/1044597/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, tags, views, share(link), comments

* [http://www.holylemon.com/ Holylemon]
** [http://www.holylemon.com/The-Animator--v818.html Video Example]
*** Information displayed: title, description, video(embeded), published, rating, views, share(link), comments

* [http://www.crooksandliars.com/ Crooks and Liars]
** [http://crooksandliars.com/david-neiwert/get-ready-rights-post-election-delig Video Example]
*** Information displayed: title, description, creator, video(embeded), published, tags, share(link), comments

* [http://video.yahoo.com Yahoo Video]
** [http://video.yahoo.com/watch/3786346/10380005 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://www.myspace.com MySpace Videos]
** [http://vids.myspace.com/index.cfm?fuseaction=vids.individual&VideoID=44857402 Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, rating, tags, views, share(link), comments

* [http://video.aol.com/ AOL Video]
** [http://uncutvideo.aol.com/tags/art-&-animation/adf34e0b55f492d0210491e9c4906362?index=7 Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, rating, views, share(link), comments

* [http://www.heavy.com/ Heavy]
** [http://www.heavy.com/channel/1179 Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.ifilm.com/ iFilm] now [http://www.spike.com/ Spike]
** [http://www.spike.com/video/spider-man-3-trailer/2783985 Video Example]
*** Information displayed: title, description, creator/s, video(embeded), published, rating, tags, views, share(link), comments, permalink(url)

* [http://www.metacafe.com/ Metacafe]
** [http://www.metacafe.com/watch/1932833/universe/ Video Example]
*** Information displayed: title, description, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments

* [http://www.atomfilms.com/ Atom Films]
** [http://www.atom.com/funny_videos/border_vcast_interview/ Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, tags, views, share(link), comments, contributors

* [http://www.veoh.com/ Veoh]
** [http://www.veoh.com/videos/v16297680ZFN5cMXb Video Example]
*** Information displayed: title, summary, creator, video(embeded), duration, published, download(enclosure), rating, tags, views, share(link), comments, permalink(url)

* [http://grouper.com/ Grouper] now [http://crackle.com/ Crackle]
** [http://crackle.com/c/Quantum_of_Solace/Quantum_Of_Solace/2327783#ml=o%3d12%26fpl%3d297691%26fx%3d Video Example]
*** Information displayed: title, description, creator, video(embeded), published, rating, views, comments, permalink(url)

* [http://revver.com/ Revver]
** [http://revver.com/video/1281276/beer-goggles-commercial/ Video Example]
*** Information displayed: title, summary, creator, video(embeded), published, download(enclosure), size, format, rating, share(link), comments, permalink(url)

==== Analysis of Video Sites ====

35 total examples Analysed

* title 100%
* video(embeded) 100%
* published 91.42%
* comments 88.57%
* tags 71.42%
* rating 65.71%
* summary 62.85%
* creator 60%
* share(link) 51.42%
* views 45.71%
* download(enclosure) 42.85%
* duration 31.42%
* permalink(url) 28.57%
* description 25.71%

other discovered elements less than 10%

* video size
* feed url
* preview image
* contributor/s

=== Photos ===
* A few photos online have region annotation and quoting. But as tools are developed that are usable for mass publishers, this will likely increase.
* Many videos have thumbnails that are jpgs, and are effectivly quotes of the video.
* Many videos use pictures and therefore the pictures themselves are quotes from the video.
* Most photos have the same elements as videos and audio, including quotes that are derived from the original photo.

==== Individual Publishing of Photos ====

* [http://blog.bouckenooghe.com/2005/09/01/em6-a-est-fache-avec-le-centimetre/ Blog A Brac » E=m6 a est fâché avec le centimètre - photo with annotated screen-caps]
** This example has a Title, Html URL, media URL, description or summary, creator, quotes and descriptions, tags/categories, and publish date and time. +200 across all individually blogged photos.

* [http://scribbling.net/projects/fotonotesrolloverviewer/fotonotesplugin.php?p=helicopterovernyc.jpg Scribbling.net implementation of Fotonotes Plugin demonstrating the fotonotes annotation tool for photos]
** This example has media url, quotes or "notes" and descriptions, creator. +200 across all individually blogged photos.

* [http://community.livejournal.com/boston_photos/ Boston photos]
** [http://www.bobspixels.com/view_album.php?album=2008/2008_10_31&photo=md_oct_31_2008_121452.jpg Photo Example]
*** Information displayed: title, summary, creator, photo, published, resolution, album

* [http://mute.rigent.com/ Mute]
** [http://mute.rigent.com/index.php?ladat=2008-11-03 Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://www.durhamtownship.com/ Durham township]
** [http://www.durhamtownship.com/blog-archives/002245.html Photo Example]
*** Information displayed: title, description, creator, photo, published, comments

* [http://blog.magnumphotos.com/ Magnum Photos]
** [http://blog.magnumphotos.com/2008/11/surfing_the_archive_a_contest.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights

* [http://www.boston.com/bigpicture/ Boston Big picture]
** [http://www.boston.com/bigpicture/2008/11/conflict_in_congo_refugees_on.html Photo Example]
*** Information displayed: title, description, creator, photo/s, published, comments, rights, share

* [http://amysteinphoto.blogspot.com/ Amy Stein Photo]
** [http://amysteinphoto.blogspot.com/2008/11/brand-new-funky-president.html Photo Example]
*** Information displayed: title, description, creator, photo, tag, published, comments, rights, share

* [http://blog.photoblogs.org/ Photoblogs Blog]
** [http://blog.photoblogs.org/2008/10/31/saturday-nights-alright-for-fighting-by-treeswing/ Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments

* [http://www.aminus3.com/ Aminus Photoblogs]
** [http://krikis.aminus3.com/image/2008-11-04.html Photo Example]
*** Information displayed: title, creator, photo, tag, published, comments, rights, exif

* [http://johnsfoto.blogspot.com/ Johns Foto]
** [http://johnsfoto.blogspot.com/2008/11/my-world-drammen-norway.html Photo Example]
*** Information displayed: title, description, creator, photo/s, tag, published, comments, rights

* For more work along the lines of 2d annotations, please see (and add to) [[photo-note-examples]].

==== Service publishing of photos ====

* [http://www.flickr.com/photos/500hats/50282408/ Flickr - Photo Sharing instance of a photo.]
** This example has a Title, Html URL, media URL, description or summary, quotes URLs and descriptions, licence, tags, upload time, playlist (set), license, creator, and other capture data. +millions across all hosters. Many photos are also part of a "set" or "viewlist." So the photo can be considered a quote of the set, or a piece of it. +millions of records.

* [http://www.webshots.com/ Webshots.]
** [http://www.webshots.com/g/32/579-sh/25695.html Photo Example.]
*** Information displayed: title, description, creator, photo, published, tag, comments, download, share, album

* [http://zooomr.com/ Zooomr - Photo sharing site]
** [http://www.zooomr.com/photos/flwrgrl/6168222/ Photo Example.]
*** Information displayed: title, creator, photo, published, tag, comments, download, share, location, rating, exif

* [http://www.deviantart.com Deviant Art]
** [http://littlemewhatever.deviantart.com/art/Autumn-Morning-102650017 Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, views, comments, file-size, resolution, download-count, download

* [http://moblog.co.uk Moblog]
** [http://moblog.net/view/861286/voted-bitches Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share

* [http://www.tabblo.com/studio Tabblo]
** [http://www.tabblo.com/studio/stories/view/1653958/?nextnav=recent Photo Example]
*** Information displayed: title, description, creator, photo, published, tag, comments, share, slides

* Twitpic
** [http://twitpic.com/6a4zlt Photo Example]

* [http://www.corbis.com Corbis Photograpy]
** [http://pro.corbis.com/popup/Enlargement.aspx?mediauids={59a81f5c-165d-4461-945c-702ecbf19f43} Photo Example]
*** Information displayed: title, summary, creator, photo, tag, file-size, slides, payment, rights, id

* [http://www.istockphoto.com istockphoto]
** [http://www.istockphoto.com/file_closeup.php?id=000004484543 Photo Example]
*** Information displayed: title, summary, creator, photo, tag, views, comments, file-size, resolution, slides, payment, rights, id

* [http://www.sxc.hu Stock.XCHNG]
** [http://www.sxc.hu/photo/478557 Photo Example]
*** Information displayed: title, creator, photo, tag, views, comments, file-size, print-size, resolution, slides, payment, rights, id, download-count, download, exif

* [http://www.photos.com/ Photos.com]
** [http://www.photos.com/en/search/close-up?oid=11525603&hoid=6cb716176348ec2870265408a3ac5d29 Photo Example]
*** Information displayed: title, description, photo, tag, resolution, slides, payment, rights, id

* [http://elfwood.lysator.liu.se/elfwood.pike Elfwood]
** [http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html Photo Example]
*** Information displayed: title, creator, description, photo, tag, comments, rights, technique, share

* [http://www.epilogue.net/cgi/database/art/editors.pl/ Epilogue]
** [http://www.epilogue.net/cgi/database/art/view.pl?id=117980&genre=2 Photo Example]
*** Information displayed: title, creator, description, photo, comments, rights, medium

* [http://ackegard.com/gallery/main.php Ackegard]
** [http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, resolution

* [http://www.caligari.com/Gallery/ImagesGallery/default.asp?Cate=GImages Caligari Images Gallery]
** [http://www.caligari.com/Gallery/ImagesGallery/2008/sep/winner.asp?img=3771&email=harri.pakarinen@gmail.com&name=Harri%20Pakarinen Photo Example]
*** Information displayed: creator, photo, contact

* [http://www.amateurillustrator.com/ Amateur Illustrator]
** [http://www.amateurillustrator.com/articles/?p=1191 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, comments, download, share

* [http://www.cgchannel.com/gallery/ CG channel]
** [http://www.cgchannel.com/gallery/viewimage.jsp?imgID=85 Photo Example]
*** Information displayed: title, creator, description, published, photo, comments, vote, rate, views, software

* [http://www.alrioart.com/ Alrioart]
** [http://alrioart.com/details.php?image_id=3246 Photo Example]
*** Information displayed: title, creator, description, published, photo, tag, views, file-size

* [http://www.freeart.org/ Freeart]
** [http://www.freeart.org/display.cgi?v=s&i=2 Photo Example]
*** Information displayed: title, creator, description, published, photo, rate, id

* [http://www.dreamstime.com/ Dreamstime]
** [http://www.dreamstime.com/family-image6933295 Photo Example]
*** Information displayed: title, description, creator, photo, tag, views, file-size, print-size, resolution, slides, payment, rights, id, download-count, download

==== Analysis of Photo Sites ====

30 total examples

* photo 100%
* creator 96.66%
* title 93.33%
* description 73.33%
* comments 70%
* tag 63.33%
* rights 43.33%
* resolution(screen) 23.33%
* slides(slide show) 23.33%
* download 20%
* file-size 20%
* views 20%
* file-size 20%
* summary 16.66%
* payment 16.66%
* id 13.33%

Other discovered properties occurring less than 10%

* download-count
* exif(extended information, camera, exposure time, etc)
* album(collection)
* print-size
* location(geo coordinates)
* rating
* technique(Artist style)
* software(Imaging application ie: photoshop)

=== Media comments ===

The following urls are examples of user/visitor comments about media items.

* http://ryanedit.blogspot.com/2006/01/light-water-music-2.html
** Information displayed: author, author-url, comment

* http://prototypen.com/blog/vjblog/archives/001318.html
** Information displayed: author, author-url, comment, published

* http://www.itsjerrytime.com/?p=89
** Information displayed: author, author-url, comment, published

* http://bottomunion.com/blog/?p=469
** Information displayed: author, author-url, comment, published

* http://www.rocketboom.com/rb_07_mar_26/
** Information displayed: author, author-url, comment, published, comments-link

* http://www.chesslodge.com/2007/03/chess-video-lesson-2/
** Information displayed: author, author-url, comment, published

* http://stevegarfield.blogs.com/videoblog/2007/04/sxsw_all_togeth.html
** Information displayed: author, author-url, comment, published

* http://blip.tv/file/1425655/
** Information displayed: author, author-url, comment, published

* http://uk.youtube.com/watch?v=KKTDRqQtPO8
** Information displayed: author, author-url, comment, published, reply-url, vote

* http://vimeo.com/162754
** Information displayed: author, author-url, comment, published

* http://www.dailymotion.com/commented-week/lang/en/video/x7a2my_lewis-hamilton-champion-f1-2008_sport
** Information displayed: author, author-url, comment, published

* http://www.nbc.com/Saturday_Night_Live/video/clips/mccain-qvc-open/805381/
** Information displayed: author, author-url, author-photo, comment, published

* http://www.accidenthash.com/2007/04/02/gray-wet-yuck-monday/
** Information displayed: author, author-url, comment, published, comment-link

* http://freakytrigger.co.uk/ft/2008/11/blondie-call-me/
** Information displayed: author, author-url, comment, published, comment-link

* http://www.scissorkick.com/2008/09/midnight-lab-band/
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html
** Information displayed: author, author-url, comment, published, comment-link

* http://www.arjanwrites.com/arjanwrites/2008/10/free-download-j.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://loki23.blogspot.com/2008/09/flower-electronics.html#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://videogum.com/archives/the-hunt-for-the-worst-movie-of-all-time/the-hunt-for-the-worst-movie-o-30_032141.html
** Information displayed: author, author-url, author-photo, comment, published, comment-link, vote, reply-url

* http://www.haloscan.com/comments/empirestatehuman/7424868678376349884/
** Information displayed: author, author-url, comment, published, comment-link, reply-link

* http://www.3hive.com/2008/10/1000_robata.php#comments
** Information displayed: author, author-url, comment, published, comment-link

* http://www.musicload.de/album/1884260_2/nik-p--dj-%C3%B6tzi/ein-stern-der-deinen-namen-tr%C3%A4gt/item.html
** Information displayed: author, comment, published, rating

* http://strongwordsinc.com/2007/05/31/episode-20-tranforming-you-into-stds-since-1983/#comments
** Information displayed: author, author-url, author-photo, comment, published, comment-link

* http://ackegard.com/gallery/v/campaigns/calipolis/LK03_Kyri_climbs.jpg.html?g2_imageViewsIndex=1
** Information displayed: author, comment, published

* http://www.elfwood.com/art/n/e/nelson/pixy.jpg.html#addnewcmt
** Information displayed: author, author-url, comment, published

==== Analysis of Media comments ====

25 examples

* author 100%
* comment 100%
* published 100%
* author-url 92%
* comment-link 40%
* author-photo 16%
* reply-url 12%

Other properties occuring less than 10%

* vote

== Notes on Existing Practices ==

Mary Hodder:
* We are finding at Dabble as we look at millions of user generated media records, that almost all have html and/or media urls, titles, uploader or creator, and at least a default licensing of Copyright. Most have tags whose functionality is made available through the hosting service (the richer the media, the more likely tagging goes toward 100% of the items), thumbnail URL(s), publishing date, and about 25% have quoting information of some sort (quotes of video or audio, and region quotes of photos).
* Tags apparently appear at the upload point on 61% of photos in Flickr, and within a short period, 80+% have tags. 12% of users in Flickr apparently tag photos other than their own.

Manu Sporny (on music):
* There is an increasing number of sites that link to different methods of acquiring content displayed on a web page. These may include links to high-quality, or full versins of the media being described on the page. The various options include: free, streaming with ads, one-time purchase, and rental.
* Summaries, long descriptions and reviews are also prevalent in some of the content.

Manu Sporny (on video):
* We should attempt to support the basic information on sites that have been operational for years such as IMDB and Rotten Tomatoes among others. These sites tend to have very detailed information on all things related to video and TV - other sites will follow their lead because their meta-data seems to be the most complete on the web - thus making every other site contain a sub-set of their meta-data.

== Next Steps ==
# Add more real-world, simple, minimal examples.
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.
# Start [[media-info-brainstorming]] based on examples.

== See Also ==
* [[media-metadata-examples]] - previous attempt to catalog and organize top down metadata systems generated by engineers and committees, as examples of elements, and includes formats which should be in a separate page. Useful as a source of research but this microformat needs to embrace the bottomup ways users are publishing photos, video and audio online.

{{Template:hmedia-related-pages}}

rel-author

2011-08-12T17:56:38Z

Singpolyma: /* query parameter alternative */ query params are not for the author's use

<entry-title>rel author</entry-title>
== Summary ==
rel="author" is for relating an article or post to a page or site representing its author, typically to give them credit for their work (or portions of it, like books, articles, blog posts etc).

E.g. a page or a post written by Erin could contain a link like:
<source lang=html4strict>
<a href="http://erin.example.com/" rel="author">Erin Smith</a>
</source>

The <code>rel="author"</code> attribute indicates that the destination of the link represents the author of the current page (or post).

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

=== Google ===
An interesting rel="author" implementation set of examples is brought up by Google in a video posted on Youtube:
* [http://www.youtube.com/watch?v=FgFb6Y-UJUI Authorship markup video] and the respective [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 implementation procedure].

== extensions ==
=== query parameter alternative ===
Google has proposed an alternate mechanism for specifying rel=author on sites/CMSs that don't permit authors to specify the rel attribute, using a query parameter added to the URL instead. e.g. the above example with query parameter:

<source lang=html4strict>
<a href="http://erin.example.com/?rel=author">Erin Smith</a>
</source>

This technique is explained in the following video:
* [http://www.youtube.com/watch?v=gG3Oh7Ues8A Authorship markup using URL parameters video] and the [http://www.google.com/support/webmasters/bin/answer.py?answer=1408986 new implementation procedure] with the help of Google Profile (and hopefully, this type of implementation can be used on any other personal BIO page of respective author).

** While I understand the motivation here, this is not a good idea. There will definitely be someone who has ?rel= as an actual query param meaning something in their app, and this will just break things. [[User:Singpolyma|Singpolyma]] 17:56, 12 August 2011 (UTC)

== see also ==
* [[rel-faq]]
* [[existing-rel-values]]

rel-home

2011-08-10T21:43:41Z

Singpolyma: /* use with rel-alternate */ quote the spec

<entry-title>rel="home"</entry-title>
{{DraftSpecification}}
__TOC__

== Draft Specification 2005-12-07 ==
=== Editor/Author ===
[http://dannyayers.com Danny Ayers]

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

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

== Abstract ==
Rel-Home is one of several [[MicroFormats]]. By adding <code>rel="home"</code> to a hyperlink, a page indicates that the destination of that hyperlink is the homepage of the site in which the current page appears. When the appropriate HTML Meta data profile is in use, the "home" type can be used alongside standard [http://www.w3.org/TR/html4/types.html#type-links Link Types].

Example usage :

<pre><nowiki>
<head>
...
<link href="http://technorati.com" rel="home" />
...
</head>
</nowiki></pre>

The rel value may also appear wherever an anchor link may appear, e.g.

<pre><nowiki>
<body>
...
<a href="http://technorati.com" rel="home">Home</a>
...
</body>
</nowiki></pre>

the author indicates that the linked page is the homepage of the site.

The linked page {{should}} exist. Use of an absolute URI is recommended.

== Scope ==
rel="home" is designed for site navigation purposes, as well as allowing some description of site structure to be derived from individual pages. Typical use might be in the archive pages of a weblog, pointing back to the front page.

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<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.
<dl>
<dt id="home">home</dt>
<dd>Indicates that the referred resource serves as the homepage,
of the site which includes the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

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

The following sites have implemented rel-home, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with rel-home, feel free to add it to the '''bottom''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://www.my-warehouse.de the my-Warehouse shopsystem] implements rel-home into the breadcrumb.
* http://chrisruppel.com uses rel-home as a link in the <head>
* [http://www.cleanertoday.com Cleaner Today] uses multiple implementations: 1) [http://www.cleanertoday.com/Moth-Traps-by-Catchmaster-s/85.htm Moth Trap] page uses rel-home in <head> 2) [http://www.cleanertoday.com/Spider-traps-s/86.htm Spider Traps] page uses rel="home" on Corner Logo Link & "Home" link in the footer.
* [http://www.jdclark.org/ www.jdclark.org] uses rel-home on virtually all web pages within the domain and its sub-domains (for example, please see [http://www.jdclark.org/card Jordan Clark's profile]).
* Tantek.com posts (e.g. [http://tantek.com/2011/220/b1/web-actions-a-new-building-block Web Actions: Identifying A New Building Block For The Web]) use rel="home" as part of the link to the site's alternate feed as such: <nowiki><link rel="home updates alternate" type="application/atom+xml" href="http://tantek.com/updates.atom" /></nowiki> to indicate that the link is an ''alternate'' for a page that is also the ''home'' for the current page, rather than an alternate for the current page.

== Implementations ==
This section is '''informative'''.
The following implementations have been developed which either generate or parse rel-home links.

''Ed. : links to follow''

* Opera browser supports rel="home"
* [http://cdn.mozdev.org/linkToolbar/ FireFox Link Toolbar] - need to confirm
* [https://addons.mozilla.org/firefox/1324/ cmSiteNavigation Toolbar] - Firefox Extension that supports rel="home" and rel="directory"

== References ==

=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax

=== Informative References ===
* [http://diveintoaccessibility.org/day_9_providing_additional_navigation_aids.html Dive Into Accessibility] (Mark Pilgrim)

''Ed. : need to track down previous discussions, e.g. re. Opera''

== Discussions ==

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

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

=== Brainstorming ===
If this section gets too large (and is not just incorporated into the draft), it can be moved to [[rel-home-brainstorming]].

==== use with rel-alternate ====
Many blog post permalink pages have feed autodiscovery links that link from the permalink page via a link element to the feed for the site using just rel="alternate".

This is semantically incorrect as the feed is an alternate for the *site*, not the permalink page.

rel="home" could (and should) be used with [[rel-alternate]] to link from a permalink page to the feed for the site (home page). e.g. on tantek.com permalink pages (e.g. [http://tantek.com/2011/220/b1/web-actions-a-new-building-block recent post]), here's a simplified version of the markup:
<source lang=html4strict>
<link rel="home alternate" type="application/atom+xml" href="../updates.atom" />
</source>

This way a feed reader / indexer / search engine knows that the link represents an ''alternate'' for the ''home'' page relative to the current page, not an alternate for the page itself.

There is one known exception which is that if the alternate link is a feed to the ''comments'' on that post, then that would make sense as an actual alternate representation of the post permalink page.

Implementations (consuming parsers) could thus treat these two types of 'alternate' links differently to provide the user a better experience, e.g. with separate buttons for:
* Subscribe to this site
* Subscribe to the comments on this post

FAQ (this might merit inclusion in [[rel-faq]]
<div class="discussion">
* Doesn't rel="home alternate" mean it's the home page ''and'' it's an alternate independently? (as asked [http://krijnhoetmer.nl/irc-logs/microformats/20110810#l-84], [https://twitter.com/tabatkins/status/101391569160114176])
** No. That's not [http://dev.w3.org/html5/spec/semantics.html#attr-link-rel how rel works]. Rel values combine. E.g. <code>[http://www.w3.org/TR/html4/present/styles.html#h-14.3.1 rel="alternate stylesheet"]</code> has worked this way for over a decade. Rel values also combine with other attributes, e.g. use <code>rel="alternate" media="handheld"</code> on a link to a separate mobile-specific version of a page. [[User:Tantek|Tantek]] 20:56, 10 August 2011 (UTC)
*** This seems to contradict the spec: "if a single link element has a rel attribute with the value next stylesheet, it creates both a hyperlink (for the next keyword) and an external resource link (for the stylesheet keyword)" implying that they are independant and not related. -- [[User:Singpolyma|Singpolyma]] 21:43, 10 August 2011 (UTC)
</div>

Discussion of this brainstorm:
<div class="discussion">
* +1 [[User:Tantek|Tantek]] - as [http://krijnhoetmer.nl/irc-logs/microformats/20110810#l-61 proposed/discussed in IRC]
* +1 [[User:Kevin Marks|Kevin Marks]] though need to check behaviour in browsers that support rel-home on link
* ...
</div>

[[Category:Draft Specifications]]
[[Category:rel-home]]

rel-up

2011-08-10T20:13:41Z

Singpolyma: list some implementations of rel-up

{{stub}}

== Implementations ==

* https://addons.mozilla.org/en-US/firefox/addon/link-widgets/
* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe

== See Also ==

* [[rel-next]]

rel-next

2011-08-10T20:06:49Z

Singpolyma: list some implementations of rel-next

{{stub}}

== Implementations ==

* https://addons.mozilla.org/en-US/firefox/addon/link-widgets/
* http://help.opera.com/Linux/9.50/en/toolbars.html
* http://userscripts.org/scripts/show/36837
* http://userscripts.org/scripts/show/23175
* https://chrome.google.com/webstore/detail/emepkgfiamgdjilgkacpciojagbolepb
* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe
* https://chrome.google.com/webstore/detail/pkjjfohgdkeomfgelibonoddaaioaopg

=== These add rel-next to pages that do not have them ===

* http://userscripts.org/scripts/show/56430
* http://userscripts.org/scripts/show/97109

languages-spoken-brainstorming

2011-06-30T15:24:52Z

Singpolyma: create note about ISO language codes

ISO language codes are very useful, but do we trust that to be a complete list? For example, Lojban uses "jbo" internally, but that's not an official language code yet.

languages-spoken-examples

2011-06-30T15:21:41Z

Singpolyma: add facebook as an example

== Facebook ==

<code><nowiki><img class="mrs fbProfileBylineIcon img" src="https://s-static.ak.facebook.com/rsrc.php/v1/yu/r/SA7oMHm2R-u.png" alt="" height="13" width="10">Knows English, French</code></nowiki>

poshformats

2011-02-25T15:01:31Z

Singpolyma: /* known poshformats */ added POSHstream as a known POSHformat

<entry-title>poshformats</entry-title>
<dfn style="font-style:italic;font-weight:bold">poshformats</dfn> are data formats constructed from the use of [[semantic class names]].

<dfn style="font-style:italic;font-weight:bold">[[microformats]]</dfn> are the proper subset of poshformats which have been developed via the microformats [[process]] and [[principles]].

== origin ==
Given that web designers have been making up their own controlled vocabularies for class names as part of [[POSH]] modern web design practices for quite some time, and that there continues to be a strong tendency for folks to want to invent their own a-priori formats by starting with a set of class names (rather than following the microformats [[process]]), it makes sense to provide a label for such class names.

[http://twitter.com/t/statuses/535911222 Coined] and [http://rbach.priv.at/Microformats/IRC/2007-12-26#T213017 further explained] on December 26th, 2007, the term "poshformats" distinguishes these one-off, ad-hoc or more informal class-name based formats efforts (based on long-standing modern web design [[POSH]] practices) from the more formally researched and documented microformats. Another way of describing the distinction is that microformats are the proper subset of poshformats which have been developed via the microformats [[process]] and [[principles]], rather than made-up a-priori.

== applicability ==
poshformats may only apply to the person who invented it, or a specific site of theirs, or maybe even just one web page.

== difference from microformats ==
If you want reusability, interoperability, etc., then you must follow the microformats principles and process which were specifically designed to produce more reusable and interoperable results.

== faq ==
=== difference between posh and poshformat ===
''What's the difference between merely using [[POSH]] in a document, and creating a poshformat?''
* When the author of that POSH declares it to be a "format" of some sort, then they've created a poshformat.
=== are xfn and xmdp poshformats ===
''Should xfn and xmdp be considered microformats created outside the microformats group, or poshformats with adoption and consensus similar to microformats?''
* [[XFN]] is a microformat by way of having followed (and frankly, inspired) the microformats principles and process. Lots of research was done in its development on both existing uses on the Web of relationship information (typically in blogs and blogrolls), and pre-existing relationship formats. XFN 1.0 was simplified down to the more common declared relationships found in the wild. XFN 1.1 was an iteration based up on real world use experience of XFN 1.0. [[XMDP]] on the other hand is more of a foundational technology, just as DTDs are a foundational technology for SGML, HTML, XML etc. XMDP does however follow a lot of the microformats principles as well.

== known poshformats ==
This section lists poshformats (often mistakenly called microformats, typically by their creators). Sorted alphabetically:

* [http://purl.org/stuff/hdoap/profile hDOAP]
* [http://hgrant.org/wiki/Main_Page hGrant]
* [http://www.socialtext.net/hrelease hRelease]
* [http://www.vitvar.com/blog/?p=64 hRESTS]
* [http://microid.org/ MicroID]
* [http://pavatar.com/spec/ Pavatar]
* [https://singpolyma.net/2009/05/poshstream-a-poshformat-profile-of-activitystreams/ POSHstream]

== see also ==
* [[POSH]]
* [[microdata]]
* [[microformats]]
* [[principles]]
* [[process]]

rev-made

2010-09-28T23:58:23Z

Singpolyma: notes about this being wrong and hcard being better

rev=made is a historical value used by browsers such as lynx to determine the email address of the web page owner/author. It is commonly (at least by links) only supported on the <nowiki><link/></nowiki> tag.

This is also, unfortunately, an example of the rev attribute being used wrong. Alice is not made by this page, but rather this page is made by Alice. rel=made or rev=made-by would be appropriate.

This content can be better got by using representative hcard.

== Example ==

<pre><nowiki><link rev="made" href="mailto:alice@example.com" title="Alice" /></nowiki></pre>

== References ==

* http://www.htmlcodetutorial.com/document/_LINK.html
* http://www.frontpagewebmaster.com/m_142732/tm.htm
* http://www.usask.ca/its/courses/cai/html/glossary/link.html

existing-rel-values

2010-09-28T23:54:43Z

Singpolyma: /* related */

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4 link type] and [http://www.w3.org/TR/grddl/ GRDDL] specs.
* [[xfn]] and other [[microformats]]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| [[rel-acquaintance|acquaintance]] || the person represented by the current document considers the person represented by the referenced document to be an acquaintance || [[XFN]]

|-
| [[rel-alternate|alternate]] || Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-appendix|appendix]]|| Refers to a document serving as an appendix in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-bookmark|bookmark]] || Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-chapter|chapter]] || Refers to a document serving as a chapter in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-child|child]] || the referenced person is a child of the person represented by the current document|| [[XFN]]

|-
| [[rel-colleague|colleague]] || the referenced person is a colleague of the person represented by the current document|| [[XFN]]

|-
| [[rel-contact|contact]] || the person represented by the current document considers the person represented by the referenced document to be a contact || [[XFN]]

|-
| [[rel-contents|contents]] || Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents"). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-copyright|copyright]] || Refers to a copyright statement for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-co-resident|co-resident]] || the referenced person lives in the same residence as the person represented by the current document|| [[XFN]]

|-
| [[rel-co-worker|co-worker]] || the referenced person is a co-worker of the person represented by the current document|| [[XFN]]

|-
| [[rel-crush|crush]] || this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)|| [[XFN]]

|-
| [[rel-date|date]] || this person considers the referenced person to be a date (i.e. is dating the referenced person)|| [[XFN]]

|-
| [[rel-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]

|-
| [[rel-glossary|glossary]]|| Refers to a document providing a glossary of terms that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-help|help]] || Refers to a document offering help (more information, links to other sources information, etc.) || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-index|index]] || Refers to a document providing an index for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-kin|kin]] || the referenced person is part of the extended family of the person represented by the current document|| [[XFN]]

|-
| [[rel-license|license]] || …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page. || [[rel-license]]

|-
| [[rel-me|me]] || the referenced document represents the same person as does the current document || [[XFN]]

|-
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]

|-
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]

|-
| [[rel-neighbor|neighbor]] || the referenced person lives nearby the person represented by the current document || [[XFN]]

|-
| [[rel-next|next]] || Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-nofollow|nofollow]] || 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). || [[rel-nofollow]]

|-
| [[rel-parent|parent]] || the referenced person is a parent of the person represented by the current document|| [[XFN]]

|-
| [[rel-prev|prev]]|| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous". || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-previous|previous]] || Synonym of <code>prev</code> || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-section|section]] || Refers to a document serving as a section in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sibling|sibling]] || the referenced person is a sibling of the person represented by the current document|| [[XFN]]

|-
| [[rel-spouse|spouse]] || the referenced person is a spouse of the person represented by the current document|| [[XFN]]

|-
| [[rel-start|start]] || Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-stylesheet|stylesheet]] || a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-subsection|subsection]] || Refers to a document serving as a subsection in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]

|-
|[[rel-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]

|-
|[[rel-toc|toc]] || Synonym of <code>contents</code> (from "Table Of Contents") || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-transformation|transformation]] || Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]] || [http://www.w3.org/TR/grddl/#transformation GRDDL spec]

|-
|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-product|product]] || … || [[product-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://www.monkinetic.com/2009/11/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||…||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-details|details]] || … || (seen on w3c.org news log in a "read more" permalink) || …

|-
| [[rel-EditURI|EditURI]] || … || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || …

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || … || HTML5

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-first|first]] || Indicates that the current document is a part of a series, and that the first document in the series is the referenced document. || … || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-lightbox|lightbox]] || … || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sidebar |sidebar ]] || Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). || || HTML5

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || …|| HTML5

|-
| [[rel-user|user]] || … || … || WCLR

|-
| [[rel-via|via]] || … || … || WCLR

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research why such values were omitted from latter specifications before using them. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

In general, you {{should not}} use any dropped values.

In addition, if any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) - has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped
|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown
|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown
|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown
|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown
|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown
|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown
|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown
|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown
|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown
|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown
|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown
|-
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown
|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown
|-
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown
|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown
|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown
|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown
|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown
|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown
|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown
|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown
|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown
|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||HTML3||unknown, but proposed for re-introduction in HTML5
|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown
|-
|}

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML4 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.

== tools ==
See [[implementations]].

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

existing-rel-values

2010-09-28T23:53:40Z

Singpolyma: /* related */

existing-rev-values

2010-09-28T23:52:57Z

Singpolyma:

* [[rev-made]]

== See Also ==

* [[existing-rel-values]]

existing-rev-values

2010-09-28T23:52:26Z

Singpolyma: New page: * rev-made

* [[rev-made]]

rev-made

2010-09-28T23:49:25Z

Singpolyma: rev=made initial description

rev=made is a historical value used by browsers such as lynx to determine the email address of the web page owner/author. It is commonly (at least by links) only supported on the <nowiki><link/></nowiki> tag.

== Example ==

<pre><nowiki><link rev="made" href="mailto:alice@example.com" title="Alice" /></nowiki></pre>

== References ==

* http://www.htmlcodetutorial.com/document/_LINK.html
* http://www.frontpagewebmaster.com/m_142732/tm.htm
* http://www.usask.ca/its/courses/cai/html/glossary/link.html

RelMeAuth

2010-04-23T13:54:55Z

Singpolyma: /* issues */ OAuth very unsuitable

[[RelMeAuth]] is a proposed open standard for using [[rel-me]] links to profiles on [[OAuth]] supporting services to authenticate via either those profiles or your own site.

<div class="vcard">
; Editor
: [[User:Tantek|Tantek Çelik]] (http://tantek.com/)
</div>

== support RelMeAuth ==
=== users ===
Want to use your own site to login to other sites? Here's all you have to do:

'''Just use [[rel-me|rel="me"]] on your personal site, and enter your personal site as your URL on other sites.'''

That's it! No odd new hidden meta tags or invisible XML side-files.

Slightly longer explanation:

'''1. Add [[rel-me|rel="me"]] links to your other profiles.'''

Add [[rel-me|rel="me"]] to links from your home page to your various profiles on other services.

'''2. Edit your other profiles to link back to your site.'''

Edit your other profiles and set their "home page" or "personal site" or "URL" field to your personal site.

Here's a [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_one_external_site|list of profile sites that have URL fields and support rel-me]].

'''3. There is no step 3. You're done.'''

==== examples in the wild ====
===== simple home page =====

Tantek's home page http://tantek.com/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="http://twitter.com/t">Twitter: @t</a></li>
<li><a rel="me" href="http://identi.ca/t">identi.ca: t</a></li>
</ul>
</source>

=== users with separate contact pages ===

'''But what if I prefer to have a separate contact or about page with my links to other profiles?'''

If you prefer to have a separate contact page that links to your other profiles, then

# add [[rel-me|rel="me"]] to links from your contact page to those other profiles
# add [[rel-me|rel="me"]] to the link from your home page to your contact page

==== more examples in the wild ====
===== separate contact page =====

Jeremy Keith's home page http://adactio.com/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="/journal/">Journal</a></li>
<li><a rel="me" href="/contact/">Contact</a></li>
</ul>
</source>

and then also:

http://adactio.com/journal/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="http://huffduffer.com/adactio/">Huffduffer</a></li>
<li><a rel="me" href="http://twitter.com/adactio/">Twitter</a></li>
<li><a rel="me" href="http://adactio.tumblr.com/">Tumblr</a></li>
<li><a rel="me" href="http://www.last.fm/user/adactio/">Last.fm</a></li>
<li><a rel="me" href="http://www.dopplr.com/traveller/adactio/public">Dopplr</a></li>
<li><a rel="me" href="http://www.vimeo.com/user196031">Vimeo</a></li>
<li><a rel="me" href="http://ffffound.com/home/adactio/found/">Ffffound</a></li>
<li><a rel="me" href="http://readernaut.com/adactio">Readernaut</a></li>
<li><a rel="me" href="http://97bottles.com/people/adactio/">97 Bottles</a></li>
</ul>
</source>

==== authentication preference ====
If you have a specific preference for what service(s) to authenticate with, just make sure that you list links to your profiles on those other services in preference order (on your home page or contact page as described above).

=== profile sites ===
Do you run a site with profiles?

Any social network site or similar site that has user profile pages should:
# provide a [[user interface]] for a user to enter and publicly publish a URL back to their home page
# publish a visible link with [[rel-me|rel="me"]] from user's profile page to their personal home page

Most [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_one_external_site|sites already do this]].

=== authentication sites ===
Do you run a site with user profiles that you want to let your users use to login to other sites?

In addition to supporting rel-me as [[#profile_sites|described above]]:

Any site that wants to allow users to login with their credentials from that site on 3rd party sites should:
# Support [[OAuth]] (2.0 even)
# Follow Twitter's conventions for:
#* endpoint paths and other protocol details
#* mimic Twitter's user interface for authentication flow (on both desktop and mobile - they've done a great job)

==== RelMeAuth providers ====
Sites that support both [[rel-me]] and are also [[OAuth]] providers:

* Twitter ([http://apiwiki.twitter.com/OAuth-Examples Twitter OAuth Examples])
* Google Profiles ([http://sites.google.com/site/oauthgoog/ Google OAuth documentation])
* Identi.ca (uses the same endpoint paths/details as Twitter)
* ...

=== sites needing a user login ===
Do you have a site and want to let users login with their own identity?

Any site that wants to let users login with their own identity should:
# provide a user interface for users to enter or choose their preferred online identity (e.g. their own URL)
# perform RelMeAuth authentication as described below

== how it works ==
=== summary algorithm ===
Summary of the RelMeAuth authentication algorithm

* input: a user identity (URL) to authenticate
* output: success or cancel authentication or no authenticatable URLs found

# start with a user identity URL (e.g from the UI, or from a cookie from previous login etc.)
# iterate through their outbound rel-me links on the user identity URL
## if
### a rel-me destination is up (HTTP Get succeeded, following any redirects)
### and rel-me links back to user identity URL
### and has OAuth endpoint
### then do OAuth authentication
### if authentication succeeded, you're done, the user has been been authenticated with the user identity URL, exit
### if it was rejected, the user canceled, thus cancel the entire authentication process, exit
## continue iteration with the next rel-me link if any
# no authenticatable URLs found (either none at all, or any provided had some other error, 404, no response, no OAuth endpoint, other OAuth error)

=== detailed algorithm ===
* input: a user identity (URL) to authenticate
* output: success or cancel authentication or no authenticatable URLs found

# start with a user identity URL (e.g from the UI, or from a cookie from previous login etc.)
# if the URL is an OAuth provider
# then try authenticating with it
## if it succeeds, exit
## if canceled, exit
## otherwise continue
# iterate through their outbound rel-me links on the user identity URL (first through direct rel-me links to external sites in order, then iterate through URLs deeper into the personal site in order, e.g. to a contacts page, and iterate through rel-me links from there to external sites in order)
## if
### a rel-me destination is up (HTTP Get succeeded, following any redirects)
### and rel-me links back to the user identity URL
### and has OAuth endpoint
### then do OAuth authentication
### if authentication succeeded, you're done, the user has been been authenticated with the user identity URL, exit
### if it was rejected, the user canceled, thus cancel the entire authentication process, exit
## continue iteration with the next rel-me link if any
# no authenticatable URLs found (either none at all, or any provided had some other error, 404, no response, no OAuth endpoint, other OAuth error)

== open source implementations ==
There are a couple of open source libraries that sites can use to implement RelMeAuth so their users can login using their own identities.

=== Python ===
* [http://github.com/ptarjan/relmeauth Python RelMeAuth] by Paul Tarjan and Jeff Lindsay

=== PHP ===
* [http://github.com/themattharris/relmeauth PHP RelMeAuth] by Matt Harris and Tantek Çelik

== issues ==
<div class="issues">
* How do you find the OAuth endpoint for any given user profile site/service? -[[User:Tantek|Tantek]]
** Use OAuth 2.0 discovery mechanism if supported
** Use a whitelist of provider site to OAuth endpoint
** Try the Twitter OAuth endpoint paths on other sites to see if they work - assuming that many OAuth providers will simply mimic Twitter's example as suggested.
*** This discovery by convention technique will work for example on:
**** http://identi.ca/
* How do you get an appID to use with any given site's OAuth? -[[User:Tantek|Tantek]]
** This appears to still be a manual process, per site, and thus a legitimate limitation of RelMeAuth in comparison to say [[OpenID]].
*** Some services are supporting appkey/secret pair anonymous/anonymous for mobile/desktop apps already. Unsure how popular this is [[User:Singpolyma|Singpolyma]] 13:51, 23 April 2010 (UTC)
* OAuth is for authorization, and as such gives the site I'm ident asserting to access to my account on the id service. This is very bad. Suggested solution: use OpenID instead. [[User:Singpolyma|Singpolyma]] 13:51, 23 April 2010 (UTC)
* After authing with OAuth, how do you know what user it is that auth'd? OAuth specifically does not tell you that information... [[User:Singpolyma|Singpolyma]] 13:54, 23 April 2010 (UTC)
</div>

== history ==
On 2010-02-01 Tantek [http://tantek.com/2010/032/t5/modest-proposal-authentication-oauth-twitter-rel-me introduced the basis for] and Jeff Lindsay [http://twitter.com/progrium/status/8521001762 suggested the name] for RelMeAuth.

In a follow-up Tantek [http://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication suggested the following simple protocol] for RelMeAuth:

<blockquote cite="http://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication">
RelMeAuth works for any #OAuth + rel-me site, and enables auto-fallback with use of alternate identities for authentication:<ol><li>user enters their site URL</li><li>iterate through their outbound rel-me links</li><li>if <ol><li>a rel-me destination is up, and</li><li> rel-me links back to user's site, and</li><li>has OAuth endpoint,</li></ol> then do OAuth authentication.</li></ol>Thus user links to their RelMeAuth profiles in preference order, and authentication code tries them in order. e.g. Twitter, Identi.ca, ... etc.</blockquote>

Later that evening Tantek, Jeff Lindsay, Paul Tarjan and others discussed RelMeAuth at the [[events/2010-02-02-weekly-dinner-mv|microformats dinner in Mountain View]] and afterwards Jeff and Paul implemented RelMeAuth in an open source Python library at Hacker Dojo and discussed/tested it in IRC.

http://krijnhoetmer.nl/irc-logs/microformats/20100203

Less than 24 hours from concept to open source implementation.

== articles posts comments ==
* 2010-03-03 [http://simonwillison.net/2010/Mar/2/bewildering/#c60551 Blaine Cook] comment
* 2010-02-16 [http://www.google.com/buzz/dclinton/HeMv1AQTXS8/Envisioning-decentralized-replies-and#1266371138608000 Tantek Çelik] comment re: user interface
* 2010-02-06 [http://aaronparecki.com/RelMeAuth Aaron Parecki] wiki page

== related ==
* [[rel-me]]
* [[OAuth]]
* [[hCard]]
* [[OpenID]]

RelMeAuth

2010-04-23T13:51:23Z

Singpolyma: /* issues */ anonymous/anonymous. use openid

[[RelMeAuth]] is a proposed open standard for using [[rel-me]] links to profiles on [[OAuth]] supporting services to authenticate via either those profiles or your own site.

<div class="vcard">
; Editor
: [[User:Tantek|Tantek Çelik]] (http://tantek.com/)
</div>

== support RelMeAuth ==
=== users ===
Want to use your own site to login to other sites? Here's all you have to do:

'''Just use [[rel-me|rel="me"]] on your personal site, and enter your personal site as your URL on other sites.'''

That's it! No odd new hidden meta tags or invisible XML side-files.

Slightly longer explanation:

'''1. Add [[rel-me|rel="me"]] links to your other profiles.'''

Add [[rel-me|rel="me"]] to links from your home page to your various profiles on other services.

'''2. Edit your other profiles to link back to your site.'''

Edit your other profiles and set their "home page" or "personal site" or "URL" field to your personal site.

Here's a [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_one_external_site|list of profile sites that have URL fields and support rel-me]].

'''3. There is no step 3. You're done.'''

==== examples in the wild ====
===== simple home page =====

Tantek's home page http://tantek.com/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="http://twitter.com/t">Twitter: @t</a></li>
<li><a rel="me" href="http://identi.ca/t">identi.ca: t</a></li>
</ul>
</source>

=== users with separate contact pages ===

'''But what if I prefer to have a separate contact or about page with my links to other profiles?'''

If you prefer to have a separate contact page that links to your other profiles, then

# add [[rel-me|rel="me"]] to links from your contact page to those other profiles
# add [[rel-me|rel="me"]] to the link from your home page to your contact page

==== more examples in the wild ====
===== separate contact page =====

Jeremy Keith's home page http://adactio.com/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="/journal/">Journal</a></li>
<li><a rel="me" href="/contact/">Contact</a></li>
</ul>
</source>

and then also:

http://adactio.com/journal/ has (simplified markup)
<source lang=html4strict>
<ul>
<li><a rel="me" href="http://huffduffer.com/adactio/">Huffduffer</a></li>
<li><a rel="me" href="http://twitter.com/adactio/">Twitter</a></li>
<li><a rel="me" href="http://adactio.tumblr.com/">Tumblr</a></li>
<li><a rel="me" href="http://www.last.fm/user/adactio/">Last.fm</a></li>
<li><a rel="me" href="http://www.dopplr.com/traveller/adactio/public">Dopplr</a></li>
<li><a rel="me" href="http://www.vimeo.com/user196031">Vimeo</a></li>
<li><a rel="me" href="http://ffffound.com/home/adactio/found/">Ffffound</a></li>
<li><a rel="me" href="http://readernaut.com/adactio">Readernaut</a></li>
<li><a rel="me" href="http://97bottles.com/people/adactio/">97 Bottles</a></li>
</ul>
</source>

==== authentication preference ====
If you have a specific preference for what service(s) to authenticate with, just make sure that you list links to your profiles on those other services in preference order (on your home page or contact page as described above).

=== profile sites ===
Do you run a site with profiles?

Any social network site or similar site that has user profile pages should:
# provide a [[user interface]] for a user to enter and publicly publish a URL back to their home page
# publish a visible link with [[rel-me|rel="me"]] from user's profile page to their personal home page

Most [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_one_external_site|sites already do this]].

=== authentication sites ===
Do you run a site with user profiles that you want to let your users use to login to other sites?

In addition to supporting rel-me as [[#profile_sites|described above]]:

Any site that wants to allow users to login with their credentials from that site on 3rd party sites should:
# Support [[OAuth]] (2.0 even)
# Follow Twitter's conventions for:
#* endpoint paths and other protocol details
#* mimic Twitter's user interface for authentication flow (on both desktop and mobile - they've done a great job)

==== RelMeAuth providers ====
Sites that support both [[rel-me]] and are also [[OAuth]] providers:

* Twitter ([http://apiwiki.twitter.com/OAuth-Examples Twitter OAuth Examples])
* Google Profiles ([http://sites.google.com/site/oauthgoog/ Google OAuth documentation])
* Identi.ca (uses the same endpoint paths/details as Twitter)
* ...

=== sites needing a user login ===
Do you have a site and want to let users login with their own identity?

Any site that wants to let users login with their own identity should:
# provide a user interface for users to enter or choose their preferred online identity (e.g. their own URL)
# perform RelMeAuth authentication as described below

== how it works ==
=== summary algorithm ===
Summary of the RelMeAuth authentication algorithm

* input: a user identity (URL) to authenticate
* output: success or cancel authentication or no authenticatable URLs found

# start with a user identity URL (e.g from the UI, or from a cookie from previous login etc.)
# iterate through their outbound rel-me links on the user identity URL
## if
### a rel-me destination is up (HTTP Get succeeded, following any redirects)
### and rel-me links back to user identity URL
### and has OAuth endpoint
### then do OAuth authentication
### if authentication succeeded, you're done, the user has been been authenticated with the user identity URL, exit
### if it was rejected, the user canceled, thus cancel the entire authentication process, exit
## continue iteration with the next rel-me link if any
# no authenticatable URLs found (either none at all, or any provided had some other error, 404, no response, no OAuth endpoint, other OAuth error)

=== detailed algorithm ===
* input: a user identity (URL) to authenticate
* output: success or cancel authentication or no authenticatable URLs found

# start with a user identity URL (e.g from the UI, or from a cookie from previous login etc.)
# if the URL is an OAuth provider
# then try authenticating with it
## if it succeeds, exit
## if canceled, exit
## otherwise continue
# iterate through their outbound rel-me links on the user identity URL (first through direct rel-me links to external sites in order, then iterate through URLs deeper into the personal site in order, e.g. to a contacts page, and iterate through rel-me links from there to external sites in order)
## if
### a rel-me destination is up (HTTP Get succeeded, following any redirects)
### and rel-me links back to the user identity URL
### and has OAuth endpoint
### then do OAuth authentication
### if authentication succeeded, you're done, the user has been been authenticated with the user identity URL, exit
### if it was rejected, the user canceled, thus cancel the entire authentication process, exit
## continue iteration with the next rel-me link if any
# no authenticatable URLs found (either none at all, or any provided had some other error, 404, no response, no OAuth endpoint, other OAuth error)

== open source implementations ==
There are a couple of open source libraries that sites can use to implement RelMeAuth so their users can login using their own identities.

=== Python ===
* [http://github.com/ptarjan/relmeauth Python RelMeAuth] by Paul Tarjan and Jeff Lindsay

=== PHP ===
* [http://github.com/themattharris/relmeauth PHP RelMeAuth] by Matt Harris and Tantek Çelik

== issues ==
<div class="issues">
* How do you find the OAuth endpoint for any given user profile site/service? -[[User:Tantek|Tantek]]
** Use OAuth 2.0 discovery mechanism if supported
** Use a whitelist of provider site to OAuth endpoint
** Try the Twitter OAuth endpoint paths on other sites to see if they work - assuming that many OAuth providers will simply mimic Twitter's example as suggested.
*** This discovery by convention technique will work for example on:
**** http://identi.ca/
* How do you get an appID to use with any given site's OAuth? -[[User:Tantek|Tantek]]
** This appears to still be a manual process, per site, and thus a legitimate limitation of RelMeAuth in comparison to say [[OpenID]].
*** Some services are supporting appkey/secret pair anonymous/anonymous for mobile/desktop apps already. Unsure how popular this is [[User:Singpolyma|Singpolyma]] 13:51, 23 April 2010 (UTC)
* OAuth is for authorization, and as such gives the site I'm ident asserting to access to my account on the id service. This is very bad. Suggested solution: use OpenID instead. [[User:Singpolyma|Singpolyma]] 13:51, 23 April 2010 (UTC)
</div>

== history ==
On 2010-02-01 Tantek [http://tantek.com/2010/032/t5/modest-proposal-authentication-oauth-twitter-rel-me introduced the basis for] and Jeff Lindsay [http://twitter.com/progrium/status/8521001762 suggested the name] for RelMeAuth.

In a follow-up Tantek [http://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication suggested the following simple protocol] for RelMeAuth:

<blockquote cite="http://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication">
RelMeAuth works for any #OAuth + rel-me site, and enables auto-fallback with use of alternate identities for authentication:<ol><li>user enters their site URL</li><li>iterate through their outbound rel-me links</li><li>if <ol><li>a rel-me destination is up, and</li><li> rel-me links back to user's site, and</li><li>has OAuth endpoint,</li></ol> then do OAuth authentication.</li></ol>Thus user links to their RelMeAuth profiles in preference order, and authentication code tries them in order. e.g. Twitter, Identi.ca, ... etc.</blockquote>

Later that evening Tantek, Jeff Lindsay, Paul Tarjan and others discussed RelMeAuth at the [[events/2010-02-02-weekly-dinner-mv|microformats dinner in Mountain View]] and afterwards Jeff and Paul implemented RelMeAuth in an open source Python library at Hacker Dojo and discussed/tested it in IRC.

http://krijnhoetmer.nl/irc-logs/microformats/20100203

Less than 24 hours from concept to open source implementation.

== articles posts comments ==
* 2010-03-03 [http://simonwillison.net/2010/Mar/2/bewildering/#c60551 Blaine Cook] comment
* 2010-02-16 [http://www.google.com/buzz/dclinton/HeMv1AQTXS8/Envisioning-decentralized-replies-and#1266371138608000 Tantek Çelik] comment re: user interface
* 2010-02-06 [http://aaronparecki.com/RelMeAuth Aaron Parecki] wiki page

== related ==
* [[rel-me]]
* [[OAuth]]
* [[hCard]]
* [[OpenID]]

hatom-issues

2010-03-20T22:40:58Z

Singpolyma: <time> element useage

<entry-title> hAtom issues </entry-title>
These are externally raised issues about [[hAtom]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hatom-faq|hAtom FAQ]] and the [[hatom-issues-resolved|hAtom resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

== closed issues ==
See: [[hatom-issues-closed]]

== resolved issues ==
See: [[hatom-issues-resolved]]

== issues ==
Please add new issues to the '''bottom''' of the list by copy and pasting the [[#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2010===
==== No defined parsing rule for <code>updated</code> timestamps in <code>ins</code>elements ====
* {{OpenIssue}} 2010-01-20 raised by [[User:BenWard|BenWard]]
*# hAtom includes the <code>updated</code> property for the last modification/revision date of an entry. HTML already has an <code>ins</code> element for marking up inserted changes to text, and that element has a <code>datetime</code> attribute, to document the date and time of the change. Currently, hAtom and microformats have no model for parsing the data from that <code>datetime</code> attribute, but the document semantics suggest it would be an appropriate source for the <code>updated</code> property. Example: <http://blog.benward.me/post/250674456>
*#* Proposed resolution. Document a parsing rule for the <code>ins</code> element, stating that for an <code>ins</code> (or <code>del</code>) element with class of <code>updated</code>, the value of the <code>datetime</code> attribute should be used as the value.
*#** +1 This sounds like a good idea and something worthy of being incorporated into [[hcard-parsing#more_semantic_exceptions]] (which is where the core of generic microformat parsing is currently documented) for special handling for all datetime properties. [[User:Tantek|Tantek]] 17:43, 21 January 2010 (UTC)
*#* Proposed extended resolution: As well as the above explicit parsing rule, an implication parsing rule stating that where <code>update</code> is not explicitly marked up, the parser may aggregate all <code>ins</code> and <code>del</code> elements in the <code>hentry</code>, and use the most recent <code>datetime</code> attribute content as the <code>updated</code> value.
*#** +1 Brilliant. Indeed right now 'updated', if missing, is implied from the 'published' property. Suggested change to that rule (incorporating your proposal) : if 'updated' is missing, use the latest in time value of: the 'published' property value, and the 'datetime' attributes of all ins and del elements inside the hentry. [[User:Tantek|Tantek]] 17:43, 21 January 2010 (UTC)

<div class="hentry">
{{OpenIssue}}

2010-03-20
raised by [[User:Singpolyma|Singpolyma]]

<div class="entry-content discussion issues">
* Should we talk about parsing of <time> element?. I use this element to mark up published on my blog. It is not supported by any implementation that I know of. Should implementors be encouraged to add this? Should the spec talk about it as an alternative to datetime-design-pattern? That page currently says to check the hcal issues, but there is nothing there about it.
</div>
</div>

===2009===
==== too many required hentry properties ====
* {{OpenIssue}} 2009-05-26 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 requires numerous properties for an hentry (often based directly on required elements from the Atom standard). Given the broad variety of situations that hAtom is used in content, many (or even most) of these properties are not already specified in such content, and thus it is poor methodology to require them because there is a good chance (experience has shown) either (a) the content author will ignore the requirement, or (b) will make something up to satisfy the requirement. A few similar/overlapping/sub-issues are noted below (e.g. [[#Author|author is required]], and not always available).
*#* Proposed resolution. Make nearly all hentry properties "optional" in hAtom 0.2. Consider keeping at most only one required property, perhaps "updated" - that is, if there is no date of update/publication in the content you are trying to mark up, then perhaps it doesn't make sense to mark up that content with hAtom, since hAtom is for episodic, time-based/stamped content.
*#** consider pattern abstraction: all microformats should minimize "required" properties for the same reason, and perhaps ''only'' require at most a single property which is indicative of what that microformat is for, that is, if the author does not publish that one required property, then perhaps they should not be using the microformat that requires that one property.
*#* I have the same problem. I'm collecting various feeds to analyse them. The sources are often RSS 0.9, but I want to put the results into an Atom feed. --[[User:Simon Brodtmann|Simon Brodtmann]] 00:51, 1 July 2009 (UTC)
*#** entry:author should be optional and could be either a hCard or a string
*#** entry lacks a [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.category category] and it shuld either use rel-tag or just be a string
* 2009-07-18 [[User:DavidJanes]] I would like to break this into a separate issue for each currently required element, as we're likely to have to define defaulting rules
* 2009-07-21 [[User:TobyInk|TobyInk]]: Why not have three levels of property: ''required'', ''recommended'' and ''optional''. There would be as few as possible ''required'' properties. Any properties which are needed to create a conformant application/atom+xml feed would be ''recommended''. Everything else would be ''optional''.'
** 2009-07-02 [[User:DavidJanes]] why not then use the RFC MUST, SHOULD and MAY terminology? I think this is a good idea though.
** 2009-09-03 [[User:Chris Cressman|Chris Cressman]] +1 to the idea of property "levels" and reusing RFC terminology.

==== entry-title optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]] but not recommended.
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model value should be
*** the empty string
**** +1 [[User:DavidJanes]]
**** -1 [[User:WebOrganics|Martin McEvoy]]
*** the value should not be blank.
**** +1 [[User:WebOrganics|Martin McEvoy]] see: [http://www.atomenabled.org/developers/syndication/#requiredEntryElements Required Entry Elements] from Atom Enabled.
**** [[User:DavidJanes]] what should it be then, if physically representing it is optional? Since Atom makes this a SHOULD and not a MUST (I'm not shouting, just following RFC convention), and we're assuming there's a good reason for the entry-title not to be present in the first place, why not an empty string?
***** [[User:WebOrganics|Martin McEvoy]] entry:title is a required attribute of atom at both feed and entry level, in both instances it says "Contains a human readable title" (a requirement) an empty string is not anything human readable (personal oppinion), maybe hAtom 0.2 should only recommend that the value of entry-title "should" not be an empty string.
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:WebOrganics|Martin McEvoy]]

==== updated optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] ... the demand for optionality of the issue is high (cf the microsoft web clips) and if it remains required we're just going to reinvent hAtom without this element
*** +1 [[User:Chris Cressman|Chris Cressman]] Agree there is demand for optionality. This requirement has previously deterred me from using hAtom.
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** the page creation date
**** +1 [[User:DavidJanes]]
**** +1 [[User:Chris Cressman|Chris Cressman]]
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:Chris Cressman|Chris Cressman]]

==== author optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] for the same reason 'updated' should be optional: we'll just reinvent hAtom slightly differently otherwise
*** +1 [[User:Chris Cressman|Chris Cressman]] Same reason as 'updated' above.
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** "anonymous" (somewhat like [[hreview]]), except not explicit
**** +0.5 [[User:DavidJanes]]
**** 0 [[User:Chris Cressman|Chris Cressman]] Using a blog post as an example, I can determine the author from surrounding context. 'Anonymous' doesn't seem like an acceptable solution. However, I don't have the technical expertise to create a better solution and would be willing to accept 'anonymous'.
*** make this implementation defined
*** something constructed from the page's URL & other information
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:Chris Cressman|Chris Cressman]]

=== 2008 ===
==== add url property to hentry ====
* {{OpenIssue}} 2008-09-10 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 uses [[rel-bookmark]] for permalinks. Permalinks may not always be hyperlinks or hyperlinkable. Thus I propose we re-use the <code>url</code> property (from [[hCard]], [[hCalendar]], [[hReview]], etc.) as a sub-property of the <code>hentry</code> property/container/root.
*#* Proposed resolution. Add "url" sub-property to "hentry" in hAtom 0.2.
*# {{ToDo}} can anyone provide examples where this would be used? [[User:DavidJanes]]

==== misuse of address element ====
* {{OpenIssue}} 2008-06-07 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 says "an Entry Author element SHOULD be encoded in an <code><address></code> element" and "find the Nearest In Parent <code><address></code> element(s) with class name author and that is/are a valid hCard" - this is a misuse of the address element. The address element means the ''contact'' for the page or major portion thereof (see [[hcard-faq#Should_I_use_ADDRESS_for_hCards|hCard FAQ: Should I use ADDRESS for hCards]]), which ''may'' also be the ''author'' but is not necessarily. See [[hcards-and-pages]] for more details on this semantic distinction.
*#* Proposed resolution: Eliminate all requirements and recommended use of the <code><address></code> element from hAtom.
*#** +1 --[[User:Csarven|Sarven Capadisli]] 11:57, 11 Nov 2008 (PST)
*#** +1 [[User:DavidJanes]]
*#** +1 [[User:Chris Cressman|Chris Cressman]] Prefer microformat solutions that don't dictate specific elements.
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:Chris Cressman|Chris Cressman]]

=== 2007 ===
==== marking up comments ====
* {{OpenIssue}} 2007-11-25 raised by [http://www.wirewd.com/ Ken Wronkiewicz].
*# There's no currently defined way to exactly handle threaded discussions. I think this is quite useful to have.
*#* The prior art is RFC [http://tools.ietf.org/html/rfc4685 4864]. The microformat solution should map fairly cleanly to this.
* include in hAtom 0.2
** -1 [[User:DavidJanes]] I think hAtom Comments should be a separate spec
*** +1 to David's -1. [[User:TobyInk|TobyInk]] They're in a separate RFC, so should be separate to hAtom too. That said, it would be nice if hAtom had a clear, documented mechanism for creating extensions.
** +1 [[User:Singpolyma|Singpolyma]] Comments are the important "next step" for hAtom. The proposal I've seen that I most liked was embedding an hfeed in an hentry.
*** [[User:DavidJanes]] would you look to explicitly write out that proposal here (or in a new section); this is my preferred solution too, but there's another proposal on the table for doing this too

==== atom:category scheme ====
* {{OpenIssue}} 2007-06-01 raised by [http://theryanking.com/ Ryan King].
*# ''[[rel-tag#Tag_Spaces|rel-tag tagspaces]] should map to atom:category schemes''
*#* hAtom already defines how to map term and label. It seems that the tagspace can easily map to scheme
*# {{ToDo}} can we get a real-world example mapping of this? [[User:DavidJanes]]

=== 2006 ===
====Geo====
* {{OpenIssue}} 2006-02-03 raised by [[BrianSuda]]
** We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
** +1 [[User:DavidJanes]] - this is just making explicit a particular composition. is it not? Also: if there's a geo in a hfeed (outside of hentry), should it be considered to apply to all entries?
** +1 [[User:Chris Cressman|Chris Cressman]]
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:Chris Cressman|Chris Cressman]]

==== Relationship of rel-bookmark to url+uid ====
The concept of permalink is available in hCard and hCalendar as the classes url and uid. This combination matches the permalink semantics by indicating that the url should be derefenced to find a more dynamic or up-to-date version of the content, and that that url is a stable unique id that can be used to identify the content.

hAtom 0.1 uses rel-bookmark for the permalink concept. The current state of [[uid-brainstorming]] indicates that the [[hCard]] and [[hCalendar]] permalink concept is likely to be used in subsequent microformats. It may be important to reconcile hAtom with that trajectory. Possible reconcilliations include:

1) To leave things as they are. The two permalink concepts are to be kept separate.

2) Treat the two concepts as equivalent. Allow both in hAtom, and consider allowing both in other formats. eg <a rel="bookmark" href="http://example.com/"> would fill out uid and url values if they are not supplied explicitly.

3) Choose one over the other for hAtom and perhaps for future microformats also. "url uid" allows for some greater freedom (uid can be pointed at a non-url uid), but it is unclear at this stage whether that freedom is warranted or advisable to permit.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] (let's wait for resolution elsewhere, also would need real world examples)
** -1 [[User:Singpolyma|Singpolyma]]

==== Datetime format (atom:updated and atom:published) ====
* 2006-05-23 raised by [[User:RobertBachmann|Robert Bachmann]]
** Atom requires the use RFC3339 datetimes, while hAtom 0.1 does not specify which datetime formats may be used.
*** ACCEPTED FAQ - hAtom references datetime-design-pattern, which discusses which date format to use
** 2009-07-20 [[User:DavidJanes]] {{ToDo}} is this moot? can we move this to resolved?

==== Feed id (atom:id) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
*# atom:id is required for atom:feed. Thus it should be available in hAtom to.

It is suggested the Feed permalink should be used as the feed ID, however a piece by Mark Pilgrim (http://diveintomark.org/archives/2004/05/28/howto-atom-id) makes arguments against using permalinks and in favour of Tag URIs.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] not enough development of these ideas yes

==== Feed permalink (atom:permalink) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules:
**# a Feed Permalink element is identified by [[rel-bookmark]] at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed <del>SHOULD</del><ins>MAY</ins> have a Feed Permalink
**# a Feed Permalink element represents the concept of an Atom link in a feed.
**# if the Feed Permalink is missing, use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI
** 2006-04-03 [[User:ChrisCasciano|ChrisCasciano]] - I'm not sure that having a rel-boomkark-able link element at the feed level / to designate a feed in an html page separate for the other content is anything close to normal usage on the web, so I'd be very hesitant on suggesting this element "SHOULD" exist. I'm also curious when this element would link to anything but the current page (or some element on the current page) for this to be useful in the context of the HTML doc. I think taking the "id" on the feed is a more workable solution in most cases.
** 2006-04-03 [[User:RobertBachmann|Robert Bachmann]]: I've replaced "SHOULD" with "MAY".
** 2006-04-24 [[User:RobertBachmann|Robert Bachmann]]: Maybe we could simplify my proposal to:
*** "''Use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI''"
*** IMO this would be good enough for at least 80% of the cases.
** 2006-04-12 [[User:DavidJanes]]: {{ToDo}} can we find an example of this in the wild and if so we should add it to the -examples page.
** [[User:Singpolyma|singpolyma]] 00:05, 13 Apr 2006 (PDT) : since the link is going to be pointing to the home page for the item wouldn't [[rel-home]] make more sense? That's what I'm using in the XOXO Blog Format and my reasoning was that if hAtom ever defined this rel=home made the most sense for what you would add, because the feed's link is not to a part of the site by to the home of the site.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] not enough development of these ideas yes

==== Feed updated (atom:updated) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:updated is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# The Feed Updated element is identified by the class name <code>updated</code> at the feed level (inside a Feed element but not inside an Entry element)
**# If no element with the class name <code>updated</code> is present, use the youngest <code>updated</code> from the feed's entries.
** 2006-04-12 [[User:DavidJanes]] I like this. And the definition of "feed level"
** 2007-06-20 [[User:MikeKaply]] The "youngest" thing is a really bad idea. If a page has 100 hAtom entries, a parser would have to go through all 100 looking for a low date. That's crazy.
*** 2008-03-20 [[User:TobyInk]] Not crazy at all. I've just implemented an hAtom to Atom converter and I do precisely this. Most (useful) hAtom parsers will "go through all 100 entries" anyway, won't they? So why not look for the youngest updated date as part of that loop. The only slight annoyance is that in RFC 4287, the <atom:updated> element must occur before the first <atom:entry> element -- this is easily solved by inserting a placeholder <atom:updated> element, looping through the entries and then going back and filling in the date. This is really, really, '''not''' a difficult thing to implement.

* include in hAtom 0.2
** +0.5 [[User:DavidJanes]]

==== Feed title (atom:title) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:title is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# a Feed Title element is identified by the class name <code><del>entry</del><ins>feed</ins>-title</code>
**# a Feed SHOULD have an Feed Title
**# a Feed Title element represents the concept of an Atom feed title
**# if the Feed Title is missing, use
**#* <del>the first <code><h#></code> element in the Feed, or</del>
**#* the <code><title></code> of the page, or
**#* assume it is the empty string
** 2006-04-01 [[User:ChrisCasciano|ChrisCasciano]] - I think that the fall back to using the first h# on the page is dangerous.. depending on the pge it may be something that changes often (first h# is a post title) or is otherwise ambiguous. I would think using <code><title></code> before h# would be prefered if not the most common desire of the page author.
** 2006-04-05 [[User:RobertBachmann|Robert Bachmann]]: Okay. Deleted "the first <code><h#></code> element in the Feed, or"
** 2006-04-12 [[User:DavidJanes]] Note also in support of this decision that many blogs use <code><h#></code> to encode the date for a group of postings
** 2006-04-12 [[User:DavidJanes]]: why <code>entry-title</code> for the feed title. Why not <code>fn</code> or <code>feed-title</code>?
** 2006-04-12 [[User:RobertBachmann|Robert Bachmann]]: Sorry, this was a "copy & paste" mistake. Fixed now.
** 2007-02-26 [[User:MikeKaply|Mike Kaply]]: I think a feed title should be mandatory if an hfeed is present. If you have multiple feeds on a page, there is no way in a user interface to distinguish between different feeds.

==== Feed author and Entry author (atom:author) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules for Feed author:
**# a Feed Author element is represented by class name <code>author</code> at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed Author element represents the concept of a Atom author
**# a Feed Author element MUST be encoded in a [[hcard|hCard]]
**# a Feed Author element SHOULD be encoded in a <code><address></code> element
**# a Feed MAY have more than one Feed Author elements
**# if the Feed 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 <del>the Feed is invalid hAtom</del> <ins>there is no Feed Author</ins>
** I'm proposing the following rules for entry author:
**# an Entry Author element is represented by class name <code>author</code>
**# an Entry Author element represents the concept of an 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
**#<del> If a Feed has no Feed author each Entry MUST have at least one Entry Author element</del>
**# <ins>If an Entry is enclosed by a Feed and this Feed has no Feed author, each Entry MUST have at least one Entry Author element. If an Entry is not enclosed by a Feed and has no Entry Author:
**#* 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</ins>
**# an Entry MAY have more than one Entry Author elements
** [[User:Singpolyma|singpolyma]] 00:11, 13 Apr 2006 (PDT) : feed should not be invalid hAtom if feed-level has no author -- it should be invalid if feed-level has no author AND one or more entries have no author. Also, one or more entries may be missing an author IF feed-level has an author.
** 2006-04-17 [[User:RobertBachmann|Robert Bachmann]]: I replaced "the Feed is invalid hAtom" with "there is no Feed Author"

==== Entry id (atom:id) ====
* {{OpenIssue}}2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:id is required for atom:entry. Thus it should be available in hAtom to. The Entry permalink should be used as the entry id.
** --[[User:Federico|Federico]] 19:52, 25 Apr 2006 (PDT): I would add "Only if the id attribute is not defined for the element that contains the entry". The id attribute can be a tag uri. If you use always use the Entry permalink as the entry id and the Atom feed uses tag uris, you would end with two different ids for the same entry.
** 2006-12-31 response by [[User:ComputerKid|Emanla Eraton]] No, it shouldn't be a permalink. It should be a "tag:" id for entries.
** 2007-06-06 [[RyanKing]] - the syntax of tag URIs and html id attributes are incompatible. HTML disallows forward-slash (/) in ids [http://www.w3.org/TR/html401/types.html#type-name], while tag URIs require them [http://www.faqs.org/rfcs/rfc4151.html].

==== Author ====
===== author as an hcard is too much to require =====
The following 3 items were extracted from the conversation starting on irc with [http://rbach.priv.at/Microformats-IRC/2006-03-24#T152248 logs available starting around here]

* [[User:Fil|Fil]] If, for example, you are programming an "aggregator" of news syndicated from many sources like in [http://sedna.spip.org/sedna/ Sedna], chances are that you don't control what "authors" look like; they can be nicely microformated (if coming from an mf-enabled system), but most probably they will be internally represented by a string that contains, in some random order, a name, and/or an email, and so on. If you want to pass on this information in an hAtom feed, you can't possibly reformat it to an hCard. But you still want to pass it on in a <div class="author"> element.
** [[Tantek]] I don't believe the "can't possibly" statement. Please provide a URL to a concrete example that you think you can't possibly reformat into an hCard so we can all take a look.
** [[User:ChrisCasciano|ChrisCasciano]] details of Fil's extraction [http://rbach.priv.at/Microformats-IRC/2006-03-24#T153453 in irc logs] including sting data passed to his app in the form of "Béatrice XXXXXXX beatrice.xxxxxx@@zzzzzzzzz.com"
** [[User:Fil|Fil]] the example url was given up there (Sedna); note that the author information comes from syndication links; nobody is going to edit them to outline what is the name, what is the email and so on, as everything is flowing through automatically... so here the "author" data is dirty, and will not be cleaned into an hCard. We can force it to be in an hCard but it will be meaningless if the source (original data) wasn't built on an mf-enabled software.

* [[pnhChris]] i don't disagree.. the field often comes from places too dumb to follow these rules well; even cases like wordpress that allow users to present their name 1 of 6 or 8 difference ways (from username to LF, FN) .. its not just writing a template to output as hatom at that point... you have to go further upstream where the string to be displayed is chosen .. I also think its pointless to have 10 vcards on the same page whose only data is a generic name like "Chris"
** [[Tantek]] 10 vcards that are the same is pointless yes, but identifying who the author of 10 posts are is not pointless - that's the difference.
** [[User:ChrisCasciano|ChrisCasciano]] Agreed, but I still have concerns that "author" in hAtom does not always make for good hCards, though the situations where it does is optimal. My comments in the conversation were old comments I've made before over concerns and hardships or the lack of desire to make crappy data more portable, in neither of these cases do I think my two comments alone provide reasons to make change from the hAtom 0.1 spec
***[[User:Phae|Frances]] - Just thought I'd mention a scenario I have where the author of an entry does make a pretty useless vCard - the author in each case is an entire team ("creative team", "technical department") etc., rather than a specific, identifiable, person. Some use may be regained when URL to specific team/information is included, in this circumstance.
****[[User:TobyInk]] - A vCard (thus an hCard) does not have to represent a person -- it could represent an organisation, or a department or team.
* [[User:Fil|Fil]] for the moment, to comply losely with hAtom 0.1, I will use <code><nowiki>My Name</nowiki></code> ; but it's not good
** [[Tantek]] You can actually simplify that (one fewer span) with: <code><nowiki>My Name</nowiki></code>

* require author as [[hCard]] (i.e. no change from 0.1)
** +2 [[User:DavidJanes]]

==== Entry source (atom:source) ====
* raised by [[User:Kevin Marks|Kevin Marks]]
** When defining hAtom 0.1, atom:source was omitted. We should consider adding this back in as a useful element for providing citations of composite feeds.
*** 2009-07-20 [[User:DavidJanes]] {{ToDo}} we need an example of how this would look in the real world

== Other Questions and Issues ==
General comments, modeling issues, algorithm issues, should have issues, etc. go here.

=== Entry Updated Required? -- Blogger Issue ===
moved to [[hatom-brainstorming]]

=== 'MAY have multiple Feed elements' -- details and viability of multiple feeds ===
moved to [[hatom-brainstorming]]

== pre 0.1 issues ==
'''This section is more or less closed, as hAtom 0.1 is out the door. If there are open issues that you are championing that didn't make it into hAtom 0.1, move them up above to the hAtom 0.2 section'''

See: [[hatom-issues-pre-0.1]]

== Template ==
{{issues-format}}

== See Also ==
* [[hatom|hAtom]] - the draft proposal
* [[hatom-faq]] - knowledge base
* [[hatom-issues-resolved]]
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[mfo-examples]]
* [[naming-principles]]

User:Singpolyma

2010-03-01T15:02:39Z

Singpolyma: change to cc0

<div class="vcard">
<div class="n">Stephen Paul Weber</div>
<div class="fn nickname">Singpolyma</div>
[http://singpolyma.net/ Website]
</div>

{{Template:cc-public-domain-release}}

Note: as a Canadian citizen, there are some rights I cannot waive. This is true in many countries. I hereby promise that I will not exercise any of my unwaivable rights to any content on this wiki or the microformats mailing lists or IRC. If you wish to be "safe" and do not trust me you can treat my contributions as http://creativecommons.org/publicdomain/zero/1.0/.

I certify that my contrubitions to this wiki, microformats mailing lists, and IRC are mine and that I have the right to waive rights and grant licenses.

datetime-design-pattern

2010-02-05T15:22:02Z

Singpolyma: /* Discussion */ <time> element

<entry-title> Datetime Design Pattern </entry-title>

<div class="usermessage">Please review the [[value-class-pattern]] page for a better understanding of the current thinking on this problem, especially with regards to [[#accessibility_issues | accessibility issues]].</div>

== Purpose ==
* Use the [[datetime-design-pattern]] to make dates and datetimes that are human readable also formally machine readable.
* Use the [[value-class-pattern]] for datetimes for better accessibility.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates and times for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable [[iso-8601|ISO8601]] datetime or date as the value

For ISO8601 datetimes, use the [[value-class-pattern]] instead for better accessibility.

==Current uses==
The pattern, which is now available as part of [[hAtom]], [[hcalendar|hCalendar]], [[hcard|hCard]] and [[hreview|hReview]], is:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where "foo" is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time, with an appropriate level of specificity, and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [[iso-8601|ISO 8601]]

Note: title strings of the form "YYYY-MM-DDTHH:MM:SSZ" may be challenging for humans to read and or understand, thus, use the [[value-class-pattern]] for datetimes.

=== Ruby ===
Ruby: An easy way to get this format from a DateTime is this:
:<pre>DateTime.now.to_s</pre>

Or alternately, if you're working with Time objects:
<pre>require 'time'
Time.now.iso8601</pre>

== Profile of ISO8601 ==
Any [[microformat]] using the date-time-design pattern {{should}} use a profile of [[iso-8601|ISO8601]]. There are currently two widely used profiles which {{should}} be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

== accessibility issues==
Note: Some [[accessibility-issues]] have been raised with Datetime Design Pattern, that have been addressed with the completion of the [[value-class-pattern]].

Note also that the accessibility concerns are considerably lessened, even eliminated when using the [[date-design-pattern]], a subset of the [[datetime-design-pattern]].

== Discussion ==
This section need significant gardening, and perhaps archiving of discussions which are primarily historic, as the [[value-class-pattern]] serves to solve much of the issues raised here. [[User:Tantek|Tantek]] 

----

What is the relationship of this pattern to the new <nowiki><time></nowiki> element? Should this pattern specify additionally that IF the element is a time element AND the element has a "datetime" attribute that the value should be taken from that attribute, otherwise fall back to value-class-pattern, otherwise fall further back to abbr-design-pattern? [[User:Singpolyma|Singpolyma]] 15:22, 5 February 2010 (UTC)

----

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

-- [http://tantek.com/log/ Tantek]

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

---

A few questions: asked by [[User:CharlesBelov|CharlesBelov]] 16:57, 24 Apr 2007 (PDT), answered by [[User:JamesCraig|JamesCraig]] on 15:58, 5 Jul 2007 (PDT).

# Would it make more sense for documenting the alternative codings pitting the abbr tag vs. other tags to be on this page? ''Answer: That documentation should go on the [[assistive-technology-abbr-results]] page.''
# Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about USA Section 508? It does appear to violate Technique for WCAG 2.0 [http://www.w3.org/TR/WCAG20-TECHS/#H28 H28: Providing definitions for abbreviations by using the abbr and acronym elements], although that is a supporting document and does not have the force of a guideline. ''Answer: Yes, it appears that is in violation of WCAG, 508, et al, so alternatives are being discussed on the [[assistive-technology-abbr-results]] page.''
# In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the abbr tag? ''Answer: please refer to and add any suggestions to [[assistive-technology-abbr-results]].''
# For that matter, wouldn't you want to style such an abbr tag with text-decoration:none to hide that an abbr tag was used? Otherwise, visitors might cursor over the time, see the machine time, and be annoyed that their time was wasted or else be confused. And I don't think you can suppress the title from coming up if the human-readable time was inadvertently hovered. ''Answer: Microformats should not rely on CSS in order to work properly, but again, that discussion can be found here: [[assistive-technology-abbr-results]].''

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== Other Proposals ==
'''This section needs a lot of clean-up. Proposals that have been relatively rejected need to be move to another section (or perhaps page), along with succinct summaries as to why they are untenable/infeasible/undesirable.

Remaining proposals probably need to be moved to proper brainstorming pages where they can be considered in a broader context.

Links to all proposals (whether relatively rejected or tentatively being considered) should be kept in this page for comparison purposes for this use case.

[[User:Tantek|Tantek]] 04:50, 4 Sep 2008 (PDT)'''

=== strtime instructions as class names ===
Proposal by DavidLaban (alsuren on freenode) on 8 Jun 2008
It might be possible to have a slightly more readable/extensible/elegant format:
<pre><nowiki>
 16 March 1987 
</nowiki></pre>
Notes:
# Underscores are used to replace whitespace, because otherwise the the formatting string will be split into an unordered set of class attributes by many parsers (thanks go to bogdanlazarsb and gsnedders on irc for explaining this to me).
# Some subset of the placeholders should be chosen from those which are supported by both python http://docs.python.org/lib/module-time.html and php http://uk3.php.net/manual/en/function.strftime.php
# A name for the class should be decided upon. strtime might not be the best name.
# Measures should be taken to avoid the format string accidentally conflicting with other valid classes (In the above example, I have prefixed it with the string "format:")
# It might be sensible (when parsing) to strip excess whitespace from the format string and contents. This is not done in this example.
# Example python code follows.

<pre><nowiki>
date = (1987,03,16,0,0,0,0,0,0)
format = " %d %B %Y "
# To encode:
classes = ["strtime"]
encoded_format = "format:" + format.replace(' ', '_')
classes.append(encoded_format)
content = time.strftime(format, birthday)
# ... dump classes and content into your document however you want

# To decode (assuming that you have managed to extract class and format from the document already):
if "strtime" in classes:
possible_formats = [ item for item in classes if item.startswith('format:') ]
assert len(possible_formats) == 1
format = possible_formats[0].strip('format:').replace('_', ' ')
date = time.strptime(content, format)
</nowiki></pre>

==== problems with strtime proposal ====

# Possible abuse of the class attribute. microformats limit the use of the class attribute to marking up additional semantics about the data, not for (potentially) arbitrary processing/programming instructions
#* HTML 4.01 Recommendation [http://www.w3.org/TR/REC-html40/struct/global.html#adef-class defines] the <code>class</code> attribute as being "for general purpose processing by user agents". [[User:TobyInk|TobyInk]] 13:21, 8 Jun 2008 (PDT)
# Requires authors to think like programmers. The larger problem is that the proposal asks web authors to think like programmers, which severely limits the number of web authors which will be able to use the technique, since the vast majority of web authors are ''not'' programmers and have never heard of "strtime", whereas most authors (even people) on the web have seen dates like 2005-06-20 and easily understand what they mean.

In general, any publishing method that requires the author to think like a programmer is a non-starter. It is a much more of a barrier than simply using ISO8601/RFC3339, and that barrier is a far worse tradeoff than the duplication / DRY violation compromise.
[[User:Tantek|Tantek]] 09:52, 8 Jun 2008 (PDT)

* Another problem: if %A/%a/%B/%b are allowed, this raises potential problems with internationalisation. Will parsers be required to understand the names and abbreviations for days and months in potentially hundreds of different languages? [[User:TobyInk|TobyInk]] 14:09, 8 Jun 2008 (PDT)

=== Machine-data in class===
The BBC ([http://microformats.org/discuss/mail/microformats-dev/2008-June/000552.html uf-dev archive, 20/06/08, "Using class for non-human data"]) has proposed as an alternative to the empty span and title solution to use the class name in the following way:
<pre><nowiki>
10 o'clock on the 10th
</nowiki></pre>
Pros:
* Allows data to be represented in a "non-harmful" way. Will not be read aloud by screenreaders or seen as tooltips.
* Minimizes mark-up used.
* Arguably more semantic than use of "title" attribute for non-human data.

Cons:
* data in the class attribute has already been discussed numerous times in the mailing list over the years and rejected and documented as an [[anti-pattern]] - captured [http://microformats.org/wiki?title=anti-patterns&diff=24271&oldid=24270 on the wiki this past January 2008].
* Possible misuse of class attribute, although as noted previously, the HTML spec states "for general purpose processing by user agents".
* The class attribute has been adopted by the broader web design community to "subclass" element semantics, and to layer additional semantics. To date, microformats has followed this existing practice developed by modern web designers ("paving the cow-paths"). This use of class for data is outside all current practices.

Discussion:
* This proposal smells icky, but I can't quite put my finger on why. Considered objectively, it does seem to be the least harmful solution proposed so far. [[User:TobyInk|TobyInk]] 06:06, 21 Jun 2008 (PDT)
* I really like it, especially given the HTML4 spec gives this as an IMO perfectly valid use (on both id and class, with the following examples given in the id section: "identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc."). Clean and simple. [[User:Dracos|Dracos]] 03:53, 23 Jun 2008 (PDT)
* I suggest dropping the redundant 'data-' prefix, unless someone can suggest a feasible case with two time-stamps requiring different prefixes. The proposal then becomes [http://www.robertnyman.com/2008/04/28/do-we-really-need-microformats/#comment-263408 one I've made before] [[User:AshSearle|AshSearle]]
** Valid class names cannot begin with a number, so a date needs some sort of letter prefix. It's sensible to make this prefix meaningful and reusable in some way. [[User:Phae|Phae]]
*** They can't in CSS, but they can in (X)HTML. http://examples.tobyinkster.co.uk/numeric-classes.html [[User:TobyInk|TobyInk]] 06:53, 24 Jun 2008 (PDT)
**** Creating classes in HTML that can't be referenced in CSS is a bad thing. Using colons and starting with numbers fall into that category. http://www.w3.org/TR/CSS21/syndata.html#characters Also, replacing whitespace with underscores breaks the ISO compatibility, which sorta defeats the whole point of using existing standards. Finally the class names are unordered, so trying to use them in a series is a bad idea. --[[User:Atamido|Atamido]] 11:43, 30 Jul 2008 (PDT)
***** They can be referenced in CSS, just not using the "dot notation". They can be referenced using attribute selectors, which are supported in all modern browsers (but not IE6). [[User:TobyInk|TobyInk]] 13:21, 30 Jul 2008 (PDT)
****** They could also be referenced by escaping the characters, but that still excludes >99% of current use cases. I'd wager that most authors don't even know about the limitations and would run into issues in implementation. --[[User:Atamido|Atamido]] 13:47, 30 Jul 2008 (PDT)
***** I don't think the proposal relies on classes being in any particular order. Even if it did, I don't know of any DOM implementations which do not provide the contents of the class attribute in their original order. [[User:TobyInk|TobyInk]] 13:21, 30 Jul 2008 (PDT)
** Not to advocate too strongly for designing for parsers (generally a bad idea), *but* having a 'data-' prefix on a class name would make identifying data orders of magnitude easier for parsing. Otherwise, how do we know what's data and what's just another class name for some other purpose? [[User:DrewMcLellan|Drew]]
** A 'data-' prefix would help authors tasked with maintaining or reviewing a page to understand the purpose of a class name that may have been applied by another author. The data prefix communicates very simply that the class name is precisely that, data. Therefore the value is less likely to be accidentally removed or changed, making for a more robust design. [[User:DrewMcLellan|Drew]]
*** I concede - regardless of whether it's valid (X)HTML / CSS - a prefix is needed to distinguish data values from genuine content. ISO 8601 allows date-time to be as simple as "2004", which could easily be misinterpreted. e.g. if a CMS outputs product model numbers into the class attribute for some other purpose. --[[User:AshSearle|AshSearle]] 01:42, 25 Jun 2008 (PDT)
*** Using <code>data-</code> as the prefix here is undesirable, as it now conflicts with HTML5's proposed <code>-data</code> prefix on attributes. It's undesirable to set ourselves up for future confusion with our own conflicting specification of ‘a data prefix’. A different prefix should be considered. See: [http://www.w3.org/html/wg/html5/#custom HTML5 Editors Draft: Embedding Custom Non-Visible Data] —[[User:BenWard|BenWard]] 07:34, 16 Jul 2008 (PDT)
* -1 [[User:Tantek|Tantek]]. I'm vehemently opposed to putting data in the class attribute. We ''must'' find better alternatives. We must not go down the path of invisible (dark) (meta)data - IMHO that [[principle]] is inviolable for microformats.
** [[User:JakeArchibald|JakeArchibald]] If you're so opposed, it'd be useful to see some justification.
*** See above cons. Already discussed/rejected many times in the history of microformats discussions. In short, quit wasting time on old ground. Abuses class attribute, or if you prefer, introduces a *new* use of the class attribute, unlike microformats to-date which have simply made use of a well established semantic of the class attribute. And worst of all, completely violates the visible data [[principle]]. Rejectable on that alone.
**** The fact that something has been discussed and rejected before is not sufficient grounds for dismissing it out of hand once additional research and thinking has taken place. The <abbr> datetime pattern arguably abused the title attribute and introduced a new use of the title attribute. In the example given (<code><nowiki>10 o'clock on the 10th</nowiki></code>), the data is presented as "10 o'clock on the 10th" - very visible. Yes, of course, it's possible to abuse this proposed pattern, and hide the data, but the same can be said of the abbr pattern or even the class pattern given CSS's display:none property. Experience shows that in most cases, people ''won't'' abuse the pattern to hide data, as they actually ''want'' to show the data on their pages. [[User:TobyInk|TobyInk]] 13:52, 24 Jun 2008 (PDT)
***** There has been no new "additional research and thinking" shown yet for data in the class attribute since it was originally proposed years ago, thus, it should be dismissed until that burden of reintroduction is met. [[User:Tantek|Tantek]] 22:05, 24 February 2009 (UTC)
**** It's not an abuse of the class attribute according to the HTML spec. as I read it. Whereas using title for non-human data is (the spec says audio agents may read it aloud, for example). If it's a new use, it's one the writers of HTML4 considered, so it wasn't new to them. [[User:Dracos|Dracos]] 03:38, 25 Jun 2008 (PDT)
** Relevant principles are 'humans first, machines second', and 'visible data is ''better'''. These are ''preferences'', not inviolable principles. Besides, the existing datetime spec doesn't adhere to these principles anyway: prioritising humans first, <code><nowiki>let's discuss this at the next meeting</nowiki></code> should be marked up as <code><nowiki>let's discuss this at the <abbr title="28th June 2008 at 3:15pm">next meeting</nowiki></code>. There's a conflict between human- and machine-readable dates. It makes more sense to 'hide' the machine-readable data in the only attribute available to us: <code>class</code>. --[[User:AshSearle|AshSearle]] 03:02, 25 Jun 2008 (PDT)
*** Indeed - by their nature, ''principles'' are ''generalisations'', and while broadly useful, usually have exceptions. After experience, the microformats community is beginning to see some of these. Human vs machine dates is the one gathering the most interest at the moment, largely thanks to <abbr class="help" style="border-bottom:1px dotted" title="the Web Standards Project">WaSP</abbr> and auntie, but I think other properties which will probably emerge as exceptions to the general microformats principles are hReview's <code>type</code> property, and the its namesake subproperty for hCard's <code>tel</code>, <code>email</code> and <code>adr</code> (and <code>label</code>?) properties. [[User:TobyInk|TobyInk]] 12:51, 25 Jun 2008 (PDT)
**** Unless you can provide better principles, it is not reasonable to violate the principles. When principles are in conflict, then one must make reasoned cases for the various possibilities (that uphold one principle but perhaps violate another). [[User:Tantek|Tantek]] 22:05, 24 February 2009 (UTC)

==== Experimental Parser Support ====

[http://buzzword.org.uk/cognition/ Cognition 0.1 alpha 10] will include experimental support for this pattern, and the [http://srv.buzzword.org.uk Cognition web service] already does. Notes:
* Support is ''opt-in''. Publishers must explicitly request support for the pattern, by including a [[profile-uris|profile URI]] of <code><nowiki>http://purl.org/uF/pattern-data-class/1</nowiki></code> in their document head.
* Support is not limited to date-time properties, but any microformat properties.
* data-X classes must use percent-encoding to encode spaces and other characters not allowed in class names.
* The data-X class must be found on the same element as the microformat property class. That is, you cannot use: <pre><nowiki>10 o'clock</nowiki></pre>
<ul><li>Multiple data-X classes may occur on the same element. When these are found, the longest string is used. This allows for: <pre><nowiki>The 10th</nowiki></pre> which may be useful for styling or other non-microformat purposes.</li>
<li>Can be combined with value excerpting. e.g. <pre><nowiki>

The concert will be held on
the 4th of August
starting at
7:30pm precisely.

</nowiki></pre></li></ul>

=== date and time separation using value excerption ===
Moved to [[value-excerption-pattern-brainstorming#date_and_time_separation|value excerption pattern brainstorming]] which is a better way of thinking about this.

=== HTML 5 <code><time></code> Element ===
[http://microformats.org/wiki/hcalendar-issues#html5-time-element See hCalendar issues]

=== Plain Old English alternative to ISO date ===
Example (in English):

<pre>
<abbr title="January 25th, 2008" class="dstart" lang="en-us">1/25</abbr>
</pre>

<pre>
January 25th, 2008
</pre>

If <code>lang="en-us"</code>, the format of the date used in the <code>title</code> attribute must conform to [http://www.ego4u.com/en/cram-up/vocabulary/date/written dates writing rules in American English].

Example (in French):

<pre>
<abbr title="25 Janvier 2008" class="dstart" lang="fr">25/1</abbr>
</pre>

If <code>lang="fr"</code>, the format of the date used in the <code>title</code> attribute must conform to date writing rules in French.

====Benefits====

* Human-hearable: should work nicely with screen readers (to be tested).
* Human-readable
* Compliance with semantics of abbr.
* Very easy to use by HTML human authors.
* DRY compliant if HTML human authors are willing to write in correct English

==== Disadvantages ====
Most extracted from discussion below.
* huge requirement of knowledge of locale-specific information in implementations
* very high complexity of implementation , perhaps even impossible, due to the knowledge required
* unreliability in general: "Getting it wrong would be worse than not getting it at all! "
* unreliability in mixed locale content
* unreliable according to implementation experience to date (see discussion below)
* authoring drift, NLP arms race. because proposal looks like natural language, authors will try any natural language format.
* widespread implementer objection to NLP based solutions

====Discussion====
* Locale-specific parsing logic.
* Not all cultures use the same calendar — Dan Brickley
* There are situations where markup clues used for localisation might be misleading, such as people using microformats in a post on a site they do not themselves run that may even be in a different country. (a shared blogging site that allows html tags in posts would be a good example here) — Michael MD
** Couldn't the person or tool adding the microformat annotation also add a lang attribute at the same time? — Benjamin Hawkes-Lewis
* Cognition already supports this as a last ditch attempt at parsing dates - but I wouldn't recommend it get adopted widely. It's too unreliable; too much work to deal with internationalisation; too much work full-stop in languages that don't provide a handy library that takes care of most of the work. — [[User:TobyInk]]
** I don't think we need to support all locales at once. I don't know in how many written languages BBC publishes in, but it might be that supporting en-uk and en-us might be enough for a start. Also, one can imagine that Microformats tools could focus on the most common written languages and then expose hooks for others to implement support for other locales. — Guillaume Lebleu
** What are our priorities? Making programmers' life easier or making content authors and content readers' life easier? — Guillaume Lebleu
*** In Australia dd/mm/yyyy is commonly used, but a significant minority of sites in Australia use US-style mm/dd/yyyy because it is the default setting in their CMS. How would a parser be able to tell which part is the day and which is the month? Getting it wrong would be worse than not getting it at all! Until the use of ambiguous formats can be ''wiped out'' we ''will'' need a version for machines! — Michael MD
*** problem which hasn't been raised with regards to this proposal is that even though you are proposing a fixed date format, because it *looks* like natural language, authors will assume that it *is* natural language, and simply start including dates in whatever format they like. Then you get an NLP "arms race" between publishers and parsers. If you don't believe that that will happen, take a look at what happened with RFC 822 dates, which are simply a mess. — [[User:TobyInk]]
**** Very true the more you make the date look like natural language, the less it looks like a fixed format. I really don't want us to get involved in any form of NLP, it just would not work. I think it was Mike who said that dates have to be parsed correctly, no level of error is acceptable. I don't want to travel to an event on the wrong day because a parser got the date wrong — Glenn Jones

====Notes====
* Could work alongside with the existing [[datetime-design-pattern]]: if ISO date parsing fails, try parsing the title as a human-readable plain old English/French/... date according to the locale.

===<code><object></code> element to represent dates===
* Re-raised by George Brocklehurst on June 25th 2008.

The idea was to do something like this:

<pre><code><object data="20050125">January 25</object></code></pre>

* From what Tantek [http://tantek.com/log/2005/01.html said on his blog] , the main reason for not using objects was that they were not well supported in Safari. However, Safari's object support is now much improved: fallbacks are supported and display:inline and intrinsic sizing will work correctly. Safari 2.0.2, which came out in November 2005, was the first version to [http://webkit.org/blog/32/webkit-fixes-in-safari-202-mac-os-x-1043/ contain these improvements]. — George Brocklehurst
* The following appears to be well behaved inline in Safari 2.04 and 3.1.1, Firefox 1, 1.5, 2 and 3, and Opera 7, 8 and 9: <code><object class="dtstart" data="data://20080712"></object></code>. Test case: http://pastie.org/224023 — Ben Ward
** IE 6, 7 and the beta version of IE 8 all visibly render the object element as a small box, similar to the way they would render a missing image: http://georgebrock.com/misc/object-in-ie.png — George Brocklehurst
** Absolute URIs can't start with a number, but relative ones can - and the data attribute is permitted to contain relative URIs. [Don't need to use data:// URI) — Toby A Inkster
* Could also look at <code><object class="dtstart"><param name="value" value="20050125" />January 25</object></code> — Scott Reynen

==== issues ====
Open issues related to this proposal. Some may require additional information to be acted upon / resolved.

* Not providing OBJECT WIDTH and HEIGHT causes the displaying page to flicker; --[[User:Yecril71pl|Yecril71pl]] 21:56, 24 February 2009 (UTC)
** Please provide specific implementation (maker, name, version number, platform) that cause the displaying page to flickr.

* OBJECT boundaries are impermeable to CSS. --[[User:Yecril71pl|Yecril71pl]] 21:56, 24 February 2009 (UTC)
** Please provide a URL to an example use of OBJECT that demonstrates problems with applying CSS to the contents of the OBJECT (i.e. beyond its boundaries).

==== resolved issues ====
Issues raised and resolved related to this proposal. Issues that are misconceptions (e.g. easily refuted by citing the HTML4 specification) are resolved by moving to the separate misconceptions section below with explanation/citation for why they are misconceptions.

* The purpose of the <object> element is to allow the browser to run an external application for a non-native data type (e.g., Java applet). See: http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3. Object is not the right way to go in this case. — Sarven Capadisli
** "datetime" *is* a non-native data type, and its common presentation is essentially a lowest common denominator (what's supported) plain text fallback. Better would be for code to recognize and present date and time information to the user in a format they can understand (perhaps adjusting the presentation for the user's locale settings). Object makes sense semantically for representing date and time information, as it is a semantic for embedding arbitrary data. [[User:Tantek|Tantek]] 21:39, 24 February 2009 (UTC)
** note the mention of "external application" may sometimes cause the misconception (i.e. see below) that object MUST be used to run an external application. This is false. Authors may specify the "classid", which implies an implementation, or they may specify the "type" and "data" attributes which the browser may then display natively or use the "type" attribute to find external code to display the data. [[User:Tantek|Tantek]] 21:39, 24 February 2009 (UTC)

* Providing OBJECT WIDTH and HEIGHT will break the typographical consistency of running text. --[[User:Yecril71pl|Yecril71pl]] 21:56, 24 February 2009 (UTC)
** This is a [http://tr.im/strawman Strawman] issue. This proposal never advocated using WIDTH and HEIGHT.

* Specifying a DATA attribute causes an unnecessary round-trip to the server. And what if it succeeds? --[[User:Yecril71pl|Yecril71pl]] 21:59, 24 February 2009 (UTC)
** This is a [http://tr.im/strawman Strawman] issue. This proposal lacks any examples which use "http:" in the DATA attribute or any other URI scheme which will cause a round-trip to the server.

==== misconceptions ====
===== external application only =====
* ''The purpose of the <object> element is to allow the browser to run an external application...'' — Sarven Capadisli
* ''OBJECT elements are for external content, not for arbitrary data;''' --[[User:Yecril71pl|Yecril71pl]] 21:56, 24 February 2009 (UTC)

This is false. From the [http://www.w3.org/TR/html401/struct/objects.html#h-13.3 HTML4.01 section on OBJECT]:

<blockquote>Still others [other objects] may not require additional implementation information, i.e., the user agent itself may already know how to render that type of data (e.g., GIF images).</blockquote>

Thus browsers may render OBJECTs themselves, like images, and external applications are not necessarily required. For example IE5/Mac supported native rendering of PNG images even as objects, while other browsers at the time (2000) which supported OBJECT, only rendered PNG images via external plugins.

===== need width and height =====
* ''OBJECT elements need WIDTH and HEIGHT'' --[[User:Yecril71pl|Yecril71pl]] 21:56, 24 February 2009 (UTC)

This is false. Per the [http://www.w3.org/TR/html401/struct/objects.html#h-13.3 HTML4.01 section on OBJECT], the width and height attributes are "#IMPLIED" not "#REQUIRED".

===Individual markup of each date/time component===
'''A variant of this idea has been documented into a [[value-excerption-pattern-brainstorming#details_for_handling_specific_property_types|specific proposal]] and is [[value-excerption-dt-separation-test|being tested]]. Please see the [[value-excerption-pattern-brainstorming#details_for_handling_specific_property_types|value excerption pattern brainstorming: date and type separation]] and [[value-excerption-dt-separation-test]] page for updated details. [[User:Tantek|Tantek]] 22:05, 24 February 2009 (UTC)'''

A combination of suggestions that originated from this [http://www.mail-archive.com/microformats-discuss@microformats.org/msg10218.html post]

This is suggested as a complementary alternative to datetime-design-pattern, when the use of the pattern is not possible due to accessibility reasons.

suggested class names:
* <code>date</code>
* <code>time</code>
* or maybe <code>datetime</code> ?
* <code>s</code> for seconds
* <code>min</code> for minutes
* <code>hr</code> for hours
* <code>ampm</code> for AM/PM
* <code>tz</code> for timezone. (ex. <code>GMT</code>)
* <code>tzo</code> for timezone offset (ex. <code>-7</code>)
* <code>day</code>
* <code>mo</code> for months
* <code>yr</code> for year

For a complete datetime:

<pre>


October 5, 2004
 at

6PM


</pre>

<code>date</code> maybe not required since <code>dstart</code> IS a <code>date</code>.

For a duration:

<pre>

1:
3:
42

</pre>

* An example of this is also documented on [[ISO-31-1]]

'''Issues'''
* the internationalization issue is not addressed, but it is limited to the month of the year.
* Tonnes and tonnes of nested elements to mark up something that's essentially very simple. Microformats are "for humans first, machines second", but this suggestion appears to be friendly to neither! [[User:TobyInk|TobyInk]] 02:21, 12 Aug 2008 (PDT)
** Also worth pointing out that the complexity issue applies less to durations. With durations, most people will probably only want to use a combination of 1 to 3 time components (e.g. d+h, h+min+s, h+min, min+s, d only, h only, min only, s only) But with datetimes, they're likely to want to specify at least five components (y+m+d+h+min) and often also the timezone (seconds, and fractions thereof, are not especially useful for the majority of use cases). So marking up the time components might be OK for durations, but becomes onerous for datetimes.

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* [[date-design-pattern]] is a subset of [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* W3C: [http://www.w3.org/QA/Tips/iso-date Use international date format (ISO) - Quality Web Tips]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

people-tagging-brainstorming

2009-12-15T19:10:46Z

Singpolyma: Mock up some examples

* Use hCard to mark up person's attributes (name/url/username)
* Use rel-tag on class=url to tag the current page with the user
** What about sites that don't have good tagspace URIs for their users? There aren't many of these left.

== Flickr example ==
(markup minimized for readability)
<pre><nowiki>


<a class="url" rel="tag" href="/photos/singpolyma/people/weebear/">
<img src="..." class="photo xBuddyIcon" />
Wee Bear
</a>
Paul Weber


</nowiki></pre>

== Facebook example ==
(markup minimized for readability)
<pre><nowiki>
<a class="url fn n" rel="tag" href="http://www.facebook.com/singpolyma">Stephen Paul Weber</a>

</nowiki></pre>

people-tagging-examples

2009-12-15T19:00:27Z

Singpolyma: Add Facebook markup (cleaned out JS stuff and formatted markup for readabitily)

== Flickr ==
<pre><nowiki>
<ul id="people-tags">

<li nsid="25688770@N00">



<a href="/photos/singpolyma/people/weebear/" title="View your photos of Wee Bear. (You added Wee Bear to this photo.)"><img src="http://farm1.static.flickr.com/15/buddyicons/25688770@N00. jpg?1118682188#25688770@N00" width="24" height="24" class="xBuddyIcon" id="pt-icon-25688770@N00"></a>
<a href="/photos/singpolyma/people/weebear/" class="photos-of-link" title="View your photos of Wee Bear. (You added Wee Bear to this photo.)">Wee Bear</a>
Paul Weber


<a href="#" class="pt-add pt-add-active" id="pt-add-25688770@N00" onclick="F.people_taggr.toggleFaceBoundryByNsid('25688770@N00', this); return false;" title="Edit face boundary?">Edit face boundary?</a>

<a href="#" class="pt-remove delete-x" id="pt-remove-25688770@N00" onclick="F.people_taggr.removePersonByNsid('25688770@N00'); return false;" title="Remove this person?">Remove this person?</a>


</li>
</ul>
</nowiki></pre>

== Facebook ==
<pre><nowiki>
<div id="phototags">In this photo:
<a href="http://www.facebook.com/singpolyma">Stephen Paul Weber</a>
(<a href="/photo_search.php?id=515373050&aid=1415&auser=1648110091">photos</a> | <a href="/ajax/photo_tagging_ajax.php?pid=49625&id=1648110091&subject=515373050&name=Stephen+Paul+Weber&action=remove" id="49625_16481100910_remove" rel="async-post">remove tag</a>)

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

people-tagging-examples

2009-12-15T18:55:35Z

Singpolyma: Example of flickr people tagging markup

hcard-issues

2009-08-06T23:47:35Z

Singpolyma: /* 2009 */ New issue about class=key

<entry-title> hCard issues </entry-title>
{{TOC-right}}
These are externally raised issues about [[hcard|hCard]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] and the [[hcard-issues-resolved|hCard resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].

== closed issues ==
See: [[hcard-issues-closed]]

== resolved issues ==
See: [[hcard-issues-resolved]]

== issues ==
Please add new issues to the '''bottom''' of the list by copy and pasting the [[#template|template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2009===

<div class="hentry">
{{OpenIssue}} 2009-218 raised by [[User:Singpolyma|Singpolyma]]
<div class="entry-content discussion issues">
* Format for key. What format should be used for key? I suggest the following:
<pre><nowiki>
<a class="key" type="application/pgp-keys" href="https://path.to/key">My PGP Key</a>
</nowiki></pre>
With MIME type obviously changed based on type of key.
</div>
</div>

== template ==
{{issues-format}}

== related pages ==
{{hcard-related-pages}}

events

2009-08-04T19:06:01Z

Singpolyma: No longer upcoming

<entry-title>Microformats related events</entry-title>
Please add microformats events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Track current and future microformats events by subscribing to <kbd style="display:block;margin:1em 0">'''webcal://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events'''</kbd> Select and copy the entire above "webcal:" URL, then choose "Subscribe..." in your calendar application (e.g. in MacOSX iCal, the first item in the '''Calendar''' menu) and paste. Set it to update (i.e. <nowiki>[x]</nowiki> Refresh) every day and new events will appear automatically.

You may also download [http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events events on this page as a standalone iCalendar file].

__TOC__

== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


== recent ==

=== July 2009 ===

*2009-07-25..<abbr style="border:0" class="value" title="2009-07-26">26</abbr> til <abbr class="value" title="17:00">5pm</abbr>: [[events/2009-07-25-dev-camp|microformatsDevCamp]] at San Francisco, CA. The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats http://upcoming.yahoo.com/event/2888376

*2009-07-09 at 10:30: [[events/2009-07-09-scibarcamp-open-data|SciBarCamp session: open science open data on today's web]] at Room 1, 2nd floor, IFTF offices, Palo Alto, CA.

*2009-07-07 at 19:00: [[events/2009-07-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Andalu, 3198 16th st., San Francisco, California. http://upcoming.yahoo.com/event/3068255

=== June 2009 ===
*2009-06-27 at 18:00: [[events/2009-06-27-microformats-vevent-london|London Microformats vEvent]] at TBC, London.

*2009-06-26 at 19:00: [[events/2009-06-26-microformats-4th-bday|microformats 4th birthday party]] at [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar], 720 Howard Street, Yerba Buena Upper Terrace, San Francisco, CA 94103 USA. http://upcoming.yahoo.com/event/3010807

*2009-06-23 at 19:30: [[events/2009-06-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2988905/

*2009-06-18 at 13:00-18:00 and 2009-06-19 from 9:00-18:00: VoCamp at Yahoo's Sunnyvale campus.

*2009-06-17 at 15:45: [http://www.semantic-conference.com/session/2144/ Semantics at Google: RDFa, Microformats, and more] at the Fairmont Hotel, San Jose, California.[http://www.semantic-conference.com/2009/travel/ 2009 Semantic Technology Conference]

*2009-06-16 at 19:00: [[events/2009-06-16-weekly-dinner-sf|Microformats Dinner San Francisco]] at Mercury Lounge, 1582 Folsom Street, San Francisco, CA 94103 USA.http://upcoming.yahoo.com/event/2922429/

*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2009-07-25-dev-camp

2009-08-01T04:14:33Z

Singpolyma: /* hack ideas */ add github link

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt in the mail). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
Like all [http://barcamp.org BarCamps], microformatsDevCamp is what it is because of what everyone put into it. It ran smoothly because of all of you volunteers, attendees, designers, coders, and builders.

[http://www.flickr.com/photos/kurafire/3756770573 http://farm3.static.flickr.com/2665/3756770573_e2d1fee886.jpg]

Click on yourself and add a note with a link to your web address!

=== participants ===
Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one. Feel free to add your twitter, or other method of contact.

# Cindy Li - designer. http://cindyli.com, http://twitter.com/cindyli. helping with microformatsDevCamp logo design. done!
#* full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
#* on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
#* designed and ordered buttons for event.Done!
# [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [http://dentedreality.com.au/ Dented Reality], http://twitter.com/beaulebens. I know my way around the venue, so can help sort out power strips, projectors etc
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction design) http://tantek.com/, http://twitter.com/t
# [http://yury.name Yury Lifshits] - http://yury.name
# [http://www.markng.co.uk Mark Ng] - http://www.markng.co.uk, http://twitter.com/markng
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer. http://www.ics.uci.edu/~rohit, http://twitter.com/rohitkhare
# [http://www.jasonbolton.com Jason Bolton] - front-end designer. http://www.jasonbolton.com, http://twitter.com/jbolt
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday). http://alpern.org, http://twitter.com/malpern
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher. http://twitter.com/hober
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher. http://singpolyma.net, http://twitter.com/singpolyma
# [http://feedblog.org Kevin Burton] - developer. http://feedblog.org, http://twitter.com/burtonator 
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# [http://chiarg.com Chirag Shah] - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# [http://dustinwhittle.com Dustin Whittle] developer
# [http://reidburke.com Reid Burke] developer
#[http://www.myspace.com/ciberch Monica Keller] - developer
# ... please add yourself if you participated in microformatsDevCamp!

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00 - planners+volunteers onsite for setup
** 12:00 - registration
** 13:00 - lunch - Indian Food from Deedees
** intro session, what is a devcamp, introductions
** 13:30 - hack/project brainstorming and proposals
** day 1 building sessions
** coffee!
** 18:10 - [http://www.flickr.com/photos/kurafire/3756770573 group photo]
** 19:00 - dinner - pizza from Amicis
** 20:30 - dinner 2.0 - more pizza from Amicis
** beer, wine, and cupcakes!
** day 1 [[#projects|projects]] demos and social hour
** evening open hacking session (DevHouse style) / iteration on hacks/projects
** day 1 clean up
** ~midnight+ - day 1 wrap up.

* Sunday July 26th
** 09:30am - planners+volunteers onsite for setup
** 10:00am - coffee, breakfast, more demos from day 1
** day 2 hack/project brainstorming, proposals, signups
** day 2 working sessions on hacks/projects
** 13:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** 18:00 venue clean-up
** 18:30 venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Café - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.
* [http://www.flickr.com/photos/tags/ufdevcamp/ ufdevcamp tag on flickr]

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
* '''twitter bus card exchange/display''' by [[User:perivision|Christopher]]
* Not related to microformats per-se, but came up at µfdevcamp. '''git-mediawiki''' [http://en.wikipedia.org/wiki/User:Singpolyma/git-mediawiki Singpolyma's brainstorming page] [http://github.com/singpolyma/git-mediawiki Github] [[User:Singpolyma|Singpolyma]]
* ... and many more on cards at the event (please add from photos taken)
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
# [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
# [[self-updating-address-book]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
# [[hcard-contact-autocompletion]] (a/k/a “CallerID 2.0”) by [[User:Rohit|rohit]], hober, chirags, lou, lauren, & jesse
# [[unified-rsvp]] by [http://www.myspace.com/ciberch Aramys], [http://dustinwhittle.com/ Dustin], [http://matthewlevine.com/ Matthew], [http://www.myspace.com/ciberch Monica], and [http://reidburke.com/ Reid]
# [[hcard-google-bookmarklet]] [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
# [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
# [[hcard-creator-redesign|hCard Creator redesign]] by Cindy Li

== photographs ==
* [http://www.flickr.com/photos/kurafire/sets/72157621834778724/ Flickr photo set by Faruk Ateş]
See all [http://flickr.com/photos/tags/ufdevcamp photos on Flickr tagged ufdevcamp].

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://github.com/blog/468-microformats-on-github 2009-07-29 Microformats on GitHub]
* [http://dentedreality.com.au/2009/07/microformatsdevcamp/ 2009-07-27 Beau Lebens: microformatsDevCamp]
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

meetup

2009-07-28T18:16:04Z

Singpolyma: /* San Francisco */ time formats

<entry-title>Weekly Meetups & Dinners</entry-title>
{{TOC-right}}<div>http://farm4.static.flickr.com/3216/2836380076_9251390ded_m.jpg</div> A regular source of microformats [[events]].
== Weekly Meetup ==
The community and adoption have grown considerably over the last year, and news of adoptions (and once in a while challenges) come up frequently enough ([http://news.google.com/news?q=microformats&ie=UTF-8&scoring=n at least once a week]) that there are no shortage of new topics to discuss on a weekly basis. See [[weekly-meetup#purpose|purpose]] for more.

[[weekly-meetup#Organize_a_weekly_meetup|Organize a weekly meetup]]!

By making this a regular (every Tuesday) event, people know it is happening regularly and can thus come whichever ones are convenient for them, and not worry about missing any one in particular.

Cities where weekly meetup events are held, sorted alphabetically:

== London ==
In London, Tuesdays at 7:30pm worked well.

Interested in general for London:
* [[User:Phae|Frances]]
* [[User:GeorgeBrock|George Brocklehurst]]
* [http://twitter.com/ptg/statuses/906735728 Patrick Griffiths]
* [[User:Spiritquest|Ketan Majmudar ]]
* ...

Possible locations:
* ...

Past London venues:
* [http://www.squaremeal.co.uk/restaurants/london/view/81375/Wagamama Wagamama at New Oxford St. & Bloomsbury St.]: [[events/2008-09-02-london-meetup-dinner|2008-09-02]]
* [http://upcoming.yahoo.com/venue/213236/ The Princess at 76 Paul St.]: [[events/2008-09-09-london-meetup-dinner|2008-09-09]]

== San Francisco ==
From having informally asked a few folks in the SF area and on IRC it seems Tuesdays at 19:00 (7pm, .79, .08Z, @125) work best, with a rotating venue to keep it interesting.

Additional suggested SF venues (suggester). Add your opinions and more suggestions:
* Osha Thai on 2nd st.
* Thirsty Bear
** +0 ok food, often too crowded for a group to actually get seating, though we did hold a [[events/2007-04-18-web-2-expo-dinner|microformats dinner there last year]] somehow. I think John Allsopp sweet talked the hostess. - [[User:Tantek|Tantek]]
* Mel's Diner
** +0 hard to order healthy here, but the food mostly tastes good, and can probably get seating for a decent crowd at 6:30pm - [[User:Tantek|Tantek]]
* Sugar Cafe
* Axis Cafe
* Naan & Curry on O'Farrell & Mason
* [http://www.yelp.com/biz/a-la-turca-restaurant-san-francisco A La Turca Restaurant]
* ...

=== past SF venues ===
Past SF venues. We'll reuse these at some point I'm sure.

'''This section needs updating with dinners that have occurred since 2008-10-28.'''

Please update the following list by looking at [[events-2008]] and more recent [[events]], and add links (even just one more would help!) to dinners starting from the "since" date above, and update that date accordingly so that other contributors know where to continue updating from. Thanks!

* Chaat Cafe: [[events/2008-06-24-weekly-meetup-dinner|2008-06-24]], [[events/2008-07-22-weekly-meetup-dinner|2008-07-22]]
* Crepes on Cole: [[events/2008-07-01-weekly-meetup-dinner|2008-07-01]]
* Westfield Food Court: [[events/2008-07-08-weekly-meetup-dinner|2008-07-08]], [[events/2008-08-19-weekly-meetup-dinner|2008-08-19]]
* South Park (lunch) : [[events/2008-07-15-weekly-meetup-lunch|2008-07-15]], [[events/2008-09-23-sf-weekly-meetup-lunch|2008-09-23]]
* Chevy's SOMA: [[events/2008-07-29-weekly-meetup-dinner|2008-07-29]]
* Brickhouse Cafe: [[events/2008-08-05-weekly-meetup-dinner|2008-08-05]]
* Pancho Villa: [[events/2008-08-12-weekly-meetup-dinner|2008-08-12]]
* 21st Amendment: [[events/2008-08-26-weekly-meetup-dinner|2008-08-26]], [[events/2008-09-16-sf-weekly-meetup-dinner|2008-09-16]], [[events/2008-10-28-sf-weekly-meetup-dinner|2008-10-28]]
* Blondie's Pizza on Powell st: [[events/2008-09-02-weekly-meetup-dinner|2008-09-02]]
* Metreon Food Court: [[events/2008-09-09-weekly-meetup-dinner|2008-09-09]]
* Naan & Chutney on Haight st.: [[events/2008-09-30-sf-weekly-meetup-dinner|2008-09-30]]
* Taylor's Automatic Refresher: [[events/2008-10-14-sf-weekly-meetup-dinner|2008-10-14]]
* Mehfil: [[events/2008-10-21-sf-weekly-meetup-dinner|2008-10-21]]
* 3rd Street Grill
* California Pizza Kitchen on 3rd
* Crepevine on Church

== Other Cities ==
Want a microformats meetup in your city? Organize one! Add your city and name to this list. Contact others from your city and [[weekly-meetup#Organize_a_weekly_meetup|organize a meetup]]. Once you do one, add another section for your city above this "Other Cities" section, and list suggested venues, past venues with links to meetup event pages etc.

There has been some interest expressed in organizing dinners in the following cities. Add yourself and/or contact the people listed and make it happen!
* Austin - [[irc]] Atamido
* Kansas City - [http://twitter.com/dckc/statuses/1116151301 Dan Connolly]
* Montreal - [[User:Csarven|Sarven Capadisli]]
* San Diego - [[User:EdwardOConnor]]
* San Jose (South Bay) - [[User:Kevin_Marks|Kevin Marks]], Rohit Khare
* Seattle, WA - [[User:jandrick|Jeremiah Andrick]], Colin Henry, Andy Woods

== Organize a weekly meetup ==
Anyone can organize a microformats weekly meetup or dinner!

At a minimum, all you need is:
# '''At least one other person''' that commits to go (so at least you know you'll have a good conversation about microformats with at least one person).
# '''A location'''

And organizing a weekly meetup requires you to at a minimum:
# '''Pick a location'''
# '''Announce it''' (location at 18:30, Tuesday) on various event sites and notification services like Twitter etc.

That's it. If you prefer a step-by-step list of instructions and details, to remove nearly all doubt, here you go:
# Pick a location
#* Ask folks on [[IRC]] if they have any suggested locations.
#* Consider locations that are easy for a variety of people to transit to.
#* Consider a new location to keep it interesting.
# Create the Events Pages
## Create specific event page on microformats.org wiki, follow the form <code>YYYY-MM-DD-weekly-dinner-CITYCODE</code> — e.g. <samp>2009-01-06-weekly-dinner-sf</samp> in San Francisco, or <samp>2009-01-06-weekly-dinner-ldn</samp> in London.
##* Copy the Weekly Dinner template code ([[weekly-meetup#Event_Template|below]]), and make the following edits:
##** Update dates and locations in the infobox at the top.
##** Update the tags list, adding the event specific tag for this event.
##** Update the URLs for Upcoming, Technorati, Google Blog Search and Flickr. These search on the event tag itself, so need to date portion updated.
##** Add yourself as an attendee
##** (For SF weekly meetup dinners, [[MatthewLevine|Matthew Levine]] has created a script to automatically generate wiki page source by parsing the [[hCalendar]] from the related [http://upcoming.org upcoming] event. To use this script, create an upcoming event '''first''', then visit <kbd>http://www.phusikos.com/event.php?upcoming_id=$upcoming_id</kbd>, e.g. [http://www.phusikos.com/event.php?upcoming_id=2656901 sample conversion link].)
## Create an [http://upcoming.org upcoming] event, summarizing the event and linking to the new wiki page you just created.
##* Just after creating the event, Upcoming gives you the option to "upload an official photo or image", click that link and upload <nowiki>http://farm4.static.flickr.com/3216/2836380076_9251390ded.jpg</nowiki>, making it the official photo for the event. Thanks to [http://www.flickr.com/photos/cindyli/2836380076 Cindy Li for the cool microformats meetup graphic!].
##* Add the event to the Microformats, Web2.0, Bay Area Web Geeks, Web Developers, Geek Dinners and Social Network Portability groups.
##* Update the wiki events page with Upcoming.org event tag (<samp>upcoming:event=00000000</samp>) you just created. You can copy and paste the previous meetup/dinner summary and change the relevant detail.
# '''Announce it'''
#* [http://twitter.com/ Tweet] the upcoming event
#* On the day of the event, post a reminder in the morning (to Twitter etc.), and again an hour before the event.
# At the event, take a photo and post it to BrightKite, Flickr etc.
# Afterwards
#* Post a thank you note thanking those that attended, invite them to add their content to the wiki.
#* Update the wiki event page with details of discussions, photographs, blog links and so forth.

===Event Template===

<source lang=html4strict><entry-title>Microformats Weekly Dinner, San Francisco</entry-title>
__TOC__
One of several microformats [[weekly-meetup]] [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-MM-DDT18:30-0800 to 2009-MM-DDT20:30-0800
;Where
:TBA
;What
:Microformats Weekly Meetup Dinner, San Francisco
;Web
:http://upcoming.yahoo.com/event/00000000/

'''[http://feeds.technorati.com/events/referer Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Weekly Meetup ==
<div class="description">The microformats community has grown and stablized over the past few years, news of adoptions, new ideas and challenges come up frequently enough that there are no shortage of new topics to discuss on a weekly basis.

Come along, meet up with the microformats community in San Francisco

In another city? Check out [[weekly-meetup#Other_Cities|Weekly Meetup: Other Cities]] and help organize one in your own city!</div>

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-dinner'''
microformats-meetup
microformats
san-francisco
''microformats-dinner-2009-MM-DD'' 
''upcoming:event=00000000'' 
</kbd>

If you use Twitter, mention ''@microformats dinner''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats+dinner Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:YourName|You]]
* …

== Notes ==

Topics Discussed:

* …

== Photographs ==


* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-dinner-2009-MM-DD Photographs tagged microformats-dinner-2009-MM-DD] or for [http://flickr.com/photos/tags/microformats-dinner all photographs from microformats dinners].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* …


Also, find posts on this meetup on [http://blogsearch.google.co.uk/blogsearch?q=microformats-dinner-2009-MM-DD Google Blog Search] or [http://technorati.com/search/microformats-dinner-2009-MM-DD Technorati].

</div> 

== Related Pages==
{{events-related-pages}}</source>

== purpose ==
In addition to providing a convenient forum for community members to get together once in a while and talk about the [http://news.google.com/news?q=microformats&ie=UTF-8&scoring=n latest news about microformats], the weekly meetups serve many good ends.

Perhaps most importantly, weekly meetups really help communication and community. People that have met in person usually treat each other nicer online, thus very much help encourage everyone to [[mailing-list#Be_nice|be nice]] in IRC, mailing lists etc.

== FAQ ==
Perhaps move to [[weekly-meetup-faq]] if this section gets too big.

=== general talk ===
* Q: Do you just talk in general about microformats?
* A: As there's been new people at every microformat meetup, there's almost always at least some general talk about microformats.

=== newcomers vs detail ===
* Q: How do you handle newcomers and at the same time get into detailed stuff?
* A: Usually there are multiple conversations going, so there's almost always a good conversation to participate in. Also, it helps everyone to talk with newcomers and get fresh perspectives, as well as practiced at effectively communicating [[what-are-microformats|what microformats are]], [[benefits]], [[get-started|how to use]] etc.

=== existing issues ===
* Q: Do you try to solve some existing issues?
* A: We have discussed existing issues in some past meetups. Often divisive or controversial topics are much easier to discuss and understand multiple perspectives on in person. For example, [[User:BenWard|Ben Ward]] and [[User:Tantek|Tantek]] have made some good progress on understanding various perspectives on [[value-excerption-brainstorming]] and are optimistic about making progress on related issues.

=== notes ===
* Q: Do you take notes?
* A: Everyone is encouraged to take notes and contribute aspects of conversations, topics etc. on the wiki page for the meetup.

== related ==
* [[weekly-meetup-brainstorming]] to capture how to make the meet-up more exciting and give more practical use-cases
* [[events]]

events/2009-07-25-dev-camp

2009-07-28T00:00:56Z

Singpolyma: /* hack ideas */ git-mediawiki

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt in the mail). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
Like all [http://barcamp.org BarCamps], microformatsDevCamp is what it is because of what everyone put into it. It ran smoothly because of all of you volunteers, attendees, designers, coders, and builders.

[http://www.flickr.com/photos/kurafire/3756770573 http://farm3.static.flickr.com/2665/3756770573_e2d1fee886.jpg]

Click on yourself and add a note with a link to your web address!

=== participants ===
Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one. Feel free to add your twitter, or other method of contact.

# Cindy Li - designer. http://cindyli.com, http://twitter.com/cindyli. helping with microformatsDevCamp logo design. done!
#* full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
#* on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
#* designed and ordered buttons for event.Done!
# [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [http://dentedreality.com.au/ Dented Reality], http://twitter.com/beaulebens. I know my way around the venue, so can help sort out power strips, projectors etc
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction design) http://tantek.com/, http://twitter.com/t
# [http://yury.name Yury Lifshits] - http://yury.name
# [http://www.markng.co.uk Mark Ng] - http://www.markng.co.uk, http://twitter.com/markng
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer. http://www.ics.uci.edu/~rohit, http://twitter.com/rohitkhare
# [http://www.jasonbolton.com Jason Bolton] - front-end designer. http://www.jasonbolton.com, http://twitter.com/jbolt
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday). http://alpern.org, http://twitter.com/malpern
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher. http://twitter.com/hober
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher. http://singpolyma.net, http://twitter.com/singpolyma
# [http://feedblog.org Kevin Burton] - developer. http://feedblog.org, http://twitter.com/burtonator 
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# [http://chiarg.com Chirag Shah] - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# [http://dustinwhittle.com Dustin Whittle] developer
# [http://reidburke.com Reid Burke] developer
#[http://www.myspace.com/ciberch Monica Keller] - developer
# ... please add yourself if you participated in microformatsDevCamp!

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00 - planners+volunteers onsite for setup
** 12:00 - registration
** 13:00 - lunch - Indian Food from Deedees
** intro session, what is a devcamp, introductions
** 13:30 - hack/project brainstorming and proposals
** day 1 building sessions
** coffee!
** 18:10 - [http://www.flickr.com/photos/kurafire/3756770573 group photo]
** 19:00 - dinner - pizza from Amicis
** 20:30 - dinner 2.0 - more pizza from Amicis
** beer, wine, and cupcakes!
** day 1 [[#projects|projects]] demos and social hour
** evening open hacking session (DevHouse style) / iteration on hacks/projects
** day 1 clean up
** ~midnight+ - day 1 wrap up.

* Sunday July 26th
** 09:30am - planners+volunteers onsite for setup
** 10:00am - coffee, breakfast, more demos from day 1
** day 2 hack/project brainstorming, proposals, signups
** day 2 working sessions on hacks/projects
** 13:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** 18:00 venue clean-up
** 18:30 venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Café - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.
* [http://www.flickr.com/photos/tags/ufdevcamp/ ufdevcamp tag on flickr]

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
* '''twitter bus card exchange/display''' by [[User:perivision|Christopher]]
* Not related to microformats per-se, but came up at µfdevcamp. '''git-mediawiki''' [http://en.wikipedia.org/wiki/User:Singpolyma/git-mediawiki Singpolyma's brainstorming page] [[User:Singpolyma|Singpolyma]]
* ... and many more on cards at the event (please add from photos taken)
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
# [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
# [[self-updating-address-book]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
# [[hcard-contact-autocompletion]] (a/k/a “CallerID 2.0”) by [[User:Rohit|rohit]], hober, chirags, lou, lauren, & jesse
# [[unified-rsvp]] by [http://www.myspace.com/ciberch Aramys], [http://dustinwhittle.com/ Dustin], [http://matthewlevine.com/ Matthew], [http://www.myspace.com/ciberch Monica], and [http://reidburke.com/ Reid]
# [[hcard-google-bookmarklet]] [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
# [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
# [[hcard-creator-redesign|hCard Creator redesign]] by Cindy Li

== photographs ==
* [http://www.flickr.com/photos/kurafire/sets/72157621834778724/ Flickr photo set by Faruk Ateş]
See all [http://flickr.com/photos/tags/ufdevcamp photos on Flickr tagged ufdevcamp].

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

self-updating-address-book

2009-07-27T01:18:06Z

Singpolyma: /* Self Updating Address Book */ github

== Self Updating Address Book ==

http://github.com/beaulebens/hCard-LDAP-Service

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==
<pre>
fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (not in inetOrgPerson)
honorific-suffix => generationQualifier (not in inetOrgPerson)
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c (not in inetOrgPerson)
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI
</pre>
=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

self-updating-address-book

2009-07-27T00:35:39Z

Singpolyma: /* vCard => LDAP */ add pre

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==
<pre>
fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (not in inetOrgPerson)
honorific-suffix => generationQualifier (not in inetOrgPerson)
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c (not in inetOrgPerson)
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI
</pre>
=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

parsers

2009-07-27T00:33:34Z

Singpolyma: /* PHP */ xmfp

<h1>Microformats Parsers</h1>
{{TOC-right}}
This page lists libraries that consume, transform or convert microformats. This is only a partial list. If you know of other such tools for microformats, please add them and list what specific microformats they support.

For now, this page ''copies'' (rather than ''moves'') information from the existing [[implementations | Implementations]] page.

== Javascript ==

=== Sumo ===
* [http://www.danwebb.net/2007/2/9/sumo-a-generic-microformats-parser-for-javascript Sumo! A Generic Microformats Parser For JavaScript]

== Perl ==

=== Data::Microformat ===
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo.
** By Brendan O'Connor / Six Apart

===Swignition ===

* [http://buzzword.org.uk/swignition/ Swignition] is a parser for both “upper case Semantic Web” (RDF, RDFa) and “lower case semantic web” (microformats) technologies. It includes modules for exporting parsed data in a variety of formats, including RDF, vCard, iCalendar, Atom and KML.
** By Toby Inkster

=== Text::Microformat ===

[http://code.google.com/p/ufperl/ Google Code]

== PHP ==

=== xmfp ===

http://code.google.com/p/xmfp/

=== hKit Microformats Toolkit for PHP5 ===
[http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

===PHP Microformats parser===
[http://www.phpclasses.org/browse/package/3597.html Microformats parser] is a PHP package for extracting the microformats data embedded into HTML. The gathered data is stored as an xArray of objects - one for each microformat type container found. [http://malatestapunk-stuff.blogspot.com/2007/01/php-microformats-parser.html Announcement]. The parser supports most of the hCard (missing SOUND), hCalendar, hReview (missing item info; spec really needs some clarification) and rel elements, according to their respective specification on microformats Wiki.

===Transformr===
A Simple set of XSLT and PHP tools for Transforming Microformats [http://code.google.com/p/transformr/ available from Google code] and as a [http://transformr.co.uk/ web service].

=== hCard Validator ===
[http://code.google.com/p/hcardvalidator/ Source code] of the [http://hcard.geekhood.net/ hCard Validator] contains XSLT and PHP code for hCard and include microformats.

== Python ==

===AUMP===

* [http://aump.googlecode.com AUMP] is a parser written by David Janes. It supports hCard, hCalendar, hAtom, hReview and hListing.
** Uses Python's [http://docs.python.org/library/xml.dom.minidom.html xml.dom.minidom] after cleaning input through [http://www.w3.org/People/Raggett/tidy/ HTML Tidy].

== Ruby ==

=== mofo ruby microformats parser===
* [http://mofo.rubyforge.org/ mofo], [http://groups.google.com/group/mofo-rb mofo Google Group], [http://github.com/defunkt/mofo/tree/master GitHub repository]
** by [[implementors#Chris Wanstrath|Chris Wanstrath]]
** Uses the [http://wiki.github.com/why/hpricot Hpricot] HTML/XML parser

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== uformats ===
* [http://rubyforge.org/projects/uformats uformats]

=== scrAPI ===
* [http://rubyforge.org/projects/scrapi scrAPI]

== XSLT ==
===X2V===
* [http://hg.microformats.org/ XSLT for extracting microformats]

== see also ==
* [[implementations]]
* [[implementors]]
* [[user-interface]]

optimus-issues

2009-07-27T00:25:56Z

Singpolyma: /* issues with 0.8 */ document issue

[[Optimus]] is a [[validator]] for microformats. This page documents known issues grouped by area of support. Feel free to add new issues, or comment on existing issues.

== issues with 0.8 ==

=== JSON output b0rked ===

http://github.com/DmitryBaranovskiy/optimus/issues/#issue/11

=== hAtom validation ===
==== properties are errantly reported as not specified ====
Bug reported 2009-05-27:
[http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F When validating microformats.org], Optimus states on a single [[hAtom]] hentry that both: <blockquote>Required property ‘author’ not specified.Required property ‘updated’ not specified.Required property ‘bookmark’ not specified. Required property ‘entry-title’ not specified.</blockquote> and <blockquote>author ... Ben Wardupdated / 2009-05-15T01:16:43bookmark / [http://microformats.org/blog/2009/05/15/rich-snippets-microformat-search/ In Search of Microformats]entry-title / In Search of Microformats</blockquote> obviously if Optimus can find those properties on the hentry, then they are not "not specified".

* Expected behavior: if Optimus finds a property on an hentry, then it should not complain about that property being not specified.

==== bookmark is not required ====
Bug reported 2009-05-27:
According to [[hatom#Schema|hAtom]], rel-bookmark is an optional property of hentry, however, [http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F when validating microformats.org], Optimus states: <blockquote> Required property ‘bookmark’ not specified.</blockquote>.

* Expected behavior: Optimus should not state that rel-bookmark is required on hentry, and if rel-bookmark is not specified, Optimus should perhaps simply provide a warning, that

=== better error documentation ===
* Enhancement request 2009-05-27: Whenever Optimus reports an error or warning, it would be great if the error message linked to the section of the specification that is being violated.

== see also ==
* [[optimus]]
* [http://code.google.com/p/mf-optimus/issues/list Optimus issues list on Google Code]
* [[debugging-tools]]

self-updating-address-book

2009-07-26T22:40:51Z

Singpolyma: /* vCard => LDAP */ ah!

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==

fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (not in inetOrgPerson)
honorific-suffix => generationQualifier (not in inetOrgPerson)
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c (not in inetOrgPerson)
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

self-updating-address-book

2009-07-26T21:59:58Z

Singpolyma: /* vCard => LDAP */ notes

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==

fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (does not work)
honorific-suffix => generationQualifier (does not work)
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c (does not work)
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

self-updating-address-book

2009-07-26T21:53:41Z

Singpolyma: /* vCard => LDAP */ found

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==

fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (does not work)
honorific-suffix => generationQualifier
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

self-updating-address-book

2009-07-26T21:28:15Z

Singpolyma: /* Participants */ add me, fix tantek's name

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==

fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (does not work)
honorific-suffix => NONE
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Çelik
* Chad Weider
* Stephen Paul Weber

self-updating-address-book

2009-07-26T21:03:33Z

Singpolyma: /* Self Updating Address Book */ vCard => LDAP schema

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

== vCard => LDAP ==

fn => displayName
n => cn
given-name => gn
family-name => sn
additional-name => NONE
honorific-prefix => personalTitle (does not work)
honorific-suffix => NONE
adr => postalAddress
post-office-box => postOfficeBox
extended-address => NONE
street-address => street
locality => l
region => st
postal-code => postalCode
country-name => c
type => NONE (only one per entry)
agent => secretary
bday => NONE
category => NONE
class => NONE
email => mail
geo => NONE
key => NONE
label => NONE
logo => jpegPhoto | photo
mailer => NONE
nickname => cn
note => description
org => o
oraganization-name => o
organization-unit => ou
photo => jpegPhoto | photo
rev => NONE
role => NONE
sort-string => NONE
sound => audio
tel => telephoneNumber
=> homePhone
=> mobile
title => title
tz => NONE
uid => uid
url => labeledURI

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Celik
* Chad Weider

bookmarklets

2009-07-26T20:18:43Z

Singpolyma: /* contacts */ autofill bookmarklet

<h1>Bookmarklets</h1>

This page lists [http://en.wikipedia.org/wiki/Bookmarklet bookmarklets]/[http://favelets.com/ favelets] (also known as "browser buttons") which can be installed in most web [[browsers]] and used to access or process microformat-marked-up content. Please feel free to add further examples.

== contacts ==
*[http://jkg3.com/Journal/81/bookmarklet Extract hCard to Gmail] - Take the hCard and convert it to gmail .CSV file
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Left Logic's microformat bookmarklet] - [[hcard]]
*[http://suda.co.uk/projects/X2V/ Extract vCard data] - [[hCard]]
*[http://technorati.com/contacts/ Technorati Contacts Feed Service] - adds hCards on the page to your address book.
*[http://www.w3.org/2001/sw/BestPractices/HTML/rdfa-bookmarklet/ RDFa] - converts [[hCard]] to RDFa
* Socialsearchme autofill http://socialsearchme.com/bookmarklet.html

== events ==
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Left Logic's microformat bookmarklet] - [[hCalendar]]
*[http://suda.co.uk/projects/X2V/ Extract iCal data] - [[hCalendar]]
*[http://technorati.com/events/ Technorati Events Feed Service] - add or subscribe to hCalendar events to your calendar

== geo ==
*[http://suda.co.uk/projects/microformats/geo/ Extract Geo data] - [[geo]]

== tools ==
*[http://tantek.com/favelets/#optimus-validator Optimus microformats validator] - one-click validates the microformats on the current page using [[Optimus]]. See also related blog post (section) : [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet Get the Optimus microformats validator browser button].
*[http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] - a lint tool (non-authoritative validator) for [[XFN]], [[rel-tag]] and other microformats that make use of the rel attribute of links.

==see also==
* [[browsers]]
* [[firefox-extensions]]
* [[implementations]]
* [[debugging-tools]]

to-do

2009-07-26T02:48:01Z

Singpolyma: /* 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]

== Lazyweb ==

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

=== for all microformats ===
* We have added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* 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 any admins to keep track of current to-do items for admins and/or 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>.

=== Website Improvements ===
* OpenID login, on behalf of a request a while ago from [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)
** The plug-in is installed, but the user experience of exposing it to commenting visitors is poor. There's no other registration function, so it's not being pushed for the time being.
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)

=== Wiki improvements ===

* URGENT FIX to regression - hCalendar for mod-date broke "Add to calendar" links/functionality.
** '''immediate fixes'''
**# change <source lang=html4strict><div class="vevent last-modified"></source> in global wiki page template
**** to: <source lang=html4strict><div class="last-modified"></source>
**# and change <source lang=html4strict></source> in global wiki page template
**** to: <source lang=html4strict></source>
** '''proper fix''' - use hAtom to semantically markup episodic content, e.g. wiki changes.
*** change global wiki page template so that this:
<source lang=html4strict>
<div class="vevent last-modified">

‘<a rel="bookmark" class="url uid" href="/wiki/index.php?title=to-do&oldid=39000">To Do</a>’
was last modified:

 
Monday, June 8th, 2009 
</div>
</source>
*** changes to:
<source lang=html4strict>
<div class="hentry last-modified">

‘<a rel="bookmark" class="url uid" href="/wiki/index.php?title=to-do&oldid=39000">To Do</a>’
was last modified:

 
Monday, June 8th, 2009 
</div>
</source>
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.
* Add Extensions - especially those that help implement more microformats on the wiki itself!
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)
** OpenID login, on behalf of a request a while ago from [[User:DanC]]. [[User:Tantek|Tantek]] 20:50, 20 Jul 2007 (PDT) (Planned for Wiki 2.0)
*** Regarding OpenID Log-in. Needs lightweight extension. Current extension turns the wiki into an OpenID *provider*. DO NOT WANT. Anyone want to write a simple OpenID login extension for MediaWiki?
**** You could always install the OpenID extension and then use Apache to block access to ''Special:OpenIDServer''.
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code><head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.
* Add admins sidebar (quick ban list access)
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)
* New link styles for links to mailing list archive
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Add proper styling to phrase elements
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]
* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)

===-Issues 2.0===

Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.

Aim is:

* Investigate possibility/santity of using Launchpad/Github/Google Code for spec issue tracking
* Wiki is excellent documentation tool. Terrible issue tracking tool.
* External services avoid large maintenance burden
* Could better handle this todo list
* Better handle issue resolutions
* Better handle issue discussions

====Considering====

=====Custom Install of Trac=====

* + Reliable
* + Well Established
* + Can customise to look like µf.org
* + Flexible milestones etc.
* + Hook into source repository of our choosing
* + OpenID support
* + Support whatever licensing we like
* - Administration overhead

Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?

=====Google Code=====

Chris Messina has ‘microformats’ on Google Code

* + Reliably Hosted, minimal admin overhead
* + Very flexible milestones/tagging
* + SVN repository for test cases, libraries
* - Can't be styled to µf.org
* - No OpenID
* - Ugly as sin
* - No Public Domain license support

=====Launchpad=====

Ben Ward has ‘microformats’ on Launchpad

* + BZR repository for test cases, libraries
* + Public Domain License Support
* - Not instantly intuitive
* - Seems better suited to software than specifications
* - Can't style like µf.org, but, quite pretty
* - No OpenID

=====Github=====

* + Git repository for test cases, libraries
* - Issue tracking is external (Lighthouse)
* - No OpenID

====Process====

* Evaluate options
** Consider integration points with µf.org
** Consider open standards a plus (OpenID)
** Consider effort in porting existing content
* Copy over issues from each wiki page as standalone bugs
* Ensure that each spec editor is added with suitable authorities to manage issues

===Deletions===
*Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]

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

===== minor update current specifications =====
* think about solving enumerated type issue (in [[hcard-issues]])
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incrementally incorporating [[hcard-issues-resolved|hCard issue resolutions]], moving them to [[hcard-issues-closed]] accordingly.
** 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]
** [[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''':
** resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-issues-resolved|hCalendar issue resolutions]], moving them to [[hcalendar-issues-closed]] accordingly.
** 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]
** [[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
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* create [[hcalendar-profile]] and have folks verify it. 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''':
* Write hReview 0.3 XMDP profile, and reconcile 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''':
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send 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?
When the Microsyntax wiki goes online, please add a link to it on the Microformats [[WikiNode]] page.
--[[User:DavidCary|DavidCary]] 08:34, 4 June 2009 (UTC)

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

=== XSLTs ===
<ul>
<li>Test scripts
<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>hAtom2Atom
<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
** 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])-- +1 Matt Dertinger
** 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]]

* Work on styles for [[zen-garden]] project.
* Style HTML cheatsheet to match Brian Suda's PDF.
* Write simplified help/implementation documents (how tos) for all finalised Microformats.
* Re-organise general FAQ and simplify
** (Feel free to add suggested tasks to my list below:)
*** Help converge on organization efforts ~bewest :-)

== 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: (hAtom2xyz.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)

hcard-google-bookmarklet

2009-07-26T02:44:34Z

Singpolyma: Created project page

http://github.com/singpolyma/hCard-to-Google-Bookmarklet

events/2009-07-25-dev-camp

2009-07-26T02:43:55Z

Singpolyma: /* projects */

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner and group photo
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.
* [http://www.flickr.com/photos/tags/ufdevcamp/ ufdevcamp tag on flickr]

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
* [[self-updating-address-book]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
* [[hcard-contact-autocompletion]] by [[User:Rohit|Rohit Khare]]
* [[microformat-services]] by ________
* [[unified-rsvp]] by _________
* [[hcard-google-bookmarklet]] [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
* [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
* [[twitter bus card exchange/display]] by [[User:perivision|Christopher]]
* [[hcard-creator-redesign|hCard Creator redesign]] by Cindy Li

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

events/2009-07-25-dev-camp

2009-07-25T22:51:51Z

Singpolyma: /* hack ideas */ Added hcard2google

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? [[User:Tantek|Tantek]]
* '''using hCard to build a self-updating address book''' - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
** +1 [[User:Tantek|Tantek]]
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''hCard to Google Address Book''' bookmarlet. [[User:Singpolyma|Singpolyma]]
* ...
</div>

== projects ==
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* hCard input/sign-up interface.
* [[hcard-contact-autocompletion]]

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

events/2009-07-25-dev-camp

2009-07-24T21:44:33Z

Singpolyma: /* participants */ added myself

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** T-shirts
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you!

Sign up to volunteer, attend, design, code, and build with microformats!

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, cleanup'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''
* ...

Planners: please see and keep up with the [[#planner_to-do]] section!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===
Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? [[User:Tantek|Tantek]]
* '''using hCard to build a self-updating address book''' - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
** +1 [[User:Tantek|Tantek]]
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* ...
</div>

== projects ==
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* ...

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planner roles ===
We need the following roles and responsibilities to be picked up by planners!
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

If you're a planner, please pick up and move one or more of these roles/responsibilities to your name above. Thanks!

Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

hatom-issues

2009-07-20T18:42:08Z

Singpolyma: Vote for comments, against url+uid

<entry-title> hAtom issues </entry-title>
These are externally raised issues about [[hAtom]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hatom-faq|hAtom FAQ]] and the [[hatom-issues-resolved|hAtom resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

== closed issues ==
See: [[hatom-issues-closed]]

== resolved issues ==
See: [[hatom-issues-resolved]]

== issues ==
Please add new issues to the '''bottom''' of the list by copy and pasting the [[#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2009===
==== too many required hentry properties ====
* {{OpenIssue}} 2009-05-26 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 requires numerous properties for an hentry (often based directly on required elements from the Atom standard). Given the broad variety of situations that hAtom is used in content, many (or even most) of these properties are not already specified in such content, and thus it is poor methodology to require them because there is a good chance (experience has shown) either (a) the content author will ignore the requirement, or (b) will make something up to satisfy the requirement. A few similar/overlapping/sub-issues are noted below (e.g. [[#Author|author is required]], and not always available).
*#* Proposed resolution. Make nearly all hentry properties "optional" in hAtom 0.2. Consider keeping at most only one required property, perhaps "updated" - that is, if there is no date of update/publication in the content you are trying to mark up, then perhaps it doesn't make sense to mark up that content with hAtom, since hAtom is for episodic, time-based/stamped content.
*#** consider pattern abstraction: all microformats should minimize "required" properties for the same reason, and perhaps ''only'' require at most a single property which is indicative of what that microformat is for, that is, if the author does not publish that one required property, then perhaps they should not be using the microformat that requires that one property.
*#* I have the same problem. I'm collecting various feeds to analyse them. The sources are often RSS 0.9, but I want to put the results into an Atom feed. --[[User:Simon Brodtmann|Simon Brodtmann]] 00:51, 1 July 2009 (UTC)
*#** entry:author should be optional and could be either a hCard or a string
*#** entry lacks a [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.category category] and it shuld either use rel-tag or just be a string
* 2009-07-18 [[User:DavidJanes]] I would like to break this into a separate issue for each currently required element, as we're likely to have to define defaulting rules

==== entry-title optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]]
*** +1 [[User:WebOrganics|Martin McEvoy]] but not recommended.
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model value should be
*** the empty string
**** +1 [[User:DavidJanes]]
**** -1 [[User:WebOrganics|Martin McEvoy]]
*** the value should not be blank.
**** +1 [[User:WebOrganics|Martin McEvoy]] see: [http://www.atomenabled.org/developers/syndication/#requiredEntryElements Required Entry Elements] from Atom Enabled.
**** [[User:DavidJanes]] what should it be then, if physically representing it is optional? Since Atom makes this a SHOULD and not a MUST (I'm not shouting, just following RFC convention), and we're assuming there's a good reason for the entry-title not to be present in the first place, why not an empty string?
***** [[User:WebOrganics|Martin McEvoy]] entry:title is a required attribute of atom at both feed and entry level, in both instances it says "Contains a human readable title" (a requirement) an empty string is not anything human readable (personal oppinion), maybe hAtom 0.2 should only recommend that the value of entry-title "should" not be an empty string.
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]
** +1 [[User:WebOrganics|Martin McEvoy]]

==== updated optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] ... the demand for optionality of the issue is high (cf the microsoft web clips) and if it remains required we're just going to reinvent hAtom without this element
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** the page creation date
**** +1 [[User:DavidJanes]]
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]

==== author optionality ====
* {{OpenIssue}} 2009-07-18 raised by [[User:DavidJanes]]
** this element should be optional
*** +1 [[User:DavidJanes]] for the same reason 'updated' should be optional: we'll just reinvent hAtom slightly differently otherwise
*** ... your vote here ...
** if this element is not in the [[hatom#In_General|physical model]], the logical model should be
*** "anonymous" (somewhat like [[hreview]]), except not explicit
**** +0.5 [[User:DavidJanes]]
*** make this implementation defined
*** something constructed from the page's URL & other information
*** ... your proposal here, your vote in a sublist ...
* include in hAtom 0.2
** +1 [[User:DavidJanes]]

=== 2008 ===
==== add url property to hentry ====
* {{OpenIssue}} 2008-09-10 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 uses [[rel-bookmark]] for permalinks. Permalinks may not always be hyperlinks or hyperlinkable. Thus I propose we re-use the <code>url</code> property (from [[hCard]], [[hCalendar]], [[hReview]], etc.) as a sub-property of the <code>hentry</code> property/container/root.
*#* Proposed resolution. Add "url" sub-property to "hentry" in hAtom 0.2.
*# {{ToDo}} can anyone provide examples where this would be used? [[User:DavidJanes]]

==== misuse of address element ====
* {{OpenIssue}} 2008-06-07 raised by [[User:Tantek|Tantek]]
*# hAtom 0.1 says "an Entry Author element SHOULD be encoded in an <code><address></code> element" and "find the Nearest In Parent <code><address></code> element(s) with class name author and that is/are a valid hCard" - this is a misuse of the address element. The address element means the ''contact'' for the page or major portion thereof (see [[hcard-faq#Should_I_use_ADDRESS_for_hCards|hCard FAQ: Should I use ADDRESS for hCards]]), which ''may'' also be the ''author'' but is not necessarily. See [[hcards-and-pages]] for more details on this semantic distinction.
*#* Proposed resolution: Eliminate all requirements and recommended use of the <code><address></code> element from hAtom.
*#** +1 --[[User:Csarven|Sarven Capadisli]] 11:57, 11 Nov 2008 (PST)
*#** +1 [[User:DavidJanes]]
* include in hAtom 0.2
** +1 [[User:DavidJanes]]

=== 2007 ===
==== marking up comments ====
* {{OpenIssue}} 2007-11-25 raised by [http://www.wirewd.com/ Ken Wronkiewicz].
*# There's no currently defined way to exactly handle threaded discussions. I think this is quite useful to have.
*#* The prior art is RFC [http://tools.ietf.org/html/rfc4685 4864]. The microformat solution should map fairly cleanly to this.
* include in hAtom 0.2
** -1 [[User:DavidJanes]] I think hAtom Comments should be a separate spec
** +1 [[User:Singpolyma|Singpolyma]] Comments are the important "next step" for hAtom. The proposal I've seen that I most liked was embedding an hfeed in an hentry.

==== atom:category scheme ====
* {{OpenIssue}} 2007-06-01 raised by [http://theryanking.com/ Ryan King].
*# ''[[rel-tag#Tag_Spaces|rel-tag tagspaces]] should map to atom:category schemes''
*#* hAtom already defines how to map term and label. It seems that the tagspace can easily map to scheme
*# {{ToDo}} can we get a real-world example mapping of this? [[User:DavidJanes]]

=== 2006 ===
====Geo====
* {{OpenIssue}} 2006-02-03 raised by [[BrianSuda]]
** We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
** +1 [[User:DavidJanes]] - this is just making explicit a particular composition. is it not? Also: if there's a geo in a hfeed (outside of hentry), should it be considered to apply to all entries?
* include in hAtom 0.2
** +1 [[User:DavidJanes]]

==== Relationship of rel-bookmark to url+uid ====
The concept of permalink is available in hCard and hCalendar as the classes url and uid. This combination matches the permalink semantics by indicating that the url should be derefenced to find a more dynamic or up-to-date version of the content, and that that url is a stable unique id that can be used to identify the content.

hAtom 0.1 uses rel-bookmark for the permalink concept. The current state of [[uid-brainstorming]] indicates that the [[hCard]] and [[hCalendar]] permalink concept is likely to be used in subsequent microformats. It may be important to reconcile hAtom with that trajectory. Possible reconcilliations include:

1) To leave things as they are. The two permalink concepts are to be kept separate.

2) Treat the two concepts as equivalent. Allow both in hAtom, and consider allowing both in other formats. eg <a rel="bookmark" href="http://example.com/"> would fill out uid and url values if they are not supplied explicitly.

3) Choose one over the other for hAtom and perhaps for future microformats also. "url uid" allows for some greater freedom (uid can be pointed at a non-url uid), but it is unclear at this stage whether that freedom is warranted or advisable to permit.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] (let's wait for resolution elsewhere, also would need real world examples)
** -1 [[User:Singpolyma|Singpolyma]]

==== Datetime format (atom:updated and atom:published) ====
* 2006-05-23 raised by [[User:RobertBachmann|Robert Bachmann]]
** Atom requires the use RFC3339 datetimes, while hAtom 0.1 does not specify which datetime formats may be used.
*** ACCEPTED FAQ - hAtom references datetime-design-pattern, which discusses which date format to use
** 2009-07-20 [[User:DavidJanes]] {{ToDo}} is this moot? can we move this to resolved?

==== Feed id (atom:id) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
*# atom:id is required for atom:feed. Thus it should be available in hAtom to.

It is suggested the Feed permalink should be used as the feed ID, however a piece by Mark Pilgrim (http://diveintomark.org/archives/2004/05/28/howto-atom-id) makes arguments against using permalinks and in favour of Tag URIs.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] not enough development of these ideas yes

==== Feed permalink (atom:permalink) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules:
**# a Feed Permalink element is identified by [[rel-bookmark]] at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed <del>SHOULD</del><ins>MAY</ins> have a Feed Permalink
**# a Feed Permalink element represents the concept of an Atom link in a feed.
**# if the Feed Permalink is missing, use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI
** 2006-04-03 [[User:ChrisCasciano|ChrisCasciano]] - I'm not sure that having a rel-boomkark-able link element at the feed level / to designate a feed in an html page separate for the other content is anything close to normal usage on the web, so I'd be very hesitant on suggesting this element "SHOULD" exist. I'm also curious when this element would link to anything but the current page (or some element on the current page) for this to be useful in the context of the HTML doc. I think taking the "id" on the feed is a more workable solution in most cases.
** 2006-04-03 [[User:RobertBachmann|Robert Bachmann]]: I've replaced "SHOULD" with "MAY".
** 2006-04-24 [[User:RobertBachmann|Robert Bachmann]]: Maybe we could simplify my proposal to:
*** "''Use the URI of the page; if the Feed has an "id" attribute, add that as a fragment to the page URI''"
*** IMO this would be good enough for at least 80% of the cases.
** 2006-04-12 [[User:DavidJanes]]: {{ToDo}} can we find an example of this in the wild and if so we should add it to the -examples page.
** [[User:Singpolyma|singpolyma]] 00:05, 13 Apr 2006 (PDT) : since the link is going to be pointing to the home page for the item wouldn't [[rel-home]] make more sense? That's what I'm using in the XOXO Blog Format and my reasoning was that if hAtom ever defined this rel=home made the most sense for what you would add, because the feed's link is not to a part of the site by to the home of the site.

* include in hAtom 0.2
** -1 [[User:DavidJanes]] not enough development of these ideas yes

==== Feed updated (atom:updated) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:updated is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# The Feed Updated element is identified by the class name <code>updated</code> at the feed level (inside a Feed element but not inside an Entry element)
**# If no element with the class name <code>updated</code> is present, use the youngest <code>updated</code> from the feed's entries.
** 2006-04-12 [[User:DavidJanes]] I like this. And the definition of "feed level"
** 2007-06-20 [[User:MikeKaply]] The "youngest" thing is a really bad idea. If a page has 100 hAtom entries, a parser would have to go through all 100 looking for a low date. That's crazy.
*** 2008-03-20 [[User:TobyInk]] Not crazy at all. I've just implemented an hAtom to Atom converter and I do precisely this. Most (useful) hAtom parsers will "go through all 100 entries" anyway, won't they? So why not look for the youngest updated date as part of that loop. The only slight annoyance is that in RFC 4287, the <atom:updated> element must occur before the first <atom:entry> element -- this is easily solved by inserting a placeholder <atom:updated> element, looping through the entries and then going back and filling in the date. This is really, really, '''not''' a difficult thing to implement.

* include in hAtom 0.2
** +0.5 [[User:DavidJanes]]

==== Feed title (atom:title) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:title is required for atom:feed. Thus it should be available in hAtom to. I'm proposing the following rules:
**# a Feed Title element is identified by the class name <code><del>entry</del><ins>feed</ins>-title</code>
**# a Feed SHOULD have an Feed Title
**# a Feed Title element represents the concept of an Atom feed title
**# if the Feed Title is missing, use
**#* <del>the first <code><h#></code> element in the Feed, or</del>
**#* the <code><title></code> of the page, or
**#* assume it is the empty string
** 2006-04-01 [[User:ChrisCasciano|ChrisCasciano]] - I think that the fall back to using the first h# on the page is dangerous.. depending on the pge it may be something that changes often (first h# is a post title) or is otherwise ambiguous. I would think using <code><title></code> before h# would be prefered if not the most common desire of the page author.
** 2006-04-05 [[User:RobertBachmann|Robert Bachmann]]: Okay. Deleted "the first <code><h#></code> element in the Feed, or"
** 2006-04-12 [[User:DavidJanes]] Note also in support of this decision that many blogs use <code><h#></code> to encode the date for a group of postings
** 2006-04-12 [[User:DavidJanes]]: why <code>entry-title</code> for the feed title. Why not <code>fn</code> or <code>feed-title</code>?
** 2006-04-12 [[User:RobertBachmann|Robert Bachmann]]: Sorry, this was a "copy & paste" mistake. Fixed now.
** 2007-02-26 [[User:MikeKaply|Mike Kaply]]: I think a feed title should be mandatory if an hfeed is present. If you have multiple feeds on a page, there is no way in a user interface to distinguish between different feeds.

==== Feed author and Entry author (atom:author) ====
* {{OpenIssue}} 2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** I'm proposing the following rules for Feed author:
**# a Feed Author element is represented by class name <code>author</code> at the feed level (inside a Feed element but not inside an Entry element)
**# a Feed Author element represents the concept of a Atom author
**# a Feed Author element MUST be encoded in a [[hcard|hCard]]
**# a Feed Author element SHOULD be encoded in a <code><address></code> element
**# a Feed MAY have more than one Feed Author elements
**# if the Feed 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 <del>the Feed is invalid hAtom</del> <ins>there is no Feed Author</ins>
** I'm proposing the following rules for entry author:
**# an Entry Author element is represented by class name <code>author</code>
**# an Entry Author element represents the concept of an 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
**#<del> If a Feed has no Feed author each Entry MUST have at least one Entry Author element</del>
**# <ins>If an Entry is enclosed by a Feed and this Feed has no Feed author, each Entry MUST have at least one Entry Author element. If an Entry is not enclosed by a Feed and has no Entry Author:
**#* 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</ins>
**# an Entry MAY have more than one Entry Author elements
** [[User:Singpolyma|singpolyma]] 00:11, 13 Apr 2006 (PDT) : feed should not be invalid hAtom if feed-level has no author -- it should be invalid if feed-level has no author AND one or more entries have no author. Also, one or more entries may be missing an author IF feed-level has an author.
** 2006-04-17 [[User:RobertBachmann|Robert Bachmann]]: I replaced "the Feed is invalid hAtom" with "there is no Feed Author"

==== Entry id (atom:id) ====
* {{OpenIssue}}2006-04-01 raised by [[User:RobertBachmann|Robert Bachmann]]
** atom:id is required for atom:entry. Thus it should be available in hAtom to. The Entry permalink should be used as the entry id.
** --[[User:Federico|Federico]] 19:52, 25 Apr 2006 (PDT): I would add "Only if the id attribute is not defined for the element that contains the entry". The id attribute can be a tag uri. If you use always use the Entry permalink as the entry id and the Atom feed uses tag uris, you would end with two different ids for the same entry.
** 2006-12-31 response by [[User:ComputerKid|Emanla Eraton]] No, it shouldn't be a permalink. It should be a "tag:" id for entries.
** 2007-06-06 [[RyanKing]] - the syntax of tag URIs and html id attributes are incompatible. HTML disallows forward-slash (/) in ids [http://www.w3.org/TR/html401/types.html#type-name], while tag URIs require them [http://www.faqs.org/rfcs/rfc4151.html].

==== Author ====
===== author as an hcard is too much to require =====
The following 3 items were extracted from the conversation starting on irc with [http://rbach.priv.at/Microformats-IRC/2006-03-24#T152248 logs available starting around here]

* [[User:Fil|Fil]] If, for example, you are programming an "aggregator" of news syndicated from many sources like in [http://sedna.spip.org/sedna/ Sedna], chances are that you don't control what "authors" look like; they can be nicely microformated (if coming from an mf-enabled system), but most probably they will be internally represented by a string that contains, in some random order, a name, and/or an email, and so on. If you want to pass on this information in an hAtom feed, you can't possibly reformat it to an hCard. But you still want to pass it on in a <div class="author"> element.
** [[Tantek]] I don't believe the "can't possibly" statement. Please provide a URL to a concrete example that you think you can't possibly reformat into an hCard so we can all take a look.
** [[User:ChrisCasciano|ChrisCasciano]] details of Fil's extraction [http://rbach.priv.at/Microformats-IRC/2006-03-24#T153453 in irc logs] including sting data passed to his app in the form of "Béatrice XXXXXXX beatrice.xxxxxx@@zzzzzzzzz.com"
** [[User:Fil|Fil]] the example url was given up there (Sedna); note that the author information comes from syndication links; nobody is going to edit them to outline what is the name, what is the email and so on, as everything is flowing through automatically... so here the "author" data is dirty, and will not be cleaned into an hCard. We can force it to be in an hCard but it will be meaningless if the source (original data) wasn't built on an mf-enabled software.

* [[pnhChris]] i don't disagree.. the field often comes from places too dumb to follow these rules well; even cases like wordpress that allow users to present their name 1 of 6 or 8 difference ways (from username to LF, FN) .. its not just writing a template to output as hatom at that point... you have to go further upstream where the string to be displayed is chosen .. I also think its pointless to have 10 vcards on the same page whose only data is a generic name like "Chris"
** [[Tantek]] 10 vcards that are the same is pointless yes, but identifying who the author of 10 posts are is not pointless - that's the difference.
** [[User:ChrisCasciano|ChrisCasciano]] Agreed, but I still have concerns that "author" in hAtom does not always make for good hCards, though the situations where it does is optimal. My comments in the conversation were old comments I've made before over concerns and hardships or the lack of desire to make crappy data more portable, in neither of these cases do I think my two comments alone provide reasons to make change from the hAtom 0.1 spec
***[[User:Phae|Frances]] - Just thought I'd mention a scenario I have where the author of an entry does make a pretty useless vCard - the author in each case is an entire team ("creative team", "technical department") etc., rather than a specific, identifiable, person. Some use may be regained when URL to specific team/information is included, in this circumstance.
****[[User:TobyInk]] - A vCard (thus an hCard) does not have to represent a person -- it could represent an organisation, or a department or team.
* [[User:Fil|Fil]] for the moment, to comply losely with hAtom 0.1, I will use <code><nowiki>My Name</nowiki></code> ; but it's not good
** [[Tantek]] You can actually simplify that (one fewer span) with: <code><nowiki>My Name</nowiki></code>

* require author as [[hCard]] (i.e. no change from 0.1)
** +2 [[User:DavidJanes]]

==== Entry source (atom:source) ====
* raised by [[User:Kevin Marks|Kevin Marks]]
** When defining hAtom 0.1, atom:source was omitted. We should consider adding this back in as a useful element for providing citations of composite feeds.
*** 2009-07-20 [[User:DavidJanes]] {{ToDo}} we need an example of how this would look in the real world

== Other Questions and Issues ==
General comments, modeling issues, algorithm issues, should have issues, etc. go here.

=== Entry Updated Required? -- Blogger Issue ===
moved to [[hatom-brainstorming]]

=== 'MAY have multiple Feed elements' -- details and viability of multiple feeds ===
moved to [[hatom-brainstorming]]

== pre 0.1 issues ==
'''This section is more or less closed, as hAtom 0.1 is out the door. If there are open issues that you are championing that didn't make it into hAtom 0.1, move them up above to the hAtom 0.2 section'''

See: [[hatom-issues-pre-0.1]]

== Template ==
{{issues-format}}

== See Also ==
* [[hatom|hAtom]] - the draft proposal
* [[hatom-faq]] - knowledge base
* [[hatom-issues-resolved]]
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[mfo-examples]]
* [[naming-principles]]

hcard-brainstorming

2009-06-25T23:32:41Z

Singpolyma: Documenting how I've done peopletagging

<h1> hCard Brainstorming </h1>
{{TOC-right}}
This page is for brainstorming about various uses and details of [[hcard|hCard]]. This page contains proposals. For the current state please see [[hcard|hCard]].

== Authors ==
* [http://suda.co.uk/ Brian Suda]
* [http://tantek.com/ Tantek Çelik] (formerly of [http://technorati.com Technorati, Inc])

== Contributors ==
* [[User:Atamido|Atamido]]
* [[User:ChrisMessina|ChrisMessina]]
* [[User:DimitriGlazkov|DimitriGlazkov]]
* [[User:AndyMabbett|Andy Mabbett]]
* ...
* ... and many others

== Problems Being Solved ==

Some of the problems that [[hcard|hCard]] helps to solve:

* having to enter business cards that go out of date (subscribe to someone's syndicated [[hcard|hCard]] instead).
* annoying "update your contact info" email from various centralized contact info services
* [[social-network-portability]] through the use of [[hcard-supporting-user-profiles|hCard supporting user profiles]] and [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]]

== Named locations ==
Most hCards contain contact information for people or organizations. But locations that aren't organizations are also deserving of their own hCard (e.g. somebody's house/apartment). This situation can be represented by combining "fn" and "extended-address".

=== "fn" and "extended-address" combination ===

'''Proposal''': Similar to [[hcard#Organization_Contact_Info|organization contact info]], if the "fn" property and an "extended-address" property have the exact same value (typically because they are set on the same element, e.g. <code>class="fn extended-address"</code>), then

# The hCard represents contact information for a place and SHOULD be treated as such.
# The author also MUST NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "".
# Parsers SHOULD handle the missing "n" property by implying empty values for all the "n" sub-properties.

'''Further proposal''': Consider also an hCard for a City, "Birmingham, England": Birmingham may be the "fn" and the "locality", but it's not an "extended-address". Perhaps the rule should be that the hCard is for a place if the "fn" is on any address component (e.g "fn locality" or "fn street-address")?

'''For further consideration''': One real problem right now is that we provide a field for our users to enter a 'Location' on our [http://timespeople.nytimes.com/view/user/9354457/1/index.html User Pages]. In real life this has ranged from '8th floor', 'New York', 'Company Name', My Desk', 'http://some.site.com' - the majority being generalized geographic city or state names. Right now there is no property to properly handle this, but this one appears to come close. If this cannot be used for such purposes I would ask that this be looked into further as I don't think its a unique problem.
* Have you considered using <code>label</code> instead of <code>adr</code>?

=== Examples in the wild ===

* The named location "Picnic benches" in the address "Picnic benches, South Park, San Francisco, California" in [http://adactio.com/journal/1364/ a blog post on adactio.com].
<pre><nowiki>


Picnic benches
South Park
San Francisco
California


</nowiki></pre>

==== Potential examples in the wild ====

* The location "Phone Boxes by the Sealife Centre" [http://upcoming.yahoo.com/venue/5668/ on Upcoming] is currently marked up as "fn org":
<pre><nowiki>
<div class="vcard">
<div class="fn org">Phone Boxes by the Sealife Centre</div>
<div class="adr">
Marine Parade 
Brighton & Hove,
England
BN2 1TB 
United Kingdom 
01273 606674
</div>
<div class="note">Just a meeting place, in case the venue changes.</div>
</div>
</nowiki></pre>
This could be marked up as:
<pre><nowiki>
<div class="vcard">
<div class="adr">
<div class="fn extended-address">Phone Boxes by the Sealife Centre</div>
Marine Parade 
Brighton & Hove,
England
BN2 1TB 
United Kingdom 
01273 606674
</div>
<div class="note">Just a meeting place, in case the venue changes.</div>
</div>
</nowiki></pre>

===Concerns===
The above seems to be an elegant solution, but a wider variety of examples form published pages are needed, to be sure it meets all common scenarios. these should include cases where "adr" is not already used; note that in that case an extra level of nesting is required. The implications of this, for hCards already published, should be considered.

Also, what about hCards for published locations, which already include an extended address?

e.g.

<pre><nowiki>
<div class="vcard">
Powell's Pool

Sutton Park
Birmingham
England

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

[[User:AndyMabbett|Andy Mabbett]] 05:40, 15 Dec 2007 (PST)

===Revised proposal===
*See revised proposal at [http://microformats.org/discuss/mail/microformats-discuss/2007-December/011169.html microformats-discuss/2007-December/011169.html]
** [http://buzzword.org.uk/cognition/ Cognition] supports this.

=== named location formats ===
Previous named location format efforts:

==== Simple GeoRSS featurename ====
The [http://georss.org/simple Simple GeoRSS] vocabulary contains the following named location example in the "Additional Properties" section that references a <code>featurename</code> tag.

<blockquote><h3>Feature Type, Feature Name, and Relationship Tags</h3>The Feature Type, Feature Name, and Relationship tags are specified as GeoRSS elements.<pre><nowiki>
<georss:point>45.256 -110.45</georss:point>
<georss:featuretypetag>city</georss:featuretypetag>

<georss:relationshiptag>is-centered-at</georss:relationshiptag>

<georss:featurename>Podunk</georss:featurename>
</nowiki></pre></blockquote>

A [http://www.google.com/search?q=site%3Ageorss.org%20featurename search for featurename on georss.org] fails to find any other references however, including a definition.

An [http://lists.eogeo.org/pipermail/georss/2006-December/000895.html email on the georss list from Dec 2006] thread "featurename, other missing bits from the site" notes that "there is some updating to do" in response to a concern that "that descriptions of "featurename" are not present on GeoRSS Simple and the GeoRSS Model. GeoRSS GML makes no mention of the non-geometric properties at all."

== FN Nickname semantic ==
There are many sites (e.g. [http://flickr.com Flickr], [http://consumating.com/ Consumating]) which permit the user to '''both''' have a multi-word login/handle/alias, '''and''' not show their ''real'' name (fn, n, given-name, family-name etc.).

For the people represented by the profile pages of these sites, the best we can do is mark-up their login/handle/alias as their "nickname". Originally, we had thought that such handles etc. were single words only, and thus we created the [[hcard#Implied_.22nickname.22_Optimization|Implied nickname optimization]] accordingly, where you can markup the handle as an "fn", and have it automatically set a "nickname" property value, and empty values for all the "n" sub-values.

In order to deal with multi-word handles, similar to the [[hcard#Organization_Contact_Info|hCard Organization contact info]] method, the following is proposed:

=== "fn" and "nickname" combination ===

Due to the use of potentially multi-word nicknames/handles/usernames in content published on the Web, (e.g. on sites like [http://flickr.com Flickr] and [http://consumating.com/ Consumating]), hCard has a mechanism for specifying a multi-word "fn" that is also a "nickname" without affecting any "n" sub-properties that are otherwise specified, and explicitly implying empty defaults for "n" sub-properties.

Similar to the [[hcard#Implied_.22nickname.22_Optimization|implied "nickname" optimization]], if the "fn" property and a "nickname" property have the exact same value (typically because they are set on the same element, e.g. <code>class="fn nickname"</code>), then

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

== Implied FN from N ==
Since the "n" property is more detailed and structured than the "fn" property, and [[hcard-examples-in-wild]] have shown that very often what is specified for "n" sub-properties is also specified for the "fn" property, we could add the following implied "fn" optimization which would permit sites to only use "n" and its subproperties.

In addition, some sites don't have contiguous uninterrupted text that represents the desired "fn" value, and would much rather have the "fn" implied from "n" subproperties. E.g. "Citizen Space Citizens" on [[hcard-examples-in-wild]].

=== implied "fn" from "n" optimization ===
If an hCard has no "fn", yet has an "n" property with one or more subproperties, then the "fn" property value can be implied by concatenating the "n" subproperty values as follows, with a space between each subproperty value, and multiple subproperty instances.

* 'honorific-prefix'es (as found in document order)
* 'given-name'
* 'additional-name's (as found in document order)
* 'family-name'
* 'honorific-suffix'es (as found in document order)

== Implied N from its subproperties ==
Since the "n" subproperties are sufficiently uniquely named (that is, they are not used by any other hCard property), and "n" is one of the [[hcard-singular-properties]], it is possible to consider leaving out the "n" property itself fo the hCard, and simply directlly using the subproperties, as properties of the hCard.
* [http://buzzword.org.uk/cognition/ Cognition] has supported this for ages.

=== implied "n" from its subproperties ===
If an hCard has no "fn" nor "n" properties, then the entire scope of the hCard is considered to be inside an implied "n" property.

E.g. this markup:
<pre><nowiki>

Tantek
Çelik

</nowiki></pre>

would be treated from a parsing perspective as:

<pre><nowiki>

Tantek
Çelik

</nowiki></pre>

Which, with the '''implied "fn" from "n" optimization''', would then be effectively treated as:

<pre><nowiki>

Tantek
Çelik

</nowiki></pre>

* a related request from the mailing list: http://microformats.org/discuss/mail/microformats-discuss/2007-September/010791.html

== Examples ==

* See [[hcard-examples]], which provides several illustrative instructive examples, as well as 1:1 hCard examples for each example in [http://www.ietf.org/rfc/rfc2426.txt RFC 2426].

=== Using RFC2806 with hCard ===

[http://www.ietf.org/rfc/rfc2806.txt RFC 2806] defines the telephone scheme "tel:", "fax:" and "modem:" to handle phone communications with URIs in the same way, "mailto:" is defined for email. It's part of the list or registered schemes by IANA : [http://www.iana.org/assignments/uri-schemes Uniform Resource Identifier (URI) SCHEMES]

<pre><nowiki>
tel telephone [RFC2806]
fax fax [RFC2806]
modem modem [RFC2806]
</nowiki></pre>

It is practical to write your tel number like this.

<pre><nowiki>
<a class="tel" href="tel:+1-919-555-7878">+1-919-555-7878</a>
</nowiki></pre>

or even

<pre><nowiki>
<a class="tel" href="tel:+1-919-555-7878">Mr Smith's phone</a>
</nowiki></pre>

You can add support for "tel:" to your desktop and to your browser

* For Gnome, edit ~/.gnome/Gnome and add something to the URL Handlers section. (Dan Connolly uses this to get galeon to launch telnum from [http://dev.w3.org/cvsweb/2001/telagent/ telagent sources] for tel URIs)
* In Mozilla, [http://dizzy.mozdev.org/ Dizzy]
* In Internet Explorer, [http://msdn.microsoft.com/workshop/networking/pluggable/overview/overview.asp Asynchronous Pluggable Protocols]

On the CSS front… You could for example add automagically an icon. I have put the property !important for those who wants to add it to their own stylesheet in their browsers, so they know type of links when browsing.

<pre><nowiki>
a[href^="tel:"]:before {
content: '\260f ' !important;
padding-left: 20px !important; }

a[href^="mailto:"]:before {
content: '\2709 ' !important;
padding-left: 20px !important; }
</nowiki></pre>

== Encoding "modern" attributes ==

Since vCard was first established, various interactive communication technologies and addressing schemes have been widely adopted. Although there aren't specific properties for these technologies / addressing schemes, they can be captured as URLs or email addresses.

This has now been written up for the most part. See:

http://microformats.org/wiki/hcard-examples#New_Types_of_Contact_Info

Still to be addressed:

* iChat mac.com addresses, simply store "@mac.com" email addresses, e.g.
** <code><nowiki><a class="email" href="mailto:steve@mac.com">...</nowiki></code>
* MSN Instant Messenger, you can simple store "@hotmail.com" or "@msn.com" or "@passport.com" email addresses.
* Internet Relay Chat (IRC), use "irc:" URLs.

A suggestion relating to the rise of VoIP protocol (Skype, etc):

Should these protocols be marked up using the <code><nowiki></nowiki></code>. It seems logical that a means to communicate with another via voice should be marked up as a telephone address, rather than the currently suggested URL property.

== Auto-Discovery ==

See [[hcard-brainstorming-autodiscovery]]

== geo improvements ==
''See [[geo-brainstorming]]''

== Other use cases ==
Please add your suggestions!

hCard microformats could be used to:
*Calculate and display the subject's age "as of today".
*Calculate and display the subject's age at death (if a [[hcard-date-of-death|Date of Death]] is available)
*Generate a recurring iCal for a living subject's birthday
*Generate a recurring iCal for a dead subject's "anniversary of birth" (if a [[hcard-date-of-death|Date of Death]] is available)
*...

== Issues with vCard Applications ==
See [[vcard-implementations]].

== Open Questions ==

Q: since many of the components would be using CSS classes for encoding data, it is possible to MIX two different profiles. (e.g. hCard and XFN) There are no real constraints on where/how to enforce class names, these are based on the html profile, since it is difficult to associate the text within the attribute to a specific profile.

<pre><nowiki>
...
<a href="mailto:joe.smith@example.com" class="fn" rel="met">Joe Smith</a>
...
</nowiki></pre>

-- [http://suda.co.uk/ Brian Suda]

Q: Preserving White space? Should the transforming applications preserve extra white space characters? For example:
<pre><nowiki>
<a href="http://mywebsite.com/" class="fn n">
John
Q.
Public
</a>
</nowiki></pre>

When transformed into a vCard, the N property will pick apart the span tags and create the value for N correctly seperated by colons. The FN property will take a string and simply display it. There are two possible renderings for FN:
<pre><nowiki>
John Q. Public

John
Q.
Public
</nowiki></pre>

Either the white-space is preserved or it is not. Which should the transforming applications render?

-- [http://suda.co.uk/ Brian Suda]

A: The parsing application should follow the white space collapsing rules of the mime type it retrieves. I.e. if it retrieves a "text/html" document, it should do HTML white space collapsing.

-- [http://tantek.com/log/ Tantek]

Many of the Questions and Answers are relevant to both ["hCal"] and hCard.

Q: Would it be appropriate to wrap the name of the vCard owner with <dfn/>? This may give the hCard some added semantic value in the XHTML document.
<pre><nowiki>



<a class="internet" href="mailto:jfriday@host.com">
<dfn>
Joe Friday
</dfn>
</a>

+1-919-555-7878
Area Administrator, Assistant


</nowiki></pre>
-- [http://www.ben-ward.co.uk/ Ben Ward]
* If the answer to the above Q is "yes", why not use the following?
<pre><nowiki>
<dfn class="fn">Joe Friday</dfn>
</nowiki></pre>
or
<pre><nowiki>

<dfn class="vcard">

<a class="internet" href="mailto:jfriday@host.com">
Joe Friday
</a>

+1-919-555-7878
Area Administrator, Assistant
</dfn>

</nowiki></pre>
This would mark the entire hcard as the "defining instance".

[[User:Bob Jonkman|Bob Jonkman]] 10:07, 13 Jul 2007 (PDT)

== Applications ==
Applications that are hCard aware or can convert hCard to vCard formats.

=== Copy hCards favelet(s) ===
* I think a Favelet would work nicely here. When you find a page that is hCard friendly, you click the favlet and you get yourself a vCard. This is done! See X2V in the implementations section of the [[hcard|hCard]] spec.

=== Distributed Commentor Icons ===

''The URL reffered to in this section is no longer available. The thoughts on using icons are however still relevant.'' [[User:WilleRaab|WilleRaab]] 16:55, 23 Jul 2007 (PDT)

* See [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] for an example of hCards used for comment authors (commentors). The system used there, "Gravatars", is a centralized site that serves commentor icons that requires login etc.

What if we gave each commentor the option of hosting their own icon?

A distributed commentor icon implementation could work like this:

# Given the URL of a commentor, look for an <code><address></code> element with classname of "vcard" at the commentor's URL. The <code><address></code> element is supposed to be the contact information for the page (see [[hcard-faq|hCard FAQ]] for more info), so this makes sense.
# Next, look for the first element inside that hcard that has a classname of "logo".
# Hopefully that element is an <code><img></code>, and if so, use its src to get the commentor's icon.
# Presto. You've got distributed commentor icons!

== Spam prevention ==
hCard uses <code>mailto:</code> links, and therefore
it automatically "inherits" the disadvantage of <code>mailto:</code> links:
These links can be easily detected by emails spiders (used by spammers).

Email addresses are picked up like any other link crawled by a search engine and trustworthy crawlers may be deterred from adding emphasis while indexing these links by including rel="nofollow" (See [[rel-nofollow]]). However, email addresses used for spam are crawled by email spiders which will likely ignore this attribute.

There are ways to prevent email address detection by simple email spiders, while
still retaining full compatibility with (X)HTML applications.
One common way is to "encode" the the "m" of "mail" and "@" with character entities, yet it's unwise to follow a convention of only encoding specific characters because the email spiders can pick up on this too:

Example of the original link:
<pre><nowiki>
<a class="email" href="mailto:john.smith@example.com">john.smith@example.com</a>
</nowiki></pre>

Example of the "encoded" link (with rel-nofollow added):
<pre><nowiki>
<a class="e&#109;ail" rel="nofollow" href="&#109;ailto:john.smith&#064;example.com">john.smith&#064;example.com</a>
</nowiki></pre>

Simple email spiders which do not do character entity decoding will therefore not be able to find your email address.

''Note:'' Perhaps there are or will be email spiders which can decode entities, so the this technique will only help with some (cheap) email spiders.
(See also: http://rbach.priv.at/Misc/2005/EmailSpiderTest)

=== Other prevention methods to consider ===
* Using server-side code to implement character entities randomly
* Displaying the address in a way thought to be only human readable (thus breaking the link):
** Using an image instead of text (could still be machine readable using OCR)
** Using human readable text that conveys the need for editing before use (eg PLEASE-NO-SPAM_name@example_NO-SPAM.com)
* Using javascript for client-side decryption of an encrypted address (requires javascript to be enabled)
* Pointing to an email form or other URL instead of an email address

== Tutorials ==
* How to hCard encode entries in Popular blog software.
* Good reasons to publish your hCard
** as a business, get people to put you in their address book so they'll find you later
** as a business with an email list, get people to add you (with email address) to their address book so that your email list works via whitelisting via the address book.

* [http://24ways.org/2006/styling-hcards-with-css Styling hCards with CSS] is a text on how to use CSS to make an improved presentation of an hCards contents.

== Parsing ==

See [[hcard-parsing-brainstorming]]

== Birthday Reminders ==
*hCard consumers could calculate the current age of hCard subjects, from the DoB. [[User:AndyMabbett|Andy Mabbett]] 07:47, 20 Apr 2007 (PDT)
*for hCards with DoB, hCard consumers could generate and export a recurring hCalendar. [[User:AndyMabbett|Andy Mabbett]] 08:06, 20 Apr 2007 (PDT)
**If/ when [[hcard-date-of-death|Date of Death]] is added to hCard, parsers could instead generate a recurring "death-anniversary" hCalendar. [[User:AndyMabbett|Andy Mabbett]] 08:08, 20 Apr 2007 (PDT)

== Post vCard additions ==

Keeping hCard properties and values as a 1:1 representation of vCard properties and values has numerous benefits such as simplicity, stability, interoperability with the vast number of existing vCard applications etc.

However some have found vCard to be limiting in terms of the data/properties/fields they want to express in contact information. Some implementations use vCard extensions to express such information [citation needed].

This section is for documentation of such suggested additions. Empirical evidence of actual *real world* examples on the Web of people publishing this information would be a good step towards considering any such additions/extensions.

* '''altitude'''. From [[hcard-issues]].
**See [[geo-elevation-examples]]
* '''vat-number''' : for VAT numbers of companies, which are used a lot in Europe and they need to be published on Belgian publications (including websites).

* '''gender'''
** See [[vcard-suggestions#Gender]]

* '''date-of-death'''
** See [[hcard-date-of-death]]

Thus see (and add to): [[vcard-suggestions]]

Another path to consider is the development of another microformat which includes an hCard and then extends it with additional properties for a particular domain. In many ways [[hresume|hResume]] has already done this. Other related efforts:
* [[genealogy]]
* [[profile]]

Using hCard as a stable building block for additional microformats may seem more desirable than incrementally growing hCard itself.

Of course if vCard were extended itself, that may provide impetus to add such extensions to hCard in order to maintain the 1:1
representation of properties/values.

==Wikipedia's Persondata==
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:02, 28 Jan 2007 (PST)

== TODO ==

* The [[hcard-profile]] needs verification and perhaps a URL for retrieving the actual XMDP, rather than as <pre> text on a wiki page.
* Complete translating the examples from the vCard spec into hCard, and place them on a separate hCard examples page.
* Create a "rich" but realistic hCard example, say for example for a salesperson, who wants to put a whole bunch of contact information on their website in order to be found/contacted easily.
* Provide examples of how to encode instant messaging (IM) accounts. Figure out what would the mailto: or aim: URL in hCard look like in vCard. And take a look at what vCard applications do today with IM addresses.
* Clarify contradictory copyright statements, per http://microformats.org/discuss/mail/microformats-discuss/2007-July/010243.html

== CSS Styles ==
Not only can you create semantics with the hCard values, but you can add CSS styles to them as well. You are free to style the terms in any way you want, but here we can list a few ideas for how to style terms.

If you want to encode hCard data, but do NOT want to display it in the HTML code (WARNING: This is very much recommended AGAINST, and in general against the microformat principle of marking up visible data), then you can hide that tag in CSS with the following code:
<pre><nowiki>
Hidden Data
</nowiki></pre>
Transforming applications will still find the data and use it when converting hCards to vCards.

== Other Implementations/Ideas ==
* [http://www.w3.org/TR/2001/NOTE-vcard-rdf-20010222/ Representing vCard Objects in RDF/XML] This could allow conversion of vCard data from XHTML to RDF and from RDF to XHTML
* It would also be possible to convert XFN and hCard to FoaF.
* [http://microid.org/ MicroID in hCard]

== Accepted Suggestions ==

=== Encoding Company data as a Business Card (proposal) ===

( Accepted: http://microformats.org/wiki/hcard#Organization_Contact_Info )

In the wild there are several hCards that do not currently validate because they are businesses that have omitted the "fn" property in favor of the "org" property.

Proposal: hCards representing a business or organization MUST set fn AND org to the same value. Parsers may then use this equivalence, if detected, to treat an hCard as the contact info for a business or organization rather than an individual.

Note that [http://microformats.org/wiki/vcard-implementations#organization_vs._individual Apple Address Book supports this semantic when importing vCards].

See the [http://technorati.com/about/contact.html Technorati Contact Info] for an example.

=== Implied "FN and N" Optimization (proposal) ===

Right now a parser first looks for an "n" element.

And then if no "n" is present, look for an "fn" element to use to imply an "n" element per the "implied n property" rules in the spec.

BACKGROUND:

Due to the prevalence of the use of "nicknames" or "handles" on the Web, in actual content published on the Web (e.g. authors of reviews), there has been a discussion about adding a "fn" shortcut to the "n" shortcut that used the "nickname" as a fallback.

PROPOSAL:

We should consider adding one more implied optimization after the steps documented above and that is:

If no "fn" is present either, then look for a "nickname" element to use to imply both the "fn", and the "n/given-name", leaving the "n/family-name" as empty.

This would enable "nickname" only hCards for denoting and individual on a website, which is quite common on blogs and reviews published on the Web.
* +1 [[User:Atamido|Atamido]]
* +1 [[User:ChrisMessina|ChrisMessina]] - note: multiple alternate nicknames should also be allowed
* +1 [[User:DimitriGlazkov|DimitriGlazkov]]

== Implied work tel ==

=== Problem ===

Some phone numbers are not always documented of type 'work'. The type 'work' is usually implied from context.

=== Examples in the wild ===

[[http://www.nvidia.com/page/contact_information.html NVidia contact information]]

Only 'Tel' is specified. The fact that it is of type 'work' can be assumed from the context: the name of an organization is present.

<pre>
NVIDIA CORPORATE OFFICE: 
2701 San Tomas Expressway 
Santa Clara, CA 95050 
Tel: 408-486-2000 

Fax: 408-486-2200 
...

</pre>

[[http://www.supermarketguru.com/page.cfm/369 Supermarketguru.com]]

<pre>


Phil Lempert: <a href="mailto:plempert@supermarketguru.com">plempert@supermarketguru.com</a> 

SupermarketGuru.com 
3015 Main Street, Suite 320 Santa Monica, California 90405 
Telephone: 323-860-3070


</pre>

Here only 'Telephone:' is specified, a FN is present ('Phil Lempert') but because an ORG is present ('SupermarketGuru.com'), it can be safely implied that '323-860-3070' is a tel or type work.

=== Proposal ===

If an ORG is present in a VCARD, a TEL with no TYPE has an implied TYPE 'work'

==== Comments ====
* Though it may be safe to make that assumption for the given example (and though it might have been wise to make this rule from the outset), we now can't know that it will alwyas be safe to do so, for all pre-existing hCards. Consider people whose organisation represents voluntary work, honorary roles and so forth. [[User:AndyMabbett|Andy Mabbett]] 00:33, 8 Jan 2008 (PST)

== Peopletagging ==

Just documenting this here so it's written down. I have been adding class="url" to hcards of people in my blog posts as a way of approximating "people tagging" (like the Facebook "tag people mentioned in this note").

I used to want to use class="url" rel="tag" in an hCard to do this, but the URL form requirements of rel="tag" do not fit typical profile URLs at all, so I have stopped trying to do things that way.

-- [[User:Singpolyma|Singpolyma]] 23:32, 25 June 2009 (UTC)

== Rejected Suggestions ==

Suggestion: ''The use of class="url" on an <a> tag to represent an hCard URL property is redundant. By virtue of the <a> tag you know this is a URL.''

Rejected. This is a bad suggestion because although it appears to reduce redunancy and keep things cleaner, it also creates a few problems. Without explicitly noting that this is a URL then any <a> tags within a 'vcard' would be considered a URL, for example:
<pre><nowiki>

...
<ul class="categories">
<li><a href="http://w3c.org">W3C</a></li>
</ul>
...

</nowiki></pre>

There is no way to "turn-off" the encoding of the W3C URL, whereas if "url" needed to be explicitly listed in the class attribute list, then by NOT listing it you could effectively turn it off.

== References ==

=== Normative References ===
* [http://www.ietf.org/rfc/rfc2426.txt RFC 2426] vCard RFC
* [http://www.ietf.org/rfc/rfc2397 RFC 2397] data URI RFC
* [http://gmpg.org/xmdp/ XMDP]

=== Informative References ===
* [http://www.imc.org/pdi/ Personal Data Interchange (PDI) at the Internet Mail Consortium]
* [http://tantek.com/log/2004/07.html#d27t1049 Markup language design notes]
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class]
* [http://www.icao.int/mrtd/download/technical.cfm ICAO - Machine Readable Travel Documents format]

== Related Pages ==

{{hcard-related-pages}}
* [[adr-poll]]

x2v-issues

2009-06-25T07:33:22Z

Singpolyma: I'm a fool and that issue isn't there...

x2v is one of the main microformats implementations.
The code is managed in an
[http://hg.microformats.org/x2v/ x2v hg repository].
BrianSuda and DanC are starting to track issues here.
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].

See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...

__TOC__

== issue2006-12-20content-encoding ==

X2V's php does not correctly check for content-encodings

== trailing_slash ==

X2V failed trailing slash in rel-tag (this is now fixed)

== FN ORG incomplete ==

FN == ORG (i don't think) is complete

== XSLT case-conversion on Nodes ==

Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::

The downside is that then it will not extract the node name from ANY namespace, but a specific one.

== language for X-WR-CALNAME ==

===Background===
The X-WR-CALNAME is a widely supported extension property of VCALENDAR that stores the calendar title. It does not currently have a LANGUAGE attribute. It's value is meant to be human readable, so maybe it should.

=== Currently ===
<pre><html lang=en>
<head>
<title>My calendar</title>
</head>
<body class=vcalendar>...</body>
</html></pre>
yields something like
<pre>BEGIN:VCALENDAR
X-WR-CALNAME:My calendar
...
END:VCALENDAR</pre>

=== Proposal ===
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code>

== No support for AGENT ==

Doesn't seem to support agent at all -- either as a human-readable string nor as a nested hCard. E-mail addresses, phone numbers, etc which are part of the agent's vcard are treated as belonging to the main contact.

Test: http://examples.tobyinkster.co.uk/hcard

== See also ==
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.

x2v-issues

2009-06-25T07:25:25Z

Singpolyma: fragment url resolution issue

x2v is one of the main microformats implementations.
The code is managed in an
[http://hg.microformats.org/x2v/ x2v hg repository].
BrianSuda and DanC are starting to track issues here.
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].

See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...

__TOC__

== issue2006-12-20content-encoding ==

X2V's php does not correctly check for content-encodings

== trailing_slash ==

X2V failed trailing slash in rel-tag (this is now fixed)

== FN ORG incomplete ==

FN == ORG (i don't think) is complete

== XSLT case-conversion on Nodes ==

Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::

The downside is that then it will not extract the node name from ANY namespace, but a specific one.

== language for X-WR-CALNAME ==

== Fragments and Relative URLs ==

When transforming a URL with a fragment (ie: http://singpolyma.net/#profile) X2V correctly pulls out just the one hCard, but when resolving relative URLs it resolves them to, eg, http://singpolyma.net/#profile/resume/

===Background===
The X-WR-CALNAME is a widely supported extension property of VCALENDAR that stores the calendar title. It does not currently have a LANGUAGE attribute. It's value is meant to be human readable, so maybe it should.

=== Currently ===
<pre><html lang=en>
<head>
<title>My calendar</title>
</head>
<body class=vcalendar>...</body>
</html></pre>
yields something like
<pre>BEGIN:VCALENDAR
X-WR-CALNAME:My calendar
...
END:VCALENDAR</pre>

=== Proposal ===
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code>

== No support for AGENT ==

Doesn't seem to support agent at all -- either as a human-readable string nor as a nested hCard. E-mail addresses, phone numbers, etc which are part of the agent's vcard are treated as belonging to the main contact.

Test: http://examples.tobyinkster.co.uk/hcard

== See also ==
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.

events/2009-06-26-microformats-4th-bday

2009-06-24T18:32:53Z

Singpolyma: /* attending */ Will be attending

<entry-title>microformats.org 4th birthday party!</entry-title>

Celebrate the 4th birthday of http://microformats.org! One of several microformats [[events]].

If you'd like to help out with or attend the party, please add your name below.

RSVP required for venue capacity tracking.

<div class="event-page vevent">
== overview ==
;When
:2009-06-26 at 19:00 to 2009-06-26 at 22:00
;Where
:[http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar], 720 Howard Street, Yerba Buena Upper Terrace, San Francisco, CA 94103 USA
;What
:microformats.org 4th birthday party!
;Web
:http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday

</div> 

'''[http://feeds.technorati.com/events/referer Add this event to your calendar]''' [http://feeds.technorati.com/events/referer http://www.boogdesign.com/images/buttons/microformat_hcalendar.png]

== sponsors ==
Please sign up to sponsor the microformats.org 4th birthday party!

* [http://objectadjective.com Object Adjective] is a proud sponsor of this event.
* [http://www.ribbit.com/ Ribbit] is proud to sponsor the party
* ...

== planners ==
This section is for organizing a party for the upcoming 4th birthday of http://microformats.org.

I'm donating my time before the event to help plan and make the party happen!
* [[User:Tantek|Tantek Çelik]] - coordinating, sponsors
* [[User:Rohit|Rohit Khare]] - sponsors
* [[User:Kevin_Marks|Kevin Marks]] - sponsors
* [[User:BenWard|Ben Ward]] - tshirts, sponsors
* [[User:Pseudowish|Lauren Scime]] - design / venue / sponsors / publicity
* [[User:Repeatpenguin|Jeremy Anderson]] - will be assisting Lauren w/ above.

We need:
* a volunteer coordinator. someone to coordinate the volunteers listed below.
* [[stickers]] - Lauren is on it
** 500 rounded square 2" stickers w/logo on black background have come in the mail
* tshirts - Ben is on it

== volunteers ==
Sign up to be a volunteer!
We need volunteers to check people in at the door, take donations, hand out stickers, t-shirts etc.
* [[User:Richardault|Richard Ault]] - how can I help?
** Richard, perhaps you could help check names from RSVP and take donations at the door for an hour or so and find another volunteer to take over? Do you have a money-box for collections? [[User:Tantek|Tantek]] 02:22, 24 June 2009 (UTC)
* ...

== donations ==
* Donation requested at the door: sliding scale $5-$20. $10 or more gets you a t-shirt.
* Donations go towards the party and [[events/2009-07-18-dev-camp|microformatsDevCamp]] this summer.
* Spinn3r would be willing to donate/sponsor some...

== attending ==
I'm going toshow up and help celebrate so I'm signing up here!
# [[User:Tantek|Tantek Çelik]]
# Kevin Marks
# [[User:BenWard|Ben Ward]]
# [[User:Pseudowish|Lauren Scime]]
# [[User:Repeatpenguin|Jeremy Anderson]]
# [[User:Richardault|Richard Ault]]
# [[User:KevinBurton|Kevin Burton]] of [http://spinn3r.com] - I will be by for an hour or so... Spinn3r's 3.0 launch dinn3r is that evening too.
# [[User:Singpolyma|Singpolyma]]
# ...

== regrets ==
I'd love to be there but can't. Happy 4th birthday from afar!
* [[User:Rohit|Rohit Khare]]
* ...

== location ==
* [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar] - June 26th, 2009 at 7pm
** Will have hors d'oeuvres and about 50-60 drink tix to hand out to people at the door. Attendees can buy drinks at cash bar after drink tix are used.

== date ==
* 2009-06-26 Friday

== Promotional Graphics ==
* Banners & Images of Various Sizes: Promote Microformats 4 Year Birthday Party!
** [http://anendlessarray.com/microformats/88x31.jpg 88x31px]
** [http://anendlessarray.com/microformats/120x240.jpg 120x240px]
** [http://anendlessarray.com/microformats/125x125.jpg 125x125px]
** [http://anendlessarray.com/microformats/200x100.jpg 200x100px]
** [http://anendlessarray.com/microformats/200x200.jpg 200x200px]
** [http://anendlessarray.com/microformats/250x250.jpg 250x250px]
** [http://anendlessarray.com/microformats/300x225.jpg 300x225px]
** [http://anendlessarray.com/microformats/468x60.jpg 468x468px]
** [http://anendlessarray.com/microformats/160x600.jpg 160x600px]
** [http://anendlessarray.com/microformats/728x90.jpg 728x90px]
** [http://anendlessarray.com/microformats/728x90-pink.jpg 728x90px w/Pink]

* Note: If you are DYING to have a different size than the ones up here I can either send you the photoshop file or make you a custom one - Just send a request to lauren@objectadjective.com or find pseudowish on the [[IRC]]

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

hcard-supporting-user-profiles

2009-06-23T16:35:08Z

Singpolyma: /* Services with hCard profiles that also provide OpenID */ Alphabetical ;)

{{TOC-right}}
<h1>hCard supporting user profiles</h1>
Welcome! If you have an account on any of the following services, you already have an [[hcard|hCard]] which you can provide to other services to import or subscribe your profile information. The ability to syndicate your profile from the service of your choice is a key component of [[social-network-portability]].

== Services with hCard profiles that also provide OpenID ==
The following web sites support both hCard on user profiles and the ability to use your user profile as an [[OpenID]]. Alphabetically sorted. Feel free to add sites with hCard profiles that are also OpenID URLs here. Please include a link to the site home page (or [[implementations]] entry).

<div style="font-size:larger">
* http://www.betaid.org/i/icn_betaid.png [http://www.betaid.org Beta ID]
* http://claimid.com/images/badges/claimidclear10x10.gif [http://claimid.com/ ClaimID]
* [http://email-verify.appspot.com/ Email Verify]
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo]
* http://pulse.plaxo.com/pulse/img/event_icons/LiveJournal.gif [http://livejournal.com LiveJournal]
* [http://myopenid.com MyOpenID]
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://www.plaxo.com/ Plaxo]
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati]
* [http://videntity.org/ Videntity.org]
</div>

== All services with hCard profiles ==
The following web sites support hCard on their user profiles and are thus suitable for importing/subscribing to other sites that support hCard. Sites that you can also use as your [[OpenID]] are annotated with a OpenID icon http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif following the name of the site.

Alphabetically sorted. Feel free to add all sites with hCard profiles here. Please include a link to the site home page (or [[implementations]] entry), and instructions for retrieving your user profile URL on that site. If the site's user profile URLs can also be used as OpenIDs, please add the OpenID icon http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif following the name of the site.

<div style="font-size:larger">
* [http://3eep.com/ 3eep] - each user's public profile is located at <nowiki>http://3eep.com/users/userNameHere</nowiki>
* [http://www.artistserver.com/ ArtistServer] - each user's public profile is located at <nowiki>http://www.artistserver.com/userURLHere</nowiki>
* [http://www.bragster.com/ bragster] - each user's public profile is located at <nowiki>http://www.bragster.com/member/username</nowiki>
* http://claimid.com/images/badges/claimidclear10x10.gif [http://claimid.com/ ClaimID] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - each user's public profile is located at <nowiki>http://claimid.com/userNameHere</nowiki>
* http://identoo.com/images/icons/services/corkd.gif [http://www.corkd.com/ Cork'd] - login and copy the URL which should start with <nowiki>http://www.corkd.com/people/</nowiki>
* http://pulse.plaxo.com/pulse/img/event_icons/Digg.gif [http://digg.com/ Digg] - e.g. http://digg.com/users/tantek
* [http://djangopeople.net/ Django People] — profiles are at djangopeople.net/username e.g. http://djangopeople.net/simon/
* http://identoo.com/images/icons/services/dopplr.gif [http://www.dopplr.com/ Dopplr] — Example public profile: http://www.dopplr.com/traveller/adactio - non-public profiles may require login to view.
* http://pulse.plaxo.com/pulse/img/event_icons/Facebook.gif [http://facebook.com/ Facebook] - not sure how to find someone's public profile URL, e.g. [http://www.facebook.com/people/Andrei_Zmievski/502957990 Andrei Zmievski] but when found it appears to have support for valid fn+photo properties. Note [[hcard-supporting-user-profiles-issues#Facebook|issue(s) with Facebook hCard profiles]].
* [http://ficlets.com/ Ficlets] — profiles are located at ficlets.com/authors/username e.g. http://ficlets.com/authors/adactio
* http://pulse.plaxo.com/pulse/img/event_icons/Flickr.gif [http://flickr.com/ Flickr] - login, click "Your Photos", click "Profile", and copy the URL which should start with <nowiki>http://flickr.com/people/</nowiki>
* [http://gaia.com/ Gaia Community] - e.g. http://sphorbis.gaia.com/ - built by [http://www.zaadz.com Zaadz]
* [http://google.com Google] - view your profile at http://www.google.com/s2/profiles/me
* [http://huffduffer.com Huffduffer] profiles are located at <nowiki>http://huffduffer.com/username</nowiki> — Example public profile: http://huffduffer.com/clagnut
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - e.g. [http://identoo.com/dirk.olbertz sample profile]
* http://idleaf.com/favicon.png [http://idleaf.com idleaf] - profiles are located at <nowiki>http://idleaf.com/IDENTITY_ID</nowiki> - e.g.: http://idleaf.com/ID4184
* http://identoo.com/images/icons/services/imthere.gif [http://imthere.com/ ImThere] - profiles are located at <nowiki>http://imthere.com/users/USERNAME</nowiki>
* http://jaiku.com/images/icons/fav-jaiku.gif [http://jaiku.com Jaiku] — profiles are located at username.jaiku.com e.g. http://adactio.jaiku.com/
* [http://jpgmag.com/ JPG Magazine] - each user's public profile is located at <nowiki>http://jpgmag.com/people/userNameHere</nowiki>, e.g. http://jpgmag.com/people/jpd
* [http://www.keevu.com Keevu.com] - profiles are located at <nowiki>http://www.keevu.com/users/USERNAME</nowiki> - e.g.: [http://www.keevu.com/users/zheileman Zheileman]
* http://pulse.plaxo.com/pulse/img/event_icons/LastFM.gif [http://www.last.fm/ Last FM] - profiles are located at <nowiki>http://last.fm/user/USERNAME</nowiki>, includes fn, photo, url.
* http://pulse.plaxo.com/pulse/img/event_icons/LinkedIn.gif [http://linkedin.com LinkedIn] - login, click on "[http://www.linkedin.com/myprofile?trk=tab_pro My Profile]" in the top blue bar, then click on "[http://www.linkedin.com/myprofile?editwp=&trk=tab_web Public Profile]" and copy the URL in the page after "Your current URL is:" which should start with <nowiki>http://www.linkedin.com/pub/ or http://www.linkedin.com/in/</nowiki>. Note: LinkedIn profiles include an [[hresume|hResume]] for you in addition to your hCard.
* http://pulse.plaxo.com/pulse/img/event_icons/LiveJournal.gif [http://livejournal.com LiveJournal] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif (see also [[implementations#LiveJournal|LiveJournal]] implementation page entry) - login, click on the "Profile" link, and copy the URL which should start with <nowiki>http://USERNAME.livejournal.com/profile</nowiki> where USERNAME is your LJ username. E.g. [http://daveman692.livejournal.com/profile].
* http://pulse.plaxo.com/pulse/img/event_icons/Magnolia.gif [http://ma.gnolia.com/ Ma.gnolia] - each user's public profile is located at <nowiki>http://ma.gnolia.com/people/userNameHere</nowiki> . Note: [[hcard-supporting-user-profiles-issues#Magnolia|issue(s)]].
* http://www.mixx.com/images/buttons/mixx-button4.png [http://www.mixx.com Mixx] - profiles are located at <nowiki>http://www.mixx.com/users/USERNAME</nowiki> e.g. http://www.mixx.com/users/jgarber
* [http://myopenid.com MyOpenID] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - profiles are located at <nowiki>http://USERNAME.myopenid.com</nowiki> e.g. http://tantek.myopenid.com/
* [http://www.nsyght.com/ Nsyght] - Visit your profile page. Should look like this: <nowiki>http://www.nsyght.com/friends/[username]/</nowiki>, e.g. [http://nsyght.com/users/lisa sample profile].
* http://www.bkmks.com/icons/nytimes.com.gif [http://timespeople.nytimes.com/ NYTimes TimesPeople] - e.g. http://timespeople.nytimes.com/view/user/19390043/1/index.html
* [http://www.obsidianportal.com Obsidian Portal] - Your profile page is located at <nowiki>http://www.obsidianportal.com/profile/USERNAME</nowiki>, e.g. [http://www.obsidianportal.com/profile/Micah Micah's profile].
* [http://www.osocial.net/network/ OSocial Network] - add the [http://www.osocial.net/network/app/osocialnetwork.xml OpenSocial application] into your social network, then in OSocial.net Web site you will be able to get your hCard profile
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://www.plaxo.com/ Plaxo] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - create a nickname in your settings, then go to NICKNAME.myplaxo.com (e.g. http://joseph.myplaxo.com) and copy the URL
* http://pulse.plaxo.com/pulse/img/event_icons/Pownce.gif [http://pownce.com/ Pownce] - login, click on the "Home" link at the top, and copy the URL.
* http://www.syncup.com/SupWeb/ajax/images/16pxSyncUpIcon.gif [http://www.syncup.com/ SyncUp] - create a free account, choose what information to expose to public or specific people, then get the hcard in your profile page
* [http://www.qmpeople.com/ qmpeople] - Uses hCard+XFN for profiles (<nowiki>http://www.qmpeople.com/users/[username]</nowiki> - e.g. [http://www.qmpeople.com/users/laserion laserion])
* [http://radar.net/ Radar] - http://radar.net/people/radarname
* [http://www.revish.com/ Revish] — profiles are located at revish.com/people/username e.g. http://www.revish.com/people/adactio
* [http://rosebleed.net/ Rosebleed] - your profile URL is <nowiki>http://rosebleed.net/users/profile.php/</nowiki> followed by your username, e.g. [http://rosebleed.net/users/profile.php/silvermoon82 silvermoon82].
* [http://www.getsatisfaction.com/ Satisfaction]
* http://skateboardspot.info/image/icon/favicon.png [http://skateboardspot.info/ skateboardspot.info] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif (The site doesn't provide, but supports OpenID to login and register) — Log in, and click on your username in the top right corner. You'll see your user page which also is your hCard. Just copy the URL and you're done.
* [http://www.sustainlane.com www.sustainlane.com] - Profile at <nowiki>http://www.sustainlane.com/members/[user id]</nowiki> [http://www.sustainlane.com/members/4YHJXMST4S1B3NZT1HCSB4OAIVYD Example]
* [http://tangler.com/ Tangler] - click on a person's profile to navigate to their profile which is marked up with hCard <nowiki>http://www.tangler.com/people/id/</nowiki> - where "id" is the user number of that person.
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - login, click on the "Signed in as username" username link at the top right of the page, and copy the URL which should start with <nowiki>http://technorati.com/profile/</nowiki>
* [http://threadless.com/ Threadless] - select "My Account" and then "Profile Page". URL looks like <nowiki>http://www.threadless.com/profile/123987/username</nowiki>
* [http://www.travellerspoint.com/ Travellerspoint] - In use on all member profiles. URLs look like <nowiki>http://www.travellerspoint.com/member_profile.cfm?user=UsernameHere</nowiki> (e.g., [http://www.travellerspoint.com/member_profile.cfm?user=Peter Peter])
* http://pulse.plaxo.com/pulse/img/event_icons/Twitter.gif [http://twitter.com/ Twitter] - login, click on "Your profile" at the top, and copy the URL
* http://pulse.plaxo.com/pulse/img/event_icons/Upcoming.gif [http://upcoming.yahoo.com/ Upcoming] - login, click on the "Welcome, username!" username link at the top right of the page, and copy the URL which should start with <nowiki>http://upcoming.yahoo.com/user/</nowiki>
* [http://videntity.org/ Videntity.org] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - e.g. http://danda.videntity.org/
* [http://www.vimeo.com/ Vimeo] — e.g. http://www.vimeo.com/user196031
* http://openid.net/wp-content/uploads/vox.png [http://vox.com/ Vox] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - profile URL is <nowiki>http://USERNAME.vox.com/profile/</nowiki> e.g. http://daveman692.vox.com/profile/ (note issue: empty "n" property. fix: remove "n" from class attribute).
* [http://www.yedda.com/ Yedda] - e.g. http://yedda.com/people/8625713501419/ built by [http://www.zaadz.com Zaadz]
* [http://www.easthampshire.org/ easthampshire.org] - hCard on events and events map - e.g. http://easthampshire.org/eventdetail/wine_society_evening/1372606 and http://easthampshire.org/eventmap/wine_society_evening/1372606 built by [http://www.callendercreates.com Callender Creates]
* [http://www.dandyid.org/ DandyID.org] - hCard on user profiles, and a hCard widget for users blogs/sits/etc. (login to see the widget). Profile e.g. http://www.dandyid.org/beta/users/user_id/3
* ... add more sites (alphabetically sorted please) that support hCard, including instructions for finding and copying your profile URL.
</div>

=== offline sites ===
Sites that supported hCard user profiles that have gone offline, perhaps permanently.
* [http://consumating.com/ Consumating] - login, click on your name or "My Profile" link, copy the URL which looks like <nowiki>http://consumating.com/profiles/userNameHere</nowiki>
** supported hCard profiles at least from sometime in 2006 to 2008-03-15 when the site went offline.

== Services that import hCard profiles==
The following web sites support importing your existing hCard user profile, e.g. from the above sites, or your own page. Feel free to add sites supporting hCard user profile import to the appropriate section here. Please include a link to the site home page, and instructions for how to import your existing hCard user profile to the site.

=== import and subscribe on sign-up ===
Site(s) that allow you to import ''and'' subscribe to your hCard user profile when signing-up.. Alphabetically sorted.
* [http://getsatisfaction.com/ Satisfaction Inc.] - go to [http://getsatisfaction.com/people/new their sign in and registration page], choose the service of your existing profile or "'''Other...'''" and enter your profile URL (which you can retrieve as described above), and click "'''Get Profile'''". Then check "'''[x] Subscribe to this profile'''". Note: [[hcard-supporting-user-profiles-issues#Satisfaction|issue(s)]].

See [[subscribe-to-hcard]] for more notes on implementing subscribing to a user's hCard to automatically update their profile information.

=== import on sign-up ===
Site(s) that allow you to import your hCard user profile to sign-up. Alphabetically sorted.
* [http://www.bragster.com/ bragster] - go to [http://www.bragster.com/signup the sign-up page], click on the service logo of your existing profile, or the microformats logo for 'other' and enter your profile username (or URL for 'other') (which you can retrieve as described above).

=== import anytime ===
Sites that let you import your external hCard profile information anytime.
* [http://php-profile-importer.origo.ethz.ch/ PHP Profile importer] - Open Source PHP and JavaScript profile importer, there is also a [http://proofile.org/profile_importer_demo demo available].
* [http://www.proofile.org proofile] - [http://proofile.org/register Sign up] for an account and view the [http://proofile.org/edit/profile edit profile] page, enabling you to import from any hCard annotated URL. Full hCard is supported.
* [http://www.dandyid.org DandyID] - import a hCard supporting url after signing up, for auto-filling user info. DandyID also renders detailed hCards on user profiles.

=== subscribe anytime ===
Sites that let you subscribe to your external hCard profile information anytime.
* None currently.
=== delegation ===
Sites that support fully delegating to your external hCard profile.
* None currently.

== For more information ==
Want to implement hCard on your site so you can list it here?

See the [[hcard-user-profile-authoring|hCard user profile authoring]] page for how to mark-up a user profile with hCard.

Join the [http://microformats.org/discuss microformats community], in particular the #microformats IRC channel on irc://irc.freenode.net#microformats and the [http://microformats.org/mailman/listinfo/microformats-dev/ microformats-dev mailing list], and send a message stating that you'd like to add hCard to the profiles and hCard+XFN supporting friends lists to your website.

Please also consider implementing [[hcard-xfn-supporting-friends-lists|hCard+XFN friends lists]].

See [[hcard-supporting-user-profiles-issues|hCard supporting user profiles issues]] for issues, problems with implementations.

== see also ==
* [[subscribe-to-hcard]]
* [[hcard-xfn-supporting-friends-lists|hCard+XFN friends lists]]
* [[social-network-portability]]
* [[user-interface]]
* [[hcard|hCard]] ([[hcard-authoring|authoring]], [[hcard-faq|FAQ]])
* [[xfn|XFN]]
* [[data-portability]]