Microformats Wiki - User contributions [en]

User:LynX

2007-09-07T09:29:46Z

LynX: fixed, thx

I'm into [http://about.psyc.eu/Social_network decentralized social networks] so I'm also interested in [[social-network-portability]], although I'd first want to see the first thing happen - then the rest can be ported, if it cares to.

I'm a bit surprised we ended up on [[microformats]] to this purpose, as publishing things on the web is fundamentally anti-[[privacy]], and that's an essential goal for social networking.

So I'm asking.. can we be private on the web? And if we need to create such a private web first, why bother? Why not use an optimized protocol to achieve our goals instead of extracting them from documents that hardly anyone will read?

Then again, if I look at how we implemented our [http://about.psyc.eu/Profile profile surfing] feature, would it make sense to have a microformat in the profile instead of having the profile page generated out of the profile data? Could be. I'll meditate about it.

social-network-portability

2007-09-07T01:40:25Z

LynX: wikilink

<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 in the area of [[data-portability]].

== 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, including [[xfn]] rel="me" on hyperlinks to users' blogs or home pages that they specify. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. Use [[xfn]] rel="me" to link to friends list pages and friends list pagination links too. 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 "auto-sync" 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 "auto-sync" 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.]

== Resources ==
=== Open Source ===
* [[hKit]] - web service and open source PHP for parsing/importing/subscribing to [[hcard-supporting-profiles|hCard open user profiles]].
* "[http://opensocialgraph.plaxo.com/ Online Identity Consolidator]" rel="me" web parser/crawler web service and open source Python.
* "[http://django-psn.googlecode.com/svn/trunk/readme.html Django-PSN (portable social networks)]" open source for a user interface to create links on a social network profile to "other profiles" marked up with rel="me" naturally. The code can be seen in action on the [http://pownce.com Pownce] website, e.g. on [http://pownce.com/t/ a Pownce profile page that links to other profiles of the same user]. This is a great complement to the above Plaxo Online Identity Consolidator. What Django-PSN publishes, Plaxo Online Identity Consolidator parses.
* [http://about.psyc.eu psyc] and [http://www.psyced.org psyced], a decentralized multi-protocol chat and event notification system with [http://about.psyc.eu/Social_Network friendship] and [http://about.psyc.eu/Trust trust] modeling.
=== User Interfaces ===
* "[http://gerardramos.com/mf/ Social Network Portability with Microformats]" - a user interface that lets you check how portable your social network is across various sites.

== 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 ==
* Beware of and avoid [[social-network-anti-patterns]]!
* See and add to [[social-network-portability-issues]].

== Discussion and suggestions ==
* 2006-11-21 Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote>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.</blockquote>
* 2006-11-21 Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* 2006-11-22 Thomas Vander Wal: [http://www.personalinfocloud.com/2006/11/following_frien.html Following Friends Across Walled Gardens]
* 2006-11-23 Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* 2006-11-23 Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* 2006-11-23 Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[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]
* 2007-03-11 Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* 2007-06-20 Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]
* 2007-07-17 Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* 2007-07-18 Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote>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</blockquote>
* 2007-07-18 Brian Oberkirch: [http://www.brianoberkirch.com/2007/07/18/highrise-microformats-and-portable-social-networks/ Highrise, microformats and portable social networks]
* 2007-07-24 Thomas Vander Wal: [http://vanderwal.net/random/entrysel.php?blog=1937 Sharing and Following/Listening in the Social Web]
* See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].
* 2007-08-01 Jeffrey Zeldman: [http://www.zeldman.com/2007/08/01/social-network-portability/ "InterNetwork" regarding social network portability]
* 2007-08-08 Brian Oberkirch: [http://www.brianoberkirch.com/2007/08/08/building-blocks-for-portable-social-networks/ Building Blocks for Portable Social Networks]
* 2007-08-16 Stephanie Booth: [http://climbtothestars.org/archives/2007/08/16/we-need-structured-portable-social-networks-spsn/ We Need Structured Portable Social Networks (SPSN)] (links to two more posts on the subject, but not certain they're relevant enough for a separate listing; edit as you see fit)
* 2007-09-07 [[User:LynX|Carlo v. Loesch]]: [http://about.psyc.eu/Social_network#But.._why_microformats.3F Privacy and the web? Notification and HTTP? Are you looking at the right technologies!?]

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

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

== Articles ==
* 2007-08-25 [http://www.ignitesocialmedia.com/linking-it-all-%e2%80%93-social-network-portability/ Linking It All-Social Network Portability] by Mike Lotz for Ignite Social Media
* 2007-08-17 [http://bradfitz.com/social-graph-problem/ Thoughts on the Social Graph] by Brad Fitzpatrick.
* 2007-08-15 [http://news.bbc.co.uk/1/hi/technology/6944653.stm Pull down the walled gardens] Internet law professor Michael Geist says the walled gardens of social networks should be pulled down.
* 2007-08-02
** [http://www.brosbeforeblogs.com/2007/08/identity-crisis.html Identity Crisis part 1] <blockquote>We need to put the ownership of how we define relationships online in the hands of the individual, not the services that utilize them.My theory on how this should be accomplished is based on a marriage of OpenID and an open standard for defining relationships such as the [[XFN]] [http://microformats.org/ Microformat]. </blockquote>
** [http://www.brianoberkirch.com/2007/08/02/deeelightful-making-profile-import-a-snap/ Deeelightful: Making Profile Import a Snap] <blockquote>Why not make it simple for them to jumpstart a profile by reusing information they already have on the [[hcard|Web? Some forward thinking Web services are marking up user profile data with hCard, a microformat that]] signifies a person, place or organization is being described.</blockquote>

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

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

* [http://www.personalinfocloud.com/2006/11/following_frien.html 2006-11-22 Following Friends Across Walled Gardens] Thomas Vander Wal
* [http://adactio.com/journal/1212/ 2006-11-23 More thoughts on portable social networks] Jeremy Keith describes the process of portability
* [http://www.glennjones.net/Post/820/Mircoformatsandportablesocialnetwork.htm 2006-11-23 Microformats and portable social network] Glenn Jones talks about portable social networks in the backnetwork
*[http://microformats.org/wiki?title=user-interface&diff=10524&oldid=10523 2006-11-24 "social network portability" phrase and problem statement introduced to microformats wiki] by [[User:Tantek|Tantek Çelik]]
*[http://www.plaxo.com/about/releases/release-20070718 2007-07-17 Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats]
*[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 portable social networks initial meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francisco, CA. Discussed portable social networks, simplified and crystalized problem statement (with progressive problems to solve), goals, design patterns, recipes. Created [[social-network-portability]] page.
* [[events/2007-08-19-social-network-portability-today|2007-08-19 BarCampBlock session on social network portability TODAY]] at Princeton Review offices, High Street, Palo Alto, CA. Reviewed problem statement, how sites can use the [[hcard|hCard]] and [[xfn|XFN]] microformats *today* to become a node on the "open social web" (phrase introduced).

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

User:LynX

2007-09-07T01:38:01Z

LynX: meditation

I'm into [http://about.psyc.eu/Social_network decentralized social networks] so I'm also interested in [[social-network-portability]], although I'd first want to see the first thing happen - then the rest can be ported, if it cares to.

I'm a bit surprised we ended up on [[microformats]] to this purpose, as publishing things on the web is fundamentally anti-[[privacy]], and that's an essential goal for social networking.

So I'm asking.. can we be private on the web? And if we need to create such a private web first, why bother? Why not use an optimized protocol to achieve our goals instead of extracting them from documents that hardly anyone will read?

Then again, if I look at how we implemented our [http://about.psyc.eu/Profile|profile surfing] feature, would it make sense to have a microformat in the profile instead of having the profile page generated out of the profile data? Could be. I'll meditate about it.

irc-people

2007-09-07T01:31:22Z

LynX: self-add

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

* [[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:CarlaHufstedler|carlamagpie]] (-0500/-0400)
* [[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:DrErnie|DrErnie]] (-0800/-0700)
* [[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:JosephHolsten|josephholsten]] (-0600/-0500)
* [[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:Linmic|linmic]] (+0800-0700)
* [[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:Andy Pemberton|pembertona]] (-0500/-0400)
* [[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:Stii|Stii]] (+0200 GMT)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100)
* [[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:WebOrganics|weborganics]] (+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)

privacy

2007-09-07T01:19:41Z

LynX: Privacy and microformats (discussion? resources?)

= Privacy and microformats =

<[[User:LynX|lynX]]> It's the one thing you can't do with microformats, right?
Or rather.. the web, the HTTP protocol, you'd first need to
have a ''private web'' where we publish things just for our
friends or our social network applications to implement the
[[social-network-portability]] thing. Only ''then'' can we
use microformats on a ''private'' scale. Does it really make sense?
I'm wondering aloud. Please comment.

rel-payment

2007-09-07T01:14:48Z

LynX: /* Security Considerations */

== 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>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="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>
payment LINK tags
 
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:
 
<link rel="appendix" type="text/html" title="payment" href="URL of Wishlist or Paypal Page" />
 
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>Kodak EasyShare DX7440 4MP Digital C...</a>
</td>
</tr>
<tr height=15%>
<td>
<center>
Kodak Digital 
</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>Best Price $157.70</a></center>
</td>
</tr>
<tr height=15%>
<td>
<center>or Buy New </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>
Privacy Information</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">
Search Now:
</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]]

social-network-portability

2007-09-07T01:13:28Z

LynX: wikilink

<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 in the area of [[data-portability]].

== 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, including [[xfn]] rel="me" on hyperlinks to users' blogs or home pages that they specify. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. Use [[xfn]] rel="me" to link to friends list pages and friends list pagination links too. 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 "auto-sync" 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 "auto-sync" 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.]

== Resources ==
=== Open Source ===
* [[hKit]] - web service and open source PHP for parsing/importing/subscribing to [[hcard-supporting-profiles|hCard open user profiles]].
* "[http://opensocialgraph.plaxo.com/ Online Identity Consolidator]" rel="me" web parser/crawler web service and open source Python.
* "[http://django-psn.googlecode.com/svn/trunk/readme.html Django-PSN (portable social networks)]" open source for a user interface to create links on a social network profile to "other profiles" marked up with rel="me" naturally. The code can be seen in action on the [http://pownce.com Pownce] website, e.g. on [http://pownce.com/t/ a Pownce profile page that links to other profiles of the same user]. This is a great complement to the above Plaxo Online Identity Consolidator. What Django-PSN publishes, Plaxo Online Identity Consolidator parses.
* [http://about.psyc.eu psyc] and [http://www.psyced.org psyced], a decentralized multi-protocol chat and event notification system with [http://about.psyc.eu/Social_Network friendship] and [http://about.psyc.eu/Trust trust] modeling.
=== User Interfaces ===
* "[http://gerardramos.com/mf/ Social Network Portability with Microformats]" - a user interface that lets you check how portable your social network is across various sites.

== 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 ==
* Beware of and avoid [[social-network-anti-patterns]]!
* See and add to [[social-network-portability-issues]].

== Discussion and suggestions ==
* 2006-11-21 Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote>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.</blockquote>
* 2006-11-21 Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* 2006-11-22 Thomas Vander Wal: [http://www.personalinfocloud.com/2006/11/following_frien.html Following Friends Across Walled Gardens]
* 2006-11-23 Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* 2006-11-23 Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* 2006-11-23 Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[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]
* 2007-03-11 Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* 2007-06-20 Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]
* 2007-07-17 Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* 2007-07-18 Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote>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</blockquote>
* 2007-07-18 Brian Oberkirch: [http://www.brianoberkirch.com/2007/07/18/highrise-microformats-and-portable-social-networks/ Highrise, microformats and portable social networks]
* 2007-07-24 Thomas Vander Wal: [http://vanderwal.net/random/entrysel.php?blog=1937 Sharing and Following/Listening in the Social Web]
* See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].
* 2007-08-01 Jeffrey Zeldman: [http://www.zeldman.com/2007/08/01/social-network-portability/ "InterNetwork" regarding social network portability]
* 2007-08-08 Brian Oberkirch: [http://www.brianoberkirch.com/2007/08/08/building-blocks-for-portable-social-networks/ Building Blocks for Portable Social Networks]
* 2007-08-16 Stephanie Booth: [http://climbtothestars.org/archives/2007/08/16/we-need-structured-portable-social-networks-spsn/ We Need Structured Portable Social Networks (SPSN)] (links to two more posts on the subject, but not certain they're relevant enough for a separate listing; edit as you see fit)
* 2007-09-07 Carlo v. Loesch: [http://about.psyc.eu/Social_network#But.._why_microformats.3F Privacy and the web? Notification and HTTP? Are you looking at the right technologies!?]

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

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

== Articles ==
* 2007-08-25 [http://www.ignitesocialmedia.com/linking-it-all-%e2%80%93-social-network-portability/ Linking It All-Social Network Portability] by Mike Lotz for Ignite Social Media
* 2007-08-17 [http://bradfitz.com/social-graph-problem/ Thoughts on the Social Graph] by Brad Fitzpatrick.
* 2007-08-15 [http://news.bbc.co.uk/1/hi/technology/6944653.stm Pull down the walled gardens] Internet law professor Michael Geist says the walled gardens of social networks should be pulled down.
* 2007-08-02
** [http://www.brosbeforeblogs.com/2007/08/identity-crisis.html Identity Crisis part 1] <blockquote>We need to put the ownership of how we define relationships online in the hands of the individual, not the services that utilize them.My theory on how this should be accomplished is based on a marriage of OpenID and an open standard for defining relationships such as the [[XFN]] [http://microformats.org/ Microformat]. </blockquote>
** [http://www.brianoberkirch.com/2007/08/02/deeelightful-making-profile-import-a-snap/ Deeelightful: Making Profile Import a Snap] <blockquote>Why not make it simple for them to jumpstart a profile by reusing information they already have on the [[hcard|Web? Some forward thinking Web services are marking up user profile data with hCard, a microformat that]] signifies a person, place or organization is being described.</blockquote>

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

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

* [http://www.personalinfocloud.com/2006/11/following_frien.html 2006-11-22 Following Friends Across Walled Gardens] Thomas Vander Wal
* [http://adactio.com/journal/1212/ 2006-11-23 More thoughts on portable social networks] Jeremy Keith describes the process of portability
* [http://www.glennjones.net/Post/820/Mircoformatsandportablesocialnetwork.htm 2006-11-23 Microformats and portable social network] Glenn Jones talks about portable social networks in the backnetwork
*[http://microformats.org/wiki?title=user-interface&diff=10524&oldid=10523 2006-11-24 "social network portability" phrase and problem statement introduced to microformats wiki] by [[User:Tantek|Tantek Çelik]]
*[http://www.plaxo.com/about/releases/release-20070718 2007-07-17 Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats]
*[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 portable social networks initial meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francisco, CA. Discussed portable social networks, simplified and crystalized problem statement (with progressive problems to solve), goals, design patterns, recipes. Created [[social-network-portability]] page.
* [[events/2007-08-19-social-network-portability-today|2007-08-19 BarCampBlock session on social network portability TODAY]] at Princeton Review offices, High Street, Palo Alto, CA. Reviewed problem statement, how sites can use the [[hcard|hCard]] and [[xfn|XFN]] microformats *today* to become a node on the "open social web" (phrase introduced).

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

attention-brainstorming

2007-09-07T01:11:56Z

LynX: wikilink

= Attention Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for an [[attention|Attention]] microformat.

This is part of an open standards community effort to update (even rethink and rewrite) the [http://developers.technorati.com/wiki/attentionxml Attention.xml] format on a strong foundation of research of existing examples and formats, as well as leveraging the Attention.XML implementation experience from [http://attensa.com Attensa], [http://commerce.net CommerceNet], [http://technorati.com Technorati], and any other interested Attention developers.

== Authors ==

* Tim Brown
* Tantek Çelik
* Eric Hayes
* Rohit Khare
* Kevin Marks

== Experience ==

Both Technorati and Attensa have implementation experience with [http://developers.technorati.com/wiki/attentionxml Attention.XML] and other attention formats.

=== Other Attention-like Things ===

* [http://www.43folders.com/2005/10/19/personal-status-page/ Personal Status Pages]

=== Lessons Learned ===
* Hierarchy in the format gets in the way more than it helps
* Need to define a minimally useful subset for ease of implementation and interoperability
* Need to "chunk" any sets of additional data

== Goals / Requirements ==

=== Definite ===
* Needs to be represent sparse (over time and source) data
* "Blendable" - get an attention "chunk" every day from a source and be able to aggregate the chunks into one attention file.
* Flat by default. Permit hierarchy but don't require it, and don't require parsing of a hierarchy (i.e. allow treating the attention as a simple flat set of attention items).

=== Non-goals ===
These are things we want to avoid in an Attention format, mostly due to [[privacy]] reasons.

* cookies
* login information
* personally identifiable information in URLs (e.g. PHP session info)

== Strawman Schema Thoughts ==

=== Each Attention Item contains ===

==== item info ====
* item url (rss article url, etc)
* parent context (feed or source site, )
* attention date (article last read time)

==== implicit info ====
* duration (attention duration, how long did i look at this page or article)
* followed links (click through. could result in a next attention item)
* read state

==== explicit info ====
* [[vote-links|voting]]
* [[hreview|hReview]]
** rating
** [[rel-tag|tags]]
* explicit read or unread state

* date removed

=== Item Containers ===

* .

== See Also ==
* [[attention-examples]]
* [[attention-formats]]
* Previous [http://developers.technorati.com/wiki/AttentionXMLBrainstorming Attention.xml brainstorming] thoughts.

social-network-portability

2007-09-07T01:10:43Z

LynX: Privacy and the web? Impossible.

<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 in the area of [[data-portability]].

== 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, including [[xfn]] rel="me" on hyperlinks to users' blogs or home pages that they specify. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. Use [[xfn]] rel="me" to link to friends list pages and friends list pagination links too. 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 "auto-sync" 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 "auto-sync" 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.]

== Resources ==
=== Open Source ===
* [[hKit]] - web service and open source PHP for parsing/importing/subscribing to [[hcard-supporting-profiles|hCard open user profiles]].
* "[http://opensocialgraph.plaxo.com/ Online Identity Consolidator]" rel="me" web parser/crawler web service and open source Python.
* "[http://django-psn.googlecode.com/svn/trunk/readme.html Django-PSN (portable social networks)]" open source for a user interface to create links on a social network profile to "other profiles" marked up with rel="me" naturally. The code can be seen in action on the [http://pownce.com Pownce] website, e.g. on [http://pownce.com/t/ a Pownce profile page that links to other profiles of the same user]. This is a great complement to the above Plaxo Online Identity Consolidator. What Django-PSN publishes, Plaxo Online Identity Consolidator parses.
* [http://about.psyc.eu psyc] and [http://www.psyced.org psyced], a decentralized multi-protocol chat and event notification system with [http://about.psyc.eu/Social_Network friendship] and [http://about.psyc.eu/Trust trust] modeling.
=== User Interfaces ===
* "[http://gerardramos.com/mf/ Social Network Portability with Microformats]" - a user interface that lets you check how portable your social network is across various sites.

== 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 ==
* Beware of and avoid [[social-network-anti-patterns]]!
* See and add to [[social-network-portability-issues]].

== Discussion and suggestions ==
* 2006-11-21 Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote>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.</blockquote>
* 2006-11-21 Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* 2006-11-22 Thomas Vander Wal: [http://www.personalinfocloud.com/2006/11/following_frien.html Following Friends Across Walled Gardens]
* 2006-11-23 Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* 2006-11-23 Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* 2006-11-23 Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[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]
* 2007-03-11 Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* 2007-06-20 Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]
* 2007-07-17 Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* 2007-07-18 Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote>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</blockquote>
* 2007-07-18 Brian Oberkirch: [http://www.brianoberkirch.com/2007/07/18/highrise-microformats-and-portable-social-networks/ Highrise, microformats and portable social networks]
* 2007-07-24 Thomas Vander Wal: [http://vanderwal.net/random/entrysel.php?blog=1937 Sharing and Following/Listening in the Social Web]
* See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].
* 2007-08-01 Jeffrey Zeldman: [http://www.zeldman.com/2007/08/01/social-network-portability/ "InterNetwork" regarding social network portability]
* 2007-08-08 Brian Oberkirch: [http://www.brianoberkirch.com/2007/08/08/building-blocks-for-portable-social-networks/ Building Blocks for Portable Social Networks]
* 2007-08-16 Stephanie Booth: [http://climbtothestars.org/archives/2007/08/16/we-need-structured-portable-social-networks-spsn/ We Need Structured Portable Social Networks (SPSN)] (links to two more posts on the subject, but not certain they're relevant enough for a separate listing; edit as you see fit)
* 2007-09-07 Carlo v. Loesch: [http://about.psyc.eu/Social_network#But.._why_microformats.3F Privacy and the web? Notification and HTTP? Are you looking at the right technologies!?]

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

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

== Articles ==
* 2007-08-25 [http://www.ignitesocialmedia.com/linking-it-all-%e2%80%93-social-network-portability/ Linking It All-Social Network Portability] by Mike Lotz for Ignite Social Media
* 2007-08-17 [http://bradfitz.com/social-graph-problem/ Thoughts on the Social Graph] by Brad Fitzpatrick.
* 2007-08-15 [http://news.bbc.co.uk/1/hi/technology/6944653.stm Pull down the walled gardens] Internet law professor Michael Geist says the walled gardens of social networks should be pulled down.
* 2007-08-02
** [http://www.brosbeforeblogs.com/2007/08/identity-crisis.html Identity Crisis part 1] <blockquote>We need to put the ownership of how we define relationships online in the hands of the individual, not the services that utilize them.My theory on how this should be accomplished is based on a marriage of OpenID and an open standard for defining relationships such as the [[XFN]] [http://microformats.org/ Microformat]. </blockquote>
** [http://www.brianoberkirch.com/2007/08/02/deeelightful-making-profile-import-a-snap/ Deeelightful: Making Profile Import a Snap] <blockquote>Why not make it simple for them to jumpstart a profile by reusing information they already have on the [[hcard|Web? Some forward thinking Web services are marking up user profile data with hCard, a microformat that]] signifies a person, place or organization is being described.</blockquote>

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

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

* [http://www.personalinfocloud.com/2006/11/following_frien.html 2006-11-22 Following Friends Across Walled Gardens] Thomas Vander Wal
* [http://adactio.com/journal/1212/ 2006-11-23 More thoughts on portable social networks] Jeremy Keith describes the process of portability
* [http://www.glennjones.net/Post/820/Mircoformatsandportablesocialnetwork.htm 2006-11-23 Microformats and portable social network] Glenn Jones talks about portable social networks in the backnetwork
*[http://microformats.org/wiki?title=user-interface&diff=10524&oldid=10523 2006-11-24 "social network portability" phrase and problem statement introduced to microformats wiki] by [[User:Tantek|Tantek Çelik]]
*[http://www.plaxo.com/about/releases/release-20070718 2007-07-17 Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats]
*[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 portable social networks initial meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francisco, CA. Discussed portable social networks, simplified and crystalized problem statement (with progressive problems to solve), goals, design patterns, recipes. Created [[social-network-portability]] page.
* [[events/2007-08-19-social-network-portability-today|2007-08-19 BarCampBlock session on social network portability TODAY]] at Princeton Review offices, High Street, Palo Alto, CA. Reviewed problem statement, how sites can use the [[hcard|hCard]] and [[xfn|XFN]] microformats *today* to become a node on the "open social web" (phrase introduced).

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

social-network-portability

2007-09-06T23:49:07Z

LynX: everybody has a plug, here's mine...

<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 in the area of [[data-portability]].

== 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, including [[xfn]] rel="me" on hyperlinks to users' blogs or home pages that they specify. See [[hcard-supporting-profiles]] for sites that have already done this.
## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. Use [[xfn]] rel="me" to link to friends list pages and friends list pagination links too. 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 "auto-sync" 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 "auto-sync" 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.]

== Resources ==
=== Open Source ===
* [[hKit]] - web service and open source PHP for parsing/importing/subscribing to [[hcard-supporting-profiles|hCard open user profiles]].
* "[http://opensocialgraph.plaxo.com/ Online Identity Consolidator]" rel="me" web parser/crawler web service and open source Python.
* "[http://django-psn.googlecode.com/svn/trunk/readme.html Django-PSN (portable social networks)]" open source for a user interface to create links on a social network profile to "other profiles" marked up with rel="me" naturally. The code can be seen in action on the [http://pownce.com Pownce] website, e.g. on [http://pownce.com/t/ a Pownce profile page that links to other profiles of the same user]. This is a great complement to the above Plaxo Online Identity Consolidator. What Django-PSN publishes, Plaxo Online Identity Consolidator parses.
* [http://about.psyc.eu psyc] and [http://www.psyced.org psyced], a decentralized multi-protocol chat and event notification system with [http://about.psyc.eu/Social_Network friendship] and [http://about.psyc.eu/Trust trust] modeling.
=== User Interfaces ===
* "[http://gerardramos.com/mf/ Social Network Portability with Microformats]" - a user interface that lets you check how portable your social network is across various sites.

== 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 ==
* Beware of and avoid [[social-network-anti-patterns]]!
* See and add to [[social-network-portability-issues]].

== Discussion and suggestions ==
* 2006-11-21 Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote>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.</blockquote>
* 2006-11-21 Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* 2006-11-22 Thomas Vander Wal: [http://www.personalinfocloud.com/2006/11/following_frien.html Following Friends Across Walled Gardens]
* 2006-11-23 Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* 2006-11-23 Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* 2006-11-23 Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[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]
* 2007-03-11 Robert Gaal: [http://www.53miles.com/archives/making-openid-your-only-online-profile-alpha-dash Making OpenID your only online profile: Alpha Dash] - An abstract attempt to create one dashboard, to be used as a starting point for all social networks. It contains four elements: identity, ownership, presence and contacts (see comments also)
* 2007-06-20 Alper Çuğun: [http://fourstarters.com/2007/06/20/the-future-of-everything-is-social-consolidate-and-take-back-your-social-network/ The Future of Everything is Social: Consolidate and take back your social network]
* 2007-07-17 Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.
* 2007-07-18 Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote>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</blockquote>
* 2007-07-18 Brian Oberkirch: [http://www.brianoberkirch.com/2007/07/18/highrise-microformats-and-portable-social-networks/ Highrise, microformats and portable social networks]
* 2007-07-24 Thomas Vander Wal: [http://vanderwal.net/random/entrysel.php?blog=1937 Sharing and Following/Listening in the Social Web]
* See [[events/2007-07-28-portable-social-networks-meetup#blog_posts|blog posts following up]] from the [[events/2007-07-28-portable-social-networks-meetup|2007-07-28-portable social networks meetup]].
* 2007-08-01 Jeffrey Zeldman: [http://www.zeldman.com/2007/08/01/social-network-portability/ "InterNetwork" regarding social network portability]
* 2007-08-08 Brian Oberkirch: [http://www.brianoberkirch.com/2007/08/08/building-blocks-for-portable-social-networks/ Building Blocks for Portable Social Networks]
* 2007-08-16 Stephanie Booth: [http://climbtothestars.org/archives/2007/08/16/we-need-structured-portable-social-networks-spsn/ We Need Structured Portable Social Networks (SPSN)] (links to two more posts on the subject, but not certain they're relevant enough for a separate listing; edit as you see fit)

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

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

== Articles ==
* 2007-08-25 [http://www.ignitesocialmedia.com/linking-it-all-%e2%80%93-social-network-portability/ Linking It All-Social Network Portability] by Mike Lotz for Ignite Social Media
* 2007-08-17 [http://bradfitz.com/social-graph-problem/ Thoughts on the Social Graph] by Brad Fitzpatrick.
* 2007-08-15 [http://news.bbc.co.uk/1/hi/technology/6944653.stm Pull down the walled gardens] Internet law professor Michael Geist says the walled gardens of social networks should be pulled down.
* 2007-08-02
** [http://www.brosbeforeblogs.com/2007/08/identity-crisis.html Identity Crisis part 1] <blockquote>We need to put the ownership of how we define relationships online in the hands of the individual, not the services that utilize them.My theory on how this should be accomplished is based on a marriage of OpenID and an open standard for defining relationships such as the [[XFN]] [http://microformats.org/ Microformat]. </blockquote>
** [http://www.brianoberkirch.com/2007/08/02/deeelightful-making-profile-import-a-snap/ Deeelightful: Making Profile Import a Snap] <blockquote>Why not make it simple for them to jumpstart a profile by reusing information they already have on the [[hcard|Web? Some forward thinking Web services are marking up user profile data with hCard, a microformat that]] signifies a person, place or organization is being described.</blockquote>

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

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

* [http://www.personalinfocloud.com/2006/11/following_frien.html 2006-11-22 Following Friends Across Walled Gardens] Thomas Vander Wal
* [http://adactio.com/journal/1212/ 2006-11-23 More thoughts on portable social networks] Jeremy Keith describes the process of portability
* [http://www.glennjones.net/Post/820/Mircoformatsandportablesocialnetwork.htm 2006-11-23 Microformats and portable social network] Glenn Jones talks about portable social networks in the backnetwork
*[http://microformats.org/wiki?title=user-interface&diff=10524&oldid=10523 2006-11-24 "social network portability" phrase and problem statement introduced to microformats wiki] by [[User:Tantek|Tantek Çelik]]
*[http://www.plaxo.com/about/releases/release-20070718 2007-07-17 Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats]
*[[events/2007-07-28-portable-social-networks-meetup|2007-07-28 portable social networks initial meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francisco, CA. Discussed portable social networks, simplified and crystalized problem statement (with progressive problems to solve), goals, design patterns, recipes. Created [[social-network-portability]] page.
* [[events/2007-08-19-social-network-portability-today|2007-08-19 BarCampBlock session on social network portability TODAY]] at Princeton Review offices, High Street, Palo Alto, CA. Reviewed problem statement, how sites can use the [[hcard|hCard]] and [[xfn|XFN]] microformats *today* to become a node on the "open social web" (phrase introduced).

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