rel-contact: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(This page was listed on "pages wanted" list.)
 
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
rel=contact is defined with different meanings by:
<h1>rel contact</h1>


* [http://www.w3.org/html/wg/html5/#link-type3 HTML 5]
rel="contact" was introduced by [http://gmpg.org/xfn/11 XFN 1.1] in 2004 and is in broad use across various social network sites (see [[hcard-xfn-supporting-friends-lists#Services_with_XFN_supporting_friends_lists|services with XFN supporting friends lists]]).
* [http://gmpg.org/xfn/11 XFN 1.1]


Use the XFN [[profile-uris|profile]] if you want to explicitly specify the XFN meaning of the term.  
Much later (~2007, citation needed), a draft of HTML5 redefined rel="contact" slightly differently (currently: [http://www.w3.org/html/wg/html5/#link-type3 HTML 5]).
 
Publishers should consider using the [http://gmpg.org/xfn/11 XFN 1.1 profile] to explicitly specify the XFN meaning.
 
Parsers should assume the earlier, well established and in use XFN rel="contact" meaning unless they encounter a document explicitly labeled as HTML5 that also lacks a reference to the [http://gmpg.org/xfn/11 XFN 1.1 profile].


This issue has been [[xfn-issues|documented]].
This issue has been [[xfn-issues|documented]].
== see also ==
* [[xfn]]
* [[existing-rel-values]]

Latest revision as of 21:04, 28 July 2008

rel contact

rel="contact" was introduced by XFN 1.1 in 2004 and is in broad use across various social network sites (see services with XFN supporting friends lists).

Much later (~2007, citation needed), a draft of HTML5 redefined rel="contact" slightly differently (currently: HTML 5).

Publishers should consider using the XFN 1.1 profile to explicitly specify the XFN meaning.

Parsers should assume the earlier, well established and in use XFN rel="contact" meaning unless they encounter a document explicitly labeled as HTML5 that also lacks a reference to the XFN 1.1 profile.

This issue has been documented.

see also