Microformats Wiki - User contributions [en]

rel-payment

2008-04-24T15:59:20Z

Alper: /* Practical examples of rel="payment" */ added tipit.to

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

[http://joshkinberg.com Joshua Kinberg]

[http://momentshowing.net Jay Dedman]

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

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

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

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

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

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

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

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

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

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

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

thank you,

Joshua Kinberg, jkinberg AT gmail DOT com

Robert Sayre, sayrer AT gmail DOT com

=== Registry ===

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

=== Attribute Value ===

"payment"

=== Description ===

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

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

=== Display Characteristics ===

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

=== Security Considerations ===

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

== Prior Art ==

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

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

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

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

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

===Open Financial Exchange===
* http://en.wikipedia.org/wiki/OFX aka OFX

== Examples from the wild ==

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

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

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

'''Text links'''

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

'''Banners'''

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

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

'''Search Boxes'''

Amazon offers search boxes:

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

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

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

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

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

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

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

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

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

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

* http://tipit.to

Tipit.to is an appreciation intermediary which allows people to put a tipjar on their website. A tipjar is a page on Tipit.to where visitors can donate money. Sample code linking to the tipjar contains rel="payment".

== Tools that currently support RelPayment ==

* http://GetFireAnt.com

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

* http://blip.tv

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

* http://MeFeedia.com

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

* http://rssbazaar.com

* http://49media.com

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

rel-payment

2008-04-24T15:38:16Z

Alper: /* Examples from the wild */ retry, original poster's markup was wrong in more places than one

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

[http://joshkinberg.com Joshua Kinberg]

[http://momentshowing.net Jay Dedman]

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

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

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

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

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

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

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

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

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

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

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

thank you,

Joshua Kinberg, jkinberg AT gmail DOT com

Robert Sayre, sayrer AT gmail DOT com

=== Registry ===

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

=== Attribute Value ===

"payment"

=== Description ===

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

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

=== Display Characteristics ===

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

=== Security Considerations ===

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

== Prior Art ==

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

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

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

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

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

===Open Financial Exchange===
* http://en.wikipedia.org/wiki/OFX aka OFX

== Examples from the wild ==

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

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

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

'''Text links'''

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

'''Banners'''

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

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

'''Search Boxes'''

Amazon offers search boxes:

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

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

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

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

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

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

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

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

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

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

== Tools that currently support RelPayment ==

* http://GetFireAnt.com

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

* http://blip.tv

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

* http://MeFeedia.com

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

* http://rssbazaar.com

* http://49media.com

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

rel-payment

2008-04-24T15:35:47Z

Alper: /* Examples from the wild */ missing close tag

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

[http://joshkinberg.com Joshua Kinberg]

[http://momentshowing.net Jay Dedman]

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

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

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

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

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

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

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

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

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

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

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

thank you,

Joshua Kinberg, jkinberg AT gmail DOT com

Robert Sayre, sayrer AT gmail DOT com

=== Registry ===

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

=== Attribute Value ===

"payment"

=== Description ===

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

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

=== Display Characteristics ===

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

=== Security Considerations ===

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

== Prior Art ==

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

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

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

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

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

===Open Financial Exchange===
* http://en.wikipedia.org/wiki/OFX aka OFX

== Examples from the wild ==

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

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

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

'''Text links'''

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

'''Banners'''

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

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

'''Search Boxes'''

Amazon offers search boxes:

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

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

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

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

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

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

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

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

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

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

== Tools that currently support RelPayment ==

* http://GetFireAnt.com

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

* http://blip.tv

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

* http://MeFeedia.com

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

* http://rssbazaar.com

* http://49media.com

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

hcard-implementations

2008-01-22T23:53:36Z

Alper: /* New Implementations */

<h1>hCard Implementations</h1>
{{TOC-right}}

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following implementations have been developed which either generate or parse [[hcard|hCards]]. If you have such an hCard implementation, feel free to add it to '''the top''' of the New Implementations section. If you have a page or site which just ''publishes'' hCards, please use [[hcard-examples-in-wild]] instead.

== New Implementations ==
Add new implementations here for evaluation and classification into the below taxonomy of implementations.
* [[hAvatar]] - Wordpress plugin displaying avatars for commenters based on their hCard
* [[org.microformats.hCard]] - java hCard parser and creator.
* [http://mobileonlinebusiness.com.au/uf/vCard_to_hCard_converter.html Mobile Online Business' vCard to hCard converter]
*[http://www.jamplanet.com Jam] is an active address book extension for Firefox/Flock. Jam imports Vcard and various CSV formats, and can output contacts in Vcard and hCard format.
*The "[http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address]" extension for [http://www.typo3.com TYPO3] supports hCard since the latest release, v2.0.0
*[https://addons.mozilla.org/firefox/4106/ Operator] lets you combine pieces of information on Web sites with applications in ways that are useful. (Firefox-plugin)
*[http://rafaeloliveira.net/labs/hcard_creator.zip Wordpress hCard Creator] - I've made this simple plugin for wordpress. It adds the hCard Options submenu at Options menu, where you can create a simple hCard and put it on your blog using < ?php hcard_creator() ?> to show it. Also, it is possible to show an "export to vCard" link, which uses Brian Suda X2V. (Got send an e-mail to him regarding this)
*[http://www.alexa.com/site/devcorner/hcard Alexa hcard search]
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Microformats Bookmarklet] is a bookmarklet designed for IE6 and IE7, Firefox, Safari, Opera and Camino, that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://domanske.de/2006/09/vcardexplorer-04/ vCardExplorer] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by [http://vcardexplorer.corefault.de Daniel Kagemann].
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined.
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] to represent people leaving comments on blog posts.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.


==Authoring==
Implementations you can use to author, create, and publish hCards.

===Web-based Creators===
;hCard Creator : [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) - create your own hCards.; ... :
: [http://www.wnas.nl/microformats/hcard/hcardCreator.html hCard creator (dutch)] ([[hcard-creator-feedback|hCard creator feedback]]) - create your own hCards, with a dutch interface.; ... :

===Blogging and CMS tools===
;Textpattern plug-in :
[http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ jmc_event_manager] is a plugin for [http://textpattern.com/ Textpattern] that outputs locations and events in hCard (and hCalendar) formats. Written by [http://euphemize.net/ Joel Courtney].
; ... :

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcard/creator microformats.org hCard creator] (see also [http://tantek.com/ Tantek]'s original [http://tantek.com/microformats/hcard-creator.html hCard creator on tantek.com].

===Desktop Authoring Tools===
* ...

==Search and Discovery==
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].



==Conversion and Import==
Implementations you can use to importing into an address book application, typically by converting hCard to vCard.

===Web Services===
These return vCard (.vcf) and other contact formats for easy importing into typical address book programs or other processing.
* [http://www.tomota.de www.tomota.de] Online address book that allows to import, export and convert hCard into vCard, ldif, csv and plain text.

* ...

===Firefox Greasemonkey Plugins===
* ...

===Aggregators===
* ...

==Browsing==
Implementations that detect, display and otherwise highlight hCards in pages.
* ...

===Firefox extension===

[http://www.kaply.com/weblog/operator Operator] - This extension is casual-user, advanced-user and developer friendly. Very customizable and unobstrusive.

===Flock extension===
* ...

==Open Source==
Open source libraries of hCard parsers and other related code for building hCard implementations. Note: it is very likely that above implementations may be duplicated in this section. That's ok.
* ...
;Javascript
: The [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.

; PHP :
* [[hKit]]
; Python :
* [http://tommorris.org/files/gmail2hcard-py.txt gmail2hcard-py.txt] - for converting Gmail CSV address book export to hCards
; Java :
* [[org.microformats.hCard]]
; Ruby :
: ...
; XSLT :
* ...

== Additional Applications ==
This section should probably be incorporated into [[hcard-brainstorming]].

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

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
** Like [http://alper.nl/cgi-bin/OpenAvatar.py?url=http://tantek.com this].
** Wordpress plugin with hCard based replacement for gravatar is in the make. [[User:Alper|Alper]] 12:59, 8 Aug 2007 (PDT)
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== Related Pages ==
{{hcard-related-pages}}

hcard-implementations

2008-01-21T14:12:07Z

Alper: /* New Implementations */

<h1>hCard Implementations</h1>
{{TOC-right}}

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following implementations have been developed which either generate or parse [[hcard|hCards]]. If you have such an hCard implementation, feel free to add it to '''the top''' of the New Implementations section. If you have a page or site which just ''publishes'' hCards, please use [[hcard-examples-in-wild]] instead.

== New Implementations ==
Add new implementations here for evaluation and classification into the below taxonomy of implementations.
* [http://fourstarters.com/2008/01/20/havatar-wordpress-plugin/ hAvatar] - Wordpress plugin displaying avatars for commenters based on their hCard
* [[org.microformats.hCard]] - java hCard parser and creator.
* [http://mobileonlinebusiness.com.au/uf/vCard_to_hCard_converter.html Mobile Online Business' vCard to hCard converter]
*[http://www.jamplanet.com Jam] is an active address book extension for Firefox/Flock. Jam imports Vcard and various CSV formats, and can output contacts in Vcard and hCard format.
*The "[http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address]" extension for [http://www.typo3.com TYPO3] supports hCard since the latest release, v2.0.0
*[https://addons.mozilla.org/firefox/4106/ Operator] lets you combine pieces of information on Web sites with applications in ways that are useful. (Firefox-plugin)
*[http://rafaeloliveira.net/labs/hcard_creator.zip Wordpress hCard Creator] - I've made this simple plugin for wordpress. It adds the hCard Options submenu at Options menu, where you can create a simple hCard and put it on your blog using < ?php hcard_creator() ?> to show it. Also, it is possible to show an "export to vCard" link, which uses Brian Suda X2V. (Got send an e-mail to him regarding this)
*[http://www.alexa.com/site/devcorner/hcard Alexa hcard search]
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Microformats Bookmarklet] is a bookmarklet designed for IE6 and IE7, Firefox, Safari, Opera and Camino, that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://domanske.de/2006/09/vcardexplorer-04/ vCardExplorer] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by [http://vcardexplorer.corefault.de Daniel Kagemann].
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined.
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] to represent people leaving comments on blog posts.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.


==Authoring==
Implementations you can use to author, create, and publish hCards.

===Web-based Creators===
;hCard Creator : [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) - create your own hCards.; ... :
: [http://www.wnas.nl/microformats/hcard/hcardCreator.html hCard creator (dutch)] ([[hcard-creator-feedback|hCard creator feedback]]) - create your own hCards, with a dutch interface.; ... :

===Blogging and CMS tools===
;Textpattern plug-in :
[http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ jmc_event_manager] is a plugin for [http://textpattern.com/ Textpattern] that outputs locations and events in hCard (and hCalendar) formats. Written by [http://euphemize.net/ Joel Courtney].
; ... :

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcard/creator microformats.org hCard creator] (see also [http://tantek.com/ Tantek]'s original [http://tantek.com/microformats/hcard-creator.html hCard creator on tantek.com].

===Desktop Authoring Tools===
* ...

==Search and Discovery==
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].



==Conversion and Import==
Implementations you can use to importing into an address book application, typically by converting hCard to vCard.

===Web Services===
These return vCard (.vcf) and other contact formats for easy importing into typical address book programs or other processing.
* [http://www.tomota.de www.tomota.de] Online address book that allows to import, export and convert hCard into vCard, ldif, csv and plain text.

* ...

===Firefox Greasemonkey Plugins===
* ...

===Aggregators===
* ...

==Browsing==
Implementations that detect, display and otherwise highlight hCards in pages.
* ...

===Firefox extension===

[http://www.kaply.com/weblog/operator Operator] - This extension is casual-user, advanced-user and developer friendly. Very customizable and unobstrusive.

===Flock extension===
* ...

==Open Source==
Open source libraries of hCard parsers and other related code for building hCard implementations. Note: it is very likely that above implementations may be duplicated in this section. That's ok.
* ...
;Javascript
: The [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.

; PHP :
* [[hKit]]
; Python :
* [http://tommorris.org/files/gmail2hcard-py.txt gmail2hcard-py.txt] - for converting Gmail CSV address book export to hCards
; Java :
* [[org.microformats.hCard]]
; Ruby :
: ...
; XSLT :
* ...

== Additional Applications ==
This section should probably be incorporated into [[hcard-brainstorming]].

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

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
** Like [http://alper.nl/cgi-bin/OpenAvatar.py?url=http://tantek.com this].
** Wordpress plugin with hCard based replacement for gravatar is in the make. [[User:Alper|Alper]] 12:59, 8 Aug 2007 (PDT)
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== Related Pages ==
{{hcard-related-pages}}

events/2007-09-28-portable-social-networks-meetup-amsterdam

2007-08-17T10:01:15Z

Alper: /* planning to attend */

<h1>portable social networks meetup amsterdam</h1>

One of several microformats related [[events]].

<div style="float:right;margin-left:1em">__TOC__</div>

== details ==
;When
:2007-09-28 14:00-17:00
;Where
:Westergasfabriek, Amsterdam, The Netherland, during the [http://picnicnetwork.org PICNIC conference]
;What
:An open brainstorm session to think about how social networks can be made portable. Ultimately, the goal is to give users total control of their virtual identity across numerous social networks, using existing standards like [[hcard|hCard]], [[XFN]] and OpenId.

[http://www.picnicnetwork.org/artefact-8259-en.html See also the PICNIC site]

== notes ==
After the event in [http://microformats.org/wiki/events/2007-07-28-portable-social-networks-meetup San Francisco] I thought it would be cool to get some people in Amsterdam together discussing the same problem. -[[User:Robert|Robert]]

Before joining the meetup, attendees are encouraged to read the following articles:

* [[social-network-portability]] ([[social-network-portability-fr|fr]])
* [[hcard-supporting-profiles]] ([[hcard-supporting-profiles-fr|fr]])
* [[hcard-xfn-supporting-friends-lists]] ([[hcard-xfn-supporting-friends-lists-fr|fr]])

== planning to attend ==
Please add your name to this list and link it to a URL representing you (preferably your URL with your hCard on it) if you plan to attend.
* [http://53miles.com/about Robert Gaal]
* [http://alper.nl/ Alper Çuğun]
* ...

== attendees ==
* ...
* ... please add your name if you attended.

== blog posts ==
* ...
* ... please add links to blog posts about this event

hcard-implementations

2007-08-08T19:59:27Z

Alper: /* Additional Applications */stuff about avatars

<h1>hCard Implementations</h1>

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following implementations have been developed which either generate or parse [[hcard|hCards]]. If you have such an hCard implementation, feel free to add it to '''the top''' of this list. If you have a page or site which just ''publishes'' hCards, please use [[hcard-examples-in-wild]] instead.

== New Implementations ==
* [http://mobileonlinebusiness.com.au/uf/vCard_to_hCard_converter.html Mobile Online Business' vCard to hCard converter]
*[http://www.jamplanet.com Jam] is an active address book extension for Firefox/Flock. Jam imports Vcard and various CSV formats, and can output contacts in Vcard and hCard format.
*The "[http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address]" extension for [http://www.typo3.com TYPO3] supports hCard since the latest release, v2.0.0
*[https://addons.mozilla.org/firefox/4106/ Operator] lets you combine pieces of information on Web sites with applications in ways that are useful. (Firefox-plugin)
*[http://rafaeloliveira.net/labs/hcard_creator.zip Wordpress hCard Creator] - I've made this simple plugin for wordpress. It adds the hCard Options submenu at Options menu, where you can create a simple hCard and put it on your blog using < ?php hcard_creator() ?> to show it. Also, it is possible to show an "export to vCard" link, which uses Brian Suda X2V. (Got send an e-mail to him regarding this)
*[http://www.alexa.com/site/devcorner/hcard Alexa hcard search]
*[http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Opera, Firefox and Camino as well) that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://elbewerk.com/2006/09/vcardexplorer-02.shtml vCardExplorer 0.2] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by Daniel Kagemann.
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined.
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.


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

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

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
** Like [http://alper.nl/cgi-bin/OpenAvatar.py?url=http://tantek.com this].
** Wordpress plugin with hCard based replacement for gravatar is in the make. [[User:Alper|Alper]] 12:59, 8 Aug 2007 (PDT)
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== Related Pages ==
{{hcard-related-pages}}

irc-people

2007-08-06T21:17:00Z

Alper:

A list of [[irc|IRC]] regulars sorted by nick and their normal timezones (winter/summer).

* [[User:WebOrganics|weborganics]] (+0100)
* [[User:Adam Ballai|AdamBallai]] (-700/-700)
* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Ajaswa|Andrew Jaswa]] (-0500)
* [[User:Alexander Graf|AlexanderGraf]] (+0100)
* [[User:AmanuelTewolde|Amanuel]] (-0500/-0400)
* [[User:Amette|amette]] (+1000)
* [[User:Amir Guindehi|AmirGuindehi]] (+1000)
* [[User:AnselHalliburton|anselxyz]] (-0800/-0700)
* [[User:Ashley|Ashley]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Tyler Roehmholdt|Baristo]] (-0800/-0700)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:HenriBergius|bergie]] (+0200/+0300)
* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:BluesMoon|bluesmoon]] (+0530)
* [[User:BobChao|BobChao]] (+0800)
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:Briski|Briski]] (+0000)
* [[User:BryanL|BryanL]] (-0500/-0400)
* [[User:BryanRieger|Bryan Rieger]] (+0000)
* [[User:Bug-E|Bug-E]] (+0200)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:CharlesRoper|charles_r]] (0000/+0100)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:Colin_Barrett|cbarrett]] (-1000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cruster|cruster]] (+0200)
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:ChrisBrentano|ctb]] (-0800/-0700)
* [[User:DanielBurka|DanielBurka]] (-0400)
* [[User:DavidMead|DavidMead]] (-0400)
* [[User:DerrickPallas|DerrickPallas]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:DanC|DanC]] (-0600/-0500)
* [[User:DannyAyers|danja]] (+0100/+0200)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DenisDefreyne|ddfreyne]] (+0100/+0200)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DiegoBudny|DiegoBudny]]
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:DrewBell|droob]] (-0600/-0500)
* [[User:DimitriosZachariadis|dzach]] (+0200/+0300)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:Fil|Fil]] (+0200)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Griffin|Griffin]] (-0600/-0500)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Aubergine10|Guy Fraser]] (+0100/+0000)
* [[User:HenrichPoehls|HenrichP]] (+0100)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Ichigo|ichigo]] (+1000)
* [[USer:Alper|illustir]] (+0100)
* [[User:Inkbase|inkbase]] (-0800/-0700)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Izo|IZO]]
* [[User:JamieKnight|JamieKnight]] (+1000/0000)
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)
* [[User:Adactio|Jeremy Keith]] (+0000)
* [[User:JasonK|jkridner]] (-0600/-0500)
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:JulianStahnke|Julian Stahnke]] (+0000)
* [[User:Kapowaz|kapowaz]] (+0000/+0100)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MattisManzel|Mattis Manzel]] (+0100/+0200)
* [[User:CiaranMc|McNulty]] (+0000/+0100)
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.
* [[User:Mike|Michael McCracken(mmc)]] (-0800/-0700)
* [[User:MikeKaply|mkaply]] (-0600/-0500)
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)
* [[User:RobManson|nambor]] (+1000)
* [[User:neuro|neuro`]]
* [[User:Niekie|niekie]] (+0100/+0200)
* [[User:NTollervey|ntoll]] (+0000/+0100)
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:PetarPopov|popov]] (-0800/-0700)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:RCanine|RCanine]] (-0500/-0400)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:Ronnos|Ron Kok]] (+0000)
* [[User:SarahWorsham|sazbean]] (-0500/-0400)
* [[User:ScottNelle|snelle]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* [[User:DavidLehn|taaz]] (-0500/-0400)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Vadania|vadania]] (-0600/-0700)
* [[User:Vant|vant]] (+0900)
* [[User:Victor|victor]] (+0100/+0200)
* [[User:V-I-P|V-I-P]] (+0100/+0200)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Wojciech|wzajac]] (+0100/+0200)
* [[User:Ianloic|yakk]] (-0800/-0700)
* [[User:StevenWoods|woodss]] (+0000 GMT)
* [[User:Linmic|linmic]] (+0800-0700)
* [[User:Stii|Stii]] (+0200 GMT)

social-network-portability

2007-08-03T12:44:15Z

Alper: /* Issues */

<h1> Social Network Portability </h1>
<div style="float:right;margin-left:1em">__TOC__</div>
One of several [[user-interface]] ideas and suggestions for working with microformats.

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

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

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

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

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

AKA a social internetwork, a network of social networks.

== Design Patterns and Recipes ==

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

# Publish microformats in your user profiles:
## implement [[hcard|hCard]] on user profile pages. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. See [[hcard-xfn-supporting-friends-lists]] for sites that already do this. (e.g. [[http://twitter.com/ Twitter]]).
# Subscribe to microformats for your user profiles:
## when signing up a new user:
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> from one of their existing [[hcard-supporting-profiles]], their name, their icon etc. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Satisfaction Inc already supports this.]
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> their list of friends from one of their existing [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]]. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Dopplr.com already supports this.]

== Social Network Portability FAQ ==
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on industry standard vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).
*''Doesn't OpenID provide people with a way to create a globally unique identifier for themselves?''
** It is URL (by way of DNS) that creates a globally unique identifier, not OpenID. All OpenID does is add ''authentication'' on top of having a URL that is itself a globally unique identifier, that is, OpenID is a way of asserting that you "own" or otherwise control a particular URL to another service/site. The essential quality of being a globally unique identifier is present in a URL even without OpenID. Thus, no, it is not OpenID that ''creates'' a ''globally unique identifier'', rather, simply using a ''URL'' creates a globally unique identifier. A URL ''by itself'' can be used as a basis for portable social networks, since it provides a way of referring to a single person that makes sense across the whole Web. And as such, people can (and will) create multiple URLs that represent them, so a method of enabling people to tie their URLs together (e.g. XFN's rel="me") becomes important. However, by adding authentication, OpenID can enhance existing globally unique identifier URLs for people, by permitting authenticated access to (perhaps more information in) profiles and social networks represented at those URLs using microformats.

== Issues ==
* For import/subscribe to hCard user profiles, "we need a defined heuristic for picking out the page owner from the friends." - Kevin Marks in IRC.
** There are some thoughts and proposed heuristics for this in [[hcard-brainstorming#Representative_hCard_discovery|hCard brainstorming: representative hCard discovery]].[[User:Tantek|Tantek]] 14:35, 31 Jul 2007 (PDT)

Profile information can be a very broad term judging from some of the horribly long profile forms I have seen on for instancy MyBlogLog. Some stuff should be essential, but optionally you can add pretty much anything as somebody's profile. Some optionals which could be nice to have:
* hResume markup for current (and previous) occupation and school history, maybe also for skills/interests.
* hReview markup to automatically get the favorite books, music, movies of somebody instead of duplicating it across sites.
[[User:Alper|Alper]] 05:44, 3 Aug 2007 (PDT)

== Discussion and suggestions ==
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
* Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote><p>What if we could port all our friends and family from one social network to another. Why do we have to continue to add people = annoying</p></blockquote>
* Brian Oberkirch: [http://urltea.com/10ee Highrise, microformats and portable social networks]
* Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]

See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].

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

== See also ==

* [[user-interface]]
* [[hcard|hCard]]
* [[xfn]]

== Notes ==
[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 Meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francsico, CA.
* discussed portable social networks, problem statement, goals, design patterns, recipes

social-network-portability

2007-08-03T12:43:46Z

Alper: /* Issues */ added richer profiles

<h1> Social Network Portability </h1>
<div style="float:right;margin-left:1em">__TOC__</div>
One of several [[user-interface]] ideas and suggestions for working with microformats.

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

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

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

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

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

AKA a social internetwork, a network of social networks.

== Design Patterns and Recipes ==

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

# Publish microformats in your user profiles:
## implement [[hcard|hCard]] on user profile pages. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. See [[hcard-xfn-supporting-friends-lists]] for sites that already do this. (e.g. [[http://twitter.com/ Twitter]]).
# Subscribe to microformats for your user profiles:
## when signing up a new user:
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> from one of their existing [[hcard-supporting-profiles]], their name, their icon etc. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Satisfaction Inc already supports this.]
### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> their list of friends from one of their existing [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]]. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Dopplr.com already supports this.]

== Social Network Portability FAQ ==
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on industry standard vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).
*''Doesn't OpenID provide people with a way to create a globally unique identifier for themselves?''
** It is URL (by way of DNS) that creates a globally unique identifier, not OpenID. All OpenID does is add ''authentication'' on top of having a URL that is itself a globally unique identifier, that is, OpenID is a way of asserting that you "own" or otherwise control a particular URL to another service/site. The essential quality of being a globally unique identifier is present in a URL even without OpenID. Thus, no, it is not OpenID that ''creates'' a ''globally unique identifier'', rather, simply using a ''URL'' creates a globally unique identifier. A URL ''by itself'' can be used as a basis for portable social networks, since it provides a way of referring to a single person that makes sense across the whole Web. And as such, people can (and will) create multiple URLs that represent them, so a method of enabling people to tie their URLs together (e.g. XFN's rel="me") becomes important. However, by adding authentication, OpenID can enhance existing globally unique identifier URLs for people, by permitting authenticated access to (perhaps more information in) profiles and social networks represented at those URLs using microformats.

== Issues ==
* For import/subscribe to hCard user profiles, "we need a defined heuristic for picking out the page owner from the friends." - Kevin Marks in IRC.
** There are some thoughts and proposed heuristics for this in [[hcard-brainstorming#Representative_hCard_discovery|hCard brainstorming: representative hCard discovery]].[[User:Tantek|Tantek]] 14:35, 31 Jul 2007 (PDT)

* Profile information can be a very broad term judging from some of the horribly long profile forms I have seen on for instancy MyBlogLog. Some stuff should be essential, but optionally you can add pretty much anything as somebody's profile. Some optionals which could be nice to have: [[User:Alper|Alper]] 05:43, 3 Aug 2007 (PDT)
*# hResume markup for current (and previous) occupation and school history, maybe also for skills/interests.
*# hReview markup to automatically get the favorite books, music, movies of somebody instead of duplicating it across sites.

== Discussion and suggestions ==
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
* Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote><p>What if we could port all our friends and family from one social network to another. Why do we have to continue to add people = annoying</p></blockquote>
* Brian Oberkirch: [http://urltea.com/10ee Highrise, microformats and portable social networks]
* Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]

See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].

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

== See also ==

* [[user-interface]]
* [[hcard|hCard]]
* [[xfn]]

== Notes ==
[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 Meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francsico, CA.
* discussed portable social networks, problem statement, goals, design patterns, recipes

User:Alper

2007-08-03T11:40:00Z

Alper:

* Write at: http://fourstarters.com
* Work for: http://tipit.to
* Live at: http://alper.nl