- short URL
rel="me" is used on hyperlinks from one page about a person to other pages about that same person.
<a href="https://twitter.com/t" rel="me">@t</a>
And his Twitter profile itself has (markup simplified)
<a href="http://tantek.com/" rel="me">http://tantek.com/</a>
Thus establishing a bi-directional rel-me link and confirming that the two URLs represent the same person.
Publishers can use the XFN creator form to create rel-me hyperlinks.
screencast and videos
Watch some short videos:
- David Recordon's excellent *30 second* explanation of XFN rel="me".
- Brad Fitzpatrick explains rel="me" and more XFN.
- Joseph Smarr's whiteboard explanation of rel="me" as implemented in the Plaxo online identity aggregator.
- Gavin Bell on "What is your provenance?" (40 minutes) - provides a much broader discussion of the problem statement of who is a person on the Web, and starting at about 0:07:30 explains how hCard 1.0 + rel="me" helps solve this problem.
A simple data portability project or is it rel=me summary by Bob Ngu
rel=me is the standard way to check that a website belongs to a user on a 3rd party site.
- read a user's website that they entered into their 3rd party site profile
- check for a rel=me hyperlink from their website to their 3rd party site profile
- if such a rel=me hyperlink is found, then the user has proven that they control that personal website sufficient to put a link back to their 3rd party site profile, and thus domain verification succeeds.
If you're the implementer of such a 3rd party site with user profiles, implement the above to implement a personal website domain verification feature.
In short it is a combination of domain verification as documented above, and OAuth authorization on the 3rd party site that the user's domain links to.
- Google uses reciprocal rel=me links for domain verification, which it also uses for independent site rel author support.
- App.net implements rel-me for officially connecting your domain to your app.net account, as well as publishing rel-me on your site.
- IndieAuth is perhaps the most comprehensive rel="me" implementation, using it to implement RelMeAuth and a superset of Web sign-in that is focused on independent websites.
- Social Links Wordpress plugin - supports rel-me links to other services
- About Me plugin (on github) - supports creation of an About Me page with rel-me links to other profiles.
Advocating rel=me support can be done a few ways, if a site has:
- user profiles but no "website" field - ask them to add a "website" field and mark it up with rel=me.
- a "website" field on profiles - ask it to support publishing rel=me
- a notion of "verification" or "verified" profiles - ask it to do so via confirming reciprocal rel=me
- login/sign-in - ask it to support RelMeAuth with a Web sign-in user interface.
- Gittip: Add "website" profile field #2477 - requested 2014-06-07 by Aaron Parecki.
examples in the wild
Examples of sites publishing rel=me support, e.g. on user profiles.