rel="me"

(Difference between revisions)

Jump to: navigation, search
(implementations notable sites, services, advocacy, awaiting gittip request)
(add domain verification how to, and description as a building block of relmeauth)
Line 30: Line 30:
== tutorials ==
== tutorials ==
[http://ungeekdapo.wordpress.com/2008/04/29/a-simple-data-portability-project-or-is-it/ A simple data portability project or is it] rel=me summary by Bob Ngu
[http://ungeekdapo.wordpress.com/2008/04/29/a-simple-data-portability-project-or-is-it/ A simple data portability project or is it] rel=me summary by Bob Ngu
 +
 +
== domain verification ==
 +
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.
== rel-me-auth ==
== rel-me-auth ==
[[RelMeAuth]] is a proposed open standard for using [[rel-me]] links to profiles on [[OAuth]] supporting services to authenticate via either those profiles or your own site.
[[RelMeAuth]] is a proposed open standard for using [[rel-me]] links to profiles on [[OAuth]] supporting services to authenticate via either those profiles or your own site.
-
Read more about [[RelMeAuth]] and [[web sign-in]].
+
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.
 +
 
 +
Read more about how to implement [[RelMeAuth]] and [[web sign-in]].
== implementations ==
== implementations ==

Revision as of 18:59, 8 June 2014

short URL
http://ufs.cc/w/relme

XFN 1.1 introduced the "me" rel value which is used to indicate profile equivalence and for identity-consolidation.

Contents

example

rel="me" is used on hyperlinks from one page about a person to other pages about that same person.

For example, Tantek's home page has (markup simplified)

<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:

Longer:

tutorials

A simple data portability project or is it rel=me summary by Bob Ngu

domain verification

rel=me is the standard way to check that a website belongs to a user on a 3rd party site.

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.

rel-me-auth

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

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.

Read more about how to implement RelMeAuth and web sign-in.

implementations

Notable Sites:

Services:

WordPress plugins:

advocacy

Advocating rel=me support can be done a few ways, if a site has:

Current requests:

examples in the wild

Examples of sites publishing rel=me support, e.g. on user profiles.

See:

see also

rel="me" was last modified: Wednesday, December 31st, 1969

Views