Microformats Wiki - User contributions [en]

existing-rel-values

2015-11-28T18:53:09Z

Adactio: Add rel=amphtml

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

This page is also the official rel registry ([http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types][http://www.w3.org/TR/html5/links.html#other-link-types]). Add new and proposed rel values to the following section:
* [[existing-rel-values#HTML5_link_type_extensions|HTML5 link type extension]]

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://www.w3.org/TR/html5/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry will not be reflected in validators in real time. But validators will typically get automatically updated with the changes within one week or so

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-amphtml|amp-html]]
| Hyperlink
| Hyperlink
| Specify an alternate version of the document written in Google's AMP format
| [https://github.com/ampproject/amphtml AMP HTML documentation]
| could be combined with rel=alternate
| proposed

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-archived|archived]]
| External Resource
| Hyperlink Annotation
| The target resource is archived and kept largely or solely for historical purposes.
| [http://www.sitemorse.com/rel-archived.html rel="archived" description]
|
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[WPVL_PRETTYPHOTO_REL]]
| Hyperlink
| Hyperlink
| Open lightbox with video
| No formal specification
|
| proposed

|-
| [[rel-authorization_endpoint|authorization_endpoint]]
| External Resource
| Not allowed
| Specify a hosted authorization server
| [http://indiewebcamp.com/distributed-indieauth distributed IndieAuth documentation]
|
| proposed

|-
| [[rel-canonical|canonical]]
| Hyperlink
| Hyperlink
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-clearbox|clearbox]]
| Not allowed
| Img Pop-Up
| Images (or any other content, depending on href link) with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (with installed "Clearbox v3"). When adding [gallery] to rel="clearbox" all images get a clickable button for next/prev; insert into <code><a rel="clearbox[gallery=Name of the gallery comes here]"> href="http:example.com/img.jpg"><img src="http:example.com/img.jpg"></a></code>
| [http://www.kreaturamedia.com/clearbox/ Clearbox 3]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-dcterms.(property)#conformsTo|DCTERMS.conformsTo]]
| External Resource
| Not allowed
| An established standard to which the described resource conforms. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.conformsTo" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#contributor|DCTERMS.contributor]]
| External Resource
| Not allowed
| An entity responsible for making contributions to the resource. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.contributor" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#creator|DCTERMS.creator]]
| External Resource
| Not allowed
| An entity primarily responsible for making the resource. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.creator" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#description|DCTERMS.description]]
| External Resource
| Not allowed
| An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.description" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#hasFormat|DCTERMS.hasFormat]]
| External Resource
| Not allowed
| A related resource that is substantially the same as the pre-existing described resource, but in another format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#hasPart|DCTERMS.hasPart]]
| External Resource
| Not allowed
| A related resource that is included either physically or logically in the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#hasVersion|DCTERMS.hasVersion]]
| External Resource
| Not allowed
| A related resource that is a version, edition, or adaptation of the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isFormatOf|DCTERMS.isFormatOf]]
| External Resource
| Not allowed
| A related resource that is substantially the same as the described resource, but in another format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isPartOf|DCTERMS.isPartOf]]
| External Resource
| Not allowed
| A related resource in which the described resource is physically or logically included. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isReferencedBy|DCTERMS.isReferencedBy]]
| External Resource
| Not allowed
| A related resource that references, cites, or otherwise points to the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isReplacedBy|DCTERMS.isReplacedBy]]
| External Resource
| Not allowed
| A related resource that supplants, displaces, or supersedes the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isRequiredBy|DCTERMS.isRequiredBy]]
| External Resource
| Not allowed
| A related resource that requires the described resource to support its function, delivery, or coherence. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isVersionOf|DCTERMS.isVersionOf]]
| External Resource
| Not allowed
| A related resource of which the described resource is a version, edition, or adaptation. Changes in version imply substantive changes in content rather than differences in format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#license|DCTERMS.license]]
| External Resource
| Not allowed
| A legal document giving official permission to do something with the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.license" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#mediator|DCTERMS.mediator]]
| External Resource
| Not allowed
| An entity that mediates access to the resource and for whom the resource is intended or useful. In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.mediator" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#publisher|DCTERMS.publisher]]
| External Resource
| Not allowed
| An entity responsible for making the resource available. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.publisher" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#references|DCTERMS.references]]
| External Resource
| Not allowed
| A related resource that is referenced, cited, or otherwise pointed to by the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#relation|DCTERMS.relation]]
| External Resource
| Not allowed
| A related resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#replaces|DCTERMS.replaces]]
| External Resource
| Not allowed
| A related resource that is supplanted, displaced, or superseded by the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#requires|DCTERMS.requires]]
| External Resource
| Not allowed
| A related resource that is required by the described resource to support its function, delivery, or coherence. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#rightsHolder|DCTERMS.rightsHolder]]
| External Resource
| Not allowed
| A person or organization owning or managing rights over the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.rightsHolder" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#source|DCTERMS.source]]
| External Resource
| Not allowed
| A related resource from which the described resource is derived. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#subject|DCTERMS.subject]]
| External Resource
| Not allowed
| The topic of the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edit|edit]]
| Hyperlink
| Not allowed
| Tells the browser where the current page can be edited
| [http://universaleditbutton.org/Registered_MIME_type#Alternate_Linking_Scheme Universal Edit Button Alternate Linking Scheme]. Implemented in at least [http://mediawiki.org MediaWiki].
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-enclosure|enclosure]]
| External Resource
| External Resource
| Indicates that the referred resource is intended to be downloaded and cached.
| [[rel-enclosure]]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-indieauth|indieauth]]
| External Resource
| Not allowed
| the IndieAuth server for the relying party to contact for IndieAuth authentication
| [http://spec.indieauth.com/ IndieAuth specification]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-jslicense|jslicense]]
| Hyperlink
| Hyperlink
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
| [[rel-jslicense]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-manifest|manifest]]
| External Resource
| Not allowed
| Imports or links to a manifest
| [http://w3c.github.io/manifest/#linking W3C Manifest for web application]
|
| proposed

|-
| [[rel-mask-icon|mask-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Pinned Tabs” on Safari 9.
| [https://developer.apple.com/library/prerelease/mac/releasenotes/General/WhatsNewInSafari/Articles/Safari_9.html#//apple_ref/doc/uid/TP40014305-CH9-SW20 What is new in Safari 9.0]
| probably redundant with rel=icon
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-indieauth|micropub]]
| External Resource
| Not allowed
| the micropub endpoint for creating new posts
| [http://indiewebcamp.com/micropub Micropub scecification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-preconnect|preconnect]]
| External Resource
| Not allowed
| Indicates an origin that will be used to fetch required resources. Initiating an early connection, which includes the DNS lookup, TCP handshake, and optional TLS negotiation, allows the user agent to mask the high costs of connection establishment latency.
| [http://www.w3.org/TR/resource-hints/ Resource Hints Working Draft]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| External Resource
| Prerenders the Web page targeted by the link including running it scripts.
| [[rel-prerender]]
|
| proposed

|-
| [[rel-prettyPhoto|prettyPhoto]]
| Not Allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked
| [http://www.no-margin-for-errors.com/projects/prettyphoto-jquery-lightbox-clone/documentation/ PrettyPhoto]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-publisher|publisher]]
| External Resource
| External Resource
| Indicates that the referenced document is a metadata profile (e.g., a social-media/real-name profile such as a Google+ profile) for the publisher of the current page, or some portion of the current page.
| [https://support.google.com/plus/answer/1713826?hl=en Google help page]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-reply-to|reply-to]]
| External Resource
| Hyperlink
| indicates any mailbox(es) (i.e. email addresses) to which responses are to be sent. ''Note: this is distinct from the 'in-reply-to' value which refers to the originating document, not to the address where comments should be sent.
| [http://tools.ietf.org/html/rfc2822 RFC2822] (originally [http://tools.ietf.org/html/rfc822#section-4.4.3 RFC822])
|
| ratified

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-token_endpoint|token_endpoint]]
| External Resource
| Not allowed
| Specify an HTTP endpoint that micropub clients can use to obtain an access token given an authorization code
| [http://indiewebcamp.com/token-endpoint token endpoint documentation]
|
| proposed

|-
| [[rel-webmention|webmention]]
| External Resource
| Hyperlink
| gives the address of the webmention endpoint that handles webmentions to the current document
| [https://indiewebcamp.com/Webmention WebMention specification]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|-
| [[rel-yandex-tableau-widget|yandex-tableau-widget]]
| External Resource
| Not allowed
| Lets webmasters configure the appearance of their own site widgets in Yandex.Browser
| [https://api.yandex.com/tableau/ Yandex's Tableau API]
|
| proposed
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-m_PageScroll2id|m_PageScroll2id]] || JS to scroll to a defined ID || [[group-brainstorming]]

|-
| [[rel-prefetch|prefetch]] || indicates the URL and content-type of a resource that is likely to be a required resource when the next action or navigation is triggered. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#prefetch resource hints draft]

|-
| [[rel-preload|preload]] || indicates the URL and content-type of a resource that should be fetched as early as possible by the user agent. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#preload resource hints draft]

|-
| [[rel-prerender|prerender]] || indicates the URL of the next navigation target. Initiating a prerender allows the user agent to deliver an instant navigation experience: the user agent downloads the top-level resource and its assets, and performs all of the processing steps required to show the page without actually showing it to the user.|| [https://igrigorik.github.io/resource-hints/#prerender resource hints draft]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]
|-
| source || the referenced document represents the source code for the current document or project || [[source-brainstorming]] [http://adactio.com/journal/6667/ blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-privacy|privacy]] || Specifies that the target resource is the privacy policy. || … || …

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-respond-proxy|respond-proxy]] || Working with respond.js - proxy on external server || [https://github.com/scottjehl/Respond] || [https://github.com/scottjehl/Respond]

|-
| [[rel-respond-redirect|respond-redirect]] || Working with respond.js - redirect location on local server || [https://github.com/scottjehl/Respond] || [https://github.com/scottjehl/Respond]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

* According to DCMI specification linked above, as well as [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] documentation, HTML5 @rel attribute proposed values table has been updated. It now includes a subset of DCMI ''/terms/'' namespace properties, more specifically those whose value can (or must) be logically expressed by a resource, so that the "href" attribute value becomes a non-literal value surrogate referring to the resource itself.
** Elements from ''/elements/1.1/'' namespace have not been included on purpose. According to [http://wiki.dublincore.org/index.php/FAQ/DC_and_DCTERMS_Namespaces "FAQ/DC and DCTERMS Namespaces"], the old namespace is maintained for legacy purposes only and it is not as suitable for non-literal values as the ones denoted by <code><link></code> elements.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]
* See [http://rels.messages.io Workflow-Related Link Relations at Messages.io]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| compensatingtx || Link to a resource representing information about a compensating transaction for each member transaction of a [http://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf Long-Lived Compensating Transaction] || See [http://rels.messages.io/#compensatingtx Compensating Transaction Link Relation]

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| events || Link to a collection resource representing a list of subscribe-able events. || See [http://rels.messages.io/#events Events Link Relation]

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox

|-
| youtube || Opens the target youtube video in using the Swipebox Plugin || Swipebox

|-
| shadowbox || shadowbox is a jQuery script for images displaying with the "lightbox" effects. || shadowbox

|-
| permission || When included in a resource, the "permission" link relation MAY identify a target resource that represents the list of entities that can access or modify the resource in the link context. || See [http://cdoc.io/spec.html#permission-link-relation Collection Document Media Type Specification]

|-
| sub || When included in a resource representation of an event, the "sub" (subscription) link relation MAY identify a target resource that represents the ability to subscribe to the pub/sub event-type resource in the link context. || See [http://rels.messages.io/#sub Subscription Link Relation]

|-
| unsub || When included in a resource representation of an event, the "unsub" (subscription cancellation) link relation MAY identify a target resource that represents the ability to un-subscribe from the pub/sub event-type resource in the link context. || See [http://rels.messages.io/#unsub Subscription Cancellation Link Relation]

|-
| version-history
| When included on a versioned resource, this link points to a resource containing the version history for this resource.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| latest-version
| When included on a versioned resource, this link points to a resource containing the latest (e.g., current) version.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| working-copy
| When included on a versioned resource, this link points to a working copy for this resource.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| working-copy-of
| When included on a working copy, this link points to the versioned resource from which this working copy was obtained.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| predecessor-version
| When included on a versioned resource, this link points to a resource containing the predecessor version in the version history.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| successor-version
| When included on a versioned resource, this link points to a resource containing the successor version in the version history.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

existing-rel-values

2015-10-13T20:34:18Z

Adactio: /* HTML5 link type extensions */ Update usage of rel="canonical"

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

This page is also the official rel registry ([http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types][http://www.w3.org/TR/html5/links.html#other-link-types]). Add new and proposed rel values to the following section:
* [[existing-rel-values#HTML5_link_type_extensions|HTML5 link type extension]]

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://www.w3.org/TR/html5/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry will not be reflected in validators in real time. But validators will typically get automatically updated with the changes within one week or so

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-archived|archived]]
| External Resource
| Hyperlink Annotation
| The target resource is archived and kept largely or solely for historical purposes.
| [http://www.sitemorse.com/rel-archived.html rel="archived" description]
|
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[WPVL_PRETTYPHOTO_REL]]
| Hyperlink
| Hyperlink
| Open lightbox with video
| No formal specification
|
| proposed

|-
| [[rel-authorization_endpoint|authorization_endpoint]]
| External Resource
| Not allowed
| Specify a hosted authorization server
| [http://indiewebcamp.com/distributed-indieauth distributed IndieAuth documentation]
|
| proposed

|-
| [[rel-canonical|canonical]]
| Hyperlink
| Hyperlink
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-clearbox|clearbox]]
| Not allowed
| Img Pop-Up
| Images (or any other content, depending on href link) with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (with installed "Clearbox v3"). When adding [gallery] to rel="clearbox" all images get a clickable button for next/prev; insert into <code><a rel="clearbox[gallery=Name of the gallery comes here]"> href="http:example.com/img.jpg"><img src="http:example.com/img.jpg"></a></code>
| [http://www.kreaturamedia.com/clearbox/ Clearbox 3]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-dcterms.(property)#conformsTo|DCTERMS.conformsTo]]
| External Resource
| Not allowed
| An established standard to which the described resource conforms. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.conformsTo" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#contributor|DCTERMS.contributor]]
| External Resource
| Not allowed
| An entity responsible for making contributions to the resource. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.contributor" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#creator|DCTERMS.creator]]
| External Resource
| Not allowed
| An entity primarily responsible for making the resource. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.creator" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#description|DCTERMS.description]]
| External Resource
| Not allowed
| An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.description" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#hasFormat|DCTERMS.hasFormat]]
| External Resource
| Not allowed
| A related resource that is substantially the same as the pre-existing described resource, but in another format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#hasPart|DCTERMS.hasPart]]
| External Resource
| Not allowed
| A related resource that is included either physically or logically in the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#hasVersion|DCTERMS.hasVersion]]
| External Resource
| Not allowed
| A related resource that is a version, edition, or adaptation of the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isFormatOf|DCTERMS.isFormatOf]]
| External Resource
| Not allowed
| A related resource that is substantially the same as the described resource, but in another format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isPartOf|DCTERMS.isPartOf]]
| External Resource
| Not allowed
| A related resource in which the described resource is physically or logically included. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isReferencedBy|DCTERMS.isReferencedBy]]
| External Resource
| Not allowed
| A related resource that references, cites, or otherwise points to the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isReplacedBy|DCTERMS.isReplacedBy]]
| External Resource
| Not allowed
| A related resource that supplants, displaces, or supersedes the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isRequiredBy|DCTERMS.isRequiredBy]]
| External Resource
| Not allowed
| A related resource that requires the described resource to support its function, delivery, or coherence. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#isVersionOf|DCTERMS.isVersionOf]]
| External Resource
| Not allowed
| A related resource of which the described resource is a version, edition, or adaptation. Changes in version imply substantive changes in content rather than differences in format. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#license|DCTERMS.license]]
| External Resource
| Not allowed
| A legal document giving official permission to do something with the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.license" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#mediator|DCTERMS.mediator]]
| External Resource
| Not allowed
| An entity that mediates access to the resource and for whom the resource is intended or useful. In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.mediator" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#publisher|DCTERMS.publisher]]
| External Resource
| Not allowed
| An entity responsible for making the resource available. Examples include a person, an organization, or a service. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.publisher" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#references|DCTERMS.references]]
| External Resource
| Not allowed
| A related resource that is referenced, cited, or otherwise pointed to by the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#relation|DCTERMS.relation]]
| External Resource
| Not allowed
| A related resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#replaces|DCTERMS.replaces]]
| External Resource
| Not allowed
| A related resource that is supplanted, displaced, or superseded by the described resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#requires|DCTERMS.requires]]
| External Resource
| Not allowed
| A related resource that is required by the described resource to support its function, delivery, or coherence. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#rightsHolder|DCTERMS.rightsHolder]]
| External Resource
| Not allowed
| A person or organization owning or managing rights over the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
| It may be replaced by the literal value in form of <code><meta name="DCTERMS.rightsHolder" content="..." /></code>
| proposed

|-
| [[rel-dcterms.(property)#source|DCTERMS.source]]
| External Resource
| Not allowed
| A related resource from which the described resource is derived. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-dcterms.(property)#subject|DCTERMS.subject]]
| External Resource
| Not allowed
| The topic of the resource. 
Requires Dublin Core namespace declaration: <code>'''<link rel="schema.DCTERMS" href="<nowiki>http://purl.org/dc/terms/</nowiki>" />'''</code>
| [http://dublincore.org/documents/dcmi-terms/ DCMI Metadata Terms]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edit|edit]]
| Hyperlink
| Not allowed
| Tells the browser where the current page can be edited
| [http://universaleditbutton.org/Registered_MIME_type#Alternate_Linking_Scheme Universal Edit Button Alternate Linking Scheme]. Implemented in at least [http://mediawiki.org MediaWiki].
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-enclosure|enclosure]]
| External Resource
| External Resource
| Indicates that the referred resource is intended to be downloaded and cached.
| [[rel-enclosure]]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-indieauth|indieauth]]
| External Resource
| Not allowed
| the IndieAuth server for the relying party to contact for IndieAuth authentication
| [http://spec.indieauth.com/ IndieAuth specification]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-jslicense|jslicense]]
| Hyperlink
| Hyperlink
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
| [[rel-jslicense]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-manifest|manifest]]
| External Resource
| Not allowed
| Imports or links to a manifest
| [http://w3c.github.io/manifest/#linking W3C Manifest for web application]
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-indieauth|micropub]]
| External Resource
| Not allowed
| the micropub endpoint for creating new posts
| [http://indiewebcamp.com/micropub Micropub scecification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| External Resource
| Prerenders the Web page targeted by the link including running it scripts.
| [[rel-prerender]]
|
| proposed

|-
| [[rel-prettyPhoto|prettyPhoto]]
| Not Allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked
| [http://www.no-margin-for-errors.com/projects/prettyphoto-jquery-lightbox-clone/documentation/ PrettyPhoto]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-publisher|publisher]]
| External Resource
| External Resource
| Indicates that the referenced document is a metadata profile (e.g., a social-media/real-name profile such as a Google+ profile) for the publisher of the current page, or some portion of the current page.
| [https://support.google.com/plus/answer/1713826?hl=en Google help page]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-reply-to|reply-to]]
| External Resource
| Hyperlink
| indicates any mailbox(es) (i.e. email addresses) to which responses are to be sent. ''Note: this is distinct from the 'in-reply-to' value which refers to the originating document, not to the address where comments should be sent.
| [http://tools.ietf.org/html/rfc2822 RFC2822] (originally [http://tools.ietf.org/html/rfc822#section-4.4.3 RFC822])
|
| ratified

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-token_endpoint|token_endpoint]]
| External Resource
| Not allowed
| Specify an HTTP endpoint that micropub clients can use to obtain an access token given an authorization code
| [http://indiewebcamp.com/token-endpoint token endpoint documentation]
|
| proposed

|-
| [[rel-webmention|webmention]]
| External Resource
| Hyperlink
| gives the address of the webmention endpoint that handles webmentions to the current document
| [http://webmention.org/ WebMention specification]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|-
| [[rel-yandex-tableau-widget|yandex-tableau-widget]]
| External Resource
| Not allowed
| Lets webmasters configure the appearance of their own site widgets in Yandex.Browser
| [https://api.yandex.com/tableau/ Yandex's Tableau API]
|
| proposed
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-m_PageScroll2id|m_PageScroll2id]] || JS to scroll to a defined ID || [[group-brainstorming]]

|-
| [[rel-preconnect|preconnect]] || indicates an origin that will be used to fetch required resources. Initiating an early connection, which includes the DNS lookup, TCP handshake, and optional TLS negotiation, allows the user agent to mask the high costs of connection establishment latency.|| [https://igrigorik.github.io/resource-hints/#preconnect resource hints draft]

|-
| [[rel-prefetch|prefetch]] || indicates the URL and content-type of a resource that is likely to be a required resource when the next action or navigation is triggered. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#prefetch resource hints draft]

|-
| [[rel-preload|preload]] || indicates the URL and content-type of a resource that should be fetched as early as possible by the user agent. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#preload resource hints draft]

|-
| [[rel-prerender|prerender]] || indicates the URL of the next navigation target. Initiating a prerender allows the user agent to deliver an instant navigation experience: the user agent downloads the top-level resource and its assets, and performs all of the processing steps required to show the page without actually showing it to the user.|| [https://igrigorik.github.io/resource-hints/#prerender resource hints draft]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]
|-
| source || the referenced document represents the source code for the current document or project || [[source-brainstorming]] [http://adactio.com/journal/6667/ blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-privacy|privacy]] || Specifies that the target resource is the privacy policy. || … || …

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-respond-proxy|respond-proxy]] || Working with respond.js - proxy on external server || [https://github.com/scottjehl/Respond] || [https://github.com/scottjehl/Respond]

|-
| [[rel-respond-redirect|respond-redirect]] || Working with respond.js - redirect location on local server || [https://github.com/scottjehl/Respond] || [https://github.com/scottjehl/Respond]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

* According to DCMI specification linked above, as well as [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] documentation, HTML5 @rel attribute proposed values table has been updated. It now includes a subset of DCMI ''/terms/'' namespace properties, more specifically those whose value can (or must) be logically expressed by a resource, so that the "href" attribute value becomes a non-literal value surrogate referring to the resource itself.
** Elements from ''/elements/1.1/'' namespace have not been included on purpose. According to [http://wiki.dublincore.org/index.php/FAQ/DC_and_DCTERMS_Namespaces "FAQ/DC and DCTERMS Namespaces"], the old namespace is maintained for legacy purposes only and it is not as suitable for non-literal values as the ones denoted by <code><link></code> elements.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]
* See [http://rels.messages.io Workflow-Related Link Relations at Messages.io]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| compensatingtx || Link to a resource representing information about a compensating transaction for each member transaction of a [http://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf Long-Lived Compensating Transaction] || See [http://rels.messages.io/#compensatingtx Compensating Transaction Link Relation]

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| events || Link to a collection resource representing a list of subscribe-able events. || See [http://rels.messages.io/#events Events Link Relation]

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox

|-
| youtube || Opens the target youtube video in using the Swipebox Plugin || Swipebox

|-
| shadowbox || shadowbox is a jQuery script for images displaying with the "lightbox" effects. || shadowbox

|-
| permission || When included in a resource, the "permission" link relation MAY identify a target resource that represents the list of entities that can access or modify the resource in the link context. || See [http://cdoc.io/spec.html#permission-link-relation Collection Document Media Type Specification]

|-
| sub || When included in a resource representation of an event, the "sub" (subscription) link relation MAY identify a target resource that represents the ability to subscribe to the pub/sub event-type resource in the link context. || See [http://rels.messages.io/#sub Subscription Link Relation]

|-
| unsub || When included in a resource representation of an event, the "unsub" (subscription cancellation) link relation MAY identify a target resource that represents the ability to un-subscribe from the pub/sub event-type resource in the link context. || See [http://rels.messages.io/#unsub Subscription Cancellation Link Relation]

|-
| version-history
| When included on a versioned resource, this link points to a resource containing the version history for this resource.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| latest-version
| When included on a versioned resource, this link points to a resource containing the latest (e.g., current) version.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| working-copy
| When included on a versioned resource, this link points to a working copy for this resource.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| working-copy-of
| When included on a working copy, this link points to the versioned resource from which this working copy was obtained.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| predecessor-version
| When included on a versioned resource, this link points to a resource containing the predecessor version in the version history.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| successor-version
| When included on a versioned resource, this link points to a resource containing the successor version in the version history.
| [http://tools.ietf.org/html/rfc5829 RFC 5829]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

existing-rel-values

2014-11-28T19:49:33Z

Adactio: /* HTML5 link type extensions */ micropub, authorization_endpoint, and token_endpoint

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

This page is also the official rel registry ([http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types][http://www.w3.org/TR/html5/links.html#other-link-types]). Add new and proposed rel values to the following section:
* [[existing-rel-values#HTML5_link_type_extensions|HTML5 link type extension]]

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://dev.w3.org/html5/spec/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry will not be reflected in validators in real time. But validators will typically get automatically updated with the changes within one week or so

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[rel-authorization_endpoint|authorization_endpoint]]
| External Resource
| Not allowed
| Specify a hosted authorization server
| [http://indiewebcamp.com/distributed-indieauth distributed IndieAuth documentation]
|
| proposed

|-
| [[rel-canonical|canonical]]
| External Resource
| Not allowed
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edit|edit]]
| Hyperlink
| Not allowed
| Tells the browser where the current page can be edited
| [http://universaleditbutton.org/Registered_MIME_type#Alternate_Linking_Scheme Universal Edit Button Alternate Linking Scheme]. Implemented in at least [http://mediawiki.org MediaWiki].
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-indieauth|indieauth]]
| External Resource
| Not allowed
| the IndieAuth server for the relying party to contact for IndieAuth authentication
| [http://spec.indieauth.com/ IndieAuth specification]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-manifest|manifest]]
| External Resource
| Not allowed
| Imports or links to a manifest
| [http://w3c.github.io/manifest/#linking W3C Manifest for web application]
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-indieauth|micropub]]
| External Resource
| Not allowed
| the micropub endpoint for creating new posts
| [http://indiewebcamp.com/micropub Micropub scecification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| External Resource
| Prerenders the Web page targeted by the link including running it scripts.
| [[rel-prerender]]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-publisher|publisher]]
| External Resource
| External Resource
| Indicates that the referenced document is a metadata profile (e.g., a social-media/real-name profile such as a Google+ profile) for the publisher of the current page, or some portion of the current page.
| [https://support.google.com/plus/answer/1713826?hl=en Google help page]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-token_endpoint|token_endpoint]]
| External Resource
| Not allowed
| Specify an HTTP endpoint that micropub clients can use to obtain an access token given an authorization code
| [http://indiewebcamp.com/token-endpoint token endpoint documentation]
|
| proposed

|-
| [[rel-webmention|webmention]]
| External Resource
| Hyperlink
| gives the address of the webmention endpoint that handles webmentions to the current document
| [http://webmention.org/ WebMention specification]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-jslicense|jslicense]]
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
|* Brainstorming page -- thoughts on the name?
* Ex. [http://www.eff.org EFF.org] (on <code>link</code>)
* Ex. [http://www.fsf.org FSF.org] (on <code>a</code>)
|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-m_PageScroll2id|m_PageScroll2id]] || JS to scroll to a defined ID || [[group-brainstorming]]

|-
| [[rel-preconnect|preconnect]] || indicates an origin that will be used to fetch required resources. Initiating an early connection, which includes the DNS lookup, TCP handshake, and optional TLS negotiation, allows the user agent to mask the high costs of connection establishment latency.|| [https://igrigorik.github.io/resource-hints/#preconnect resource hints draft]

|-
| [[rel-prefetch|prefetch]] || indicates the URL and content-type of a resource that is likely to be a required resource when the next action or navigation is triggered. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#prefetch resource hints draft]

|-
| [[rel-preload|preload]] || indicates the URL and content-type of a resource that should be fetched as early as possible by the user agent. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#preload resource hints draft]

|-
| [[rel-prerender|prerender]] || indicates the URL of the next navigation target. Initiating a prerender allows the user agent to deliver an instant navigation experience: the user agent downloads the top-level resource and its assets, and performs all of the processing steps required to show the page without actually showing it to the user.|| [https://igrigorik.github.io/resource-hints/#prerender resource hints draft]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]
|-
| source || the referenced document represents the source code for the current document or project || [[source-brainstorming]] [http://adactio.com/journal/6667/ blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox

|-
| youtube || Opens the target youtube video in using the Swipebox Plugin || Swipebox

|-
| shadowbox || shadowbox is a jQuery script for images displaying with the "lightbox" effects. || shadowbox

|-
| permission || When included in a resource, the "permission" link relation MAY identify a target resource that represents the list of entities that can access or modify the resource in the link context. || See [http://cdoc.io/spec.html#permission-link-relation Collection Document Media Type Specification]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

existing-rel-values

2014-07-11T08:44:50Z

Adactio: /* brainstorming */ Add resource hints values

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

This page is also the official rel registry ([http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types][http://www.w3.org/TR/html5/links.html#other-link-types]). Add new and proposed rel values to the following section:
* [[existing-rel-values#HTML5_link_type_extensions|HTML5 link type extension]]

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://dev.w3.org/html5/spec/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry may not be reflected in validators in real time.

If you add a rel value to this table and you want it supported in the validator(s), you need to either [http://bugzilla.validator.nu/ open a validator bug] or e-mail the [mailto:www-validator@w3.org www-validator@w3.org] list to ask that it be added and reference your change to this page.

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[rel-canonical|canonical]]
| External Resource
| Not allowed
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edit|edit]]
| Hyperlink
| Not allowed
| Tells the browser where the current page can be edited
| [http://universaleditbutton.org/Registered_MIME_type#Alternate_Linking_Scheme Universal Edit Button Alternate Linking Scheme]. Implemented in at least [http://mediawiki.org MediaWiki].
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-indieauth|indieauth]]
| External Resource
| Not allowed
| the IndieAuth server for the relying party to contact for IndieAuth authentication
| [http://spec.indieauth.com/ IndieAuth specification]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-manifest|manifest]]
| External Resource
| Not allowed
| Imports or links to a manifest
| [http://w3c.github.io/manifest/#linking W3C Manifest for web application]
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| External Resource
| Prerenders the Web page targeted by the link including running it scripts.
| [[rel-prerender]]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-publisher|publisher]]
| External Resource
| External Resource
| Indicates that the referenced document is a metadata profile (e.g., a social-media/real-name profile such as a Google+ profile) for the publisher of the current page, or some portion of the current page.
| [https://support.google.com/plus/answer/1713826?hl=en Google help page]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-webmention|webmention]]
| External Resource
| Hyperlink
| gives the address of the webmention endpoint that handles webmentions to the current document
| [http://webmention.org/ WebMention specification]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-jslicense|jslicense]]
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
|* Brainstorming page -- thoughts on the name?
* Ex. [http://www.eff.org EFF.org] (on <code>link</code>)
* Ex. [http://www.fsf.org FSF.org] (on <code>a</code>)
|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-preconnect|preconnect]] || indicates an origin that will be used to fetch required resources. Initiating an early connection, which includes the DNS lookup, TCP handshake, and optional TLS negotiation, allows the user agent to mask the high costs of connection establishment latency.|| [https://igrigorik.github.io/resource-hints/#preconnect resource hints draft]

|-
| [[rel-prefetch|prefetch]] || indicates the URL and content-type of a resource that is likely to be a required resource when the next action or navigation is triggered. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#prefetch resource hints draft]

|-
| [[rel-preload|preload]] || indicates the URL and content-type of a resource that should be fetched as early as possible by the user agent. Initiating an early fetch allows the user agent to mask the request latency of the resource and make it available sooner to the application.|| [https://igrigorik.github.io/resource-hints/#preload resource hints draft]

|-
| [[rel-prerender|prerender]] || indicates the URL of the next navigation target. Initiating a prerender allows the user agent to deliver an instant navigation experience: the user agent downloads the top-level resource and its assets, and performs all of the processing steps required to show the page without actually showing it to the user.|| [https://igrigorik.github.io/resource-hints/#prerender resource hints draft]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]
|-
| source || the referenced document represents the source code for the current document or project || [[source-brainstorming]] [http://adactio.com/journal/6667/ blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox

|-
| youtube || Opens the target youtube video in using the Swipebox Plugin || Swipebox

|-
| shadowbox || shadowbox is a jQuery script for images displaying with the "lightbox" effects. || shadowbox

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

rel-syndication

2014-06-14T12:37:11Z

Adactio: /* Examples in the wild */

{{stub}}

== Publishers ==

A permalink for a blog post should hyperlink with <code>rel="syndication"</code> to copies that the author has syndicated onto other sites.

This is a page to page relationship, and thus blog posts in aggregate form, e.g. archive pages, home/updates pages, should NOT use rel="syndication".

== Consumers ==

Consuming applications can use rel=syndication in a number of ways:
* site specific post and other [http://indiewebcamp.com/webactions webaction] buttons can discover the syndicated copy for their site.
* connecting POSSE'd comment posts to each other and to the POSSE'd copies of original posts. See http://indiewebcamp.com/comment#POSSE_a_comment for more.

== Alternatives ==
=== u-syndication ===
In addition rel=syndication on links from a blog post to syndicated copies of it, those links can also have the markup:
* <code>class="u-syndication"</code> which will likely get picked up as part of their containing [[h-entry]] object.

Advantages:
* Blog posts can use on links to syndicated copies, in any context, e.g. blog posts in aggregate form like archive pages or home/updates pages, may use class="u-syndication".

== Examples in the wild ==
Sites that are using rel="syndication"

On all their blog posts/notes automatically:
* aaronparecki.com
* tommorris.org
* waterpigs.co.uk

On some blog posts:
* tantek.com
* adactio.com

== See also ==
* [[rel-in-reply-to]]
* http://indiewebcamp.com/posts-elsewhere
* http://indiewebcamp.com/rel-syndication
* http://indiewebcamp.com/syndication
* http://indiewebcamp.com/comments

source-code-brainstorming

2014-02-04T12:02:33Z

Adactio: /* Examples */ Add unison.js as an example

<entry-title> Source Brainstorming </entry-title>

Per the microformats [[process]], this page is for brainstorming about ideas, proposals, constraints, requirements for a microformat for indicating the link relationship between a document (or site) and its source code.

== Usage ==

<pre><nowiki><a href="https://github.com/adactio/html5forwebdesigners" rel="source">the source for this book</a></nowiki></pre>

<pre><nowiki><link href="https://github.com/adactio/html5forwebdesigners" rel="source" /></nowiki></pre>

== Use Cases ==

When an author links to a project's (or document's) source code (e.g. on GitHub, Google Code, etc.) a rel value of "source" could be used to explicitly define that relationship.

== Examples ==

These examples demonstrate situations where an explicit rel value could be used to mark up an existing document (or project's) link to its source.

* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me the source code on GitHub].
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].
* [http://tom.preston-werner.com/ Tom Preston-Warner] links to [http://github.com/mojombo his Github account].
* [http://responsivedesign.is/resources/javascript-jquery/unison.js The Unison.js project] links to [https://github.com/bjork24/Unison the source code on Github] and [https://github.com/bjork24/Unison/archive/master.zip a direct link to download a .zip file of the source code].

source-code-brainstorming

2014-02-03T23:41:28Z

Adactio: /* Usage */ Fixing markup error

existing-rel-values

2014-02-03T23:40:38Z

Adactio: /* brainstorming */ rel="source"

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

This page is also the official rel registry ([http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types][http://www.w3.org/TR/html5/links.html#other-link-types]). Add new and proposed rel values to the following section:
* [[existing-rel-values#HTML5_link_type_extensions|HTML5 link type extension]]

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://dev.w3.org/html5/spec/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry may not be reflected in validators in real time.

If you add a rel value to this table and you want it supported in the validator(s), you need to either [http://bugzilla.validator.nu/ open a validator bug] or e-mail the [mailto:www-validator@w3.org www-validator@w3.org] list to ask that it be added and reference your change to this page.

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[rel-canonical|canonical]]
| External Resource
| Not allowed
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-indieauth|indieauth]]
| External Resource
| Not allowed
| the IndieAuth server for the relying party to contact for IndieAuth authentication
| [http://spec.indieauth.com/ IndieAuth specification]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/rdf-syntax-grammar/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| External Resource
| Prerenders the Web page targeted by the link including running it scripts.
| [[rel-prerender]]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-webmention|webmention]]
| External Resource
| Not allowed
| gives the address of the webmention endpoint that handles webmentions to the current document
| [http://webmention.org/ WebMention specification]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-jslicense|jslicense]]
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
|* Brainstorming page -- thoughts on the name?
* Ex. [http://www.eff.org EFF.org] (on <code>link</code>)
* Ex. [http://www.fsf.org FSF.org] (on <code>a</code>)
|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]
|-
| source || the referenced document represents the source code for the current document or project || [[source-brainstorming]] [http://adactio.com/journal/6667/ blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-publisher|publisher]] || Connecting the website of a publisher with their G+ profile || Google || [http://support.google.com/webmasters/bin/answer.py?answer=1708844]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox
|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

source-code-brainstorming

2014-02-03T19:12:40Z

Adactio: Add example of a "fork me on Github" ribbom

<entry-title> Source Brainstorming </entry-title>

Per the microformats [[process]], this page is for brainstorming about ideas, proposals, constraints, requirements for a microformat for indicating the link relationship between a document (or site) and its source code.

== Usage ==

<pre><nowiki><a href="https://github.com/adactio/html5forwebdesigners" rel="source">the source for this book</a></nowiki></pre>

<pre><nowiki><link href="https://github.com/adactio/html5forwebdesigners" rel="source /></nowiki></pre>

== Use Cases ==

When an author links to a project's (or document's) source code (e.g. on GitHub, Google Code, etc.) a rel value of "source" could be used to explicitly define that relationship.

== Examples ==

These examples demonstrate situations where an explicit rel value could be used to mark up an existing document (or project's) link to its source.

* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me the source code on GitHub].
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].
* [http://tom.preston-werner.com/ Tom Preston-Warner] links to [http://github.com/mojombo his Github account].

source-code-brainstorming

2014-02-03T19:06:18Z

Adactio: Use cases

<entry-title> Source Brainstorming </entry-title>

Per the microformats [[process]], this page is for brainstorming about ideas, proposals, constraints, requirements for a microformat for indicating the link relationship between a document (or site) and its source code.

== Usage ==

<pre><nowiki><a href="https://github.com/adactio/html5forwebdesigners" rel="source">the source for this book</a></nowiki></pre>

<pre><nowiki><link href="https://github.com/adactio/html5forwebdesigners" rel="source /></nowiki></pre>

== Use Cases ==

When an author links to a project's (or document's) source code (e.g. on GitHub, Google Code, etc.) a rel value of "source" could be used to explicitly define that relationship.

== Examples ==

These examples demonstrate situations where an explicit rel value could be used to mark up an existing document (or project's) link to its source.

* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me the source code on GitHub].
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].

source-code-brainstorming

2014-02-03T19:03:10Z

Adactio: Adding an example from Dan Mall's site

<entry-title> Source Brainstorming </entry-title>

Per the microformats [[process]], this page is for brainstorming about ideas, proposals, constraints, requirements for a microformat for indicating the link relationship between a document (or site) and its source code.

== Usage ==

<pre><nowiki><a href="https://github.com/adactio/html5forwebdesigners" rel="source">the source for this book</a></nowiki></pre>

<pre><nowiki><link href="https://github.com/adactio/html5forwebdesigners" rel="source /></nowiki></pre>

== Use Cases ==

When an author links to a project's (or document's) source code (e.g. on GitHub, Google Code, etc.) a rel value of "source" could be used to

== Examples ==

These examples demonstrate situations where an explicit rel value could be used to mark up an existing document (or project's) link to its source.

* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me the source code on GitHub].
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].

source-code-brainstorming

2014-02-03T12:36:31Z

Adactio: Brainstorming for rel="source"

existing-rel-values

2013-07-03T11:38:39Z

Adactio: Adding rel value of subresource, originally listed on the WHATWG rel registry but somehow lost in the move over here,

<entry-title> existing rel values </entry-title>

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add proposed rel values for HTML5 here, add them to the [[#HTML5_link_type_extensions|HTML5 link type extensions]] table.
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C Recommendations:
** [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4.01 section 6.12 Link types] (HTML4 Link types)
** [http://www.w3.org/TR/grddl/ Gleaning Resource Descriptions from Dialects of Languages] (GRDDL)
* [[microformats]] specifications
** [[xfn]]
** [[rel-license]]
** [[rel-nofollow]]

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description (from the relevant specification where possible)
! Link to defining specification

|-
| [[rel-acquaintance|acquaintance]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance
| [[XFN]]

|-
| [[rel-alternate|alternate]]
| external resource
| external relation
| Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media).
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-appendix|appendix]]
| allowed
| allowed
| Refers to a document serving as an appendix in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-bookmark|bookmark]]
| not allowed
| allowed
| Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-chapter|chapter]]
| allowed
| allowed
| Refers to a document serving as a chapter in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-child|child]]
| not allowed
| external relation
| the referenced person is a child of the person represented by the current document
| [[XFN]]

|-
| [[rel-colleague|colleague]]
| not allowed
| external relation
| the referenced person is a colleague of the person represented by the current document
| [[XFN]]

|-
| [[rel-contact|contact]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a contact
| [[XFN]]

|-
| [[rel-contents|contents]]
| allowed
| allowed
| Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents").
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-copyright|copyright]]
| allowed
| allowed
| Refers to a copyright statement for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-co-resident|co-resident]]
| not allowed
| external relation
| the referenced person lives in the same residence as the person represented by the current document
| [[XFN]]

|-
| [[rel-co-worker|co-worker]]
| not allowed
| external relation
| the referenced person is a co-worker of the person represented by the current document
| [[XFN]]

|-
| [[rel-crush|crush]]
| not allowed
| external relation
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)
| [[XFN]]

|-
| [[rel-date|date]]
| not allowed
| external relation
| this person considers the referenced person to be a date (i.e. is dating the referenced person)
| [[XFN]]

|-
| [[rel-friend|friend]]
| not allowed
| external relation
| the person represented by the current document considers the person represented by the referenced document to be a friend
| [[XFN]]

|-
| [[rel-glossary|glossary]]
| allowed
| allowed
| Refers to a document providing a list of terms and their definitions that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-help|help]]
| allowed
| allowed
| Refers to a document offering help (more information, links to other sources information, etc.)
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-its-rules|its-rules]]
| allowed
| not allowed
| Refers to a document with external ITS rules.
| [http://www.w3.org/TR/its20/#selection-global-html5 Internationalization Tag Set (ITS) Version 2.0]

|-
| [[rel-kin|kin]]
| not allowed
| external relation
| the referenced person is part of the extended family of the person represented by the current document
| [[XFN]]

|-
| [[rel-license|license]]
| allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page.
| [[rel-license]]

|-
| [[rel-me|me]]
| external relation
| external relation
| the referenced document represents the same person as does the current document
| [[XFN]]

|-
| [[rel-met|met]]
| not allowed
| external relation
| this person has met the referenced person
| [[XFN]]

|-
| [[rel-muse|muse]]
| not allowed
| external relation
| the referenced person inspires the person represented by the current document
| [[XFN]]

|-
| [[rel-neighbor|neighbor]]
| not allowed
| external relation
| the referenced person lives nearby the person represented by the current document
| [[XFN]]

|-
| [[rel-next|next]]
| external relation
| external relation
| Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-nofollow|nofollow]]
| not allowed
| external relation
| indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines).
| [[rel-nofollow]]

|-
| [[rel-parent|parent]]
| not allowed
| external relation
| the referenced person is a parent of the person represented by the current document
| [[XFN]]

|-
| [[rel-prev|prev]]
| external relation
| external relation
| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous".
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-previous|previous]]
| external relation
| external relation
| Synonym of <code>prev</code>
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-section|section]]
| allowed
| allowed
| Refers to a document serving as a section in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sibling|sibling]]
| not allowed
| external relation
| the referenced person is a sibling of the person represented by the current document
| [[XFN]]

|-
| [[rel-spouse|spouse]]
| not allowed
| external relation
| the referenced person is a spouse of the person represented by the current document
| [[XFN]]

|-
| [[rel-start|start]]
| allowed
| allowed
| Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-stylesheet|stylesheet]]
| external resource
| not allowed
| a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-subsection|subsection]]
| allowed
| allowed
| Refers to a document serving as a subsection in a collection of documents.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-sweetheart|sweetheart]]
| not allowed
| external relation
| this person considers the referenced person to be their sweetheart
| [[XFN]]

|-
| [[rel-tag|tag]]
| not allowed
| allowed
| …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page.
| [[rel-tag]]

|-
| [[rel-toc|toc]]
| allowed
| allowed
| Synonym of <code>contents</code> (from "Table Of Contents")
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 Link types]

|-
| [[rel-transformation|transformation]]
| allowed
| allowed
| Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]]
| [http://www.w3.org/TR/grddl/#transformation GRDDL]

|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-pronunciation|pronunciation]] || …indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || …indicates that the destination of the hyperlink provides a way to show or give support (e.g. financial) for the current page|| [[rel-payment]]
|}

== HTML5 link type extensions ==

The following values are registered as link type extensions per the [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types requirements in the WHATWG HTML spec] and the [http://dev.w3.org/html5/spec/links.html#other-link-types requirements in the W3C HTML5 spec].

Before you register a new value:
* '''Please check the [[#formats|Formats table]] and DO NOT re-register''' rel values that are already there. Please note that the W3C HTML WG has made a [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Decision] to drop <code>index</code>, <code>up</code>, <code>first</code> and <code>last</code> from the HTML5 spec itself.
* '''Please check the [[#dropped|Dropped table]] and DO NOT register''' values that are already there. If you believe a rel value was dropped from another specification without prejudice, please provide link/cite to explicit text/decision stating as such, e.g. the value was merely postponed, or perhaps expected to be spun-out into its own spec from the group developing that specification.

Note that entries in the [[#formats|Formats table]] and entries that are already in HTML5 as built-in keywords are also considered extensions with the "Ratified" status.

Please make sure that registrations added here have all the required data filled in ''including'':
* "Effect on link"
* "Effect on a and area" and
* a link to a spec that documents the keyword ''as an HTML <code>rel</code> keyword''. (A spec that merely defines the file format of the link target but does not define the <code>rel</code> keyword for use in HTML is not the kind of spec that is being required here.)

Entries lacking any of the above required data will likely be removed.

Changes to this registry may not be reflected in validators in real time.

{| border="1"
|+
! Keyword
! Effect on <code>link</code>
! Effect on <code>a</code>, <code>area</code>
! Brief description
! Link to specification
! Synonyms
! Status

|-
| [[rel-apple-touch-icon|apple-touch-icon]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-icon-precomposed|apple-touch-icon-precomposed]]
| External Resource
| Not allowed
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| probably redundant with rel=icon
| proposed

|-
| [[rel-apple-touch-startup-image|apple-touch-startup-image]]
| External Resource
| Not allowed
| Specify a splashscreen for Web apps on iOS Safari
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]
| maybe redundant with rel=icon with the sizes attribute?
| proposed

|-
| [[rel-attachment|attachment]]
| Hyperlink
| Hyperlink
| The resource linked to is "attached" to this document, similar to email attachments. Used in WordPress.
| No formal specification
|
| proposed

|-
| [[rel-canonical|canonical]]
| External Resource
| Not allowed
| Specifies the canonical URL for the current document in order to help avoid duplicate content.
| [http://en.wikipedia.org/wiki/Canonical_meta_tag Canonical meta tag] [http://www.Google.com/support/webmasters/bin/answer.py?answer=139066#2 Canonicalization at Google Webmaster Central] [http://www.Bing.com/community/site_blogs/b/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft Webmaster Center] [http://www.YSearchBlog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo! Search Blog]
|
| proposed

|-
| [[rel-category|category]]
| Hyperlink
| Hyperlink
| Refers to a category assigned to the current document or post. Implemented by WordPress for indicating a relation between a blog post and a category.
| [[rel-category]]
|
| proposed

|-
| [[rel-component|component]]
| External Resource
| Not allowed
| Specify an HTML document that is treated as a component of this document.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html Web Components]
|
| proposed

|-
| [[rel-chrome-webstore-item|chrome-webstore-item]]
| External Resource
| Not allowed
| Link tag to declare for app and extensions inline installations hosted in the Chrome Web Store.
| [https://developers.google.com/chrome/web-store/docs/inline_installation Using Inline Installation]
|
| proposed

|-
| [[rel-disclosure|disclosure]]
| Not allowed
| External Resource
| The 'disclosure' Link Relation Type designates a list of patent disclosures or a particular patent disclosure itself made with respect to material for which such relation type is specified.
| [http://tools.ietf.org/html/draft-yevstifeyev-disclosure-relation The 'disclosure' Link Relation Type]
|
| proposed

|-
| [[rel-discussion|discussion]]
| Hyperlink
| Hyperlink
| Refers to discussion of the current document or post.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-dns-prefetch|dns-prefetch]]
| External Resource
| Not allowed
| Tells the browser to perform dns lookup for host names ahead of use.
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla documentation] [http://dev.chromium.org/developers/design-documents/dns-prefetching Google documentation]
|
| proposed

|-
| [[rel-edituri|EditURI]]
| External Resource
| Not allowed
| A blogging auto discovery value, commonly used by WordPress
| [http://bitworking.org/projects/atom/draft-gregorio-09.html#Edit AtomAPI]
|
| proposed

|-
| [[rel-entry-content|entry-content]]
| Not allowed
| External Resource
| Indicates that the referenced document is an alternative display source for an Internet Explorer Web Slice.
| [http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx#_alternative Web Slice format specification 0.9]
|
| proposed

|-
| [[rel-external|external]]
| Not allowed
| Hyperlink
| Indicates that the referenced document is not part of the same site as the current document.
| [[rel-external]]
|
| proposed

|-
| [[rel-home|home]]
| Hyperlink
| Hyperlink
| Refers to the top level document for the current document. It can be combined with 'alternate' to indicate a feed for the site of the current page.
| [[rel-home]]
|
| proposed

|-
| [[rel-hub|hub]]
| Hyperlink
| Hyperlink
| Refers to a hub that enables registration for notification of updates to the current page.
| [http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#discovery PubSubHubbub Spec]
|
| proposed

|-
| [[rel-in-reply-to|in-reply-to]]
| Hyperlink
| Hyperlink
| Refers to an original post that the current page is a comment on or reply to.
| [[rel-in-reply-to]]
|
| proposed

|-
| [[rel-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing a list of topics with pointers that pertain to the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| proposed

|-
| [[rel-issues|issues]]
| Hyperlink
| Hyperlink
| Refers to issues regarding the current document or specification.
| [[rel-discussion]]
|
| proposed

|-
| [[rel-lightbox|lightbox]]
| Not allowed
| Img Pop-Up
| Images with this attribute are displayed in a larger way than embedded in a website (or how you specified it) when clicked (e.g. with installed "Lightbox 2"-Plugin). When adding [group] to rel="lightbox" all images get a clickable button for next/prev; insert into <code><a rel="lightbox[group]"><img src="http:example.com/img.jpg"></a></code>
| [http://lokeshdhakar.com/projects/lightbox2/ Lightbox 2] (needs actual specification to be kept in this list, this link is just documentation of one implementation)
|
| proposed

|-
| [[rel-meta|meta]]
| External Resource
| Not allowed
| External metadata about the HTML document
| [http://www.w3.org/TR/rdf-syntax-grammar/#section-rdf-in-HTML W3C's RDF/XML Syntax Specification]
|
| proposed

|-
| [[rel-openid.delegate|openid.delegate]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 1.1 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid.server|openid.server]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 1.1 authentication
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]
|
| proposed

|-
| [[rel-openid2.local_id|openid2.local_id]]
| External Resource
| Not allowed
| When the page that contains the link is used as an OpenID indentifier, the relying party perform sOpenID 2.0 authentication with the link target as the identifier instead.
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-openid2.provider|openid2.provider]]
| External Resource
| Not allowed
| The OpenID server for the relying party to contact for OpenID 2.0 authentication
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]
|
| proposed

|-
| [[rel-p3pv1|p3pv1]]
| External Resource
| Not allowed
| References a machine-readable privacy policy description in the P3P format
| [http://www.w3.org/TR/P3P/#syntax_link P3P spec]
|
| proposed

|-
| [[rel-pgpkey|pgpkey]]
| External Resource
| Not allowed
| Associates a PGP key with a Web page so that the Web page URL can be used as the commenter's URL in PGP-signed blog comments and the blogging system receiving the comment can fetch the key and verify the signature as belonging to the owner of the URL.
| [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html PGP-Signed Comments]
|
| proposed

|-
| [[rel-pingback|pingback]]
| External Resource
| Not allowed
| gives the address of the pingback server that handles pingbacks to the current document
| [http://www.hixie.ch/specs/pingback/pingback Pingback]
|
| proposed

|-
| [[rel-prerender|prerender]]
| External Resource
| Not allowed
| Prerenders the Web page targeted by the link including running it scripts.
| [http://dev.chromium.org/developers/design-documents/prerender Chrome Prerendering]
|
| proposed

|-
| [[rel-profile|profile]]
| External Resource
| Contextual External Resource
| indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof. See also [[xmdp-brainstorming]].
| [http://microformats.org/wiki/rel-profile rel-profile]
|
| proposed

|-
| [[rel-rendition|rendition]]
| External Resource
| External Resource
| Indicates some example rendering, interpretation, or depiction of the source. User agents may choose to execute, display, or render the target in-place; or navigate to the target.
| [http://www.globalmentor.com/specs/html-rel-rendition/ HTML rel rendition]
|
| proposed

|-
| [[rel-service|service]]
| External Resource
| Not allowed
| Atom Publishing Protocol editing service autodiscovery.
| [http://wiki.whatwg.org/wiki/ServiceRelExtension Documentation on the WHATWG wiki]
|
| proposed

|-
| [[rel-shortlink|shortlink]]
| External Resource
| Not allowed
| Specifies the preferred shortened URL for the page.
| [http://code.google.com/p/shortlink/wiki/Specification shortlink spec]
|
| proposed

|-
| [[rel-sidebar|sidebar]]
| Hyperlink
| Hyperlink
| Indicates that the referenced document is intended to be shown in a secondary browsing context.
| [[rel-sidebar]]
|
| proposed

|-
| [[rel-sitemap|sitemap]]
| External Resource
| Not allowed
| Provides a link to an XML document describing the layout of the site.
| [[rel-sitemap]]
|
| proposed

|-
| [[rel-subresource|subresource]]
| External Resource
| Not allowed
| An external resource intended for use within the current page.
| [http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource Chromium documentation]
|
| proposed

|-
| [[rel-syndication|syndication]]
| Hyperlink
| Hyperlink
| Refers to a page which is a syndicated copy of the current page.
| [[rel-syndication]]
|
| proposed

|-
| [[rel-timesheet|timesheet]]
| External Resource
| Not allowed
| Applies a timesheet to the document.
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet non-normative section in the Timesheet spec]
|
| proposed

|-
| [[rel-widget|widget]]
| External Resource
| External Resource
| Autodiscovery for W3C widgets
| [http://dev.w3.org/2006/waf/widgets/Overview.html#linking-to-a-widget-package-from-a-html- non-normative section in the Widget packaging spec]
|
| proposed

|-
| [[rel-wlwmanifest|wlwmanifest]]
| External Resource
| Not allowed
| Windows Live Writer manifest autodiscovery
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx documentation on MSDN]
|
| proposed

|-
| [[rel-image_src|image_src]]
| External Resource
| Not allowed
| Specify a Webpage Icon for use by Facebook, Yahoo, Digg, etc.
| Unknown, but see for instance [http://www.niallkennedy.com/blog/2009/03/enhanced-social-share.html this]
| probably redundant with rel=icon
| proposed

|-
| [[rel-cmis-acl|http://docs.oasis-open.org/ns/cmis/link/200908/acl]]
| External Resource
| External Resource
| Identifies the resource containing a CMIS ACL document for the link context
| [http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html#_Toc243905525 CMIS 1.0, Section 3.4.3.4]
|
| proposed

|-
| [[rel-stylesheet/less|stylesheet/less]]
| External Resource
| Not allowed
| Less CSS framework stylesheets.
| [http://lesscss.org/#-client-side-usage Less CSS usage]
|
| proposed

|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.

{| border="1"
|+
! rel value !! summary !! brainstormed in and usage in the wild

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post] which itself uses the rel value in a <link> tag in the head of the document.

|-
| [[rel-author|author]] || indicate[s] that the destination of that hyperlink represents the author of the current page. Combines with [[rel-me|rel-me]] to chain authorship information. || Google has said it will index rel-Author in this [http://googlewebmastercentral.blogspot.com/2011/06/authorship-markup-and-web-search.html blog post], with further [http://www.google.com/support/webmasters/bin/answer.py?answer=1229920 discussion of the rel-me connection] See also [http://dev.w3.org/html5/spec/Overview.html#link-type-author the HTML5 spec]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-jslicense|jslicense]]
| Refers to a document with JavaScript source code and license information (also called a [http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Labels] page). We might want choose a keyword for this that is more general -- there are many situations besides JavaScript in which it is desirable or required by license agreements (e.g., GNU GPL) to make an offer of both the source code and a copy of a license when distributing object code versions of a given work.
|* Brainstorming page -- thoughts on the name?
* Ex. [http://www.eff.org EFF.org] (on <code>link</code>)
* Ex. [http://www.fsf.org FSF.org] (on <code>a</code>)
|-
| [[rel-longdesc|longdesc]] || Alternative to the img longdesc attribute, for use on visible links || [http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild] shows many sources of proposals. Please edit this to list the earliest and perhaps most recent/comprehensive proposal. No known real world POSH usage in the wild yet.

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://monkinetic.com/2009/11/24/status-autodiscovery-relstatus.html blog post]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: If a value is missing from this table, it may have either already been promoted by writing it up as a proposal, or demoted by being explicitly dropped. Please check the other tables first before adding to this table.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||see brainstorming above for suggested use by google||unknown || DevMo / HTML5

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google]/[http://www.bing.com/community/blogs/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx Microsoft]/[http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ Yahoo!], [http://blog.ask.com/2009/02/ask-is-going-canonical.html Ask Jeeves]

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-edituri|EditURI]]
| Location of the xml-rpc gateway for a Wordpress install that allows external programs to add, edit and delete posts. Used by "[http://codex.wordpress.org/Weblog_Client WordPress blog client]" software for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. || Description stubbed in [[rel-edituri]].

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-footnote|footnote]] || Location of the footnote on a link to a footnote. || Markdown preprocessors such as [http://maruku.rubyforge.org/ Maruku] || HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || [http://dev.w3.org/html5/spec-LC/links.html#rel-icon HTML5] || WCLR/HTML5

|-
| [[rel-kinetic-stylesheet|kinetic-stylesheet]] || Imports a [http://kssproject.org/ KSS] 'kinetic stylesheet' to bind dynamic behavior to elements || Used in the [http://plone.org Plone] Content Management System || …

|-
| [[rel-lightbox|lightbox]] || Hook - Indicates that following the link will trigger a "lightbox" script (Allowed in <code>link</code> only) || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-lightbox|lightbox[group_name]]] || Used by lightbox scripts to group different sets of images together. Images from one group will not appear in another group's lightbox. See also "lightbox". || [http://lokeshdhakar.com/projects/lightbox2/#how Lightbox 2] || …

|-
| [[rel-prettyPhoto|prettyPhoto]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22prettyphoto%22 Google search for rel="prettyphoto" in the wild]) || …

|-
| [[rel-clearbox|clearbox]] || See also "lightbox" || ([http://www.google.fr/search?q=rel%3D%22clearbox%22 Google search for rel="clearbox" in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-noreferrer|noreferrer]] || indicates that no referrer information is to be leaked when following the link. || [http://dev.w3.org/html5/spec-LC/links.html#rel-noreferrer HTML5] || HTML5

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-popover|popover]] || Used by a JS widget to display a large, descriptive tooltip. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#popovers Popover.js] || …

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-publisher|publisher]] || Connecting the website of a publisher with their G+ profile || Google || [http://support.google.com/webmasters/bin/answer.py?answer=1708844]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sitemap|sitemap]] || Links to a site map document. || … || http://www.sitemaps.org/

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-tooltip|tooltip]] || Used by a JS widget to display a tooltip similar (though more customizable) to what is shown by browsers if the 'title' attribute is present. || [http://twitter.github.com/bootstrap Twitter's Bootstrap] [http://twitter.github.com/bootstrap/javascript.html#tooltips Tooltip.js] (and likely other JS tools) || …

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-user|user]] || … || … || WCLR
|-
| [[rel-wlwmanifest|wlwmanifest]] || Used by "[http://explore.live.com/windows-live-writer Windows Live Writer]," a Microsoft [http://codex.wordpress.org/Weblog_Client blog client] for automating posting and updating blog content from your desktop. || Seen in [http://www.wordpress.org/ WordPress], e.g. [http://www.tom-watson.co.uk/]. Similar values are probably used by other blog content management systems as well. || …

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== Dublin Core ==
In the past, Dublin Core values have been added to this page in the table about HTML5 features, but no examples, nor an actual specification explicitly stating how the value(s) should be used in HTML could be found. The linked specifications below have been updated so we should start considering Dublin Core values accordingly.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, with regard to the fifteen terms of the Dublin Core Metadata Element Set already published || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || a specification of all metadata terms maintained by the Dublin Core Metadata Initiative, reflecting the changes described more fully in the 2012 document "Maintenance changes to DCMI Metadata Terms" [http://dublincore.org/usage/decisions/2012/dcterms-changes/] || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

'''Issues need updating given new information from linked resources.'''

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
*** The scheme proposed above provides metadata namespace declarations. As described by DCMI specifications, such indications '''cannot''' be provided w/o a suitable namespace. In order to give complete pieces of information, the correct description set must be: <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> (for the namespace declaration, followed by) <code><meta name="DCTERMS.<nowiki>[element]</nowiki>" content="<nowiki>[element.value]</nowiki>"></code> for related elements.
**** Note: [http://purl.org/dc/terms/ schema.DCTERMS] is conventionally related to an upgraded elements list than [http://purl.org/dc/elements/1.1/ schema.DC] and should be preferred as rel values. Both are discussed here for subject completeness)
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.
*** '''recent improvements'''. DCMI solves some trouble concerning metadata through the ''description set model''. Some of these informations cannot currently be provided in any standard ways other than DC, namely dates, validity and periodicity. Following this public bug report ([https://www.w3.org/Bugs/Public/show_bug.cgi?format=multiple&id=22520]), the correct namespace declaration for DC and DCTERMS metadata are now considered valid HTML code. We '''must''' encourage this practice both for internal usefulness and for shared practices.

* The Dublin Core document [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] is a specification for, and gives examples of, both <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> and <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/">. Note that Dublin Core encourages the use of DCTERMS elements over DC. A list of projects which use Dublin Core metadata is maintained [http://dublincore.org/projects/ here].
* [http://dublincore.org/documents/dc-html/ "Expressing Dublin Core metadata using HTML/XHTML meta and link elements"] also includes examples of <link rel="DCTERMS.[element]" href="">, where [element] = subject, isReferencedBy, creator, and publisher. The <link> tag is used instead of the <meta> tag whenever the content is a URL. (Note that this use is different from, but related to, <link rel="schema.DCTERMS" href="">.) Potentially, ''any'' of the 55 DCTERMS elements could be used in this way, and this could include use in HTML 5.
** As said before, HTML5 validators now allow the use of <code><link rel="schema.DCTERMS" href="http://purl.org/dc/terms/"></code> for namespace declarations.

== Use with HTTP Link Header ==
You can also use any of the rel values (that are allowed for link elements) with HTTP Link Headers,

Example: returning a Javascript file with a license (since JS itself has no way to indicate a license)
<source lang=text>
Link: <http://creativecommons.org/publicdomain/zero/1.0/>; rel="license"
</source>

For multiple licenses (e.g. CC-SA and GPL), simply use multiple <code>Link:</code> headers.
<source lang=text>
Link: <http://creativecommons.org/licenses/by-sa/3.0/>; rel="license"
Link: <http://www.gnu.org/licenses/gpl.html>; rel="license"
</source>

Example: similarly, linking to a copyright statement for an image:
<source lang=text>
Link: <http://example.org/copyright.html>; rel="copyright"
</source>
or providing a brief inline copyright statement:
<source lang=text>
Link: <data:text/plain;charset=utf-8,Copyright 2013 ExampleCo, All Rights Reserved.>; rel="copyright"
</source>

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

A simple list here is sufficient.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.
* See [http://amundsen.com/media-types/maze/format/#link-relations Maze+XML]
* See [http://amundsen.com/media-types/collection/format/#link-relations Collection+JSON]
* See [http://www.opensearch.org/Specifications/OpenSearch/1.1#Url_rel_values OpenSearch]
* See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self
| From http://www.ietf.org/rfc/rfc4287.txt : <blockquote>The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.</blockquote>
| [[Atom]] http://www.ietf.org/rfc/rfc4287.txt

|-
| http://gdata.youtube.com/schemas/2007#in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube extension to Atom

|-
| collection || Refers to a resource which represents a collection of which the current resource is a member.

When used in the Maze+XML media type, the associated URI returns the available collection of mazes.
|| Maze+XML, Collection+JSON, OpenSearch

|-
| east || Refers to a resource to the "east" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the east in the active maze.

|| Maze+XML

|-
| exit || Refers to a resource that represents the exit or end of the current client actvity or process.

When used in the Maze+XML media type, the associated URI points to the final exit resource of the active maze.

|| Maze+XML

|-
| north || Refers to a resource that is "north" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the north in the active maze.

|| Maze+XML

|-
| south || Refers to a resource that is "south" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the south in the active maze.

|| Maze+XML

|-
| [[rel-via|via]] || Identifies a resource that is the source of the information in the context. || Atom 1.0 Syndication format (RFC 4287)

|-
| west || Refers to a resource that is "west" of the current resource.

When used in the Maze+XML media type, the associated URI points to a neighboring cell resource to the west in the active maze.

|| Maze+XML

|-
| item || The target IRI points to a resource that is a member of a collection represented by the context IRI. || Collection+JSON

|-
| create-form || When included in a resource, the "create-form" link relation MAY identify a target resource that represents the form to append a new member to the link context. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| edit-form || When included in a resource, the "edit-form" link relation identifies a target resource that represents the form for editing associated resource. || See [http://tools.ietf.org/html/rfc6861 The Create-Form and Edit-Form Link Relations (RFC6861)]

|-
| lightframe || Opens the target in a lightbox. On inclusion it provides a simple target the lightframe and loads the content in a lightbox effect || Lightbox

|-
| superbox[image] || jQuery Superbox! is a script which allows you display windows with the lightbox effect. || superbox

|-
| wp-video-lightbox || wp-video-lightbox! is a rel to anchor tag script display videos with the lightbox effect. || wp-video-lightbox
|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

In particular:
* if a rel value was in a draft and is missing (without explanation) from the final spec, or
* if a rel value was in a previous version of and is missing (without explanation) from an update to the specification (even a draft update)

Then absent any other information or explanation, it is presumed that the group/editors working on that specification decided to explicitly drop it (either in development, or in the updated version) and thus it should be obsoleted (not re-registered).

If you wish to add them, please research why such values were omitted from latter specifications before doing so. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

If there is more data, e.g. a link to an email of discussion of the spec development that explains ''why'' the rel value was dropped, and it explicitly states, e.g. it was without prejudice, or merely post-poned, or perhaps expected to be spun-out into its spec (or some other explicit positive reason), then it makes to link/cite that explicit text as part of a proposal.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) / has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped

|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown

|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown

|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown

|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown

|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown

|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown

|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown

|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown

|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown

|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown

|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown

|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown

|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown

|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown

|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown

|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown

|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown

|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown

|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown

|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown

|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown

|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown

|-
|}

== dropped without prejudice ==
In one known instance (from HTML4 to HTML5), some rel values were in an earlier version of a specification (or a proposal) and were dropped from a latter (draft) version, and it was noted that these values were dropped with the intent that they could still be proposed in a registry and thus they explicitly were not deprecated or obsoleted. This section documents such values as separate from the [[#dropped|dropped]] section.

In general, you {{should not}} use any dropped values.

If any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Rel values that were dropped without prejudice from a specification will be considered similar to new values that have never been specified.

If you know of additional rel values that were dropped without prejudice from an update to a specification, please cite a URL and quote from the group developing the specification that officially states from that group that the dropping of the values was done without prejudice, or equivalent statement (such as explicit allowance of external registration, proposal, and/or development).

This table serves a historical purpose. If you wish to propose a value from this table, please copy it and leave it in place.

Sources:
* Several rel values were [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475#c15 explicitly dropped from HTML5]. Per: [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Issue 118 Decision] ('''emphasis''' added): <blockquote>"The final proposal argues for the removal of some relation values, to wit, it suggests removal of '''index, up, first and last'''. It was pointed out in survey comments that these relations are already registered in the IANA link relation registry. Presumably, '''these relations could also be entered in whatever other registry or registries HTML5 adopts for this purpose'''...."Next Steps..."Since the relations to be removed are already registered at the IANA link relation registry, no further action is needed to include them there. WG members are '''free to register or record these relations elsehwere''' [sic], as well."</blockquote>

{| border="1"
|+
! rel value
! summary
! defining specification
! why dropped

|-
| [[rel-first|first]]
| synonym for <code>begin</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-index|index]]
| Refers to a document providing an index for the current document.
| was in [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-last|last]]
| synonym for <code>end</code>
| HTML4dropped - never in an official spec
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
| [[rel-up|up]]
|When the document forms part of a hierarchy, this link references the immediate parent of the current document.
| was in [http://www.w3.org/MarkUp/html3/dochead.html HTML3] - but [http://www.w3.org/TR/html401/types.html#type-links dropped in HTML4]
| [http://lists.w3.org/Archives/Public/public-html/2011Feb/att-0481/issue-118-decision.html Explicitly dropped from HTML5 interim draft yet permitted for external registry]

|-
|}

See related [http://dev.w3.org/html5/spec/links.html#linkTypes HTML5: Link types] for existing HTML5 specified rel values.

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
| [[rel-logo|logo]]
| [http://relogo.org Relogo.org]
| [[rejected-formats#Logo]]
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== tools ==
See [[implementations]].

== addtional external research ==
Here are some additional historical references to the development or rel-values which may be useful when researching values, especially why specific values may have been proposed but abandoned.
* 1996-06-07 [http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt Hypertext links in HTML] (copies: [http://ftp.ics.uci.edu/pub/ietf/html/draft-ietf-html-relrev-00.txt ftp.ics.uci.edu])
* 1996-11-13 [http://www.w3.org/Architecture/NOTE-link Describing and Linking Web Resources]
* 1997-01-23 [http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00537.html LYNX-DEV Lynx and the LINK tag]
* 1997-01-24 [http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Jan/0357.html Taxonomy list]
* 1997-03-28 [http://www.w3.org/TR/WD-htmllink-970328 W3C Working Draft: Hypertext Links and Meta Information in HTML]

=== previous attempts at documenting ===
There have been previous attempts at documenting known rel values, most of which fell out of date due to being dependent on a single author maintaining them. They're listed here purely for historical reasons, and are not sufficient to be references of their own (since they're just individual curations of other references)
* [http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html Link Type Definitions Glossary] by fantasai
* ...

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-rev-values]]
* [[existing-class-names]]

== copyright ==

{{cc-pd-license}}

events/2011-04-12-uk

2011-03-19T02:26:17Z

Adactio: /* attendees */

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
** +1 Convenient for Glenn, Tantek, Toby, Andy and me. Plus: Brighton's fun! [[User:Adactio|Jeremy]]
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
* The Yorkshire Grey — 29-33 Grays Inn Road, London
** This is where we had the last vEvent (ages ago). They let us have the upstairs room for free. [[User:Phae|Phae]]
</div>

== what date ==
Which is the best date for the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
** +1 London pubs are more easily bookable early in the week. [[User:Phae|Phae]]
** +1 Tuesday evening [[User:ntoll|Nicholas Tollervey]]
* Wednesday 13 April
** -1 UX London is on this day
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
** -1 UX London is on this day
* Friday 15 April
** -1 UX London is on this day
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:PaulDowney|Paul Downey (fn)]]
* [[User:SpikeUK|Chris Foote]]
* [[User:AndyHume|Andy Hume]]
* [[User:TobyInk|Toby Inkster]] (tentative)
* [[User:GlennJones|Glenn Jones (fn)]]
* [[User:Adactio|Jeremy Keith]]
* [[User:ntoll|Nicholas Tollervey]] (tentative)
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

events/2011-04-12-uk

2011-03-19T02:24:44Z

Adactio: /* what venue */

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
** +1 Convenient for Glenn, Tantek, Toby, Andy and me. Plus: Brighton's fun! [[User:Adactio|Jeremy]]
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
* The Yorkshire Grey — 29-33 Grays Inn Road, London
** This is where we had the last vEvent (ages ago). They let us have the upstairs room for free. [[User:Phae|Phae]]
</div>

== what date ==
Which is the best date for the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
** +1 London pubs are more easily bookable early in the week. [[User:Phae|Phae]]
** +1 Tuesday evening [[User:ntoll|Nicholas Tollervey]]
* Wednesday 13 April
** -1 UX London is on this day
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
** -1 UX London is on this day
* Friday 15 April
** -1 UX London is on this day
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:PaulDowney|Paul Downey (fn)]]
* [[User:SpikeUK|Chris Foote]]
* [[User:AndyHume|Andy Hume]]
* [[User:TobyInk|Toby Inkster]] (tentative)
* [[User:GlennJones|Glenn Jones (fn)]]
* [[User:ntoll|Nicholas Tollervey]] (tentative)
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

Main Page

2011-02-16T17:54:04Z

Adactio: /* Specifications */ reverting spam

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|پارسی (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

h2vx

2010-09-08T15:23:41Z

Adactio: Reverted edits by TStone (Talk) to last version by Tantek

<entry-title>H2VX</entry-title>
__TOC__
<dfn>[http://h2vx.com H2VX]</dfn> is a production deployment of the [[X2V]] hCard and hCalendar conversion transforms.

It converts [[hCard]] contacts and [[hCalendar]] events on web pages to .vcf and .ics respectively for use in desktop and other client software applications.

== documentation ==
To convert hCards to vCards, go http://h2vx.com/vcf/ and enter the URL to the hCards.

To convert hCalendar to iCalendar, go http://h2vx.com/ics/ and enter the URL to the hCalendar events.

=== URLs ===
Links to H2VX.com to convert a URL (like <nowiki>http://microformats.org/wiki/events</nowiki> ) can be constructed as follows:

You may omit the leading "http://" from the URL to be converted for a briefer more readable URL:

;download vCards from hCards
:<kbd><nowiki>http://h2vx.com/vcf/URL</nowiki></kbd>
:e.g. <kbd><nowiki>http://h2vx.com/vcf/microformats.org/wiki/events</nowiki></kbd>
;download iCalendar from hCalendar
:<kbd><nowiki>http://h2vx.com/ics/URL</nowiki></kbd>
:e.g. <kbd><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></kbd>
;subscribe to hCalendar from hCalendar
:<kbd><nowiki>webcal://h2vx.com/ics/URL</nowiki></kbd>
:e.g. <kbd><nowiki>webcal://h2vx.com/ics/microformats.org/wiki/events</nowiki></kbd>
:<kbd><nowiki>http://h2vx.com/ics/sub/URL</nowiki></kbd> for systems which don't support auto-linking of webcal: URLs, e.g. MediaWiki, Twitter.
:e.g. <kbd><nowiki>http://h2vx.com/ics/sub/microformats.org/wiki/events</nowiki></kbd>

=== user agent strings ===
H2VX uses two user agent strings, when retrieving hCards and hCalendars respectively:
* <samp><nowiki>H2VX contacts proxy (http://h2vx.com/vcf/)</nowiki></samp>
* <samp><nowiki>H2VX events proxy (http://h2vx.com/ics/)</nowiki></samp>
You may see occurrences of these in your web server logs when users of H2VX convert hCards and hCalendar events on your pages.

=== built ===
H2VX is built and maintained by [[User:Tantek|Tantek]] with:
* [[X2V]] XSLTs by [[User:Brian|Brian Suda]]
* PHP get-contact.php get-cal.php originally written by Brian, updated/factored by Tantek with various improvements. [[to-do]]: open source these.
* PHP common.php (and Javascript common.js) by Tantek which incorporate CASSISv0 open source from http://cassisproject.com/
* XHTML1+CSS+JS front-end design/interface by Tantek (view source of h2vx.com in your browser for more).

== feedback ==
Have feedback on H2VX? Feel free to add to the top of this list and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-feedback]]

* It would be very useful to be able to POST or GET an HTML snippet to request a conversion. I have created a Javascript button that will easily rip out the code and send it to H2VX.com: http://1daylater.com/H2VX_snippets.html useful for dynamic or password protected webpages
* As a Web page author I find the H2XV site a bit awkward to use -- it's difficult to find the URLs to use in my Web page. As an end-user it fine to have the H2VX bookmarklets in my toolbar, but as a page author I can't be sure everyone has the bookmarklets or Operator installed. [[User:Bob Jonkman|Bob Jonkman]] 00:56, 10 November 2009 (UTC)
* "Also, a short 'about' page would be worthwhile IMO, especially for adding to the homepage." - Norm on microformats-discuss.
* ...

== issues ==
Found a problem with H2VX? Please note it here at the top of this list (consider grouping it under an existing subhead or introduce a new subhead if necessary) and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-issues]]

=== .vcf not formed properly ===

When opening the resultant .vcf files with Outlook, all non-standard characters are not shown correctly, due to the fact that the returned file is not encoded as UTF-8 without the BOM. Thus, these files are useless for use with Outlook - one of the most used e-mail clients.

Can we get a UTF-8 file returned without the BOM?

=== Missing data/Wrong encoding ===

* We'd like to use your service for the new version of our location list ([http://www.freewave.at/en/ Free WiFi Hotspots in Austria]) but ran into problems:
** After importing the vCard, the Mac OS X Address book showed only the phone number (not as work), the URL, zip code and city. No name and no street.
** The vCard itself is encoded in ISO-8859-1, although having “CHARSET=utf-8” instructions. The source is also encoded in UTF-8.
** Here's the HTML code, we've been using:
<source lang=html4strict>
<div class="vcard">
<h2 class="fn org"><img class="photo" src="http://static.freewave.at/logos/testa_rossa_caffe_150.gif" alt="Testa Rossa Caffèbar Logo" />Testa Rossa Caffèbar</h2>
<div class="adr work">Mahlerstraße 4 
1010 Wien 
Österreich</div>
<div>+43 699 161 616 61 
<a class="url work" href="http://www.testarossawien.at/">http://www.testarossawien.at/</a> 
<a class="email work" href="mailto:"></a></div>
<div class="geo">48.20275,16.37079</div>
</div>
</source>

Thanks! --[[User:Vividvisions|Vividvisions]] 17:25, 4 May 2010 (UTC)

I got the same type of problem with non ASCII content. Don't know which part is responsible, though. --[[User:jlgeering|Jean-Luc Geering]] 2010-05-10

=== HTML5 support ===
* <code><meta charset=utf-8></code> isn't recognized so the output is double encoded. [[User:Greut|Greut]] 11:12, 4 January 2010 (UTC)
* new HTML5 elements (such as header, footer, section) are not supported (this is because they are stripped out by PHP Tidy and thus ignored). [[User:Tantek|Tantek]] 16:13, 19 January 2010 (UTC) possible solutions:
** UPDATE: new HTML5 elements and time datetime preliminary support added to http://dev.h2vx.com/ - try it out - give feedback!

<div class="discussion">
'''Please give feedback on the http://dev.h2vx.com/ HTML5 support here:'''
* ...
* ...
</div>

Previously:
* Possible options
** 1. Use a proper PHP html5lib (being coded by the HTML5 community, but not available/functional yet AFAIK) - still might do this long term.
** 2. Add a flag to the H2VX processing URL which says "I'm a crazy XML person and my markup is 100% well formed XML, please don't tidy, please break and fail to process if it's not well formed".
** in either case, new special HTML5 elements (like time) will require an update to [[X2V]] to know to properly handle/parse new semantic attributes (like datetime).

=== mouse events ===
* The "what are microformats?" style descriptions only appear on mouse-over of the trigger terms (those with class="term"). It does not appear at all when keyboard navigation is used, making it somewhat inaccessible. The problem here is that the trigger elements are the ones that should receive focus, but not being links they are not in the tabbing order so do not, hence the helper text never appears for keyboard users. [[User:Norm|Norm]] 10:39, 6 November 2009 (UTC)
** Quick fix: remove '''visibility:hidden''' from '''.term .info'''. [[User:Andr3|Andr3]]

=== page semantics ===
* should be made into 's for semantic reasons. ;) [[User:Andr3|Andr3]]
** Note that the <code></code> element is used deliberately for "instance" of a term - this is an [[HTML5]] semantic, and is more accurate in this instance than "em"phasis. — [[User:Tantek|Tantek]] 18:29, 11 November 2009 (UTC)

=== not possible to use dtstart with timezone in abbr title ===
* Adding a timezone to dtstart using abbr pattern leads to The Shining-style debug output repeating “Object is a string”. I tried adding a time with timezone via the value class pattern, and while the vcard downloads the time is incorrect ~~[[User:Oli|Oli]] 00:53 15 February 2010 (+09:00)
** Oli, could you provide a URL to a live example/test case that you were using so we can test with it to try to see exactly what is going on? Thanks! [[User:Tantek|Tantek]] 17:35, 15 February 2010 (UTC)

=== resolved ===
Resolved issues are moved to this section. If this grows too big we can move it to [[h2vx-issues-resolved]]
* ...

* 2009-11-11 We were using the Technorati hosted service. Surprised to see it redirected to H2XV, took a minute to realize what was going on. Thanks for picking up the service! Both the hosting provider and the new user agent are blocked by default on our side to prevent scraping. To be more transparent, maybe you could change the UA similar to the old one: from <nowiki>"Technorati contacts proxy (http://technorati.com/contacts/)"</nowiki> to <nowiki>"H2VX contacts proxy (http://h2vx.com/vcf/)"</nowiki> [[User:DineMonkey|DineMonkey]] 15:47, 11 November 2009 (UTC)
** I've updated the user agent strings per your recommendation and documented them above as well. [[User:Tantek|Tantek]] 18:29, 11 November 2009 (UTC)
*** <nowiki>H2VX contacts proxy (http://h2vx.com/vcf/)</nowiki>
*** <nowiki>H2VX events proxy (http://h2vx.com/ics/)</nowiki>

=== closed ===
Once a resolved issue has no further actions (and ideally is verified by the issue reporter), it can be closed and moved to this section. If this grows too big we can move it to [[h2vx-issues-closed]]
* 2009-11-04 It would be good to have the option to pass "referer" instead of a URL. [[User:Adactio|Adactio]] 10:47, 4 November 2009 (UTC)
** http://h2vx.com/vcf/referrer and http://h2vx.com/ics/referrer are now up and running. Example of /vcf/referrer is live on http://tantek.com/ and the alternate spelling /vcf/referer is used live on http://clearleft.com/ - as such, closing this issue. [[User:Tantek|Tantek]] 20:25, 5 November 2009 (UTC)
* ...

== see also ==
* [[X2V]]
* [[hCard]]
* [[hCalendar]]
* [[implementations]]

value-class-date-time-tests

2010-03-15T21:57:22Z

Adactio: /* updating results for Firefox 3.6*/

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.7 || [[Operator]] 0.9.5
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || {{testfail|fail}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || {{testpass|pass}} || {{testpass|pass**}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|}

;Notes

: * [[User:Tantek|Tantek Çelik]] has found that these tests pass in Firefox 3.5.8 with Operator 0.9.5 by using the "Debug" option in Operator and looking at both the "Structure" and "vCard/iCalendar" tabs and verifying that both agree with expected output for the test. However, [[User:Adactio|Jeremy Keith]] has found that these tests only partially pass in Firefox 3.6 with Operator 0.9.5. The date was correctly parsed, but not the time. Call for test verification: to anyone else: please run these tests in Firefox 3.5.8 or Firefox 3.6 with Operator 0.9.5 and report back and explicitly note any specific problems you see. 
: ** [[User:Tantek|Tantek Çelik]] has found that these tests pass in Firefox 3.5.8 with Operator 0.9.5 by using the "Debug" option in Operator and looking at both the "Structure" and "vCard/iCalendar" tabs and verifying that both agree with expected output for the test. However, [[User:Adactio|Jeremy Keith]] has found that these tests FAIL in Firefox 3.6 with Operator 0.9.5 The timezone field is interpreted as the end date.

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

value-class-date-time-tests

2010-03-15T21:48:09Z

Adactio: /* results */

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.7 || [[Operator]] 0.9.5
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || {{testpass|pass}} || {{testpass|pass*}}
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || {{testfail|fail}} || {{testpass|pass**}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || {{testpass|pass}} || {{testpass|pass**}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || {{testpass|pass}} || {{testpass|pass**}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || {{testpass|pass}} || {{testpass|pass**}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || {{testpass|pass}} || {{testpass|pass**}}
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || {{testpass|pass}} || {{testpass|pass*}}
|}

;Notes

: * [[User:Tantek|Tantek Çelik]] has found that these tests pass in Firefox 3.5.8 with Operator 0.9.5 by using the "Debug" option in Operator and looking at both the "Structure" and "vCard/iCalendar" tabs and verifying that both agree with expected output for the test. However, [[User:Adactio|Jeremy Keith]] has found that these tests only partially pass in Firefox 3.6 with Operator 0.9.5. The date was correctly parsed, but not the time. Call for test verification: to anyone else: please run these tests in Firefox 3.5.8 or Firefox 3.6 with Operator 0.9.5 and report back and explicitly note any specific problems you see. 
: ** [[User:Tantek|Tantek Çelik]] has found that these tests pass in Firefox 3.5.8 with Operator 0.9.5 by using the "Debug" option in Operator and looking at both the "Structure" and "vCard/iCalendar" tabs and verifying that both agree with expected output for the test. However, [[User:Adactio|Jeremy Keith]] has found that these tests FAIL in Firefox (version unknown - Jeremy, please fill in) with Operator 0.9.5 (Jeremy, please verify you were using this version and delete this note). Jeremy, please document how you ran the tests and what specifically was wrong in the expected result(s) that led you to mark these results as testfail.

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

value-class-date-time-tests

2010-01-08T11:42:50Z

Adactio: /* updating Operator test results */

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.7 || [[Operator]] 0.9.5
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || {{testfail}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || {{testpass}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || {{testpass}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || {{testpass}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || {{testpass}} || {{testfail}}
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpartial}}
|}

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

value-class-date-time-tests

2010-01-07T19:36:11Z

Adactio: /* results: updating one result from pass to partial */

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.7 || [[Operator]] 0.9.5
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || {{testpass}} || {{testpartial}}
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || {{testfail}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|}

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

Template:testpartial

2010-01-07T19:35:23Z

Adactio: Template for third state of test results: partial support.

<div style="text-align:center;background:#ccc">partial</div>

h2vx

2009-11-04T10:47:44Z

Adactio: /* issues: requesting referer parsing */

<entry-title>H2VX</entry-title>

{{stub}}

<dfn>[http://h2vx.com H2VX]</dfn> is a production deployment of the [[X2V]] hCard and hCalendar conversion transforms.

It converts [[hCard]] contacts and [[hCalendar]] events on web pages to .vcf and .ics respectively for use in desktop and other client software applications.

== feedback ==
Have feedback on H2VX? Feel free to add to the top of this list and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-feedback]]
* ...

== issues ==
Found a problem with H2VX? Please note it here at the top of this list and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-issues]]
* It would be good to have the option to pass "referer" instead of a URL. [[User:Adactio|Adactio]] 10:47, 4 November 2009 (UTC)
* ...

== see also ==
* [[X2V]]
* [[hCard]]
* [[hCalendar]]
* [[implementations]]

dtend-issue

2009-08-27T11:38:50Z

Adactio: /* +1 for inclusive end dates */

<entry-title>dtend-issue</entry-title>

An [[hCalendar]] issue.

== summary ==

The [[hCalendar]] dtend property as of hCalendar 1.0 requires that end *dates* be marked up as occuring a whole day after what people typically consider the end date of an event.

E.g. if a conference starts on 2010 March 12th and ends 2010 March 16th, then the dtend must be marked up with the value of "2010-03-17" - seemingly a whole day after the end of the conference. hCalendar suggests obscuring this disparity between the human visible end date and the machine specified date using the <code><nowiki><abbr></nowiki></code> tag:

<source lang=html4strict>
<div class="vevent">
a conference
starts on 2010-03-12, and
ends on <abbr class="dtend" title="2010-03-17">2010-03-16</abbr>.
</div>
</source>

This is due to hCalendar being originally specified with the same semantics as iCalendar, which places that requirement on the DTEND property of the VEVENT object.

== problems ==
This is problematic for several reasons:
* '''Appears inconsistent.''' It is odd that the value specified for machine consumption is different than the value specified for human consumption - regardless of format/syntax - and appears inconsistent to anyone who sees the tooltip, or views and copy/pastes the source. It looks like a bug or mistake, and in fact has been errantly "corrected" as such (e.g. even in the hCalendar spec itself).
* '''Unintuitive for authoring.''' When authors are writing up the end date for an event, they write up what a human expects to see - the last day of the event. It is an unintuitive leap to think to specify +1 day for machine consumption, and an additional cognitive load (in order to get it right).
* '''Semantic abuse of abbr.''' An abbr's title attribute provides an expansion for the inner text. In no way is a +1 date an expansion of a date, it appears more like a completely different value.
* '''Required DRY violation.''' While the <code>dtstart</code> in the above example is specified only once, readable to both humans and machines, the dtend must be specified twice, once for humans, and once for machines, thus requiring a particularly bad DRY (Don't Repeat Yourself) violation, that of requiring data be specified twice, but slightly different in one instance than another, thus increasing the chances of duplication based errors even more (since verifiability is more difficult).
** '''Prevents use of simple markup''' As a result of the forced DRY violation, it is not possible to use simple markup like <code><nowiki>2010-03-16</nowiki></code> because while a human reads that as an event that ends on the 16th, an hCalendar 1.0 processor will read that as an event that ended the day before, on the 15th.

== possible solutions ==
As noted in the [[hcalendar-issues#issues_2007|issue description]] on the hCalendar issues page, there are at least a couple of possible solutions.

<div class="discussion">
* '''new hCalendar 1.0.1 property for end dates'''. As noted in the first resolution of the issue, we could introduce a new property, '''dtlast''' (described more in [[hcalendar-brainstorming#dtlast|hCalendar brainstorming: dtlast]]) which authors would use to specify the ''last'' day of an event, instead of dtend.
** Advantage: Maintains iCalendar conceptual compatibility for DTEND values.
** Advantage: Compatibility with existing hCalendar 1.0 content that just happened to get the end date +1 distinction right.
** ... any other advantages?
** Disadvantage: Increased vocabulary. '''dtlast''' is a new term, even if it is not new functionality. Essentially this puts additional burden on authors.
** Disadvantage: Increased complexity/confusion. When to use dtend vs. dtlast? hCalendar authors would now have to remember, use dtend for end *times* and dtlast for end *dates*. More explanation of the additional burden on authors.
** ... any other disadvantages?
** Opinions:
*** -1 despite originally proposing this solution, I now think an additional term, and rule for when to use the new term vs. the old term will actually make this problem worse and more confusing to web authors. [[User:Tantek|Tantek]]
*** ... please add your +1/0/-1 opinion here and sign with three tildas (<nowiki>~~~</nowiki>)
* '''redefine hCalendar 1.0.1 dtend to be inclusive for whole dates'''. This is a bit more radical.
** Advantage: Zero impact on vocabulary.
** Advantage: No increase to hCalendar authoring complexity.
** Advantage: Will reflect dominant use of dtend in examples in the wild (more research and citations needed to back this up!). In other words, authors have ALREADY been using dtend assuming it works this way (inclusive end dates), and will actually be surprised to find out that it doesn't. Making this change to DTEND semantics may actually reflect hCalendar publishing reality more than keeping the precise iCalendar DTEND semantic. Examples of inclusive dtend usage in the wild:
*** http://barcamp.org/ - BarCamp wiki, dates for BarCamps
*** [[event|microformats.org/wiki/events/]] - several multi-day event listings, as recently as Glenn Jones (who himself is a ''very'' knowledgable and prolific microformats developer) [[events/2010-03-12-sxsw|event page for SXSW 2010]] use inclusive DTENDs (notably, using a span element that does NOT duplicate content).
*** draft of Emily Lewis' book Microformats Made Simple, uses dtend for inclusive end dates.
*** ... more instances of existing use of DTEND for *inclusive* end dates.
** Advantage: Some number of implementations treat DTEND dates as *inclusive* (technically these are violating the current hCalendar spec, but they may be doing so deliberately to reflect actual hCalendar publishing practices). Implementations
*** Google's Rich Snippet validator. The [http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fmicroformats.org%2Fwiki%2Fevents Rich Snippet validator on microformats.org/wiki/events] shows the SXSW event as ending on 2010-03-16, consistent with the published intent.
*** ... more implementations that treat hCalendar dtend dates as inclusive
** ... any other advantages?
** Disadvantage: Redefines DTEND to be *slightly* different from how it is defined in iCalendar. This may lead to errors on the part of developers.
*** Mitigation: it may be possible to mitigate this disadvantage by providing ''both'' very precise hCalendar to iCalendar processor conformance requirements, and sufficient test cases for hCalendar to iCalendar processors for them to get this correct in their code.
** Disadvantage: breaking some amount of existing hCalendar content on the web (research needed to determine the extent of the problem)
*** Workarounds: Based on aforementioned research, workarounds may be possible, e.g. heuristics for when abbr is used similar to the example at the top of the page, to detect "off by one" cases and accommodate accordingly). Make it an explicit error for the human visible date to be different than the machine parsed date, and state specific error handling rules for hCalendar processors that "repair" this problem.
** ... any other disadvantages?
** Opinions:
*** +1 Based on the fact that this problem just hasn't gone away, and that people (smart knowledgable people!) continue to treat "dtend" end dates *inclusively*, I now think it makes more sense (and is more practical) to change the spec to be consistent with the dominant expectation of web authors, rather than continue attempting to change the expectations of web authors to be consistent with the spec. I think this is the simplest, most effective, and least risky option. [[User:Tantek|Tantek]]
*** +1 This appears logical and intuitive. We are effectively saying that end dates such as <code>DTEND</code> should parse to <code>YYYY-MM-DDT24:00:00</code>, and not <code>YYYY-MM-DDT00:00:00</code>. Seems simple, and entirely logical from a publishing stand —[[User:BenWard|BenWard]] 08:18, 27 August 2009 (UTC)
*** +1 The spec should reflect the intuitive publishing behaviour (inclusive end dates). Humans first. —[[User:Adactio|Jeremy Keith]]
*** ... please add your +1/0/-1 opinion here and sign with three tildas (<nowiki>~~~</nowiki>)
* ... other possible solutions?
</div>

== origins ==
This issue was raised to me (Tantek) in person pretty much since the first time I gave such an example back in 2004, was something I had to explicitly cover and point out in nearly every microformats [[presentation]] I gave, was eventually pointed out on the microformats discuss mailing list (citation needed), and eventually explicitly documented as an issue on the wiki [[hcalendar-issues]] page by Andy Mabbett on 2007-01-20.

== see also ==
* [[hCalendar]]
* [[hcalendar-issues]]
* [[iCalendar]]

rel-enclosure

2009-08-04T10:26:04Z

Adactio: Adding an "Examples in the wild" section.

<entry-title>rel="enclosure"</entry-title>
{{DraftSpecification}}

rel-enclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.
__TOC__
== Draft Specification 2005-06-21 ==
=== Author ===
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==

relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:

<pre><nowiki>
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a>
</nowiki></pre>

the author indicates that the movie should be downloaded.

== Multiple Enclosures ==
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.

'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?

'''Response:''' rel="alternate" is defined in the HTML spec:

<blockquote>Designates substitute versions for the document in which the link occurs.</blockquote>

In the case of enclosure links "alternate" is not suited, because the media file is not a substitute version of the document in which the link occurs - it is a substitute version of another link on the document in which the link occurs.

'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://search.yahoo.com/mrss MRSS]

===reply===
*"In the case of enclosure links "alternate" is not suited, because the media file is not a substitute version of the document in which the link occurs "
**That's not necessarily the case; the linked file may be an audio reading of the text on the page, for instance. [[User:AndyMabbett|Andy Mabbett]] 02:37, 5 Oct 2007 (PDT)

== 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="enclosure"> enclosure </dt>
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

==Examples in the Wild==
This section is '''informative'''.

The following sites have implemented rel-enclosure, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with rel-enclosure, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.
* [http://huffduffer.com/ Huffduffer] uses rel-enclosure on links to audio files marked "download".

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://www.feedburner.com FeedBurner]: the [http://forums.feedburner.com/viewtopic.php?t=20 SmartCast] service looks for the rel="enclosure" microformat and converts it to an enclosure in the feed.
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates Javascript to launch a pop-up window with the video embedded. (Also available at [http://embedthevideo.com/ embedthevideo.com])

== References ==
=== Normative References ===
* [http://gmpg.org/xmdp/ XMDP]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc4287.txt The Atom Syndication Format]:
** 4.2.7.2 The "rel" Attribute
4. The value "enclosure" signifies that the IRI in the value of the
href attribute identifies a related resource which is potentially
large in size and might require special handling. For atom:link
elements with rel="enclosure", the length attribute SHOULD be
provided.

==See also==

{{rel-related-pages}}

[[Category:Draft Specifications]]
[[Category:rel-enclosure]]

existing-rel-values

2009-08-04T10:07:44Z

Adactio: /* Adding rel-shortlink to brainstorming */

<h1> existing rel values </h1>
{{TOC-right}}

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4 link type] and [http://www.w3.org/TR/grddl/ GRDDL] specs.
* [[xfn]] and other [[microformats]]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| [[rel-acquaintance|acquaintance]] || the person represented by the current document considers the person represented by the referenced document to be an acquaintance || [[XFN]]

|-
| [[rel-alternate|alternate]] || Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-appendix|appendix]]|| Refers to a document serving as an appendix in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-bookmark|bookmark]] || Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-chapter|chapter]] || Refers to a document serving as a chapter in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-child|child]] || the referenced person is a child of the person represented by the current document|| [[XFN]]

|-
| [[rel-colleague|colleague]] || the referenced person is a colleague of the person represented by the current document|| [[XFN]]

|-
| [[rel-contact|contact]] || the person represented by the current document considers the person represented by the referenced document to be a contact || [[XFN]]

|-
| [[rel-contents|contents]] || Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents"). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-copyright|copyright]] || Refers to a copyright statement for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-co-resident|co-resident]] || the referenced person lives in the same residence as the person represented by the current document|| [[XFN]]

|-
| [[rel-co-worker|co-worker]] || the referenced person is a co-worker of the person represented by the current document|| [[XFN]]

|-
| [[rel-crush|crush]] || this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)|| [[XFN]]

|-
| [[rel-date|date]] || this person considers the referenced person to be a date (i.e. is dating the referenced person)|| [[XFN]]

|-
| [[rel-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]

|-
| [[rel-glossary|glossary]]|| Refers to a document providing a glossary of terms that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-help|help]] || Refers to a document offering help (more information, links to other sources information, etc.) || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-index|index]] || Refers to a document providing an index for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-kin|kin]] || the referenced person is part of the extended family of the person represented by the current document|| [[XFN]]

|-
| [[rel-license|license]] || …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page. || [[rel-license]]

|-
| [[rel-me|me]] || the referenced document represents the same person as does the current document || [[XFN]]

|-
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]

|-
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]

|-
| [[rel-neighbor|neighbor]] || the referenced person lives nearby the person represented by the current document || [[XFN]]

|-
| [[rel-next|next]] || Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-nofollow|nofollow]] || indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). || [[rel-nofollow]]

|-
| [[rel-parent|parent]] || the referenced person is a parent of the person represented by the current document|| [[XFN]]

|-
| [[rel-prev|prev]]|| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous". || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-previous|previous]] || Synonym of <code>prev</code> || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-section|section]] || Refers to a document serving as a section in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sibling|sibling]] || the referenced person is a sibling of the person represented by the current document|| [[XFN]]

|-
| [[rel-spouse|spouse]] || the referenced person is a spouse of the person represented by the current document|| [[XFN]]

|-
| [[rel-start|start]] || Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-stylesheet|stylesheet]] || a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-subsection|subsection]] || Refers to a document serving as a subsection in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]

|-
|[[rel-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]

|-
|[[rel-toc|toc]] || Synonym of <code>contents</code> (from "Table Of Contents") || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-transformation|transformation]] || Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]] || [http://www.w3.org/TR/grddl/#transformation GRDDL spec]

|-
|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

{| border="1"
|+
! rel value !! summary !! brainstormed in

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-product|product]] || … || [[product-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||…||unknown || DevMo

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || Google/Microsoft/Yahoo!

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-details|details]] || … || (seen on w3c.org news log in a "read more" permalink) || …

|-
| [[rel-EditURI|EditURI]] || … || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || …

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || … || HTML5

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-lightbox|lightbox]] || … || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sidebar |sidebar ]] || Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). || || HTML5

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || …|| HTML5

|-
| [[rel-user|user]] || … || … || WCLR

|-
| [[rel-via|via]] || … || … || WCLR

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research why such values were omitted from latter specifications before using them. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

In general, you {{should not}} use any dropped values.

In addition, if any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) - has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped
|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown
|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown
|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown
|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown
|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown
|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown
|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown
|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown
|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown
|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown
|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown
|-
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown
|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown
|-
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown
|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown
|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown
|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown
|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown
|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown
|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown
|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown
|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown
|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||HTML3||unknown, but proposed for re-introduction in HTML5
|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown
|-
|}

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML4 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.

== tools ==
See [[implementations]].

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-class-names]]

google-rich-snippets-examples

2009-05-19T17:17:11Z

Adactio: /* removing a superfluous span from Google's example */

== intro ==
On 2009-05-12, Google launched a "rich snippets" feature in [[google-search|their search engine]] which shows extra information in their search results based on information indexed from [[hCard]], [[hReview]], [[hreview-aggregate|hReview aggregate]], and [[hProduct]]. As part of that launch Google documented their support with microformats markup examples. This page documents those examples with corrections and improvements (in the hopes that Google will incorporate the fixes).

== Reviews ==
=== Reviews Example Microformat ===
==== Google review example 2009-05-12 ====
Google example on 2009-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146645

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hReview">

L'Amourita Pizza

3.5
Ulysses Grant</div>
2009-01-06
"Delicious, tasty pizza in Eastlake."
</div>
</source>
</div>

==== review example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hreview">

L'Amourita Pizza

3.5
Ulysses Grant
2009-01-06
"Delicious, tasty pizza in Eastlake."
</div>
</source>
</div>

Common mistakes noted:
* non-wellformed (invalid) (X)HTML. e.g. </div> used to close 
* root class name miscapitalized. e.g. wrong: hReview. right: hreview.

==== more information review example ====
This example demonstrates additional features of hReview with hCard that provides the same features and functionality as the second RDFa example, with visible data (e.g. <code>category</code> property, hyperlink for reviewer URL) rather than invisible metadata ('typeof' attribute, 'about' attribute).

"You can use the additional expressiveness of hReview with hCard to provide more information about the subject of your review."

<source lang=html4strict>


Komala Vilas
(Restaurant)


<a class="fn url" href="http://example.com/person/meenakshi_ammal">
Meenakshi Ammal
</a>

3.7
2005-04-01
Best south Indian vegetarian food in the bay area

</source>

=== Aggregated Review Example Microformats ===
==== Google review example 2008-05-12 ====
Google example on 2008-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146645

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hReview-aggregate">
<div class="item">
L'Amourita Pizza
</div>
<div class="rating">
4.4
</div>
1,313
</div>
</source>
</div>

==== aggregated review example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hreview-aggregate">
<div class="item">
L'Amourita Pizza
</div>
<div class="rating">
4.4
</div>
1313
</div>
</source>
</div>

Common mistakes noted:
* class name miscapitalized. e.g. wrong: hReview-aggregate. right: hreview-aggregate.
* numerical values should not include any locale-specific digit grouping (e.g. "," after thousands digit)

== People ==
=== People Example Microformat XFN ===
==== Google people example 2008-05-12 ====
Google example on 2008-05-12 from from http://google.com/support/webmasters/bin/answer.py?answer=146646

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<div class="fn">John Smith</div>
Smithy
http://www.example.com
ACME

Albuquerque

Engineer
<a href="http://darryl-blog.example.com/" rel="friend">Darryl</a>
</div>
</source>
<blockquote>
Note: We'll also accept class="friend". The friend property is imported from XFN.
</blockquote>
</div>

==== people example improved ====
No actual problems were found in the Google people example code from 2008-05-12, however a few improvements can be made:
* Hyperlink names for more typical and concise market. In practice, names of people are often hyperlinked to the pages that represent them.
* Links to a user's home page should also be hyperlinked with rel="me":

And the prose comment following the example is flawed however, as XFN only defines <code>rel</code> values, not <code>class</code> values, thus class="friend" is invalid and should not be explicitly supported.

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<a class="fn url" rel="me" href="http://john-smith.example.com/">
John Smith
</a>
"Smithy"

ACME

Albuquerque

Engineer
<a href="http://darryl-blog.example.com/" rel="friend">Darryl</a>
</div>
</source>
<blockquote>
Note: The rel values of "me" and "friend" are both from [[XFN]].
</blockquote>
</div>

==== more information people example ====
For the structured data geeks out there, you can also use hCard's ability to express additional structure using nesting.

<source lang=html4strict>
<div class="vcard">
<a class="fn url" rel="me" href="http://john-smith.example.com/">
John Smith
</a>
Smithy

<a class="fn org url" href="http://en.wikipedia.org/wiki/Acme_Corporation">
ACME
</a>


Albuquerque

Engineer

<a class="fn url" href="http://darryl-blog.example.com/" rel="friend">
Darryl
</a>

</div>
</source>

== Products ==
=== Products Example Microformats ===
==== Google product example 2009-05-12 ====
Google example on 2009-05-12 from
from http://google.com/support/webmasters/bin/answer.py?answer=146750

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hProduct">
ACME
Heavy objects
Large all-purpose anvil
If you need an object to drop from a height, the classic
A23859 anvil from ACME is the way to go.
http://anvil.example.com
</div>
</source>
</div>

==== product example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hproduct">
ACME
Heavy objects
Large all-purpose anvil

If you need an object to drop from a height, the classic
A23859 anvil from ACME is the way to go.
http://anvil.example.com
</div>
</source>
</div>

Common mistakes noted:
* root class name miscapitalized. e.g. wrong: hProduct. right: hproduct.

== Businesses and organizations ==
=== Business Example Microformats ===
==== Google business example 2009-05-12 ====
Google example on 2009-05-12 from
http://google.com/support/webmasters/bin/answer.py?answer=146861

<source lang=html4strict>
<div class="vcard">
L'Amourita Pizza
(206) 555-7242
<div class="adr">
2040 Any Street
Springfield
WA
98102
</div>
</div>
</source>

This example has no known problems.

== About microformats ==
=== Marking up data using microformats ===
==== Google hCard example 2009-05-12 ====
Google example on 2009-05-12 from
http://google.com/support/webmasters/bin/answer.py?answer=146897

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<img class="photo" src="www.example.com/bobsmith.jpg" />
Bob Smith
Senior editor at ACME Reviews

200 Main St 
Desertville, AZ
12345

</div>
</source>
</div>

==== hCard example corrected ====
<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<img class="photo" src="http://www.example.com/bobsmith.jpg" alt="Photo of Bob">
Bob Smith
Senior editor at ACME Reviews

200 Main St 
Desertville, AZ
12345

</div>
</source>
</div>
Common mistakes noted:
* misordered close tags (invalid) in (X)HTML. e.g. <code><nowiki>...</nowiki></code> instead of <code><nowiki>...</nowiki></code>
* unecessary empty paragraph element. e.g. <code><nowiki>...</nowiki></code> instead of simply <code><nowiki>...</nowiki></code>
* <code><img></code> tag missing <code>alt</code> attribute.
* mixed use of XHTML and HTML4 empty elements. e.g. using both <code><img ... /></code> and <code> </code>.
* Instead of using an extra <code>span</code> element to wrap <code>adr</code>, the class can simply be put on the containing paragraph element.

=== Nested microformats example ===
==== Google nested example 2009-05-12 ====
Google example on 2009-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146897

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hreview">
Blast 'Em Up Review
by 
by Bob Smith, Senior Editor
at ACME Reviews

This is a great game. I enjoyed it from the
opening battle to the final showdown with the evil aliens.
4.5
</div>
</source>
</div>

==== nested example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict style="background:EFE">
<div class="hreview">

Blast 'Em Up Review

by 
Bob Smith,
Senior Editor
at ACME Reviews

This is a great game. I enjoyed it from the
opening battle to the final showdown with the evil aliens.
4.5
</div>
</source>
</div>

Common mistakes noted:
* duplicated words. e.g. "by by"
* disallowed (X)HTML nesting, e.g. putting a <code></code> inside a <code></code>

== common mistakes ==
These mistakes were noted from the Google examples but have nearly all been seen in examples of documentation or markup on other sites as well. Some of these items should be incorporated into [[debugging-tools]] such as the [[Optimus]] microformats [[validator]]. This section could probably be moved to its own article. [[User:Tantek|Tantek]] 08:48, 19 May 2009 (UTC)

=== English mistakes ===
* '''duplicated words.''' e.g. "by by" or "the the", often across a line break or in two adjacent or parent/first-child elements.

=== HTML mistakes ===
* '''non-wellformed (invalid) (X)HTML.''' e.g. </div> used to close 
** caught by W3C Validator
* '''misordered close tags (invalid) in (X)HTML.''' e.g. <code><nowiki>...</nowiki></code> instead of <code><nowiki>...</nowiki></code>
** caught by W3C Validator
* '''disallowed (X)HTML nesting''', e.g. putting a <code></code> inside a <code></code>
** caught by W3C Validator
* '''<code><img></code> tag missing <code>alt</code> attribute.'''
** caught by W3C Validator
* '''mixed use of XHTML and HTML4 empty elements.''' e.g. using both <code><img ... /></code> and <code> </code>.
** might be caught by HTML validator - results depend on DOCTYPE used.
* '''unecessary empty paragraph element.''' e.g. <code><nowiki>...</nowiki></code> instead of simply <code><nowiki>...</nowiki></code>
** warning provided by HTML validator
* '''missing http in URL attribute value.''' e.g. <code>www.example.com</code> instead of <code>http://www.example.com</code>
** could be caught by an HTML validator that checked for unlikely relative URL starting with "www." with directory name ending in ".com".

=== microformats class name mistakes ===
* '''class name miscapitalized.''' e.g. wrong: hReview hReview-aggregate. right: hreview hreview-aggregate.
** microformats class names are always all lower case, (apparent) words separated with dash characters, e.g. "family-name", per Semantic XHTML naming principles.
** TODO Optimus: this is probably worth adding to Optimus - to check for mis-capitalized microformats root and property class names.

=== microformats property value mistakes ===
* '''integer values with punctuation.''' numerical values should not include any locale-specific digit grouping (e.g. "," after thousands digit)
** TODO Optimus: Optimus could also validate the values of numeric properties

== implied feedback on microformats ==
From analyzing the examples provided by Google, the following improvements could be made to microformats. These should be recorded additionally in [[hreview-issues]] + [[hreview-aggregate-issues]], resolved accordingly and incorporated into the specification pages.

* '''Even simpler is better.''' In the common case where the entirety of the "item" of an hReview (or hReview aggregate) is its "fn", then perhaps the "fn" subproperty markup could be omitted, e.g.:
** interpret <code><nowiki>L'Amourita Pizza</nowiki></code> as:
** <code><nowiki>L'Amourita Pizza</nowiki></code>
* '''Permit human friendlier values when possible.''' In some cases the type of a property is sufficiently constrained as to permit the use of punctuation that makes the values more human readable, better matching existing content. e.g. for the <code>count</code> property which is a whole number:
** interpret <code><nowiki>1,313</nowiki></code>
** or <code><nowiki>1.313</nowiki></code>
** as <code><nowiki>1313</nowiki></code>

== see also ==
* [[google-search]]
* [[search-engines]]
* [[implementations]]

google-rich-snippets-examples

2009-05-19T17:09:49Z

Adactio: /* adding org to the same element as fn */

== intro ==
On 2009-05-12, Google launched a "rich snippets" feature in [[google-search|their search engine]] which shows extra information in their search results based on information indexed from [[hCard]], [[hReview]], [[hreview-aggregate|hReview aggregate]], and [[hProduct]]. As part of that launch Google documented their support with microformats markup examples. This page documents those examples with corrections and improvements (in the hopes that Google will incorporate the fixes).

== Reviews ==
=== Reviews Example Microformat ===
==== Google review example 2009-05-12 ====
Google example on 2009-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146645

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hReview">

L'Amourita Pizza

3.5
Ulysses Grant</div>
2009-01-06
"Delicious, tasty pizza in Eastlake."
</div>
</source>
</div>

==== review example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hreview">

L'Amourita Pizza

3.5
Ulysses Grant
2009-01-06
"Delicious, tasty pizza in Eastlake."
</div>
</source>
</div>

Common mistakes noted:
* non-wellformed (invalid) (X)HTML. e.g. </div> used to close 
* root class name miscapitalized. e.g. wrong: hReview. right: hreview.

==== more information review example ====
This example demonstrates additional features of hReview with hCard that provides the same features and functionality as the second RDFa example, with visible data (e.g. <code>category</code> property, hyperlink for reviewer URL) rather than invisible metadata ('typeof' attribute, 'about' attribute).

"You can use the additional expressiveness of hReview with hCard to provide more information about the subject of your review."

<source lang=html4strict>


Komala Vilas
(Restaurant)


<a class="fn url" href="http://example.com/person/meenakshi_ammal">
Meenakshi Ammal
</a>

3.7
2005-04-01
Best south Indian vegetarian food in the bay area

</source>

=== Aggregated Review Example Microformats ===
==== Google review example 2008-05-12 ====
Google example on 2008-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146645

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hReview-aggregate">
<div class="item">
L'Amourita Pizza
</div>
<div class="rating">
4.4
</div>
1,313
</div>
</source>
</div>

==== aggregated review example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hreview-aggregate">
<div class="item">
L'Amourita Pizza
</div>
<div class="rating">
4.4
</div>
1313
</div>
</source>
</div>

Common mistakes noted:
* class name miscapitalized. e.g. wrong: hReview-aggregate. right: hreview-aggregate.
* numerical values should not include any locale-specific digit grouping (e.g. "," after thousands digit)

== People ==
=== People Example Microformat XFN ===
==== Google people example 2008-05-12 ====
Google example on 2008-05-12 from from http://google.com/support/webmasters/bin/answer.py?answer=146646

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<div class="fn">John Smith</div>
Smithy
http://www.example.com
ACME

Albuquerque

Engineer
<a href="http://darryl-blog.example.com/" rel="friend">Darryl</a>
</div>
</source>
<blockquote>
Note: We'll also accept class="friend". The friend property is imported from XFN.
</blockquote>
</div>

==== people example improved ====
No actual problems were found in the Google people example code from 2008-05-12, however a few improvements can be made:
* Hyperlink names for more typical and concise market. In practice, names of people are often hyperlinked to the pages that represent them.
* Links to a user's home page should also be hyperlinked with rel="me":

And the prose comment following the example is flawed however, as XFN only defines <code>rel</code> values, not <code>class</code> values, thus class="friend" is invalid and should not be explicitly supported.

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<a class="fn url" rel="me" href="http://john-smith.example.com/">
John Smith
</a>
"Smithy"

ACME

Albuquerque

Engineer
<a href="http://darryl-blog.example.com/" rel="friend">Darryl</a>
</div>
</source>
<blockquote>
Note: The rel values of "me" and "friend" are both from [[XFN]].
</blockquote>
</div>

==== more information people example ====
For the structured data geeks out there, you can also use hCard's ability to express additional structure using nesting.

<source lang=html4strict>
<div class="vcard">
<a class="fn url" rel="me" href="http://john-smith.example.com/">
John Smith
</a>
Smithy

<a class="fn org url" href="http://en.wikipedia.org/wiki/Acme_Corporation">
ACME
</a>


Albuquerque

Engineer

<a class="fn url" href="http://darryl-blog.example.com/" rel="friend">
Darryl
</a>

</div>
</source>

== Products ==
=== Products Example Microformats ===
==== Google product example 2009-05-12 ====
Google example on 2009-05-12 from
from http://google.com/support/webmasters/bin/answer.py?answer=146750

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hProduct">
ACME
Heavy objects
Large all-purpose anvil
If you need an object to drop from a height, the classic
A23859 anvil from ACME is the way to go.
http://anvil.example.com
</div>
</source>
</div>

==== product example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="hproduct">
ACME
Heavy objects
Large all-purpose anvil

If you need an object to drop from a height, the classic
A23859 anvil from ACME is the way to go.
http://anvil.example.com
</div>
</source>
</div>

Common mistakes noted:
* root class name miscapitalized. e.g. wrong: hProduct. right: hproduct.

== Businesses and organizations ==
=== Business Example Microformats ===
==== Google business example 2009-05-12 ====
Google example on 2009-05-12 from
http://google.com/support/webmasters/bin/answer.py?answer=146861

<source lang=html4strict>
<div class="vcard">
L'Amourita Pizza
(206) 555-7242
<div class="adr">
2040 Any Street
Springfield
WA
98102
</div>
</div>
</source>

This example has no known problems.

== About microformats ==
=== Marking up data using microformats ===
==== Google hCard example 2009-05-12 ====
Google example on 2009-05-12 from
http://google.com/support/webmasters/bin/answer.py?answer=146897

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<img class="photo" src="www.example.com/bobsmith.jpg" />
Bob Smith
Senior editor at ACME Reviews

200 Main St 
Desertville, AZ
12345

</div>
</source>
</div>

==== hCard example corrected ====
<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict>
<div class="vcard">
<img class="photo" src="http://www.example.com/bobsmith.jpg" alt="Photo of Bob">
Bob Smith
Senior editor at ACME Reviews

200 Main St 
Desertville, AZ
12345


</div>
</source>
</div>
Common mistakes noted:
* misordered close tags (invalid) in (X)HTML. e.g. <code><nowiki>...</nowiki></code> instead of <code><nowiki>...</nowiki></code>
* unecessary empty paragraph element. e.g. <code><nowiki>...</nowiki></code> instead of simply <code><nowiki>...</nowiki></code>
* <code><img></code> tag missing <code>alt</code> attribute.
* mixed use of XHTML and HTML4 empty elements. e.g. using both <code><img ... /></code> and <code> </code>.

=== Nested microformats example ===
==== Google nested example 2009-05-12 ====
Google example on 2009-05-12 from http://google.com/support/webmasters/bin/answer.py?answer=146897

<div style="border:2px dashed red;display:inline-block">
<source lang=html4strict>
<div class="hreview">
Blast 'Em Up Review
by 
by Bob Smith, Senior Editor
at ACME Reviews

This is a great game. I enjoyed it from the
opening battle to the final showdown with the evil aliens.
4.5
</div>
</source>
</div>

==== nested example corrected ====

<div style="border:2px solid lime;display:inline-block">
<source lang=html4strict style="background:EFE">
<div class="hreview">

Blast 'Em Up Review

by 
Bob Smith,
Senior Editor
at ACME Reviews

This is a great game. I enjoyed it from the
opening battle to the final showdown with the evil aliens.
4.5
</div>
</source>
</div>

Common mistakes noted:
* duplicated words. e.g. "by by"
* disallowed (X)HTML nesting, e.g. putting a <code></code> inside a <code></code>

== common mistakes ==
These mistakes were noted from the Google examples but have nearly all been seen in examples of documentation or markup on other sites as well. Some of these items should be incorporated into [[debugging-tools]] such as the [[Optimus]] microformats [[validator]]. This section could probably be moved to its own article. [[User:Tantek|Tantek]] 08:48, 19 May 2009 (UTC)

=== English mistakes ===
* '''duplicated words.''' e.g. "by by" or "the the", often across a line break or in two adjacent or parent/first-child elements.

=== HTML mistakes ===
* '''non-wellformed (invalid) (X)HTML.''' e.g. </div> used to close 
** caught by W3C Validator
* '''misordered close tags (invalid) in (X)HTML.''' e.g. <code><nowiki>...</nowiki></code> instead of <code><nowiki>...</nowiki></code>
** caught by W3C Validator
* '''disallowed (X)HTML nesting''', e.g. putting a <code></code> inside a <code></code>
** caught by W3C Validator
* '''<code><img></code> tag missing <code>alt</code> attribute.'''
** caught by W3C Validator
* '''mixed use of XHTML and HTML4 empty elements.''' e.g. using both <code><img ... /></code> and <code> </code>.
** might be caught by HTML validator - results depend on DOCTYPE used.
* '''unecessary empty paragraph element.''' e.g. <code><nowiki>...</nowiki></code> instead of simply <code><nowiki>...</nowiki></code>
** warning provided by HTML validator
* '''missing http in URL attribute value.''' e.g. <code>www.example.com</code> instead of <code>http://www.example.com</code>
** could be caught by an HTML validator that checked for unlikely relative URL starting with "www." with directory name ending in ".com".

=== microformats class name mistakes ===
* '''class name miscapitalized.''' e.g. wrong: hReview hReview-aggregate. right: hreview hreview-aggregate.
** microformats class names are always all lower case, (apparent) words separated with dash characters, e.g. "family-name", per Semantic XHTML naming principles.
** TODO Optimus: this is probably worth adding to Optimus - to check for mis-capitalized microformats root and property class names.

=== microformats property value mistakes ===
* '''integer values with punctuation.''' numerical values should not include any locale-specific digit grouping (e.g. "," after thousands digit)
** TODO Optimus: Optimus could also validate the values of numeric properties

== implied feedback on microformats ==
From analyzing the examples provided by Google, the following improvements could be made to microformats. These should be recorded additionally in [[hreview-issues]] + [[hreview-aggregate-issues]], resolved accordingly and incorporated into the specification pages.

* '''Even simpler is better.''' In the common case where the entirety of the "item" of an hReview (or hReview aggregate) is its "fn", then perhaps the "fn" subproperty markup could be omitted, e.g.:
** interpret <code><nowiki>L'Amourita Pizza</nowiki></code> as:
** <code><nowiki>L'Amourita Pizza</nowiki></code>
* '''Permit human friendlier values when possible.''' In some cases the type of a property is sufficiently constrained as to permit the use of punctuation that makes the values more human readable, better matching existing content. e.g. for the <code>count</code> property which is a whole number:
** interpret <code><nowiki>1,313</nowiki></code>
** or <code><nowiki>1.313</nowiki></code>
** as <code><nowiki>1313</nowiki></code>

== see also ==
* [[google-search]]
* [[search-engines]]
* [[implementations]]

existing-rel-values

2009-04-20T16:15:14Z

Adactio: /* brainstorming */ adding proposed accessibility value

<h1> existing rel values </h1>
{{TOC-right}}

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4 link type] and [http://www.w3.org/TR/grddl/ GRDDL] specs.
* [[xfn]] and other [[microformats]]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| [[rel-acquaintance|acquaintance]] || the person represented by the current document considers the person represented by the referenced document to be an acquaintance || [[XFN]]

|-
| [[rel-alternate|alternate]] || Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-appendix|appendix]]|| Refers to a document serving as an appendix in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-bookmark|bookmark]] || Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-chapter|chapter]] || Refers to a document serving as a chapter in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-child|child]] || the referenced person is a child of the person represented by the current document|| [[XFN]]

|-
| [[rel-colleague|colleague]] || the referenced person is a colleague of the person represented by the current document|| [[XFN]]

|-
| [[rel-contact|contact]] || the person represented by the current document considers the person represented by the referenced document to be a contact || [[XFN]]

|-
| [[rel-contents|contents]] || Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents"). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-copyright|copyright]] || Refers to a copyright statement for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-co-resident|co-resident]] || the referenced person lives in the same residence as the person represented by the current document|| [[XFN]]

|-
| [[rel-co-worker|co-worker]] || the referenced person is a co-worker of the person represented by the current document|| [[XFN]]

|-
| [[rel-crush|crush]] || this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)|| [[XFN]]

|-
| [[rel-date|date]] || this person considers the referenced person to be a date (i.e. is dating the referenced person)|| [[XFN]]

|-
| [[rel-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]

|-
| [[rel-glossary|glossary]]|| Refers to a document providing a glossary of terms that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-help|help]] || Refers to a document offering help (more information, links to other sources information, etc.) || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-index|index]] || Refers to a document providing an index for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-kin|kin]] || the referenced person is part of the extended family of the person represented by the current document|| [[XFN]]

|-
| [[rel-license|license]] || …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page. || [[rel-license]]

|-
| [[rel-me|me]] || the referenced document represents the same person as does the current document || [[XFN]]

|-
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]

|-
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]

|-
| [[rel-neighbor|neighbor]] || the referenced person lives nearby the person represented by the current document || [[XFN]]

|-
| [[rel-next|next]] || Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-nofollow|nofollow]] || indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). || [[rel-nofollow]]

|-
| [[rel-parent|parent]] || the referenced person is a parent of the person represented by the current document|| [[XFN]]

|-
| [[rel-prev|prev]]|| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous". || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-previous|previous]] || Synonym of <code>prev</code> || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-section|section]] || Refers to a document serving as a section in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sibling|sibling]] || the referenced person is a sibling of the person represented by the current document|| [[XFN]]

|-
| [[rel-spouse|spouse]] || the referenced person is a spouse of the person represented by the current document|| [[XFN]]

|-
| [[rel-start|start]] || Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-stylesheet|stylesheet]] || a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-subsection|subsection]] || Refers to a document serving as a subsection in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]

|-
|[[rel-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]

|-
|[[rel-toc|toc]] || Synonym of <code>contents</code> (from "Table Of Contents") || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-transformation|transformation]] || Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]] || [http://www.w3.org/TR/grddl/#transformation GRDDL spec]

|-
|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

{| border="1"
|+
! rel value !! summary !! brainstormed in

|-
| [[rel-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post]

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-product|product]] || … || [[product-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||…||unknown || DevMo

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || Google/Microsoft/Yahoo!

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-details|details]] || … || (seen on w3c.org news log in a "read more" permalink) || …

|-
| [[rel-EditURI|EditURI]] || … || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || …

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || … || HTML5

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-lightbox|lightbox]] || … || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sidebar |sidebar ]] || Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). || || HTML5

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || …|| HTML5

|-
| [[rel-user|user]] || … || … || WCLR

|-
| [[rel-via|via]] || … || … || WCLR

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research why such values were omitted from latter specifications before using them. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

In general, you {{should not}} use any dropped values.

In addition, if any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) - has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped
|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown
|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown
|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown
|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown
|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown
|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown
|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown
|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown
|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown
|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown
|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown
|-
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown
|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown
|-
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown
|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown
|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown
|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown
|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown
|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown
|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown
|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown
|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown
|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||HTML3||unknown, but proposed for re-introduction in HTML5
|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown
|-
|}

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML4 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.

== tools ==
See [[implementations]].

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-class-names]]

hcard-xfn-supporting-friends-lists

2009-01-01T18:59:13Z

Adactio: /* Adding Huffduffer to the list of services with XFN rel="me" to multiple external sites */

<h1>hCard+XFN supporting friends lists</h1>
{{TOC-right}}

Welcome! If you have an account on any of the following services, you already have a list of your friends' hCards with your relationship to them in XFN which you can provide to other services to save time by either importing or subscribing to social network information so you can change it on one site, and have other sites automatically updated, rather than having to re-add/remove all your social network contacts multiple times every time you meet a new person, decide to unfriend someone etc.

== Services with hCard+XFN supporting friends lists ==
The following web sites support publishing hCard+XFN friends lists and are thus suitable for importing/subscribing to other sites that support hCard+XFN. Alphabetically sorted. Feel free to add sites with hCard+XFN supporting friends lists here. Please include a link to the site home page, and instructions for retrieving your the URL of your hCard+XFN supporting friends list on that site.

<div style="font-size:larger">
* http://identoo.com/images/icons/services/corkd.gif [http://www.corkd.com/ Cork'd] - login and copy the URL which should start with <nowiki>http://www.corkd.com/people/</nowiki>
* http://identoo.com/images/icons/services/dopplr.gif [http://dopplr.com Dopplr] - login and note that your user page has hCard and XFN for your contacts
* [http://gaia.com/ Gaia Community] - e.g. http://sphorbis.gaia.com/ - built by [http://www.zaadz.com Zaadz]
* [http://hi5.com/ Hi5] - e.g. http://lindner.hi5.com/
* http://pulse.plaxo.com/pulse/img/event_icons/LastFM.gif [http://www.last.fm/ Last FM] - login, click the "Friends" tab, and copy the URL which should look like: <nowiki>http://www.last.fm/user/[username]/friends/</nowiki>
* http://pulse.plaxo.com/pulse/img/event_icons/Magnolia.gif [http://ma.gnolia.com/ Ma.gnolia] - View your contacts page <nowiki>http://ma.gnolia.com/people/[username]/contacts</nowiki> . Note [[hcard-xfn-supporting-friends-lists-issues#Magnolia|issue(s)]].
* [http://www.nsyght.com/ Nsyght] - Visit your profile page and select "view all" on the friends component. Should look like this: <nowiki>http://www.nsyght.com/friends/[username]/</nowiki>, e.g. [http://nsyght.com/users/lisa sample profile].
* http://www.bkmks.com/icons/nytimes.com.gif [http://timespeople.nytimes.com/ NYTimes TimesPeople] - e.g. http://timespeople.nytimes.com/view/user/19390043/1/index.html
* [http://proofile.org Proofile] - Full support of hCard and XFN.
* [http://www.qmpeople.com/ qmpeople] - Uses hCard+XFN for profiles (<nowiki>http://www.qmpeople.com/users/[username]</nowiki> - e.g. [http://www.qmpeople.com/users/laserion laserion])
* [http://soup.io Soup] - On user profile if the "Friends list" element is displayed (on by default), else at <nowiki>/friends</nowiki>
* http://pulse.plaxo.com/pulse/img/event_icons/Twitter.gif [http://twitter.com/ Twitter] - login, click on "Your profile" at the top, and copy the URL
* http://lifestrea.ms/animated_favicon1.gif [http://lifestrea.ms/ lifestrea.ms] - you have one user profile per social group that you want to share information with: <nowiki>http://lifestrea.ms/user/[username]/</nowiki>. Examples: [http://lifestrea.ms/user/thomas.huhn/ public profile] or [http://lifestrea.ms/user/solution-media.thomas.huhn/ professional profile] of the same person.
</div>

== Services that import hCard+XFN supporting friends lists ==
The following web sites let you import hCard+XFN friends lists, e.g. from the above sites, and make use of both the XFN information and the hCards in the friends lists. Alphabetically sorted. Feel free to add sites supporting hCard+XFN import here. Please include a link to the site home page, and instructions for how to import friends on the site.

=== import ===
The following sites do one time imports of friends lists.

* http://identoo.com/images/icons/services/dopplr.gif [http://dopplr.com Dopplr] - as [http://blog.dopplr.com/index.php/2007/06/23/importing-your-social-network-from-other-sites/ announced] login and go to Dopplr's [http://www.dopplr.com/account/invitations_via/hcard hCard contact import page] to import.
* [http://t.heproject.com/ The Project] - Login with your OpenID and the site automatically tries to subscribe to your XFN friends list where it intersects with their userbase
** appears to fail logging in with a delegated OpenID, e.g. http://tantek.com/ - unable to verify import friends list support. [[User:Tantek|Tantek]] 10:03, 1 Feb 2008 (PST)

=== import and subscribe ===
The following sites support both importing and subscribing to friends lists.
* None currently.

=== delegation ===
The following sites support fully delegating your friends list to an external hCard+XFN friends list.
* None currently.

== Services with XFN supporting friends lists ==
These sites support XFN markup on friends lists. It is a superset of the sites that support XFN and hCard on friends lists.
<div style="font-size:larger">
* [http://3eep.com/ 3eep] - each user's friends are linked to with XFN is located at <nowiki>http://3eep.com/users/[username]</nowiki>
* http://identoo.com/images/icons/services/corkd.gif [http://www.corkd.com/ Cork'd] - login and copy the URL which should start with <nowiki>http://www.corkd.com/people/</nowiki>
* [http://couchsurfing.com CouchSurfing] profiles have XFN Friendly friends lists (e.g. [http://www.couchsurfing.com/people/guaka Guaka's]).
* http://identoo.com/images/icons/services/dopplr.gif [http://dopplr.com Dopplr] - login and note that your user page has hCard and XFN for your contacts
* http://flugpo.com/images/flugpo_icon.gif [http://flugpo.com Flugpo] - check your friends page linked from your profile.
* [http://gaia.com/ Gaia Community] - e.g. http://sphorbis.gaia.com/ - built by [http://www.zaadz.com Zaadz]
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo] - e.g. [http://identoo.com/dirk.olbertz sample profile]
* http://www.linkedin.com/img/pic/pic_in_17x17.gif [http://www.linkedin.com/ LinkedIn] - LinkedIn Connections use XFN and are marked up with rel="contact".
* http://pulse.plaxo.com/pulse/img/event_icons/LastFM.gif [http://www.last.fm/ Last FM] - login, click the "Friends" tab, and copy the URL which should look like: <nowiki>http://www.last.fm/user/[username]/friends/</nowiki>
* http://pulse.plaxo.com/pulse/img/event_icons/LiveJournal.gif [http://livejournal.com LiveJournal] (see [[implementations#LiveJournal|LiveJournal]] implementation entry) - login, click on the "Profile" link, and copy the URL which should start with <nowiki>http://USERNAME.livejournal.com/profile</nowiki> where USERNAME is your LJ username. E.g. [http://daveman692.livejournal.com/profile]. LiveJournal profiles have complete friends lists marked up in XFN.
* http://pulse.plaxo.com/pulse/img/event_icons/Magnolia.gif [http://ma.gnolia.com/ Ma.gnolia] - View your contacts page <nowiki>http://ma.gnolia.com/people/[username]/contacts</nowiki> . Note [[hcard-xfn-supporting-friends-lists-issues#Magnolia|issue(s)]].
* [http://meetlisten.com Meetlisten] - e.g. http://meetlisten.com/home/profile.php?id=1 and (e.g. [http://meetlisten.com/home/friends.php?id=6 MAKACOW-Brazil's]).
* [http://www.nsyght.com/ Nsyght] - Visit your profile page and select "view all" on the friends component. Should look like this: <nowiki>http://www.nsyght.com/friends/[username]/</nowiki>, e.g. [http://nsyght.com/users/lisa sample profile].
* http://identoo.com/images/icons/services/odeo.gif [http://odeo.com Odeo] — the "peep's" list of each user is marked up with XFN (rel="contact") e.g. http://odeo.com/profile/JeremyKeith . See [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html announcing blog post].
* http://pulse.plaxo.com/pulse/img/event_icons/Pownce.gif [http://pownce.com/ Pownce] - login, click on the "Home" link at the top, and copy the URL.
* [http://www.qmpeople.com/ qmpeople] - Uses XFN for public friendships - e.g. http://www.qmpeople.com/users/laserion
* [http://soup.io Soup] - On user profile if the "Friends list" element is displayed (on by default), else at <nowiki>/friends</nowiki>
* http://skateboardspot.info/image/icon/favicon.png [http://skateboardspot.info/ skateboardspot.info] - Log in and click on your username in the top right corner. The URL to your userpage (that you'll see now) is the URL to your hCard. Also 10 people of your contact list will be displayed there. To see all of them click the "... display all friends" link.
* http://pulse.plaxo.com/pulse/img/event_icons/Twitter.gif [http://twitter.com/ Twitter] - login, click on "Your profile" at the top, and copy the URL
* [http://videntity.org/ Videntity.org] - e.g. http://danda.videntity.org/ (see also [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity XFN support documentation]).
* [http://wordpress.com Wordpress.com] and any other blogs using Wordpress 1.5 or later have XFN supporting blog rolls (for friends and [[rel-me]]).
* http://lifestrea.ms/animated_favicon1.gif [http://lifestrea.ms/ lifestrea.ms] - one friends list per social group that you want to share information with: <nowiki>http://lifestrea.ms/user/[username]/</nowiki>. Examples: [http://lifestrea.ms/user/thomas.huhn/ public profile] or [http://lifestrea.ms/user/solution-media.thomas.huhn/ professional profile] of the same person.
</div>

== Services that import XFN supporting friends lists ==
The following web sites support importing your existing XFN supporting friends lists, e.g. from the above sites. Alphabetically sorted. Feel free to add sites supporting XFN import here. Please include a link to the site home page, and instructions for how to import friends on the site.
=== import ===
The following sites do one time imports of friends lists.
* None currently.
=== import and subscribe ===
The following sites support both importing and subscribing to friends lists.
* None currently.
=== delegation ===
The following sites support fully delegating your friends list to an external XFN friends list.
* None currently.

== Services with XFN rel="me" to multiple external sites ==
The following services have a UI for entering any number of websites/homepages/blogs and publish it as part of your profile, linking to it with [[rel-me]].
<div style="font-size:larger">
* http://pulse.plaxo.com/pulse/img/event_icons/Digg.gif [http://digg.com/ Digg] - e.g. http://digg.com/users/tantek
* [http://huffduffer.com/ Huffduffer] uses rel="me" on profile pages if a URL is provided and then uses the Google Social Graph API to find other profiles which are then also linked with rel="me" — e.g. http://huffduffer.com/clagnut
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo] - e.g. [http://identoo.com/dirk.olbertz sample profile]
* http://www.linkedin.com/img/pic/pic_in_17x17.gif [http://www.linkedin.com/ LinkedIn] - e.g. http://www.linkedin.com/in/steveganz rel="me" is applied to "My Website" and "My Blog" on your public profile.
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://plaxo.com/ Plaxo] - e.g. http://joseph.myplaxo.com/
* [http://proofile.org Proofile] - e.g. http://proofile.org/ueli.weiss
* http://pulse.plaxo.com/pulse/img/event_icons/Pownce.gif [http://pownce.com/ Pownce] - login, go to your profile, and copy the URL which should start with <nowiki>http://pownce.com/</nowiki>
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati] - e.g. http://technorati.com/people/technorati/tantek
* http://www.postreach.com/images/logo_typepad.gif [http://typepad.com/ TypePad] - e.g. http://www.markpasc.typepad.com/
* [http://videntity.org/ Videntity.org] - e.g. http://danda.videntity.org/
* http://openid.net/wp-content/uploads/vox.png [http://vox.com/ Vox] - e.g. http://anil.vox.com/
* [http://wordpress.com Wordpress.com] and any other blogs using Wordpress 1.5 or later have XFN supporting blog rolls (for friends and [[rel-me]]).
* http://lifestrea.ms/animated_favicon1.gif [http://lifestrea.ms/ lifestrea.ms] - supporting all your appearances on the web. Examples: [http://lifestrea.ms/user/thomas.huhn/ public profile] or [http://lifestrea.ms/user/solution-media.thomas.huhn/ professional profile] of the same person.
</div>

== Services with XFN rel="me" to one external site ==
The following services have a UI for entering one website/homepage/blog and publish it as part of your profile, linking to it with [[rel-me]].
<div style="font-size:larger">
* http://pulse.plaxo.com/pulse/img/event_icons/Digg.gif [http://digg.com/ Digg] - e.g. http://digg.com/users/tantek
* http://identoo.com/images/icons/services/dopplr.gif [http://dopplr.com Dopplr] - enter your website/homepage/blog into the "Website:" field on the [http://www.dopplr.com/account/profile Dopplr: Account Management] page, and enable your public profile and be sure the "Show homepage" checkbox is checked.
* [http://eventful.com/ Eventful] - login, click on your username, and copy that URL.
* http://pulse.plaxo.com/pulse/img/event_icons/Flickr.gif [http://flickr.com/ Flickr] - login, click "Your Photos", click "Profile", and copy the URL which should be <nowiki>http://flickr.com/people/[username]/</nowiki>
** Flickr supports rel="me" identity consolidation with your webpage that you enter into your profile, and with your Flickr contacts page. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo] - e.g. [http://identoo.com/dirk.olbertz sample profile]
* [http://jpgmag.com JPG Magazine]
* http://pulse.plaxo.com/pulse/img/event_icons/LastFM.gif [http://www.last.fm/ Last.FM] - login, go to your profile, and copy the URL which should start with <nowiki>http://www.last.fm/user/</nowiki>
** Last.FM supports rel="me" identity consolidation with your webpage that you enter into your profile, and with your Last.FM friends page.
* http://pulse.plaxo.com/pulse/img/event_icons/Magnolia.gif [http://ma.gnolia.com/ Ma.gnolia] - see [http://ma.gnolia.com/blog/2006/08/21/a-microadvance-in-our-microformats supports rel=me announcement].
* [http://nsyght.com Nsyght] - e.g. [http://nsyght.com/users/lisa sample profile].
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://plaxo.com/ Plaxo] - e.g. http://joseph.myplaxo.com/
* http://pulse.plaxo.com/pulse/img/event_icons/Pownce.gif [http://pownce.com/ Pownce] - login, go to your profile, and copy the URL which should start with <nowiki>http://pownce.com/</nowiki>
** Pownce [http://pownce.com/t/notes/644806/ supports rel="me" for LOTS of other profiles].
* [http://www.qmpeople.com/ qmpeople] - e.g. http://www.qmpeople.com/users/laserion
* [http://soup.io Soup] - on user profile
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati] - e.g. http://technorati.com/people/technorati/tantek
* http://www.postreach.com/images/logo_typepad.gif [http://typepad.com/ TypePad] - e.g. http://www.markpasc.typepad.com/
* http://pulse.plaxo.com/pulse/img/event_icons/Twitter.gif [http://twitter.com/ Twitter] - login, click on "Your profile" at the top, and copy the URL
* [http://videntity.org/ Videntity.org] - e.g. http://danda.videntity.org/
* http://openid.net/wp-content/uploads/vox.png [http://vox.com/ Vox] - e.g. http://anil.vox.com/
* [http://wordpress.com Wordpress.com] and any other blogs using Wordpress 1.5 or later have XFN supporting blog rolls (for friends and [[rel-me]]).
* http://lifestrea.ms/animated_favicon1.gif [http://lifestrea.ms/ lifestrea.ms] - supporting all your external appearances on the web. Examples: [http://lifestrea.ms/user/thomas.huhn/ public profile] or [http://lifestrea.ms/user/solution-media.thomas.huhn/ professional profile] of the same person.
</div>

== Implement hCard XFN supporting friends lists ==
Want to implement hCard+XFN on your site so you can list it here?

# '''Markup friends with hCard.''' See the [[hcard-authoring|hCard authoring]] page for how to mark-up names, links, icons of people in friends lists with hCard.
# '''XFN on friend links.''' Friends lists should be marked up with XFN per [[xfn-clarifications#mapping_community_site_.22friends.22|XFN clarifications: mapping community site friends]]. See also the [http://www.gmpg.org/xfn/join XFN: Getting Started] page for how to markup links to people with XFN. See also the [[hcard-examples#hCard_and_XFN|hCard examples: hCard and XFN]] which demonstrates this and the previous step quite well.
# '''rel="me" to a user's other URLs'''. Hyperlinks to users' home pages or blogs should have the XFN <code>rel="me"</code> attribute to support user-driven (since the user chooses the URL to link to) identity consolidation.
# '''rel="me" on "View All Friends..." links'''. If a user profile page on your site links to a separate page for that user's friends list, add <code>rel="me"</code> to that link.
# '''rel="me" on friends list pagination links'''. If your site paginates a user's friend list into multiple pages, be sure to add <code>rel="me next"</code> to your "Next" pagination hyperlinks, and similarly <code>rel="me prev"</code> to your "Previous" pagination hyperlinks.

Please also consider implementing [[hcard-supporting-user-profiles|hCard user profiles]].

== Implement import XFN friends lists ==
Want to implement importing (and preferably subscribing to) XFN friends lists on your site so you can list it here?

In addition to implementing hCard XFN supporting friends lists yourself (see above), do the following:

# '''Provide a user interface to "Import Friends"''' (like a button or menu item)
# '''When chosen, provide a text input field for the user to enter their profile URL''' (such as their blog or XFN friends list URL). If you already have the user's "Website", pre-fill the field with it, or if the user has many "Other Profiles", pre-fill the field with the first, and let the user pick any of them with a Select pop-up menu, or provide the user the option to just import XFN from all of them at once.
# '''Parse the [[XFN]] at the URL(s) given''' (links with rel="contact" or "acquaintance" or "friend" etc.) and check to see if there are any users on your site with any of those links as their rel="me" "Website" or among their rel="me" "Other Profiles" and add them to a list of people to invite. Crawl any symmetrical rel="me" links, especially symmetrical rel="me next" and/or rel="me prev" friends list pagination links for additional URLs to parse for XFN. Consider also parsing those URLs simultaneously for hCards that have those XFN links as class="url" hCard properties, and if the hCards have additional contact information such as instant messaging or email, add them to the list of people to invite.
# '''Present the list of people to invite''', perhaps sorted by "closeness" of XFN relationships (e.g. list family relationships before just romantic relationships before just friends before just professional relationships before just acquaintances before just contacts before just met etc.) with a "Add Friend" button next to each. When clicked, use [[XHR]] to add that person without altering the overall list, and change the Add button into a Cancel button. Perhaps put an "Add all" button at the top (or bottom) to let the user simply add everyone listed with one click.
# '''Consider also providing a checkbox "<nowiki>[x]</nowiki> Subscribe to XFN friends"''' which would automatically run this import perhaps once a day and notify the user of new contacts found that they may want to add, and similarly present an "Add all" button.

== Sites that should support hCard and XFN ==
=== Should support rel-me ===
See and please add to: [[hcard-advocacy#XFN_rel_me|hCard advocacy - XFN rel="me"]].
=== Should support friend lists ===
See and please add to: [[hcard-advocacy#hCard_XFN_friends_lists|hCard advocacy - hCard XFN friends lists]].

== For more information ==
In addition to the previous "Implement" sections, see the [[hcard-authoring|hCard authoring]] page for how to mark-up information about a person with hCard, and [http://gmpg.org/xfn/join XFN getting started] page for how to mark-up friend links with XFN.

Join the [http://microformats.org/discuss microformats community], in particular the #microformats IRC channel on irc://irc.freenode.net#microformats and the [http://microformats.org/mailman/listinfo/microformats-dev/ microformats-dev mailing list], and send a message stating that you'd like to add hCard to the profiles and hCard+XFN supporting friends lists (and importing thereof) to your website.

Please also consider implementing [[hcard-supporting-user-profiles|hCard supporting user profiles]].

See [[hcard-xfn-supporting-friends-lists-issues|hCard+XFN supporting friends lists issues]] for issues, problems with implementations.

== See also ==
* [[xfn|XFN]] ([http://gmpg.org/xfn/ spec], [[xfn-faq|FAQ]], [[xfn-implementations|implementations]] - there are a few more in there that need to be copied and expanded in this page.)
* [[hcard-supporting-user-profiles]]
* [[hcard|hCard]] ([[hcard-authoring|authoring]], [[hcard-faq|FAQ]])
* [[social-network-portability]]
* [[data-portability]]
* [[user-interface]]

hcard-supporting-user-profiles

2009-01-01T18:55:07Z

Adactio: /* Adding Huffduffer to the list of all services with hCard profiles */

{{TOC-right}}
<h1>hCard supporting user profiles</h1>
Welcome! If you have an account on any of the following services, you already have an [[hcard|hCard]] which you can provide to other services to import or subscribe your profile information. The ability to syndicate your profile from the service of your choice is a key component of [[social-network-portability]].

== Services with hCard profiles that also provide OpenID ==
The following web sites support both hCard on user profiles and the ability to use your user profile as an [[OpenID]]. Alphabetically sorted. Feel free to add sites with hCard profiles that are also OpenID URLs here. Please include a link to the site home page (or [[implementations]] entry).

<div style="font-size:larger">
* http://claimid.com/images/badges/claimidclear10x10.gif [http://claimid.com/ ClaimID]
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo]
* http://pulse.plaxo.com/pulse/img/event_icons/LiveJournal.gif [http://livejournal.com LiveJournal]
* [http://myopenid.com MyOpenID]
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://www.plaxo.com/ Plaxo]
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati]
* [http://videntity.org/ Videntity.org]
</div>

== All services with hCard profiles ==
The following web sites support hCard on their user profiles and are thus suitable for importing/subscribing to other sites that support hCard. Sites that you can also use as your [[OpenID]] are annotated with a OpenID icon http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif following the name of the site.

Alphabetically sorted. Feel free to add all sites with hCard profiles here. Please include a link to the site home page (or [[implementations]] entry), and instructions for retrieving your user profile URL on that site. If the site's user profile URLs can also be used as OpenIDs, please add the OpenID icon http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif following the name of the site.

<div style="font-size:larger">
* [http://3eep.com/ 3eep] - each user's public profile is located at <nowiki>http://3eep.com/users/userNameHere</nowiki>
* [http://www.artistserver.com/ ArtistServer] - each user's public profile is located at <nowiki>http://www.artistserver.com/userURLHere</nowiki>
* [http://www.bragster.com/ bragster] - each user's public profile is located at <nowiki>http://www.bragster.com/member/username</nowiki>
* http://claimid.com/images/badges/claimidclear10x10.gif [http://claimid.com/ ClaimID] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - each user's public profile is located at <nowiki>http://claimid.com/userNameHere</nowiki>
* http://identoo.com/images/icons/services/corkd.gif [http://www.corkd.com/ Cork'd] - login and copy the URL which should start with <nowiki>http://www.corkd.com/people/</nowiki>
* http://pulse.plaxo.com/pulse/img/event_icons/Digg.gif [http://digg.com/ Digg] - e.g. http://digg.com/users/tantek
* [http://djangopeople.net/ Django People] — profiles are at djangopeople.net/username e.g. http://djangopeople.net/simon/
* http://identoo.com/images/icons/services/dopplr.gif [http://www.dopplr.com/ Dopplr] — Example public profile: http://www.dopplr.com/traveller/adactio - non-public profiles may require login to view.
* http://pulse.plaxo.com/pulse/img/event_icons/Facebook.gif [http://facebook.com/ Facebook] - not sure how to find someone's public profile URL, e.g. [http://www.facebook.com/people/Andrei_Zmievski/502957990 Andrei Zmievski] but when found it appears to have support for valid fn+photo properties. Note [[hcard-supporting-user-profiles-issues#Facebook|issue(s) with Facebook hCard profiles]].
* [http://ficlets.com/ Ficlets] — profiles are located at ficlets.com/authors/username e.g. http://ficlets.com/authors/adactio
* http://pulse.plaxo.com/pulse/img/event_icons/Flickr.gif [http://flickr.com/ Flickr] - login, click "Your Photos", click "Profile", and copy the URL which should start with <nowiki>http://flickr.com/people/</nowiki>
* [http://gaia.com/ Gaia Community] - e.g. http://sphorbis.gaia.com/ - built by [http://www.zaadz.com Zaadz]
* [http://google.com Google] - view your profile at http://www.google.com/s2/profiles/me
* [http://huffduffer.com Huffduffer] profiles are located at <nowiki>http://huffduffer.com/username</nowiki> — Example public profile: http://huffduffer.com/clagnut
* http://identoo.com/images/icons/services/identoo.gif [http://identoo.com/ Identoo] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - e.g. [http://identoo.com/dirk.olbertz sample profile]
* http://idleaf.com/favicon.png [http://idleaf.com idleaf] - profiles are located at <nowiki>http://idleaf.com/IDENTITY_ID</nowiki> - e.g.: http://idleaf.com/ID4184
* http://identoo.com/images/icons/services/imthere.gif [http://imthere.com/ ImThere] - profiles are located at <nowiki>http://imthere.com/users/USERNAME</nowiki>
* http://jaiku.com/images/icons/fav-jaiku.gif [http://jaiku.com Jaiku] — profiles are located at username.jaiku.com e.g. http://adactio.jaiku.com/
* [http://jpgmag.com/ JPG Magazine] - each user's public profile is located at <nowiki>http://jpgmag.com/people/userNameHere</nowiki>, e.g. http://jpgmag.com/people/jpd
* [http://www.keevu.com Keevu.com] - profiles are located at <nowiki>http://www.keevu.com/users/USERNAME</nowiki> - e.g.: [http://www.keevu.com/users/zheileman Zheileman]
* http://pulse.plaxo.com/pulse/img/event_icons/LastFM.gif [http://www.last.fm/ Last FM] - profiles are located at <nowiki>http://last.fm/user/USERNAME</nowiki>, includes fn, photo, url.
* http://pulse.plaxo.com/pulse/img/event_icons/LinkedIn.gif [http://linkedin.com LinkedIn] - login, click on "[http://www.linkedin.com/myprofile?trk=tab_pro My Profile]" in the top blue bar, then click on "[http://www.linkedin.com/myprofile?editwp=&trk=tab_web Public Profile]" and copy the URL in the page after "Your current URL is:" which should start with <nowiki>http://www.linkedin.com/pub/ or http://www.linkedin.com/in/</nowiki>. Note: LinkedIn profiles include an [[hresume|hResume]] for you in addition to your hCard.
* http://pulse.plaxo.com/pulse/img/event_icons/LiveJournal.gif [http://livejournal.com LiveJournal] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif (see also [[implementations#LiveJournal|LiveJournal]] implementation page entry) - login, click on the "Profile" link, and copy the URL which should start with <nowiki>http://USERNAME.livejournal.com/profile</nowiki> where USERNAME is your LJ username. E.g. [http://daveman692.livejournal.com/profile].
* http://pulse.plaxo.com/pulse/img/event_icons/Magnolia.gif [http://ma.gnolia.com/ Ma.gnolia] - each user's public profile is located at <nowiki>http://ma.gnolia.com/people/userNameHere</nowiki> . Note: [[hcard-supporting-user-profiles-issues#Magnolia|issue(s)]].
* http://www.mixx.com/images/buttons/mixx-button4.png [http://www.mixx.com Mixx] - profiles are located at <nowiki>http://www.mixx.com/users/USERNAME</nowiki> e.g. http://www.mixx.com/users/jgarber
* [http://myopenid.com MyOpenID] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - profiles are located at <nowiki>http://USERNAME.myopenid.com</nowiki> e.g. http://tantek.myopenid.com/
* [http://www.nsyght.com/ Nsyght] - Visit your profile page. Should look like this: <nowiki>http://www.nsyght.com/friends/[username]/</nowiki>, e.g. [http://nsyght.com/users/lisa sample profile].
* http://www.bkmks.com/icons/nytimes.com.gif [http://timespeople.nytimes.com/ NYTimes TimesPeople] - e.g. http://timespeople.nytimes.com/view/user/19390043/1/index.html
* [http://www.obsidianportal.com Obsidian Portal] - Your profile page is located at <nowiki>http://www.obsidianportal.com/profile/USERNAME</nowiki>, e.g. [http://www.obsidianportal.com/profile/Micah Micah's profile].
* [http://www.osocial.net/network/ OSocial Network] - add the [http://www.osocial.net/network/app/osocialnetwork.xml OpenSocial application] into your social network, then in OSocial.net Web site you will be able to get your hCard profile
* http://pulse.plaxo.com/pulse/img/event_icons/plaxo.gif [http://www.plaxo.com/ Plaxo] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - create a nickname in your settings, then go to NICKNAME.myplaxo.com (e.g. http://joseph.myplaxo.com) and copy the URL
* http://pulse.plaxo.com/pulse/img/event_icons/Pownce.gif [http://pownce.com/ Pownce] - login, click on the "Home" link at the top, and copy the URL.
* http://www.syncup.com/SupWeb/ajax/images/16pxSyncUpIcon.gif [http://www.syncup.com/ SyncUp] - create a free account, choose what information to expose to public or specific people, then get the hcard in your profile page
* [http://www.qmpeople.com/ qmpeople] - Uses hCard+XFN for profiles (<nowiki>http://www.qmpeople.com/users/[username]</nowiki> - e.g. [http://www.qmpeople.com/users/laserion laserion])
* [http://radar.net/ Radar] - http://radar.net/people/radarname
* [http://www.revish.com/ Revish] — profiles are located at revish.com/people/username e.g. http://www.revish.com/people/adactio
* [http://rosebleed.net/ Rosebleed] - your profile URL is <nowiki>http://rosebleed.net/users/profile.php/</nowiki> followed by your username, e.g. [http://rosebleed.net/users/profile.php/silvermoon82 silvermoon82].
* [http://www.getsatisfaction.com/ Satisfaction]
* http://skateboardspot.info/image/icon/favicon.png [http://skateboardspot.info/ skateboardspot.info] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif (The site doesn't provide, but supports OpenID to login and register) — Log in, and click on your username in the top right corner. You'll see your user page which also is your hCard. Just copy the URL and you're done.
* [http://tangler.com/ Tangler] - click on a person's profile to navigate to their profile which is marked up with hCard <nowiki>http://www.tangler.com/people/id/</nowiki> - where "id" is the user number of that person.
* http://technorati.com/tools/mozsearch/technorati.png [http://technorati.com/ Technorati] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - login, click on the "Signed in as username" username link at the top right of the page, and copy the URL which should start with <nowiki>http://technorati.com/profile/</nowiki>
* [http://threadless.com/ Threadless] - select "My Account" and then "Profile Page". URL looks like <nowiki>http://www.threadless.com/profile/123987/username</nowiki>
* [http://www.travellerspoint.com/ Travellerspoint] - In use on all member profiles. URLs look like <nowiki>http://www.travellerspoint.com/member_profile.cfm?user=UsernameHere</nowiki> (e.g., [http://www.travellerspoint.com/member_profile.cfm?user=Peter Peter])
* http://pulse.plaxo.com/pulse/img/event_icons/Twitter.gif [http://twitter.com/ Twitter] - login, click on "Your profile" at the top, and copy the URL
* http://pulse.plaxo.com/pulse/img/event_icons/Upcoming.gif [http://upcoming.yahoo.com/ Upcoming] - login, click on the "Welcome, username!" username link at the top right of the page, and copy the URL which should start with <nowiki>http://upcoming.yahoo.com/user/</nowiki>
* [http://videntity.org/ Videntity.org] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - e.g. http://danda.videntity.org/
* [http://www.vimeo.com/ Vimeo] — e.g. http://www.vimeo.com/user196031
* http://openid.net/wp-content/uploads/vox.png [http://vox.com/ Vox] http://openid.net/wp-content/uploads/2007/10/openid_small_logo_white.gif - profile URL is <nowiki>http://USERNAME.vox.com/profile/</nowiki> e.g. http://daveman692.vox.com/profile/ (note issue: empty "n" property. fix: remove "n" from class attribute).
* [http://www.yedda.com/ Yedda] - e.g. http://yedda.com/people/8625713501419/ built by [http://www.zaadz.com Zaadz]
* [http://www.easthampshire.org/ easthampshire.org] - hCard on events and events map - e.g. http://easthampshire.org/eventdetail/wine_society_evening/1372606 and http://easthampshire.org/eventmap/wine_society_evening/1372606 built by [http://www.callendercreates.com Callender Creates]
* [http://www.dandyid.org/ DandyID.org] - hCard on user profiles, and a hCard widget for users blogs/sits/etc. (login to see the widget). Profile e.g. http://www.dandyid.org/beta/users/user_id/3
* ... add more sites (alphabetically sorted please) that support hCard, including instructions for finding and copying your profile URL.
</div>

=== offline sites ===
Sites that supported hCard user profiles that have gone offline, perhaps permanently.
* [http://consumating.com/ Consumating] - login, click on your name or "My Profile" link, copy the URL which looks like <nowiki>http://consumating.com/profiles/userNameHere</nowiki>
** supported hCard profiles at least from sometime in 2006 to 2008-03-15 when the site went offline.

== Services that import hCard profiles==
The following web sites support importing your existing hCard user profile, e.g. from the above sites, or your own page. Feel free to add sites supporting hCard user profile import to the appropriate section here. Please include a link to the site home page, and instructions for how to import your existing hCard user profile to the site.

=== import and subscribe on sign-up ===
Site(s) that allow you to import ''and'' subscribe to your hCard user profile when signing-up.. Alphabetically sorted.
* [http://getsatisfaction.com/ Satisfaction Inc.] - go to [http://getsatisfaction.com/people/new their sign in and registration page], choose the service of your existing profile or "'''Other...'''" and enter your profile URL (which you can retrieve as described above), and click "'''Get Profile'''". Then check "'''[x] Subscribe to this profile'''". Note: [[hcard-supporting-user-profiles-issues#Satisfaction|issue(s)]].

See [[subscribe-to-hcard]] for more notes on implementing subscribing to a user's hCard to automatically update their profile information.

=== import on sign-up ===
Site(s) that allow you to import your hCard user profile to sign-up. Alphabetically sorted.
* [http://www.bragster.com/ bragster] - go to [http://www.bragster.com/signup the sign-up page], click on the service logo of your existing profile, or the microformats logo for 'other' and enter your profile username (or URL for 'other') (which you can retrieve as described above).

=== import anytime ===
Sites that let you import your external hCard profile information anytime.
* [http://php-profile-importer.origo.ethz.ch/ PHP Profile importer] - Open Source PHP and JavaScript profile importer, there is also a [http://proofile.org/profile_importer_demo demo available].
* [http://www.proofile.org proofile] - [http://proofile.org/register Sign up] for an account and view the [http://proofile.org/edit/profile edit profile] page, enabling you to import from any hCard annotated URL. Full hCard is supported.
* [http://www.dandyid.org DandyID] - import a hCard supporting url after signing up, for auto-filling user info. DandyID also renders detailed hCards on user profiles.

=== subscribe anytime ===
Sites that let you subscribe to your external hCard profile information anytime.
* None currently.
=== delegation ===
Sites that support fully delegating to your external hCard profile.
* None currently.

== For more information ==
Want to implement hCard on your site so you can list it here?

See the [[hcard-user-profile-authoring|hCard user profile authoring]] page for how to mark-up a user profile with hCard.

Join the [http://microformats.org/discuss microformats community], in particular the #microformats IRC channel on irc://irc.freenode.net#microformats and the [http://microformats.org/mailman/listinfo/microformats-dev/ microformats-dev mailing list], and send a message stating that you'd like to add hCard to the profiles and hCard+XFN supporting friends lists to your website.

Please also consider implementing [[hcard-xfn-supporting-friends-lists|hCard+XFN friends lists]].

See [[hcard-supporting-user-profiles-issues|hCard supporting user profiles issues]] for issues, problems with implementations.

== see also ==
* [[subscribe-to-hcard]]
* [[hcard-xfn-supporting-friends-lists|hCard+XFN friends lists]]
* [[social-network-portability]]
* [[user-interface]]
* [[hcard|hCard]] ([[hcard-authoring|authoring]], [[hcard-faq|FAQ]])
* [[xfn|XFN]]
* [[data-portability]]

rel-tag

2009-01-01T18:45:42Z

Adactio: /* Adding Huffduffer to Examples in the Wild */

<entry-title>rel="tag"</entry-title>
__TOC__
== Draft Specification 2005-01-10 ==
; Editors/Authors
:[http://tantek.com/ Tantek Çelik]
:[http://epeus.blogspot.com/ Kevin Marks]

;Concept
:[http://powazek.com/ Derek Powazek]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==
[[Rel-Tag]] is one of several [[MicroFormats]]. By adding <code>rel="tag"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated "tag" (or keyword/subject) for the current page. Note that a tag may just refer to a major portion of the current page (i.e. a blog post). e.g. by placing this link on a page,

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

the author indicates that the page (or some portion of the page) has the tag "tech".

The linked page SHOULD exist, and it is the linked page, rather than the link text, that defines the tag. The last path component of the URL
is the text of the tag, so

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

would indicate the tag "tech" rather than "fish".

== Scope ==
rel="tag" is specifically designed for "tagging" content, typically web pages (or portions thereof, like blog posts).

rel="tag" is NOT designed for "tagging" arbitrary URLs or external content. There is demand for a general decentralized syntax for tagging URLs external to the current page, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.

If you need to define tags as part of a more specialized format, rel="tag" is the recommended way to do so, and [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]] and [[hcalendar|hCalendar]] all do this.
== 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="tag">tag</dt>
<dd>Indicates that the referred resource serves as a "tag",
or keyword/subject, for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Tag Spaces ==

Tags are embedded in HTTP URIs in a well-defined manner so that the tag embedded in an HTTP URI can be mechanically extracted from that URI. Specifically, the last segment of the path portion of the URI (after the final "/" character) contains the tag value. For example, the URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contains the tag "foo".

Thus, for the purposes of comparing two HTTP URIs as tags, the last segment of the path portion should be extracted and only that value (that value of the tag) should be compared.

''Need more formal language about comparison and extraction process.''

The destination of a rel="tag" hyperlink is required to be a tag space (a place that collates or defines tags), where the last segment of the path of the URL is the tag, e.g.

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

is a URL for the tag "tech".

Tags may only be placed in the URL path, and only in the last segment of the path. Tags may not be placed in query parameters or fragment identifiers. e.g.

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

is still a URL for the tag "tech", not "fish" or "emu".

Since the only part of a tag space URL of which any structure is required is the last path segment, a tag space URL can be hosted at any domain. Authors may choose to link to a tag at a particular tag space in order to provide a specific meaning. E.g. a tag for technology could link to:

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

Trailing slashes in tag URLs are ignored, that is:

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
as a rel-tag URL is treated as:
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>

== Encoding issues ==
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt <nowiki>RFC 3986</nowiki>]. For example:

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>

Note that if using Wikipedia as a tagspace, as discussed above, you should use <code>%20</code> as they remap '+' to <code>%2B</code>, causing a page with a plus sign in the title (which usually does not exist) to appear.

== Tags Are Visible Metadata ==
<code>rel="tag"</code> hyperlinks are intended to be visible links on pages and posts. This is in stark contrast to meta keywords (which were invisible and typically never revealed to readers), and thus is at least somewhat more resilient to the problems which plagued meta keywords.

Making tag hyperlinks visible has the additional benefit of making it more obvious to readers if a page is abusing tag links, and thus providing more peer pressure for better behavior. It also makes it more obvious to authors, who may not always be aware what invisible metadata is being generated on their behalf.

As a result the invisible tag link syntax variant: <code><link rel="tag" href="..." /></code> SHOULD NOT be supported by implementations.

==Examples in the Wild==
This section is '''informative'''.

The following sites have implemented rel-tag, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site marked up with rel-tag, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://huffduffer.com/ Huffduffer] uses rel-tag on every page, pointing to its own tag space e.g. http://huffduffer.com/tags/microformats
* [http://www.pantrymothtrap.com/ Pantry Moth Traps] implements the rel-tag in articles where an authoritative source is known. (for example in the article [http://www.pantrymothtrap.com/MothTrapsPick.html Moth Trap Picks] the tag [http://www.cleanertoday.com/tag/moth%20trap Moth Trap])
* [http://www.hightechcville.com/ HighTechCville] uses rel-tag on all the pages listing tagged content for [http://www.hightechcville.com/people people], [http://www.hightechcville.com/organizations organizations] and [http://www.hightechcville.com/events events] related to high tech in Charlottesville, VA.
* [http://skateboardspot.info skateboardspot.info] uses rel-tag in spotguide entries which are added to the site and categorized by the users (for example: [http://skateboardspot.info/cat/spotguide/action/view/id/1 “El Toro High School” spotguide entry]).
* [http://www.idoneos.com Idoneos.com] uses rel-tag for conceptual links to its own tag space, a collection of 'concepts' (mostly spanish).
* [http://www.professionalontheweb.com Professional On The Web] uses rel-tag for user entered tags which categorize web professionals and freelancers.
* [https://www.coderesort.com/p/epicode/wiki/CloudCuckoo CloudCuckoo] (secure site but open to all) an [http://www.episerver.com EPiServer] module distributed free by [http://www.interakting.co.uk Interakting], generates tag clouds with rel-tag links.
* [http://www.lifetime.com Lifetime.com] uses rel- and rev-tags in all content pages.
* [http://www.my-warehouse.de the my-Warehouse shopsystem] implements rel-tags in box headings and categories links.
* Joseph Bergantine uses tags to categorize [http://bergantinedesign.us/wallpaper/ wallpapers] and [http://bergantinedesign.us/blog/my-name-is-rachel-corrie blog posts]
* [http://www.codesignville.com Codesignville] uses rel-tag to indicate content categories.
* [http://www.bossalive.com BossaLive] uses rel-tag for tagging music. Publishes rel-tags for album, artist and genre.
** Also uses [[hcard|hCard]] on user profile pages.
* [http://www.qmpeople.com/ qmpeople] Uses rel-tag for translated tags into english, french and italian to meet new friends in different countries.
* [http://www.keevu.com Keevu.com] uses rel-tag to indicate content categories on most pages, like [http://www.keevu.com/venues venues]
* [http://www.amazingincredible.com Amazing Incredible] uses rel-tag on content pages
* [http://www.auctionlink.com.au AuctionLink] uses rel-tag on [http://www.auctionlink.com.au/TagList/Auctioneers/ Auction Sales Listings] tags.
** Could also use [[hcard|hCard]], e.g. on [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Bonhams_Goodman_1/] [[User:AndyMabbett|Andy Mabbett]]
* Christian Hess uses rel-tag on his [http://www.hess-cr.com homepage blog] and several other pages of his site.
* [http://spacedust.atspace.com/ Spacedust] uses rel-tag to mark up gallery pages.
* [http://my.opera.com/dstorey/blog/ My Opera] uses rel-tag for tags on all user's blog entries.
* [http://dev.opera.com/articles/view/making-wii-friendly-pages/ Dev Opera] uses rel-tag on all article tags.
* [http://www.international.unt.edu UNT International] uses rel-tag to indicate content categories on most pages
* [http://yedda.com Yedda] - Yedda publishes rel-tags for all of the tags the people entered on themselves as well as on all tags entered on questions asked on Yedda.
* [http://www.lingr.com Lingr] publishes rel-tags for all user entered tags.
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.
* [http://eventful.com Eventful] publishes rel-tags for user entered tags.
* [http://spinn3r.com Spinn3r] implements rel-tag as well as RSS and Atom subject and categories.
* [http://www.weboffate.com Web of Fate] publishes rel-tags for future predictions.

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse rel-tag links. If you have a rel-tag implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://www.textcube.org Textcube.org] makes a blogging tool, Textcube which generates rel-tag for tags on blog posts.
* [http://hashtags.org/ HashTags] tags Twitter posts, converting "#example" into a tag of "example"
* [http://ikiwiki.info ikiwiki] generates rel-tag for all tagged pages (as of version 2.6)
* [http://www.hubtag.com HubTag] helps users find a unique tag across the web for their event - eg. JohnAndBettysWeddingWimbledonMarch07
* [http://www.necctar.com Necctar] is a search engine exclusively based on tag microformat parsing and processing. Necctar uses tags entered by bloggers to index the world wide web
* Nutch has a [[rel-tag]] parser [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html committed to their svn repository].
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables rel-tagging from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] slide show creator allows authors to generate rel-tags and group slide shows by rel-tag via a list or cloud with tag usage count.
* The Freetag plugin for the [http://www.s9y.org Serendipity] blog software supports rel-tags on a per-entry basis, as well as inside of its tag clouds. (The Freetag plugin is available inside of SPARTACUS)
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel-tags and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://www.truist.com/blog/493/trutags-a-tagging-plugin-for-textpattern tru_tags] is a plugin for [http://textpattern.com/ Textpattern] that supports rel-tagging blog posts via the Keywords field.
* [http://news.livejournal.com/86492.html?thread=24881884 LiveJournal] - see also [http://www.livejournal.com/support/faq.bml?cat=tags their FAQ regarding their tags support]
* [http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/TagsLinks TagsLinks] Turn each tag into links that let you find related content on tagging services.
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags Tag plugin for WordPress]
** Note that some sites using WordPress (http://microformatique.com/ for instance) are getting incorrect tags. The tag is ?cat=12 instead of the actual tag value.
* [http://noone.org/blog/tags/Tagging Tag plugin for Blosxom]
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.
* [http://consumingexperience.blogspot.com/2005/12/updated-multiple-word-technorati-tag.html Greasemonkey script for Firefox that generates tags for Blogger]
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] is a validation tool by [[User:DrewMcLellan|Drew McLellan]] that will validate existence of rel-tag attributes.

== References ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

=== Informative References ===
* [[hreview|hReview]] uses rel-tag for tags and scalar tags
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds
* [[hcard|hCard]] can use rel-tag for categories
* [[hcalendar|hCalendar]] can use rel-tag for categories
* [http://technorati.com/help/tags.html Using Technorati Tags]
* Contributed from http://developers.technorati.com/wiki/RelTag
* [http://microformatique.com/?p=61 Know your rel-tag] at microformatique.com

== Discussions ==
* Feedback is encouraged on the [[rel-tag-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]

=== Q&A ===
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.

==Related pages==
{{rel-tag-related-pages}}

[[Category:Specifications]]
[[Category:rel-tag]]

hatom-examples-in-wild

2009-01-01T18:42:37Z

Adactio: /* adding Huffdfuffer to 0.1 hAtom examples */

=hAtom Examples in the Wild=

The following sites have implemented [[hatom|hAtom]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site marked up with hAtom, feel free to add it o the '''top''' of this list. Please check back after a few days, to see if anyone has found any problems with the examples supplied.

== 0.1 hAtom examples==

* [http://huffduffer.com/ Huffduffer] uses hAtom for the [http://huffduffer.com/new newest] and the most [http://huffduffer.com/popular popular] additions as well as on every user profile and on tag places.
* [http://fairvote.ca/en/WaterlooRegion Waterloo Region Chapter Fair Vote Canada] hAtom enabled until the site enables RSS/Atom in Drupal. Self-referentially linked with Luke Arno's [http://www.lukearno.com/projects/hatom2atom/ hatom2atom service].
* [http://www.aduk.org/ ADUK] use hAtom to mark up news on their home page.
* [http://thetyee.ca/Blogs/TheHook/ The Hook] a Canadian political blog, uses hAtom for blog posts and list of blog posts, however also offers a feedburner RSS feed.
* [http://www.plaintxt.org/experiments/blog-summary/ Blog Summary] is a [[wordpress|WordPress]] plugin from plaintxt.org that generates a semantic list of recent entries in hAtom. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
* [http://www.yigg.de YiGG (a german social-news community)] Marks up all there Pages with stories using hAtom.
* [http://www.dancefederation.co.uk Dance Federation Salsa Dancing & Jive Dancing Lessons and Events ] Directory for classes, lessons and events users hatom for its news page and generating rss.
* [http://blog.kakkoi.net/ Kakkoi] - combine hAtom (i.e., xFolk RC1, hreview, hAtom) for blog posts and comments.
* [http://www.vibereview.com/ VibeReview] uses hAtom for sex toy reviews and articles (no nudity, but still maybe NSFW). Two feeds can be found on the homepage.
* [http://www.linuxinfusion.com/ Linux Infusion] uses hAtom for blog posts and comments.
* Joseph Bergantine has used hAtom to mark up [http://bergantinedesign.us/blog/my-microwave-has-a-button-that-says-record blog posts], [http://bergantinedesign.us/blog/ article lists], and [http://bergantinedesign.us/blog/doneish#comment000068 comments]
* [http://microrevie.ws/ MicroReviews] marks up each review with [[hAtom]] so that every page can be a feed. See [http://microrevie.ws/ the home page] or [http://microrevie.ws/????? 5-Star Reviews]
* LocalHero (localhero dot biz) A local search which returns it search results in hatom (as well as other microformats).
* [http://blog.livedoor.jp/forestk/ forestk's blog] uses hAtom (note it is Japanese!)
* [http://www.niallkennedy.com/blog/ Niall Kennedy's Weblog] features hAtom on every page. includes comments.
* [http://weborganics.co.uk/ WebOrganics] - Has hAtom feeds on every page.
* [http://journal.redflavor.com/ Reprise] - A [http://redflavor.com/reprise.rb minimal blog] application which uses hAtom out of the box.
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, with hAtom entries & other microformats. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].
* [http://www.people.com/people/news/ People Magazine] uses hAtom to markup the latest news stories.
* [http://www.bo.ingv.it/italiano/News.html Istituto Nazionale Geofisica e Vulcanologia, Bologna] implemented hAtom entries with embedded rel-tags for categories in its news-page (custom template for [http://www.modxcms.com MODx CMS]).
* [http://v1.itvp.pl/blog/przebojowanoc/i.tvp/idb/24/ ITVP] uses hAtom for entries. See [http://twitter.com/Wojtek/statuses/299700082 Wojtek's announcement 2007-09-28].
* [http://shiftingpixel.com Shifting Pixel] uses hAtom for blog posts and comments.
* [http://lazylibrary.com LazyLibrary] uses hAtom on book results pages.
* [http://findsubstance.com Find Substance Blog] uses hAtom for blog posts.
* [http://www.blogger.com Blogger]
** [http://groups.google.com/group/bloggerDev/browse_thread/thread/69344c5cc35b472e Announcement] on Blogger Dev that all new blogs will have hAtom classes
* AOL
**[http://news.aol.com AOL News], AOL News has implemented hAtom into their center column. This display will be used on other AOL channels as well
**[http://sports.aol.com AOL Sports], AOL Sports is the second AOL channel to use the hAtom display for its center column data
* [http://www.creation.uk.com Creation design & marketing] uses hAtom for a lot of the content as well as [http://www.creation.uk.com/news/2007/06/06/easy-money/ comments on articles].
* [http://www.sndbx.org/ The Sandbox Designs Competition] uses hAtom for all content, hCard for participant (the competition designers) and sponsor information, hCalendar for the competition schedule, XFN for links, and rel-license for licensing information. It's all GNU GPL.
* [http://guyleech.net guyleech.net] uses hAtom for blog posts, and uses hCard for contact information. There is also an [http://guyleech.net/technical/html/minimal-microformats article] on how to minimise hAtom, to save time and code.
* [http://kpumuk.info/ Dmytro Shteflyuk] uses hAtom for all blog posts.
* [http://blog.no-panic.at Florian Beer] uses hAtom to mark up all the blog posts. There is also a [http://blog.no-panic.at/2006/11/16/hatom-and-wordpress/ tutorial] on how to convert [[wordpress|WordPress]] themes to include hAtom.
* [http://ficlets.com/ Ficlets] uses hAtom on the [http://ficlets.com/stories main stories page] and on [http://ficlets.com/stories/12 individual story pages].
* [http://www.international.unt.edu UNT International] uses hAtom combined with hCard on news/announcement pages (e.g., [http://www.international.unt.edu/quick/news the main news page]) in addition to providing traditional Atom feeds
* [http://www.absalom.net.au Absalom Media] uses hAtom combined with hCard for articles.
* [http://www.joomlamug.com Joomla! Melbourne User Group] uses hAtom combined with hCard for articles.
* [http://www.volume.co.uk Volume] - Main news page is marked up as hAtom 0.1
* [http://yedda.com Yedda] - Yedda support hAtom on exploration of questions where there is also support for Atom and RSS feeds. ([http://yedda.com/questions/recent/ example])
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club's] frequently-updated [http://www.westmidlandbirdclub.com/new.htm What's New] page, [http://www.westmidlandbirdclub.com/ladywalk/latest.htm news from its Ladywalk Reserve] and [http://www.westmidlandbirdclub.com/worcs/grimley/latest.htm news from Grimley Pits] — comments welcome on my talk page [[User:AndyMabbett|Andy Mabbett]]
* [http://pixelsebi.com pixelsebi's repository] uses hAtom 0.1 for blog posts (and hCard, hCalendar, XFN, xFolk and many more) based on manual [[wordpress|WordPress]] template modifications
* [http://www.qmpeople.com/ qmpeople] uses hAtom combined with hCard for [http://www.qmpeople.com/blog/ blog].
* [http://www.geekinthepark.co.uk Geek in the Park] uses hAtom for the comments. -- by [[User:Trovster|trovster]]
* [http://www.csarven.ca Sarven Capadisli] uses hAtom for the articles and comments -- by [[User:Csarven|csarven]]
* [http://www.capital.edu Capital University] uses hAtom 0.1 to mark up the feed of latest posts by student bloggers on its home page.
* [http://blog.davidjanes.com Ranting and Roaring] (David Janes)
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site — by [[User:ChrisCasciano|Chris Casciano]]
* [http://sedna.spip.org/sedna/ Sedna RSS] (a feed aggregator based on SPIP, by Fil, IZO and others; GPLd sources are available at [http://zone.spip.org/trac/spip-zone/browser/_squelettes_/sedna SPIP-Zone])
* [http://quotedprintable.com/pages/scribbish Scribbish] is a Typo theme which uses hAtom.
* [http://rbach.priv.at/hAtom2Atom/Changelog/ hAtom2Atom.xsl's Changelog] is published as hAtom and Atom.
* [http://federali.st/ federali.st]'s webbed Federalist Papers are each marked up in hAtom.
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] is a theme for [[wordpress|WordPress]] that uses hAtom. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
** The theme is also available to accounts on the [http://wordpress.com/ <username>.wordpress.com] hosting service. The [http://blog.coworking.info Coworking] and [http://barcamp.wordpress.com BarCamp] blogs are examples of custom Sandbox themes.
** Over 40 designs available for the Sandbox at the [http://www.sndbx.org/ Sandbox Designs Competition], which also uses hAtom
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] is a modification of the default WordPress theme (Kubrick) with hAtom support.
** It points to the hAtom2Atom proxy service as the link for syndication feeds.
* All [http://www.plaintxt.org/themes/ plaintxt.org themes] for [[wordpress|WordPress]] now use hAtom. The themes are also coded for hCard compliance. The themes, by name, are:
** [http://www.plaintxt.org/themes/barthelme/ Barthelme] (two-column, fluid), [http://www.plaintxt.org/themes/blogtxt/ blog.txt] (two- or three-column, elastic), [http://www.plaintxt.org/themes/plaintxtblog/ plaintxtBlog] (three-column, fluid), [http://www.plaintxt.org/themes/simplr/ Simplr] (one column, elastic), [http://www.plaintxt.org/themes/veryplaintxt/ veryplaintxt] (two column, fluid)
** By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
* [http://www.pats.ua.ac.be/courses PATS Courses], the PATS Research Group uses hAtom to mark up the latest course documents for some of their courses
* [http://mix.excite.co.uk Excite MIX], the Ajax Start Page from Excite Europe, uses hAtom 0.1 and hCard in the Feed Viewer to mark up feed entries and authors.
* [http://last.fm Last.FM], a social music sharing platform, uses hAtom markup for [http://blog.last.fm/2007/05/30/rss-your-shoutbox-and-you shoutbox], and recommends using [http://tools.microformatic.com microformatic]'s transcode tool
* [http://vlograzor.com/ Vlog Razor] - Contains multiple hAtom feeds on the same page.



==Examples with some problems==

Entries may be moved here if there's a problem with the way hAtom is used on the page concerned. If the page is yours, and you want to improve it, see the [[hatom-faq|hAtom FAQ]], or raise any queries on [[hatom-issues|hAtom Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.

=== Pre 0.1 hAtom examples===
These pages conform to an older draft standard and need to be updated.

* [http://www.myelin.co.nz/post/ Second p0st] (Phil Pearson)

==See Also==
{{hatom-related-pages}}

operator-phone-tests

2008-09-04T15:17:10Z

Adactio: /* How to test your device */

<h1>Operator phone tests</h1>
{{TOC-right}}
[[Operator]] has a "Send to Bluetooth device" option that uses the Bluetooth File Exchange functionality of OS X (and similarly in Windows?) to send hCards and hCalendar events to mobile devices - cell phones, PDAs etc.

This page lists tests and results for different devices.

== How to test your device ==
Use Operator to try to add hCards or hCalendar events to your handset over Bluetooth, then add it to the wiki to say whether it passed or failed.

The "Send to Bluetooth device" script and other user scripts can be downloaded from http://www.kaply.com/weblog/operator-user-scripts/

Launch Firefox, click the Operator icon and choose "Options". Under the "User Scripts" tab, you can now add any scripts you've downloaded. Then under "Actions", click "New" and select any actions you want, like "Send to Bluetooth device."

== Device compatibility ==

=== Motorola V3 ('RAZR') ===
The V3 RAZR does not support the vCard 3.0 implementation oused in Operator and X2V but requires vCard 2.1. If one uses vCard 2.1, it seems to work fine. The RAZR does not support being sent hCalendar events using Operator.

=== Palm T|X PDA ===
The T|X does not support hCard or hCalendar import through Bluetooth.

=== Sony Ericsson W810i ===
The W810i supports both vCard 3.0 and vCard 2.1, but does not transfer the 'fn' field properly. It has also choked on some of the 'type' data it has seen in the wild.

The W810i did not want to add an hCalendar event from the past. [[User:TomMorris|I]] tested it with [http://upcoming.yahoo.com/event/388286/ this event] and it said "Cannot add appointment", but I did already have it in another calendar. I tried [http://upcoming.yahoo.com/event/371244/ another event] and got the same result. It seems the W810i does not support "Send to Bluetooth device" for hCalendar.

=== Sony Ericsson K600i ===

Exporting hCards (from, for example, http://suda.co.uk/contact/ ) works like a charm. When I tried to add events from http://2008.dconstruct.org/schedule/ the phone reported "Cannot add appointment." It looks like "Send to Bluetooth device" works for hCard but doesn't work for hCalendar on this phone.

== related ==
Jeremy Keith has demonstrated the "bluetooth an hCard to your phone" functionality using the [[Tails]] plugin (which has yet to be updated to work with Firefox 3 unfortunately). Here is a video he made demonstrating this:

[http://www.youtube.com/watch?v=azoNnLoJi-4 http://i2.ytimg.com/vi/azoNnLoJi-4/default.jpg]

== see also ==
* [[operator]]
* [[firefox]]

events

2008-07-07T01:15:42Z

Adactio: Moving Open Tech from upcoming to recent.

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* none.

== Upcoming ==


Soonest first:

*2008-07-01: [[events/2008-07-01-weekly-meetup-dinner| microformats weekly meetup dinner]] at Crepes on Cole, San Francisco, CA. http://pownce.com/t/notes/2627529/

* [http://semanticcamp.wordpress.com Vancouver Semantic(Web)Camp 2008], British Columbia (B.C.), Canada - Fall 2008 - Free One Day Unconference about Microformats et al

== Recent ==
Most recent first:

=== July ===

*2008-07-05: [[events/2008-07-05-opentech-publishing-with-microformats| Publishing With Microformats]] at Open Tech 2008, London, UK

=== June ===
*2008-06-24: [[events/2008-06-24-weekly-meetup-dinner| microformats weekly meetup dinner]] at Chaat Cafe, San Francisco, CA. http://pownce.com/t/notes/2558970/
*2008-06-20: [[events/2008-06-20-3rd-bday-dinner-sf| microformats happy 3rd bday dinner]] at Westfield Food Court, San Francisco. http://pownce.com/t/notes/2533568/
* 2008-06-17: Supernova 2008 [http://www.socialtext.net/openflow/ Open Flow track], San Francisco, CA
* 2008-06-17: [[events/2008-06-17-LinkedData-Planet| LinkedData Planet Spring 2008]] at Roosevelt Hotel, New York City, United States — "Web of Data" keynote presentation by W3C Director '''Sir Tim Berners-Lee'''. http://www.linkeddataplanet.com

=== May ===
* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] at The Yorkshire Grey — part of London Web Week
* 2008-05-13: [[events/2008-05-13-webstock-workshop| Webstock Microformats Workshop in Christchurch]] at Millenium Hotel, Christchurch, New Zealand — a workshop with Tantek Çelik.http://upcoming.yahoo.com/event/603905
* 2008-05-09: [[events/2008-05-09-webstock-workshop| Webstock Microformats Workshop in Wellington]] at Wellington Town Hall, Wellington, New Zealand — a workshop with Tantek Çelik. http://upcoming.yahoo.com/event/603769
* 2008-05-08: [[events/2008-05-08-xtech|Creating portable social networks with microformats]] at XTech 2008 in Dublin — a presentation by Jeremy Keith.

=== April ===

* 2008-04-18: [[events/2008-04-18-fowd|Microformats — Building blocks 'for a beautiful web']] at FOWD 2008 in London — a workshop by Andy Clarke.
* 2008-04-14: [[events/2008-04-14-openweb|Microformats with Ryan King et al]] at Open Web Vancouver 2008 in Canada — incl. (Open)Social(Web)Camp (Un)conference.
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events

2008-06-30T16:12:57Z

Adactio: /* Upcoming */

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* none.

== Upcoming ==


Soonest first:

*2008-06-24: [[events/2008-06-24-weekly-meetup-dinner| microformats weekly meetup dinner]] at Chaat Cafe, San Francisco, CA. http://pownce.com/t/notes/2558970/

*2008-07-05: [[events/2008-07-05-opentech-publishing-with-microformats| Publishing With Microformats]] at Open Tech 2008, London, UK

* [http://semanticcamp.wordpress.com Vancouver Semantic(Web)Camp 2008], British Columbia (B.C.), Canada - Fall 2008 - Free One Day Unconference about Microformats et al

== Recent ==
Most recent first:

=== June ===
*2008-06-20: [[events/2008-06-20-3rd-bday-dinner-sf| microformats happy 3rd bday dinner]] at Westfield Food Court, San Francisco. http://pownce.com/t/notes/2533568/
* 2008-06-17: Supernova 2008 Open Flow track, San Francisco, CA
* 2008-06-17: [[events/2008-06-17-LinkedData-Planet| LinkedData Planet Spring 2008]] at Roosevelt Hotel, New York City, United States — "Web of Data" keynote presentation by W3C Director '''Sir Tim Berners-Lee'''. http://www.linkeddataplanet.com

=== May ===
* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] at The Yorkshire Grey — part of London Web Week
* 2008-05-13: [[events/2008-05-13-webstock-workshop| Webstock Microformats Workshop in Christchurch]] at Millenium Hotel, Christchurch, New Zealand — a workshop with Tantek Çelik.http://upcoming.yahoo.com/event/603905
* 2008-05-09: [[events/2008-05-09-webstock-workshop| Webstock Microformats Workshop in Wellington]] at Wellington Town Hall, Wellington, New Zealand — a workshop with Tantek Çelik. http://upcoming.yahoo.com/event/603769
* 2008-05-08: [[events/2008-05-08-xtech|Creating portable social networks with microformats]] at XTech 2008 in Dublin — a presentation by Jeremy Keith.

=== April ===

* 2008-04-18: [[events/2008-04-18-fowd|Microformats — Building blocks 'for a beautiful web']] at FOWD 2008 in London — a workshop by Andy Clarke.
* 2008-04-14: [[events/2008-04-14-openweb|Microformats with Ryan King et al]] at Open Web Vancouver 2008 in Canada — incl. (Open)Social(Web)Camp (Un)conference.
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2008-07-05-opentech-publishing-with-microformats

2008-06-30T16:06:07Z

Adactio:

<h1>Open Tech 2008 — Publishing With Microformats</h1>
{{TOC-right}}
One of several microformats [[events]].

==Subscribe==
You can:
*Add this event to your Calendar: http://feeds.technorati.com/events/microformats.org/wiki/events/2008-07-05-opentech-publishing-with-microformats
*Subscribe to this event: webcal://feeds.technorati.com/events/microformats.org/wiki/events/2008-07-05-opentech-publishing-with-microformats

== details ==
<div class="vevent">
;When
:2008-07-05T10:00:00–2008-07-05T19:15:00
;Where
:University of London Union, Malet Street, London WC1E 7HY, <abbr class="country-name" title="United Kingdom">UK</abbr>
;What
:Open Tech 2008
;Presenter
:[http://adactio.com/ Jeremy Keith]
;Web
:http://www.ukuug.org/events/opentech2008/
</div>

'''[http://technorati.com/events/microformats.org/wiki/events/2008-07-05-opentech-publishing-with-microformats Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):



tags: '''opentech08 microformats adactio jeremykeith upcoming:event=437827'''

If you Twitter with [[twitter-syntax#Hash_tags|hash tags]], mention '''#opentech08''' (with the "#") in tweets about the event.

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

*[http://adactio.com/ Jeremy Keith]
* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''opentech08 microformats adactio jeremykeith upcoming:event=437827'''


* ...

== notes ==
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''microformats opentech08 adactio jeremykeith upcoming:event=437827'''

* ...



== related pages==
{{events-related-pages}}

iso-8601

2008-04-28T15:34:03Z

Adactio: /* Related pages */

=ISO 8601=

The '''International Standards Organisation''''s standard, number '''8601''' is an international standard for date and time representations. It is used for all date-time representations in microformats.

==Overview==

For a plain-language overview of ISO 8601, we recommend the [http://www.cl.cam.ac.uk/~mgk25/iso-time.html ISO 8601 summary by Markus Kuhn].

==Microformats==

Microformats using ISO8601 include:

*[[hAtom]]
*[[hCalendar]]
*[[hCard]]
*[[hReview]]
*...

==<nowiki>RFC 3339</nowiki>==

RFC 3339 defines a profile of ISO 8601 for the use in Internet protocols and standards.

*It explicitly excludes durations and dates before the [http://en.wikipedia.org/wiki/Common_era common era].
*The more complex formats like week numbers and ordinal day are not permitted (see <nowiki>RFC 3339</nowiki>, section 5.6).

Microformats {{should}} use <nowiki>RFC 3339</nowiki>.

==Issues==
* How should dates before the common era be marked up? [[User:AndyMabbett|Andy Mabbett]]

==See also==
*[http://en.wikipedia.org/wiki/ISO_8601 ISO 8601 on Wikipedia]
* [http://isotc.iso.org/livelink/livelink/4021199/ISO_8601_2004_E.zip?func=doc.Fetch&nodeid=4021199 ISO 8601:2004(E) from ISO] (zip-pdf, 228KB)
* [http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html Summary of 8601 by ISO]
* [http://isotc.iso.org/livelink/livelink/fetch/2000/2122/138351/138352/customview.html?func=ll&objId=138352&objAction=browse&sort=name Technical Committee ISO/TC 154], Processes, data elements and documents in commerce, industry and administration.
* [http://www.phys.uu.nl/~vgent/calendar/isocalendar.htm The Mathematics of the ISO 8601 Calendar]
* [http://www.personal.ecu.edu/mccartyr/isowdcal.html Current date in '''week date''' and '''ordinal date''' format]
* [http://www.dmoz.org/Science/Reference/Standards/Individual_Standards/ISO_8601/ ISO 8601 at the Open Directory Project]
* [http://www.w3.org/TR/NOTE-datetime W3C Specification about UTC Date and Time] and IETF Internet standard <nowiki>RFC 3339</nowiki>, based on ISO 8601

==Related pages==
*[[datetime-design-pattern]]
*[[date-design-pattern]]
*[[abbr-design-pattern]]

datetime-design-pattern

2008-04-28T15:31:45Z

Adactio: /* Accessibility issues */

'''This page is a draft.'''

= Datetime Design Pattern =
This is a page for exploring a datetime design pattern.

== Purpose ==
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable [[iso-8601|ISO8601]] datetime or date as the value

==Current uses==

The pattern, which is now available as part of [[hAtom]], [[hcalendar|hCalendar]], [[hcard|hCard]] and [[hreview|hReview]], is:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time, with an appropriate level of specificity, and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [[iso-8601|ISO 8601]]

== Profile of ISO8601 ==

Any [[microformat]] using the date-time-design pattern {{should}} use a profile of [[iso-8601|ISO8601]]. There are currently two widely used profiles which {{should}} be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

==Accessibility issues==

Note: There are some accessibility issues [http://www.webstandards.org/2007/04/27/haccessibility/] with Datetime Design Pattern, and concerns that its use could breach WCAG accessibility guidelines, that are being addressed as part of the [[abbr-design-pattern-issues]] discussion. Possible change recommendations may follow after the accessibility testing is complete. The accessibility concerns are considerably lessened when using the [[date-design-pattern]], a subset of the [[datetime-design-pattern]].

== Discussion ==

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

-- [http://tantek.com/log/ Tantek]

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

---

A few questions: asked by [[User:CharlesBelov|CharlesBelov]] 16:57, 24 Apr 2007 (PDT), answered by [[User:JamesCraig|JamesCraig]] on 15:58, 5 Jul 2007 (PDT).

# Would it make more sense for documenting the alternative codings pitting the abbr tag vs. other tags to be on this page? ''Answer: That documentation should go on the [[assistive-technology-abbr-results]] page.''
# Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about USA Section 508? It does appear to violate Technique for WCAG 2.0 [http://www.w3.org/TR/WCAG20-TECHS/#H28 H28: Providing definitions for abbreviations by using the abbr and acronym elements], although that is a supporting document and does not have the force of a guideline. ''Answer: Yes, it appears that is in violation of WCAG, 508, et al, so alternatives are being discussed on the [[assistive-technology-abbr-results]] page.''
# In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the abbr tag? ''Answer: please refer to and add any suggestions to [[assistive-technology-abbr-results]].''
# For that matter, wouldn't you want to style such an abbr tag with text-decoration:none to hide that an abbr tag was used? Otherwise, visitors might cursor over the time, see the machine time, and be annoyed that their time was wasted or else be confused. And I don't think you can suppress the title from coming up if the human-readable time was inadvertently hovered. ''Answer: Microformats should not rely on CSS in order to work properly, but again, that discussion can be found here: [[assistive-technology-abbr-results]].''

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* [[date-design-pattern]] is a subset of [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

datetime-design-pattern

2008-04-28T15:26:11Z

Adactio: /* See Also */

'''This page is a draft.'''

= Datetime Design Pattern =
This is a page for exploring a datetime design pattern.

== Purpose ==
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable [[iso-8601|ISO8601]] datetime or date as the value

==Current uses==

The pattern, which is now available as part of [[hAtom]], [[hcalendar|hCalendar]], [[hcard|hCard]] and [[hreview|hReview]], is:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time, with an appropriate level of specificity, and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [[iso-8601|ISO 8601]]

== Profile of ISO8601 ==

Any [[microformat]] using the date-time-design pattern {{should}} use a profile of [[iso-8601|ISO8601]]. There are currently two widely used profiles which {{should}} be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

==Accessibility issues==

Note: There are some accessibility issues [http://www.webstandards.org/2007/04/27/haccessibility/] with Datetime Design Pattern, and concerns that its use could breach WCAG accessibility guidelines, that are being addressed as part of the [[abbr-design-pattern-issues]] discussion. Possible change recommendations may follow after the accessibility testing is complete.

== Discussion ==

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

-- [http://tantek.com/log/ Tantek]

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

---

A few questions: asked by [[User:CharlesBelov|CharlesBelov]] 16:57, 24 Apr 2007 (PDT), answered by [[User:JamesCraig|JamesCraig]] on 15:58, 5 Jul 2007 (PDT).

# Would it make more sense for documenting the alternative codings pitting the abbr tag vs. other tags to be on this page? ''Answer: That documentation should go on the [[assistive-technology-abbr-results]] page.''
# Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about USA Section 508? It does appear to violate Technique for WCAG 2.0 [http://www.w3.org/TR/WCAG20-TECHS/#H28 H28: Providing definitions for abbreviations by using the abbr and acronym elements], although that is a supporting document and does not have the force of a guideline. ''Answer: Yes, it appears that is in violation of WCAG, 508, et al, so alternatives are being discussed on the [[assistive-technology-abbr-results]] page.''
# In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the abbr tag? ''Answer: please refer to and add any suggestions to [[assistive-technology-abbr-results]].''
# For that matter, wouldn't you want to style such an abbr tag with text-decoration:none to hide that an abbr tag was used? Otherwise, visitors might cursor over the time, see the machine time, and be annoyed that their time was wasted or else be confused. And I don't think you can suppress the title from coming up if the human-readable time was inadvertently hovered. ''Answer: Microformats should not rely on CSS in order to work properly, but again, that discussion can be found here: [[assistive-technology-abbr-results]].''

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* [[date-design-pattern]] is a subset of [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

Template:design patterns

2008-04-28T15:21:13Z

Adactio:

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]], [[date-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]], [[include-pattern-feedback]] {{NewMarker}}
* [[rel-design-pattern]]

date-design-pattern

2008-04-28T15:19:51Z

Adactio:

'''This page is a draft.'''

= Date Design Pattern =

This is a page for exploring a date design pattern. This pattern is a subset of the [[datetime-design-pattern]].

== Purpose ==

Use the [[date-design-pattern]] to make dates that are human readable also formally machine readable.

== Practical Need ==

The [[datetime-design-pattern]] arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]]. While concerns have been raised about the readability of complete datetimes, those concerns don't apply for date stamps that do not include time or timezone information.

The date design pattern provides an internationalized way of representing dates. For example, the string 02/03/01 could represent February 3rd 2001, March 2nd 2001 or even March 1st 2002 depending on the cultural context. The string 2001-03-02 is less ambiguous.

== How to use it ==

The full [[datetime-design-pattern]] has the format:

:<pre>YYYY-MM-DDTHH:MM:SS+ZZ:ZZ</pre>

The date design pattern, which is a subset of the datetime design pattern, has the format:

:<pre>YYYY-MM-DD</pre>

The date design pattern can be used like any other value that uses the [[class-design-pattern]]:

:<pre>YYYY-MM-DD</pre>

The date design pattern can also be used in combination with the [[abbr-design-pattern]] where authors want to provide an alternative representation of the date:

:<pre><abbr class="foo" title="YYYY-MM-DD">Date</abbr></pre>

As with the datetime design pattern, the date design pattern is based on the [[iso-8601|ISO8601]] standard. This standard allows for dates to be written without dashes (YYYYMMDD). This usage is strongly discouraged when publishing microformats as it significantly reduces the readability of the date.

==Current uses==

This pattern can be used in [[hCalendar]] for:

* dtstart
* dtend

In [[hCard]] the date design pattern can be used for:

* bday

This pattern can be used in [[hReview]] for:

* dtreviewed

==Accessibility issues==

Concerns have raised about accessibility issues [http://www.webstandards.org/2007/04/27/haccessibility/] with the [[datetime-design-pattern]] when it is used in conjunction with the [[abbr-design-pattern]]. These concerns are significantly lessened with the [[date-design-pattern]] as only dates, rather than full datetimes, are represented

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* The date design pattern is a subset of the [[datetime-design-pattern]]
* The [[abbr-design-pattern]] can be used by [[date-design-pattern]]
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

events/2008-04-18-fowd

2008-04-03T18:07:53Z

Adactio: /* details */

<h1>Microformats — Building blocks 'for a beautiful web'</h1>

{{TOC-right}}
A workshop at The Future of Web Design. One of several microformats [[events]].

== details ==
<div class="vevent">
;When
:2008-04-18T13:30:00+00:00
;Where
:Kensington Close Hotel, Wrights Lane, London W8 5SP, England
;What
:Microformats — Building blocks 'for a beautiful web'
;Presenter
:[http://www.stuffandnonsense.co.uk/ Andy Clarke]
;Web
: http://futureofwebdesign.com/workshops.html#jumper08
</div>

'''[http://technorati.com/events/microformats.org/wiki/events/microformats.org/wiki/events/2008-04-18-fowd Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

== attendees ==
Add yourself alphabetically by family-name if you're stopping by:

* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

== notes ==
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

* ...



== related pages==
{{events-related-pages}}

events/2008-05-08-xtech

2008-04-03T18:05:44Z

Adactio: /* details */

<h1>Creating portable social networks with microformats</h1>

{{TOC-right}}
A presentation at XTech 2008. One of several microformats [[events]].

== details ==
<div class="vevent">
;When
:2008-05-08T09:45:00+01:00
;Where
:Radisson SAS Royal Hotel, Golden Lane, Dublin 8, Ireland
;What
:Creating portable social networks with microformats
;Presenter
:[[User:Adactio|Jeremy Keith]]
;Web
: http://2008.xtech.org/public/schedule/detail/492
</div>

'''[http://technorati.com/events/microformats.org/wiki/events/microformats.org/wiki/events/2008-05-08-xtech Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

== attendees ==
Add yourself alphabetically by family-name if you're stopping by:

* [[User:Adactio|Jeremy Keith]]
* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

== notes ==
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

* ...



== related pages==
{{events-related-pages}}

events

2008-04-03T17:57:35Z

Adactio: /* Upcoming */

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* ...

== Upcoming ==


Soonest first:

* 2008-04-18: [[events/2008-04-18-fowd|Microformats — Building blocks 'for a beautiful web']] at FOWD 2008 in London — a workshop by Andy Clarke.
* 2008-04-15: [http://socialcamp.wordpress.com (Open)Social(Web)Camp 2008] — SocialCamp (Un)conference @ Open Web Vancouver 2008 - Vancouver, B.C., Canada
* 2008-05-08: [[events/2008-05-08-xtech|Creating portable social networks with microformats]] at XTech 2008 in Dublin — a presentation by Jeremy Keith.
* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] at The Yorkshire Grey — part of London Web Week

== Recent ==
Most recent first:

=== April ===
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2008-04-18-fowd

2008-04-03T17:46:38Z

Adactio:

<h1>Microformats — Building blocks 'for a beautiful web'</h1>

{{TOC-right}}
A workshop at The Future of Web Design. One of several microformats [[events]].

== details ==
<div class="vevent">
;When
:2008-04-18T13:30:00+00:00
;Where
:Kensington Close Hotel, Wrights Lane, London W8 5SP, England
;What
:Microformats — Building blocks 'for a beautiful web'
;Web
: http://futureofwebdesign.com/workshops.html#jumper08
</div>

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

== attendees ==
Add yourself alphabetically by family-name if you're stopping by:

* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

== notes ==
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''fowd fowd2008 fowd08 microformats andyclarke malarkey workshop'''

* ...



== related pages==
{{events-related-pages}}

events

2008-04-03T17:29:07Z

Adactio: /* Upcoming */

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* ...

== Upcoming ==


Soonest first:

* 2008-04-15: [http://socialcamp.wordpress.com (Open)Social(Web)Camp 2008] — SocialCamp (Un)conference @ Open Web Vancouver 2008 - Vancouver, B.C., Canada
* 2008-05-08: [[events/2008-05-08-xtech|Creating portable social networks with microformats]] at XTech 2008 in Dublin — a presentation by Jeremy Keith.
* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] at The Yorkshire Grey — part of London Web Week

== Recent ==
Most recent first:

=== April ===
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events

2008-04-03T17:23:38Z

Adactio: /* Upcoming */

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* ...

== Upcoming ==


Soonest first:

* 2008-04-15: [http://socialcamp.wordpress.com (Open)Social(Web)Camp 2008] — SocialCamp (Un)conference @ Open Web Vancouver 2008 - Vancouver, B.C., Canada
* 2008-05-08: [[events/2008-05-08-xtech|Building portable social networks with microformats]] at XTech 2008 in Dublin — a presentation by Jeremy Keith.
* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] at The Yorkshire Grey — part of London Web Week

== Recent ==
Most recent first:

=== April ===
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2008-05-08-xtech

2008-04-03T17:16:13Z

Adactio:

<h1>Creating portable social networks with microformats</h1>

{{TOC-right}}
A presentation at XTech 2008. One of several microformats [[events]].

== details ==
<div class="vevent">
;When
:2008-05-08T09:45:00+01:00
;Where
:Radisson SAS Royal Hotel, Golden Lane, Dublin 8, Ireland
;What
:Creating portable social networks with microformats
;Web
: http://2008.xtech.org/public/schedule/detail/492
</div>

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

== attendees ==
Add yourself alphabetically by family-name if you're stopping by:

* [[User:Adactio|Jeremy Keith]]
* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

== notes ==
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''xtech xtech2008 jeremykeith portablesocialnetworks socialnetworkportability microformats upcoming:event=354407'''

* ...



== related pages==
{{events-related-pages}}

events

2008-04-03T16:41:02Z

Adactio: /* Microformats related events */

__NOTOC__
=Microformats related events=
Please add any microformats related events (specifically, events where there will be talks on microformats) to this page.

Create a page for each event using the [[events-template|events template]], and list URLs for the event, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages for the schedule/sessions and speakers/venues, or ask the organizers to do so.

== subscribe to or add events to your calendar ==
Subscribe to or add microformats related events to your [[calendar program]]:
{| border="1"
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org</nowiki>''' || '''[http://technorati.com/events/microformats.org/ Add home page events]'''
|-
| Subscribe to '''<nowiki>webcal://feeds.technorati.com/events/microformats.org/wiki/events</nowiki>''' || '''[http://feeds.technorati.com/events/microformats.org/wiki/events Add events page events]'''
|-
|}

==Current==
Events in progress:
* ...

== Upcoming ==


Soonest first:

* 2008-04-15: [http://socialcamp.wordpress.com (Open)Social(Web)Camp 2008] — SocialCamp (Un)conference @ Open Web Vancouver 2008 - Vancouver, B.C., Canada

* 2008-05-27: [[events/2008-london-microformats-vevent|London Microformats vEvent]] — London Microformats vEvent

== Recent ==
Most recent first:

=== April ===
*2008-04-01: [[events/2008-04-01-san-diego-web-standards-group|Microformwhats?]] at San Diego Web Standards Group. A couple of 20-30 minute presentations, time to connect with fellow tag warriors and perhaps some good beer.. http://www.sdwebstandards.com/

=== March ===
*2008-03-28: [[events/2008-03-28-san-diego-dinner|San Diego microformats dinner meetup]] at TBD, San Diego, CA. Tantek and Jeremy were in San Diego and met local microformatters for dinner. http://microformats.com/wiki/events/2008-03-28-san-diego-dinner
*2008-03-07..<abbr style="border:0" class="dtend" title="2008-03-12">11</abbr>: [[events/2008-03-07-sxsw-interactive|SXSW Interactive]] at Austin, TX. http://2008.sxsw.com/interactive
**2008-03-10: [[events/2008-03-10-sxsw-building-blocks|SXSW Interactive - Microformats Building Blocks]] at Austin, TX. 
**2008-03-10: [[events/2008-03-10-sxsw-portability-panel|Building Portable Social Networks]] at South By Southwest Interactive 2008. Thoughts, techniques and technologies that will allow your identity and your contacts to flow freely between social networking sites. http://upcoming.yahoo.com/event/450703/
**2008-03-10: [[events/2008-03-10-sxsw-admins-meetup|SXSW microformats admins meetup]] at Las Manitas, Congress Ave., Austin, TX.

*2008-03-03..<abbr style="border:0" class="dtend" title="2008-03-05">04</abbr>: [[events/2008-03-03-Blogtalk-2008-cork|Mashups, Microformats and the Mobile Web]] at Cork, Ireland. Invited panel discussion at Blogtalk 2008, Cork, Ireland. http://2008.blogtalk.net/invitedspeakers

=== February ===
*2008-02-29 11:15-11:55am: [[events/2008-02-29-fowa-miami-social-networks|FOWA Miami Future of Social Networks]] at Knight Concert Hall, Carnival Centre, Miami, Florida. The Future of Social Networks session http://www.futureofwebapps.com/2008/miami/schedule.php#hcalendar-Presentation-3
*2008-02-28 9am-12:30pm: [[events/2008-02-28-fowa-miami-workshop|FOWA Miami Microformats Workshop]] at Knight Concert Hall, Carnival Centre, Miami, Florida. Introduction to Microformats workshop http://www.futureofwebapps.com/2008/miami/workshops.php#jumper01
*2008-02-16..<abbr style="border:0" class="dtend" title="2008-02-18">17</abbr>: [[events/2008-02-16-semanticcamplondon|SemanticCampLondon]] in London, England. A BarCamp specifically addressing Semantic Web related technologies. [http://semanticcamp.tommorris.org/ SemanticCampLondon]
*2008-02-01..<abbr style="border:0" class="dtend" title="2008-02-04">03</abbr>: [[events/2008-02-01-sgfoocamp|sgfoocamp08]] at Sebastopol, CA. A FooCamp focusing on [[social network portability]]. http://sgfoocamp08.pbwiki.com

=== January ===

*2008-01-31: [[events/2008-01-30-geekdinner|microformats geek dinner]] at San Francisco, CA. An impromptu gathering of geeks. http://pownce.com/t/notes/1276197/
*2008-01-15T13:00:00-0500: [[events/2008-01-15-hresume-webinar|hResume Webinar]] on-line at gotowebinar.com. [http://theryanking.com/ Ryan King] on [[hResume]], with the HR-XML crowd. http://microformats.org/wiki/events/2008-01-15-hresume-webinar
* 2008-01-15: [[events/2008-01-15-barcamp-psi|'BarCamp' on the Power of Information Review Recommendation 8]] at London, England — "To improve [UK] government's responsiveness to demand for public sector information, by July 2008 OPSI should create a web-based channel to gather and assess requests for publication of public sector information."
* 2008-01-05–2008-01-06: [[events/2008-01-05-codefest2008-microformats|CodeFest on Microformats]] at Montréal, Canada and online at http://wiki.facil.qc.ca/CodeFest2008 — Adding microformats to several open source projects

==2007==
See [[events-2007]]

==2006==
See [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}