View source

You do not have permission to edit pages, for the following reason:
The action you have requested is limited to users in the group Users.
You can view and copy the source of this page:
<h1> Social Network Portability FAQ </h1>
This page documents frequently asked questions (FAQ) about [[social network portability]].

__TOC__

== Do microformats or any standard make ''all'' my social info portable ==
''Do microformats or any standard make all my social info portable across social network sites?''
* No, nor is it a goal to do so. The [[hcard|hCard]] microformat can represent the 80% of common information across social network sites like name, birthday, URLs, interests etc., and just being able to share that common 80% is quite valuable.  In addition, many social networking and social media sites add their own distinct value for the problems they solve, and it's unrealistic to expect a standard (any stanadard) to try to represent/share all that info in a 100% interoperable matter.

== Is the Web itself a social network ==
''Isn't the Web itself a social network minus some proprietary software?''

Precisely, the Web (plus a few open data formats) is itself a social network platform.

The key is, what are the minimal simple open data formats to describe the 80/20 of that social internetwork.

When [[XFN]] was introduced back in 2003, the choices of relationship values were based on real world uses of what relationships people were already publishing in their visible '''blog rolls''' on their '''blogs'''.  The hypothesis being that blogs + blogrolls already presented us with a giant distributed social network (in contrast to the dominant social silo of the time, Friendster).

With [[hcard|hCard]], one can easily capture, publish and share the 80/20 of common profile information across social networks.

With the combination of these two, most of the problem is solved.

We'll know what problems to solve next once more sites have implemented hCard+XFN and we start to take such support for granted, much as we take syndication support for granted in web sites today.

== Does clientside forms autofill solve the reenter your profile problem ==

''Does client-side forms autofill (e.g. RoboForm) solve the re-enter your profile info problem?''

Yes, clientside tools can help with the <em>initial</em> form filling out.

However, what happens when:
* you move
* you change jobs
* you get promoted
* you get a new URL/phone/email
* etc.

... then you have to go browse 20+ sites and update them all one by one!

If instead those sites supported [[social network portability]] and <em>subscribed</em> to your <em>syndicated</em> hCard profile (either from some other social network, or perhaps from your blog), then you could update this info in one place, and have your profiles everywhere else automatically get the updates.

That's where you really start to see the benefits of social network portability beyond just the initial sign-up on new sites.  It helps eliminate the "update tax" burden that builds with each new site you sign up on.

== Does OpenID solve the re-enter your personal profile problem ==
''Does [[OpenID]] solve the re-enter 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).

== Does OpenID create a globally unique identifier for people ==
''Does OpenID provide people with a way to create a globally unique identifier for themselves?''
* OpenID does not <em>create</em> a globally unique identifier for a person. It is URL (by way of DNS) that <em>creates</em> a globally unique identifier (whether or a person or other purpose), not OpenID. What OpenID does do is add <em>authentication</em> on top of having a globally unique 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.
* See also "[http://segala.com/blog/identity-the-most-widely-misuse-term-by-internet-experts/ OpenID does not prove identity.]"
Return to social-network-portability-faq.
Retrieved from "http://mt.microformats.org/wiki/social-network-portability-faq"
Views

Microformats Wiki

Toolbox

Hey! You're not logged in
