Microformats Wiki - User contributions [en]

Template:hmedia-related-pages

2013-08-23T00:35:36Z

Jonathantneal: /* Related Pages */

== Related Pages ==

* A new proposal for h-media [https://gist.github.com/jonathantneal/6313548]

* [[hmedia|hMedia]]
* [[hmedia-issues]]
* [[hmedia-brainstorming]]
* [[media-info-examples]]
* [[media-info-formats]]
* [[media-info-brainstorming]]

media-info-brainstorming

2013-08-23T00:34:01Z

Jonathantneal: /* Contributors */

= Brainstorming for Media Microformat =

This is a brainstorm for media microformat. Examples of media-info can be found here [http://microformats.org/wiki/media-info-examples media-info-examples]

== Contributors ==

* [http://napsterization.org/stories/ Mary Hodder]
* [http://onlisareinsradar.com/ Lisa Rein]
* [http://microformats.org/wiki/User:ChrisNewell Chris Newell]
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
* [[User:WebOrganics|Martin McEvoy]]
* [[User:JonathanTNeal|Jonathan Neal]]

== The Problem ==

There are many ways to publish media by users, but as people try to access those remixing and aggregation become more and more prevalent, having consistent records becomes important. Audio, photos and video show up in each other's publishing spaces, even though they are unique media objects. A photo might be next to the link for an audio piece, as it's visual artwork. A video can be comprised of quotes of other videos, photos and audio. Still photos can be made from videos. All three types of objects can contain subsets of media that is tagged and described. Having a single publishing format to relate them as needed in an organized structure makes sense.

== Elements that come up often in practice ==
Here are some examples of elements that might be included because they seem to come up often in user generated media publishing, either on their own blogs or on service sites, include the following:

Base elements:
* Title
* Html URL
* Media URL
* Image URL (video and audio)
* Tags
* Description / summary
* Quotes (subsets of the object: a video quote and tags/description associated with it, a region annotation note for a photo, or the quote of a podcast or audio piece, with tags/description -- the technical detail for these subsets exists in the 'more info' section below)
* Creator
* License (defaults to copyright, if none exists, but it's there, by US law, and many other areas of the world)
* XML Feed URL
* Contributor

and for audio and visual:
* Episode
* Duration
* Interval

Other info:
(This is not the same for all types of media, and is published by users in very limited ways in practice, or is captured from the device or service or in some way, invisible to the user, and therefore often depends on a service to pick it up. It should only appear in a publishing tool under 'more data' at then end, for enthusiast users.)

<table border="1" cellspacing="2" cellpadding="2">

<tr><th>JPG</th><th>Video</th><th>Audio</th></tr>

<tr><th>Device</th><th>Device</th><th>Device</th></tr>

<tr><th>Ratio</th><th>Aspect Ratio</th><th>?</th></tr>

<tr><th>file size</th><th>file size</th><th>file size</th></tr>

<tr><th>.</th><th>audio codec</th><th>audio codec</th></tr>

<tr><th>.</th><th>video codec</th><th>.</th></tr>

<tr><th>.</th><th>bit / frame rate</th><th>bit rate</th></tr>

<tr><th>Portrait or Landscape</th><th>.</th><th>.</th></tr>

<tr><th>Region Annotation (subphotos: calculation of location, size)</th><th>Quotes of Video (subvideo: in and out points)</th><th>Quotes of Audio (subaudio: in and out points)</th></tr>

<tr><th>iPod compliant?</th><th>iPod compliant?</th><th>iPod compliant?</th></tr>

<tr><th>Time</th><th>Time</th><th>Date</th></tr>

<tr><th>Date</th><th>Date</th><th>Date</th></tr>

<tr><th>Inclusion in playlist?</th><th>Inclusion in playlist?</th><th>Inclusion in playlist?</th></tr>

</table>
 

== Combining with other microformats ==

Although media items are sometimes presented in isolation they are often found in data structures that are supported by existing microformats. It should therefore be possible to use the media microformat as a child (or in some cases a parent) of these microformats.

=== [http://microformats.org/wiki/hatom hAtom] ===
Podcast feeds reference a sequence of media items. A media microformat could therefore be used as a child element of hAtom.

=== [http://microformats.org/wiki/hcalendar hCalendar] ===
A media microformat may used to describe a continuous media stream e.g. a TV channel. An event or a schedule of events on the channel can be signaled using hEvents as child elements. This combination would provide what is necessary to capture a specific event; the media stream information and the timing information.

== Schema ==

=== Analysis of all Media Info examples ===

Common discovered properties occuring 70% or more of the time across all [[media-info-examples|media info examples]] completed 2008-11-07

<table border="1">
<tr>
<th>[[media-info-examples#Analysis_of_Photo_Sites|Photo]]</th>
<th>[[media-info-examples#Analysis_of_Video_Sites|Video]]</th>
<th>[[media-info-examples#Analysis_of_Podcasting_Sites|Podcasting]]</th>
<th>[[media-info-examples#Analysis_of_Individual_Publishing_of_Speech_Sites|Speech]]</th>
<th>[[media-info-examples#Analysis_of_Music_Sites|Music]]</th>
</tr>
<tr>
<td>Title 93.33%</td>
<td>Title 100%</td>
<td>Title 100%</td>
<td>Title 100%</td>
<td>Title 92%</td>
</tr>
<tr>
<td>Creator 96.66%</td>
<td></td>
<td>Creator 95.65%</td>
<td>Creator 100%</td>
<td>Creator 100%</td>
</tr>
<tr>
<td>Description 73.33%</td>
<td></td>
<td>Description 95.65%</td>
<td>Description 100%</td>
<td></td>
</tr>
<tr>
<td>Photo 100%</td>
<td>Video 100%</td>
<td>Download 95.65%</td>
<td>Download 95.65%</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Published 91.42%</td>
<td>Published 95.65%</td>
<td>Published 83.33%</td>
<td>Published 77%</td>
</tr>
<tr>
<td>Comments 70%</td>
<td>Comments 88.57%</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Feed 100%</td>
<td>Feed 100%</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Tag 71.42%</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Tracks 85%</td>
</tr>
</table>

=== hMedia Schema ===

Proposed hmedia schema and description defined by common elements discovered during the analysis of all [[media-info-brainstorming#Analysis_of_all_Media_Info_examples|Media Info examples]].

<table border="1">
<tr>
<th><code>hmedia</code></th>
<th>Definition</th>
</tr>
<tr>
<td><code>fn</code></td>
<td>The name of a media. Reused from [[hcard|hcard]]</td>
</tr>
<tr>
<td><code>contributor</code></td>
<td>A Contributor is any person or organization that takes part in the creation or distribution of the Media. Reused from [[haudio|haudio]]</td>
</tr>
<tr>
<td><code>description</code></td>
<td>A full-text description of the Media. Reused from [[hreview|hreview]]</td>
</tr>
<tr>
<td><code>photo</code></td>
<td>An embedded Image or Photograph of the Media. Reused from [[hcard|hcard]]</td>
</tr>
<tr>
<td><code>video</code></td>
<td>The contents are an embedded video or movie of the Media. {{NewMarker}}</td>
</tr>
<tr>
<td><code>enclosure</code></td>
<td>Indicates that the referred url is a download of the Media. Using [[rel-enclosure|rel-enclosure]].</td>
</tr>
<tr>
<td><code>published</code></td>
<td>Represents the date that the Media was made available to the public. Reused from [[hatom|hatom]]</td>
</tr>
<tr>
<td><code>comment</code></td>
<td>A user/visitor submitted comment on the media, see: [[media-info-brainstorming#Media_Comments|Media Comments]]{{NewMarker}}</td>
</tr>
<tr>
<td><code>alternate</code></td>
<td>Designates an alternate version for the document or Media typically an RSS, Atom or XML feed using the [[rel-design-pattern]] {{NewMarker}}</td>
</tr>
<tr>
<td><code>category</code></td>
<td>An author-designated "category" or a keyword/subject of the Media. Reused from [[hcalendar|hcalendar]], additionaly keywords may be defined using [[rel-tag|rel-tag]].</td>
</tr>
<tr>
<td><code>item</code></td>
<td>A container element for another Media item. Reused from [[haudio|haudio]]</td>
</tr>
</table>

=== Media Comments ===

User submitted comments are highly prevalent across all media domains the following table is a definition of the discovered elements of a comment. A separate analysis was made on 25 model examples, the results are available at [[media-info-examples#Media_comments|Media comments examples]]

Please see the [[comment|comment discussion]] on how to mark up a comment

== Comments ==

=== Differentiating File Content from File Format ===

We should consider splitting file content from file format. A song (content) can be represented as an MP3 audio file (format), or an MPEG-2 music video (format). media-info should be used to describe file content with a separate microformat or link-rel design pattern to describe file format.

Example 1:

* media-info (content): A song called "Hung Up" by "Madonna"
* file-format (format): 4.5MB MP3 file encoded at 192Kbps bitrate.

Example 2:

* media-info (content): A music video called "Hung Up" by "Madonna"
* file-format (format): 35MB AVI file, MP3 audio codec encoded at 192Kbps, DiVX video codec encoded at 600Kbps

[[User:ManuSporny|ManuSporny]] 06:50, 5 Apr 2007 (PDT)

=== Microformats and Democracy Player/Miro ===

Democracy (soon to be Miro) is a desktop program attempting to create a more television like experience for internet video.
Microformats present several unique challenges to our project. This is my (Nick Nassar's) attempt to summarize them. My opinions don't reflect the opinion of my employer (PCF). My email address at pculture.org is nassar.

Re-reading this, I realize it sounds very negative. Please, tell me why I'm totally wrong. I hope I'm totally wrong. :)

==== Loose specifications are difficult to parse and create ====

This is a problem we're seeing with RSS that could potentially multiply with the popularity of microformats.

The RSS "standard" is very loose, and our experience is that most feeds don't even conform to that standard. Because of this, we lose the main benefits of XML: easy parsing and creation. On the parsing end, we're forced to use complex third party libraries such as [http://www.feedparser.org/ Feed Parser] rather than just being able to parse with a simple XML parser. This is the same problem we saw with HTML in the 90s where the "standard" involves doing the right thing in a lot of non-standard cases.

Content creators need to use complex validators like [http://www.feedvalidator.org/ Feed Validator] rather than just being able to write valid XML so they make sure they don't do things that confuse reg-exp based parsers. It's much more difficult to create a program you trust to conform to a loose spec than one you trust to conform to a more rigid spec.

For search engines and other applications where exact data isn't important, this isn't a big deal. For an application that's expected to show exactly the videos the author published, it's a lot of work to get the parsing right. Even in "valid" RSS we see people faking the length and type attributes for enclosures all the time, forcing programs like ours not to trust that information.

Microformats could easily make those problems explode. In general, microformats are more dangerous because they're even looser, and they're embedded in the XHTML, so the data is tied to the presentation. In practice, you need extra divs and spans to get XHTML formatting right. Inserting that extra div tag to get the formatting right will change the data. The formats must be well defined enough to deal with this.

When I tell this to people, they say "Nick, you're crazy. It's easy to generate valid XML." To prove my point, there are two real world examples of this on your own site. The [http://microformats.org/code/hcalendar/creator hCalendar creator] and the [http://microformats.org/code/hcard/creator hCard creator] don't deal with quotes and angle brackets in the input, resulting in invalid XHTML when those characters are included. I don't bring this up to pick on this site, just to point out that this sort of mistake is the norm in supposedly easy to create XML formats.

One way to mostly solve this is to write a parser, a validator, and a generator for each format when you define it. This way there's a de facto correct implementation that can act like Netscape did for HTML or the perl implementation does for perl. It would also force a real world implementation of the "standard" before it gets adopted. If it's difficult to parse correctly, you can go back and redefine it to be more easily parsable.

''Strict formats are easier for everyone. As long as you insist on keeping it loose, writing parsers, validators, and generators for each format are a step forward.''

===== HTML data =====

A complex problem for authors of feed readers is how to deal with HTML encoded areas such as the description. HTML can contain JavaScript, plugins, and other "dangerous" content that you don't necessarily want in your program. [http://www.feedparser.org/ Feed Parser] only allows white listed tags and attributes. This is generally accepted as the right thing to do, but causes problems in programs like Democracy player when content authors expect certain tags to appear but they get blocked. This might be tricky when combined with the problem of allowing extra divs and spans without altering the data itself.

A microformat spec should include details on what fields content creators can expect to show up in an application such as Democracy Player

===== Character Sets =====

A very common problem with RSS feeds is incorrect character sets. The XML header might specify utf-8, but the document is actually latin-1, which causes it not to parse. Requiring or strongly recommending that all microformat documents are UTF-8 might improve the situation.

==== Mime types are useful ====

Another problem we're seeing with RSS that could get worse with microformats is the lack of a mime type. There is no standard RSS mimetype and extension (although application/xml+rss and .rss are finally catching on), so an application doesn't know what to do with an RSS file saved to disk. We have to assume that text/xml links sent into Democracy are RSS. Feed readers can't just associate with the mime type like most programs, they need to hook in in different ways.

Combining data into XHTML means there's no way to determine what programs can handle that page without downloading it first. If an XHTML page with media information is saved to disk, we have no way of determining it has data that can be used in Democracy player without first opening it up.

''This is a fundamental problem with microformats. You will never be able to load microformat documents into the correct program without parsing them.''

==== Media specific concerns ====

It should always be possible to use media microformats as a feed. It would be a very poor experience if, for example, media items were duplicated in programs like Democracy whenever their HTML changed. Making them an extension of the hAtom format should cover this. Recommend that real world implementations do correct HTTP caching so programs like Democracy can avoid downloading the entire file every time.

The format shouldn't require any fields other than URL and title. As is, most sites fake the length and type attributes for RSS enclosures. Don't make people fake data they don't have.

Tag each piece of data. It's difficult for us to parse strings like "35MB AVI file, MP3 audio codec encoded at 192Kbps, DiVX video codec encoded at 600Kbp" into anything useful, but if those fields are separated out with span tags, we can actually use that data.

''Make media microformats feeds. Don't require any fields. Tag each piece of data.''

{{Template:hmedia-related-pages}}

recently-in-microformats

2013-05-30T17:33:56Z

Jonathantneal: /* new rel me support */

<entry-title>Recently in microformats</entry-title>
'''<dfn>Recently in microformats</dfn>''' is a place to collaboratively draft blog posts about what's recently going on with microformats. Feel free to write things in any of the sections below, and ping an [[admin]] on [[IRC]] when you'd like your writing reviewed and posted to the [http://microformats.org blog].

== Recently in microformats ==
In the past several months there has been a considerable increase in activity in, with, and around microformats. From continued growth of stalwarts like [[hCard]] and [[rel-me]], to emergence of federated indieweb comments based on the [[microformats2]] [[h-entry]] and [[h-card]]. Search engines are crawling more microformats than ever, most recently [[hAtom]] and [[hMedia]]. Lastly, informal microformats meetups, as well as sessions and presentations at conferences, continue at a good monthly pace.

=== New implementations ===
New real world publishing and uses of microformats emerge every week. Here are a few examples that are enabling and enhancing key features on the web.

==== new rel me support ====
Both [https://app.net App.net] and [https://svbtle.com Svbtle] now support [[rel-me]] for user profiles linking to their home pages.

https://twitter.com/microformats/status/328992420463271936

App.net in particular implemented their Domain Claiming feature based on rel-me linking from your personal site to your app.net profile (and entering your personal site in your app.net profile).

Thus the list of OAuth providers available to authenticate for [[web sign-in]] backends continues to grow. The [[IndieAuth]] library and service that implements [[RelMeAuth]] has already added support for App.net as a RelMeAuth authentication provider.

==== Storytlr using microformats2 for indieweb comments ====
The [http://indiewebcamp.com/Storytlr Storytlr] open source blogging tool now consumes [[microformats2]], in particular [[h-entry]] and [[h-card]] to [http://indiewebcamp.com/comment#Display_received_comments display comments] made from indieweb blog to [http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html another].

==== Taproot and p3k reply contexts ====
The [http://indiewebcamp.com/Taproot Taproot] and [http://indiewebcamp.com/p3k p3k] blogging tools are also consuming [[h-entry]] and [[h-card]] to display original post context when publishing replies.

==== Google is parsing hMedia ====
As of somewhere in the end of 2012 or early 2013, Google has began parsing hMedia.

While not officially supporting hMedia like they do in the [http://support.google.com/webmasters/bin/answer.py?hl=en&answer=99170 rich snippet support page] for [[hCard]], [[hReview]], [[hCalendar]] (event too)& [[hRecipe]], Google surprisingly has began to show the [[hMedia]] in the webmaster tools result.

===== Does Google really support [[hMedia]]? =====
Officially - I could not find anything related to think that Google actually support it or can read it, even when searching "Google hMedia" I could not find anything related to the fact that Google supporting [[hMedia]].

The main focus I will take is for the [[hMedia]] is the image deceleration, because as so far it is the only type within the [[hMedia]] schema that I could say that Google supports.
===== Google! where is my hMedia? =====
The first thing many people do to find out if they have coded their web page properly with the [[Microformats]], is entering [http://www.google.com/webmasters/tools/richsnippets Google Rich Snippet Tool] and check their page to see if Google is parsing it correctly.

The first time I have used the [[hMedia]] schema, I could not find anything that could say that Google parses my [[hMedia]].

Example: lets parse this page: [http://goo.gl/CZQFu http://goo.gl/CZQFu] And we will get:

[http://i.imgur.com/FCRm58s.png http://i.imgur.com/FCRm58s.png]

By this Google gives us the impression that it does not parse [[hMedia]].

===== hMedia! There you are =====
I have personally used this [[hMedia]] image tagging since the 2012, and Google webmaster tools hasn`t shown me any information about reading the hMedia, somewhere near the start of year 2013, I have found Google has began parsing almost all of the [[hMedia]] photos I have tagged.

[http://i.imgur.com/LcDYDSz.png http://i.imgur.com/LcDYDSz.png]

'''Please share your thoughts regarding the parsing of [[hMedia]], and your opinions about what [[hMedia]] should include in [[Microformats2]], and if you have found any other type of [[hMedia]] schema`s that Google parses. '''

Thanks to [[User:ISRAELi|Aviran Zazon]] for investigating, screenshotting, and writing up his research on Google's hMedia support. Content has been reformatted for this blog post.

=== In articles and other web sites ===
* ...

=== Face-to-Face ===
* [[events/2013-03-01-microformats-dinner]]
* [[events/2013-04-02-html5devconf-microformats2-html5]]
** video: http://www.youtube.com/watch?v=BNk-Bkc-CAo
* [[events/2013-04-02-microformats-dinner]]
* [[events/2013-04-08-sensored-meetup]]
* [[events/2013-05-14-microformats-google-io]]
* ...

=== New microformats and rel values ===
* [[rel-in-reply-to]]
* [[rel-syndication]]
* [[rsvp]]
* [[sheet-music]] is being developed
* ...

=== Interesting wiki updates ===
* New [[Main_Page-ka|Georgian]] wiki translation started!

=== From Twitter ===
* ...

=== Interesting Discussions on IRC and mailing lists ===
* ...

== Past ==
Early on we did "[[this-week|This week in microformats]]" when there were weekly changes and discussions. See here for examples of that. These early posts are excellent examples, e.g. for guidance on formatting:
* [http://microformats.org/blog/2006/11/27/this-week-1/ This Week #1]
* [http://microformats.org/blog/2006/12/04/this-week-2/ This Week #2]

irc-people

2013-05-22T17:58:31Z

Jonathantneal: I exist a little differently than I remember.

A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).

* {{irc user|Amodal1| amodal1|-0500/-0600}}
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}
* {{irc user|Adam Craven|AdamCraven|+0000}}
* {{irc user|Alenonimo|Alenonimo|-0300}}
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}
* {{irc user|Axelator|ax|-0700}}
* {{irc user|Tomasino|aloneone|-0500}}
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}
* {{irc user|Amette|amette|+1000}}
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}
* {{irc user|Andr3|andr3|+0000}}
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}
* {{irc user|AndrewDisley|AndrewDisley|+0000}}
* {{irc user|Andrii Ponomarov|Andrii|+0300}}
* {{irc user|AngeloGladding|angelogladding|-0800/-0700}}
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}
* {{irc user|Ashe Dryden|Ashe|-600}}
* {{irc user|Atamido|Atamido|-0600/-0500}}
* {{irc user|Barce|Barce|-0800/-0700}}
* {{irc user|Azathoth|Florian Beer|+1000}}
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}
* {{irc user|BarnabyWalters|barnabywalters|+0000}}
* {{irc user|Belling|Belling|-0800/-0700}}
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|-0800/-0700}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|BluesMoon|bluesmoon|+0530}}
* {{irc user|BobChao|BobChao|+0800}}
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}
* {{irc user|Oli|boblet|+0900}}
* {{irc user|Boneill|boneill|+0000}}
* {{irc user|Brian|briansuda|+0000}}
* {{irc user|TimT|bringo|-0800/-0700}}
* {{irc user|Briski|Briski|+0000}}
* {{irc user|ChrisBroadfoot|broady|+1000}}
* {{irc user|BryanL|BryanL|-0500/-0400}}
* {{irc user|BryanRieger|Bryan Rieger|+0000}}
* {{irc user|Bug-E|Bug-E|+0200}}
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}
* {{irc user|Colin_Barrett|cbarrett|-1000}}
* {{irc user|Cognizance|Cognizance|-0800/-0700}}
* {{irc user|Colares|colares|-0300}}
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}
* {{irc user|CoryGwin|corygwin|-0500/-0600}}
* {{irc user|Cgriego|cgriego|-0600/-0500}}
* {{irc user|Charlvn|Charl|+0200/+0200}}
* {{irc user|CharlesRoper|charles_r|0000/+0100}}
* {{irc user|ChiefRA|ChiefRA|+0200}}
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}
* {{irc user|Cloud|Cloud|+0000}}
* {{irc user|Cruster|cruster|+0200}}
* {{irc user|Csarven|csarven|-0500/-0400}}
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}
* {{irc user|DanC|DanC|-0600/-0500}}
* {{irc user|DanielBurka|DanielBurka|-0400}}
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}
* {{irc user|DannyAyers|danja|+0100/+0200}}
* {{irc user|Dave Cardwell|davecardwell|+0000}}
* {{irc user|DavidMead|DavidMead|-0400}}
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}
* {{irc user|DBounds|Darren Bounds|-0500}}
* {{irc user|Ddonat|David Gratton|-0800/-700}}
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}
* {{irc user|DeanEro|deanero|-0800/-0700}}
* {{irc user|DeepText|Deep Text|-0800/-0700}}
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}
* {{irc user|DiegoBudny|DiegoBudny|-unspecified-}}
* {{irc user|DKerzman|DKerzman|-0600}}
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}
* {{irc user|Dotjay|dotjay|+0000}}
* {{irc user|Dreamisle|dreamisle|-0500}}
* {{irc user|DrErnie|DrErnie|-0800/-0700}}
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}
* {{irc user|DrewBell|droob|-0600/-0500}}
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}
* {{irc user|Ed Summers|edsu|-0500/-0400}}
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")
* {{irc user|Evan|evanpro|-0500}}
* {{irc user|Evan|e_s_p|-0500}}
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}
* {{irc user|EdwardWelker|ewelker|-0500}}
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}
* {{irc user|Fil|Fil|+0200}}
* {{irc user|CFinke|Finke|-0700/-0600}}
* {{irc user|FoundAtion|Foundation|-0800}}
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}
* {{irc user|GarethR|garethr|+0000/+0100}}
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}
* {{irc user|Grantbow|Grantbow|-0800/-0700}}
* {{irc user|Griffin|Griffin|-0600/-0500}}
* {{irc user|Guillaume Lebleu|glebleu|-0800}}
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}
* {{irc user|HenrichPoehls|HenrichP|+0100}}
* {{irc user|IanHickson|Hixie|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}
* {{irc user|iSRAELi|iSRAELi|+0200}}
* {{irc user|Hlb|hlb|+0800-0700}}
* {{irc user|EdwardOConnor|hober|-0800/-0700}}
* {{irc user|Ichigo|ichigo|+1000}}
* {{irc user|Alper|illustir|+0100}}
* {{irc user|Inkbase|inkbase|-0800/-0700}}
* {{irc user|IwaiMasaharu|iwaim|+0900}}
* {{irc user|Izo|IZO|-unspecified-}}
* {{irc user|Jabz|Jabz|+0000}}
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}
* {{irc user|JayMyers|jaymyers|-0600/-0500}}
* {{irc user|JoeGregorio|jcgregorio|-unspecified-}}
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}
* {{irc user|Adactio|Jeremy Keith|+0000}}
* {{irc user|jrodgers|JesseRodgers|-0500}}
* {{irc user|JasonK|jkridner|-0600/-0500}}
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}
* {{irc user|jesudasjj|jesudas nadar|+0530}}
* {{irc user|JimboJW|jimbojw|-0600/-0500}}
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}
* {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}
* {{irc user|JonathanTNeal|JonathanTNeal|-0800/-0700}}
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}
* {{irc user|JulianStahnke|julianstahnke|+0000}}
* {{irc user|Juraj|jurajsivak|+0100}}
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}
* {{irc user|Keri Henare|kerihenare|+1200}}
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* {{irc user|RyanKing|kingryan|-0800/-0700}}
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}
* {{irc user|Levitation|levitation[A]|+0200/+0300}}
* {{irc user|Linmic|linmic|+0800-0700}}
* {{irc user|Loiseau2nuit|Loiseau2nuit|+0100}} (Fr.)
* {{irc user|MarkNg|madness|+0000/+0100}}
* {{irc user|Mark Mansour|Mark Mansour|+1100}}
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}
* {{irc user|Maddiin|Martin Czura|+0100}}
* {{irc user|LarsStrojny|mastaYoda|+0100}}
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}
* {{irc user|Groningen|Matthias Kluth|+0100}}
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}
* {{irc user|CiaranMc|McNulty|+0000/+0100}}
* {{irc user|MicroAngelo|MicroAngelo|+0000/+0100}}
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}
* {{irc user|MikeKaply|mkaply|-0600/-0500}}
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}
* {{irc user|MWTE|mwte|+0000/+0100}}
* {{irc user|RobManson|nambor|+1000}}
* {{irc user|Natalie Downe|NatBat|+0000}}
* {{irc user|Naterkane|Nater Kane|-0500}}
* {{irc user|Nelix|nelix|+1000}}
* {{irc user|Neuro|neuro|+0000/+0100}}
* {{irc user|Niekie|niekie|+0100/+0200}}
* {{irc user|NTollervey|ntoll|+0000/+0100}}
* {{irc user|Pawlik|pawlik|+0100/+0200}}
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}
* {{irc user|Phae|Phae|+0000/+0100}}
* {{irc user|pius|Pius Uzamere|+0500}}
* {{irc user|PJKix|pjkix|-0800/-700}}
* {{irc user|PriitLaes|plaes|+0200/+0300}}
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}
* {{irc user|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}
* {{irc user|DavidOsolkowski|qid|-0500}}
* {{irc user|RCanine|RCanine|-0500/-0400}}
* {{irc user|Remi|Remi|-0500/-0400}}
* {{irc user|ZachCarter|riah|-0500/-0400}}
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}
* {{irc user|RobLinton|RobLinton|-0800/-0700}}
* {{irc user|Ronnos|Ron Kok|+0000}}
* {{irc user|SamJohnston|samj|+0100/+0200}}
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}
* {{irc user|sebheath|sebheath|-0500/-0400}}
* {{irc user|ScottNelle|snelle|-0500/-0400}}
* {{irc user|ScottRozic|gravitas|-0500/+0100}}
* {{irc user|Dana Benson|Snowden|-0800/-0700}}
* {{irc user|SinDoc|SinDoc|+0100/+0200}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Savell Martin|Savell|+0000/+0000}}
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}
* {{irc user|Stii|Stii|+0200 GMT}}
* {{irc user|ReinierZ|surial|+0100 GMT}}
* {{irc user|SuperPhly|SuperPhly|-600/-500}}
* {{irc user|SyedSRahman|syedsrahman|+0530}}
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}
* {{irc user|DavidLehn|taaz|-0500/-0400}}
* {{irc user|Tantek|tantek|-0800/-0700}}
* {{irc user|tbmartin|tbmartin|-0800/-0700}}
* {{irc user|themattharris|themattharris|-0800/-0700}}
* {{irc user|Wojciech|theanxy|+0100/+0200}}
* {{irc user|TheJbf|thejbf|+0100/+0200}}
* {{irc user|TheSisb|TheSisb|-0800/-0700}}
* {{irc user|Thierrymarianne|Thierry Marianne|+0100/+0200}}
* {{irc user|Thomasknoll|thomasknoll|-0800}}
* {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}
* {{irc user|TobyInk|tobyink|+0000/+0100}}
* {{irc user|TomMorris|tommorris|+0000/+0100}}
* {{irc user|Trovster|trovster|-0800/-0700}}
* {{irc user|Vadania|vadania|-0600/-0700}}
* {{irc user|Vant|vant|+0900}}
* {{irc user|venkateswaran|vensilver|+5.30 GMT}}
* {{irc user|Victor|victor|+0100/+0200}}
* {{irc user|V-I-P|V-I-P|+0100/+0200}}
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}
* {{irc user|WebOrganics|weborganics|+0100}}
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}
* {{irc user|Richard Conyard|WhiskeyM|+0000}}
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}
* {{irc user|StevenWoods|woodss|+0000 GMT}}
* {{irc user|ChristopheDucamp|xtof_fr|+0000/+0100}}
* {{irc user|Ianloic|yakk|-0800/-0700}}
* {{irc user|ZimbaTm|zimbatm|+0100}}
* {{irc user|PeterHellberg|zil|+0100}}
* {{irc user|Kiryl Zhybul|zkv|+0400}}

Needs alpha sorting into the above list (please help!)

* {{irc user|Bui Thanh Hai|haibtdt}}
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}
* {{irc user|Steven Osborn|steve918|-0700/-0800}}
* {{irc user|Trodrigues|trodrigues|+0000}}
* {{irc user|Epicurious|epicurious|+0000/+0100}}
* {{irc user|GermanMartinez|German|-0500}}

Inactive:
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.

irc-people

2013-05-22T17:57:41Z

Jonathantneal: I exist.

A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).

* {{irc user|Amodal1| amodal1|-0500/-0600}}
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}
* {{irc user|Adam Craven|AdamCraven|+0000}}
* {{irc user|Alenonimo|Alenonimo|-0300}}
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}
* {{irc user|Axelator|ax|-0700}}
* {{irc user|Tomasino|aloneone|-0500}}
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}
* {{irc user|Amette|amette|+1000}}
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}
* {{irc user|Andr3|andr3|+0000}}
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}
* {{irc user|AndrewDisley|AndrewDisley|+0000}}
* {{irc user|Andrii Ponomarov|Andrii|+0300}}
* {{irc user|AngeloGladding|angelogladding|-0800/-0700}}
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}
* {{irc user|Ashe Dryden|Ashe|-600}}
* {{irc user|Atamido|Atamido|-0600/-0500}}
* {{irc user|Barce|Barce|-0800/-0700}}
* {{irc user|Azathoth|Florian Beer|+1000}}
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}
* {{irc user|BarnabyWalters|barnabywalters|+0000}}
* {{irc user|Belling|Belling|-0800/-0700}}
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|-0800/-0700}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|BluesMoon|bluesmoon|+0530}}
* {{irc user|BobChao|BobChao|+0800}}
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}
* {{irc user|Oli|boblet|+0900}}
* {{irc user|Boneill|boneill|+0000}}
* {{irc user|Brian|briansuda|+0000}}
* {{irc user|TimT|bringo|-0800/-0700}}
* {{irc user|Briski|Briski|+0000}}
* {{irc user|ChrisBroadfoot|broady|+1000}}
* {{irc user|BryanL|BryanL|-0500/-0400}}
* {{irc user|BryanRieger|Bryan Rieger|+0000}}
* {{irc user|Bug-E|Bug-E|+0200}}
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}
* {{irc user|Colin_Barrett|cbarrett|-1000}}
* {{irc user|Cognizance|Cognizance|-0800/-0700}}
* {{irc user|Colares|colares|-0300}}
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}
* {{irc user|CoryGwin|corygwin|-0500/-0600}}
* {{irc user|Cgriego|cgriego|-0600/-0500}}
* {{irc user|Charlvn|Charl|+0200/+0200}}
* {{irc user|CharlesRoper|charles_r|0000/+0100}}
* {{irc user|ChiefRA|ChiefRA|+0200}}
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}
* {{irc user|Cloud|Cloud|+0000}}
* {{irc user|Cruster|cruster|+0200}}
* {{irc user|Csarven|csarven|-0500/-0400}}
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}
* {{irc user|DanC|DanC|-0600/-0500}}
* {{irc user|DanielBurka|DanielBurka|-0400}}
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}
* {{irc user|DannyAyers|danja|+0100/+0200}}
* {{irc user|Dave Cardwell|davecardwell|+0000}}
* {{irc user|DavidMead|DavidMead|-0400}}
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}
* {{irc user|DBounds|Darren Bounds|-0500}}
* {{irc user|Ddonat|David Gratton|-0800/-700}}
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}
* {{irc user|DeanEro|deanero|-0800/-0700}}
* {{irc user|DeepText|Deep Text|-0800/-0700}}
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}
* {{irc user|DiegoBudny|DiegoBudny|-unspecified-}}
* {{irc user|DKerzman|DKerzman|-0600}}
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}
* {{irc user|Dotjay|dotjay|+0000}}
* {{irc user|Dreamisle|dreamisle|-0500}}
* {{irc user|DrErnie|DrErnie|-0800/-0700}}
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}
* {{irc user|DrewBell|droob|-0600/-0500}}
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}
* {{irc user|Ed Summers|edsu|-0500/-0400}}
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")
* {{irc user|Evan|evanpro|-0500}}
* {{irc user|Evan|e_s_p|-0500}}
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}
* {{irc user|EdwardWelker|ewelker|-0500}}
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}
* {{irc user|Fil|Fil|+0200}}
* {{irc user|CFinke|Finke|-0700/-0600}}
* {{irc user|FoundAtion|Foundation|-0800}}
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}
* {{irc user|GarethR|garethr|+0000/+0100}}
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}
* {{irc user|Grantbow|Grantbow|-0800/-0700}}
* {{irc user|Griffin|Griffin|-0600/-0500}}
* {{irc user|Guillaume Lebleu|glebleu|-0800}}
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}
* {{irc user|HenrichPoehls|HenrichP|+0100}}
* {{irc user|IanHickson|Hixie|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}
* {{irc user|iSRAELi|iSRAELi|+0200}}
* {{irc user|Hlb|hlb|+0800-0700}}
* {{irc user|EdwardOConnor|hober|-0800/-0700}}
* {{irc user|Ichigo|ichigo|+1000}}
* {{irc user|Alper|illustir|+0100}}
* {{irc user|Inkbase|inkbase|-0800/-0700}}
* {{irc user|IwaiMasaharu|iwaim|+0900}}
* {{irc user|Izo|IZO|-unspecified-}}
* {{irc user|Jabz|Jabz|+0000}}
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}
* {{irc user|JayMyers|jaymyers|-0600/-0500}}
* {{irc user|JoeGregorio|jcgregorio|-unspecified-}}
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}
* {{irc user|Adactio|Jeremy Keith|+0000}}
* {{irc user|jrodgers|JesseRodgers|-0500}}
* {{irc user|JasonK|jkridner|-0600/-0500}}
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}
* {{irc user|jesudasjj|jesudas nadar|+0530}}
* {{irc user|JimboJW|jimbojw|-0600/-0500}}
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}
* {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}
* {{irc user|JonathanNeal|JonathanNeal|-0800/-0700}}
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}
* {{irc user|JulianStahnke|julianstahnke|+0000}}
* {{irc user|Juraj|jurajsivak|+0100}}
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}
* {{irc user|Keri Henare|kerihenare|+1200}}
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* {{irc user|RyanKing|kingryan|-0800/-0700}}
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}
* {{irc user|Levitation|levitation[A]|+0200/+0300}}
* {{irc user|Linmic|linmic|+0800-0700}}
* {{irc user|Loiseau2nuit|Loiseau2nuit|+0100}} (Fr.)
* {{irc user|MarkNg|madness|+0000/+0100}}
* {{irc user|Mark Mansour|Mark Mansour|+1100}}
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}
* {{irc user|Maddiin|Martin Czura|+0100}}
* {{irc user|LarsStrojny|mastaYoda|+0100}}
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}
* {{irc user|Groningen|Matthias Kluth|+0100}}
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}
* {{irc user|CiaranMc|McNulty|+0000/+0100}}
* {{irc user|MicroAngelo|MicroAngelo|+0000/+0100}}
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}
* {{irc user|MikeKaply|mkaply|-0600/-0500}}
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}
* {{irc user|MWTE|mwte|+0000/+0100}}
* {{irc user|RobManson|nambor|+1000}}
* {{irc user|Natalie Downe|NatBat|+0000}}
* {{irc user|Naterkane|Nater Kane|-0500}}
* {{irc user|Nelix|nelix|+1000}}
* {{irc user|Neuro|neuro|+0000/+0100}}
* {{irc user|Niekie|niekie|+0100/+0200}}
* {{irc user|NTollervey|ntoll|+0000/+0100}}
* {{irc user|Pawlik|pawlik|+0100/+0200}}
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}
* {{irc user|Phae|Phae|+0000/+0100}}
* {{irc user|pius|Pius Uzamere|+0500}}
* {{irc user|PJKix|pjkix|-0800/-700}}
* {{irc user|PriitLaes|plaes|+0200/+0300}}
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}
* {{irc user|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}
* {{irc user|DavidOsolkowski|qid|-0500}}
* {{irc user|RCanine|RCanine|-0500/-0400}}
* {{irc user|Remi|Remi|-0500/-0400}}
* {{irc user|ZachCarter|riah|-0500/-0400}}
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}
* {{irc user|RobLinton|RobLinton|-0800/-0700}}
* {{irc user|Ronnos|Ron Kok|+0000}}
* {{irc user|SamJohnston|samj|+0100/+0200}}
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}
* {{irc user|sebheath|sebheath|-0500/-0400}}
* {{irc user|ScottNelle|snelle|-0500/-0400}}
* {{irc user|ScottRozic|gravitas|-0500/+0100}}
* {{irc user|Dana Benson|Snowden|-0800/-0700}}
* {{irc user|SinDoc|SinDoc|+0100/+0200}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Savell Martin|Savell|+0000/+0000}}
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}
* {{irc user|Stii|Stii|+0200 GMT}}
* {{irc user|ReinierZ|surial|+0100 GMT}}
* {{irc user|SuperPhly|SuperPhly|-600/-500}}
* {{irc user|SyedSRahman|syedsrahman|+0530}}
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}
* {{irc user|DavidLehn|taaz|-0500/-0400}}
* {{irc user|Tantek|tantek|-0800/-0700}}
* {{irc user|tbmartin|tbmartin|-0800/-0700}}
* {{irc user|themattharris|themattharris|-0800/-0700}}
* {{irc user|Wojciech|theanxy|+0100/+0200}}
* {{irc user|TheJbf|thejbf|+0100/+0200}}
* {{irc user|TheSisb|TheSisb|-0800/-0700}}
* {{irc user|Thierrymarianne|Thierry Marianne|+0100/+0200}}
* {{irc user|Thomasknoll|thomasknoll|-0800}}
* {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}
* {{irc user|TobyInk|tobyink|+0000/+0100}}
* {{irc user|TomMorris|tommorris|+0000/+0100}}
* {{irc user|Trovster|trovster|-0800/-0700}}
* {{irc user|Vadania|vadania|-0600/-0700}}
* {{irc user|Vant|vant|+0900}}
* {{irc user|venkateswaran|vensilver|+5.30 GMT}}
* {{irc user|Victor|victor|+0100/+0200}}
* {{irc user|V-I-P|V-I-P|+0100/+0200}}
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}
* {{irc user|WebOrganics|weborganics|+0100}}
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}
* {{irc user|Richard Conyard|WhiskeyM|+0000}}
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}
* {{irc user|StevenWoods|woodss|+0000 GMT}}
* {{irc user|ChristopheDucamp|xtof_fr|+0000/+0100}}
* {{irc user|Ianloic|yakk|-0800/-0700}}
* {{irc user|ZimbaTm|zimbatm|+0100}}
* {{irc user|PeterHellberg|zil|+0100}}
* {{irc user|Kiryl Zhybul|zkv|+0400}}

Needs alpha sorting into the above list (please help!)

* {{irc user|Bui Thanh Hai|haibtdt}}
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}
* {{irc user|Steven Osborn|steve918|-0700/-0800}}
* {{irc user|Trodrigues|trodrigues|+0000}}
* {{irc user|Epicurious|epicurious|+0000/+0100}}
* {{irc user|GermanMartinez|German|-0500}}

Inactive:
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.

parsers

2013-03-07T20:06:20Z

Jonathantneal: /* Microformat Node */ broken link

<entry-title>Microformats Parsers</entry-title>
;shortlink
:http://ufs.cc/w/ufprs
This page lists libraries that consume, transform or convert microformats. This is only a partial list. If you know of other such tools for microformats, please add them and list what specific microformats they support. There is a separate page for [[validators]].

Alphabetical listing by programming language:

== .Net ==
[http://ufxtract.com/ UfXtract] is an open source .Net microformats parser. It can parse microformats from URLs or HTML strings. The extracted data can be used directly in .Net or converted into JSON, JSON-P or XML. Currently Supports 16 microformats and can easily be extended with new definitions.

== Java ==
* [http://code.google.com/p/any23/ Any23 (Anything to Triples)] parses microformats into RDF triples
* [http://zwitserloot.com/org.microformats.hCard/ org.microformats.hCard] by Reinier Zwitserloot

== Javascript ==
=== Microformat Node ===
* [http://github.com/glennjones/microformat-node microformat-node] microformat-node is a microformat parser for node.js. It is built using a well tested light-weight JavaScript parsing engine (Microformat Shiv), which already powers a number of browser extensions. It currently supports the following formats:
** Release version: http://microformat-node.jit.su/ supports microformats: [[hCard]], [[XFN]], [[hReview]], [[hCalendar]], [[hAtom]], [[hResume]], [[geo]], [[adr]], and [[rel-tag|tag]].
** Beta version(Still in development) with [[microformats2]] support: http://microformat2-node.jit.su supports [[microformats2]]: h-adr h-card h-event h-entry h-geo - all in addition to the above.

=== Microformat Shiv ===
* [http://microformatshiv.com/ Microformat Shiv] The microformat shiv provides a simple to use, light-weight, cross-browser microformat API. It even works with modern mobile browsers and is backward compatible with Internet Explore 6. Based on the microformat API for Mozilla's extensions. This is the same code base as the popular Operater plug-in.

=== Sumo ===
* [http://www.danwebb.net/2007/2/9/sumo-a-generic-microformats-parser-for-javascript Sumo! A Generic Microformats Parser For JavaScript]

== Perl ==
=== Data::Microformat ===
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo.
** By Brendan O'Connor / Six Apart

=== HTML::Microformats ===
Perhaps we can capture and update this info on a page like [[perl-html-microformats-parser]].
[http://search.cpan.org/~tobyink/HTML-Microformats/ HTML::Microformats] is a CPAN module that has support for:
* input:
** rel: [[rel-enclosure]], [[rel-license]], [[rel-tag]], [[VoteLinks]], [[XFN]].
** class: [[adr]], [[figure]], [[geo]], [[hAtom]], [[hAudio]], [[User:TobyInk/hcalendar-1.1|hCalendar]], [[hCard]], [[hListing]], [[hNews]], [[hProduct]], [[hRecipe]], [[hResume]], [[hReview]], [[hReview-aggregate]], [[xFolk]], [[XMDP]], [[XOXO]].
*** highly experimental: [[measure]], [[species]].
** poshformats: [http://ocoins.info/ OpenURL COinS].
* output:
** RDF: RDF/XML, Turtle, N-Triples, RDF/JSON, etc.
** JSON
** domain specific: vCard (3.0, 4.0 and XML), iCalendar, Atom, KML.
* By [[User:TobyInk|Toby Inkster]].

Versions and releases notes:
* 2011-02-05 [http://microformats.org/discuss/mail/microformats-dev/2011-February/000667.html 0.102]
* 2010-12-22 0.101
* 2010-12-16 [http://microformats.org/discuss/mail/microformats-discuss/2010-December/013363.html 0.100]
* 2010-10-18 0.00_13
* 2010-06-25 0.00_12
* 2010-06-23 0.00_11
* 2010-05-13 0.00_10
* 2010-05-12 0.00_09
* 2010-04-29 0.00_08
* 2010-04-28 0.00_07
* 2010-04-16 [http://microformats.org/discuss/mail/microformats-dev/2010-April/000651.html 0.00_06]
* 2010-04-16 0.00_05
* 2010-03-20 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000647.html 0.00_04]
* 2010-03-09 [http://microformats.org/discuss/mail/microformats-dev/2010-March/000642.html 0.00_03]
* 2010-02-28 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000641.html 0.00_02]
* 2010-02-24 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000640.html 0.00_01]
* 2010-02-20 [http://microformats.org/discuss/mail/microformats-dev/2010-February/000639.html 0.00_00]
* see also the "Changes" file included in the CPAN distribution.

==== XML::Atom::Microformats ====

[http://search.cpan.org/~tobyink/XML-Atom-Microformats/ XML::Atom::Microformats] provides the same functionality for Atom. It finds microformats in Atom entry content elements.

===Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a parser for both “upper case Semantic Web” (RDF, RDFa) and “lower case semantic web” (microformats) technologies. It includes modules for exporting parsed data in a variety of formats, including RDF, vCard, iCalendar, Atom and KML.
** By Toby Inkster
** Active development has moved to HTML::Microformats (see above).

=== Text::Microformat ===
* Text::Microformat is a microformats parser hosted on [http://code.google.com/p/ufperl/ Google Code] that supports:
** [[hCard]], [[hCalendar]], [[rel-tag]]

== PHP ==
=== php-mf2 ===
* PHP generic microformats2 parser
** source: https://github.com/indieweb/php-mf2

=== XMFP ===
[http://code.google.com/p/xmfp/ XMFP] (eXtensible MicroFormats Parser for PHP 5) by [http://www.metonymie.com Emiliano Martínez Luque] is a set of PHP 5 classes providing a simple API for extracting Microformated Content either from a URI or a String representing HTML/XML. It can return the results as a PHP associative array, a JSON definition or an XML representation of the data. It supports most of the currently accepted microformats and can be easily extended to add new ones, it also has full support of the include pattern and provides basic validation of microformated data.

=== hKit Microformats Toolkit for PHP5 ===
[http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

===PHP Microformats parser===
[http://www.phpclasses.org/browse/package/3597.html Microformats parser] is a PHP package for extracting the microformats data embedded into HTML. The gathered data is stored as an xArray of objects - one for each microformat type container found. [http://malatestapunk-stuff.blogspot.com/2007/01/php-microformats-parser.html Announcement]. The parser supports most of the hCard (missing SOUND), hCalendar, hReview (missing item info; spec really needs some clarification) and rel elements, according to their respective specification on microformats Wiki.

===Transformr===
A Simple set of XSLT and PHP tools for Transforming Microformats Source [http://github.com/WebOrganics/TransFormr available from github] Live webservice available at [http://microform.at/ microform.at].

=== hCard Validator ===
[http://code.google.com/p/hcardvalidator/ Source code] of the [http://hcard.geekhood.net/ hCard Validator] contains XSLT and PHP code for hCard and include microformats.

=== ARC2 ===
[http://arc.semsol.org/ ARC2] is a semantic web toolkit which includes support for hCard, adr, geo, XFN, hCalendar, hAtom, hResume, hReview, xFolk, rel-license and rel-tag. It's tri-licensed under the GPL 2 and 3, and the W3C Software licence.

== Python ==
===AUMP===
* [http://aump.googlecode.com AUMP] is a parser written by David Janes. It supports hCard, hCalendar, hAtom, hReview and hListing.
** Uses Python's [http://docs.python.org/library/xml.dom.minidom.html xml.dom.minidom] after cleaning input through [http://www.w3.org/People/Raggett/tidy/ HTML Tidy].

===Microtron===
{{main|Microtron}}
* [[Microtron]] is a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

=== python-hcalendar ===
[http://pypi.python.org/pypi/python-hcalendar/0.1dev python-hcalendar] is a basic hCalendar parser.

== Ruby ==
===Prism ===
* [[Prism]]
** by [[implementors#Mark_Wunsch|Mark Wunsch]]
** Library and command line tool for parsing POSH/Microformats
** Uses the [http://nokogiri.org/ Nokogiri] HTML, XML, SAX, and Reader parser

=== mofo ruby microformats parser===
* [http://mofo.rubyforge.org/ mofo], [http://groups.google.com/group/mofo-rb mofo Google Group], [http://github.com/defunkt/mofo/tree/master GitHub repository]
** by [[implementors#Chris Wanstrath|Chris Wanstrath]]
** Uses the [http://wiki.github.com/why/hpricot Hpricot] HTML/XML parser

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== uformats ===
* [http://rubyforge.org/projects/uformats uformats]

=== scrAPI ===
* [http://rubyforge.org/projects/scrapi scrAPI]

== XSLT ==
===Optimus===
* [[Optimus]] is open source XSLT that parses microformats, converts them into JSON or XML, and validates them too.

===X2V===
* [[X2V]] is [http://hg.microformats.org/ open source XSLT for extracting microformats].
** by Brian Suda

== editing this page ==
For now, this page ''copies'' (rather than ''moves'') information from the existing [[implementations | Implementations]] page.

== see also ==
* [[implementations]]
* [[implementors]]
* [[open-source]]
* [[user-interface]]
* [[validators]]

existing-rel-values

2013-03-06T19:35:04Z

Jonathantneal: /* HTML5 link type extensions */ home definition

<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]]
|}

== 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-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-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.

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

|}

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

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

|-
| in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube + 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]]
|-
|}

== 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.
* 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.

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

2013-03-06T18:42:13Z

Jonathantneal: /* HTML5 link type extensions */ index definition

<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]]
|}

== 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-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-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.

== 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-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-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
| …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. can be combined with 'alternate' to indicate for example 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-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-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-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

|}

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

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

|-
| in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube + 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]]
|-
|}

== 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.
* 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.

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

2013-03-06T18:39:16Z

Jonathantneal: /* formats */ glossary definition

<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]]
|}

== 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-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-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.

== 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-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-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
| …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. can be combined with 'alternate' to indicate for example 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-index|index]]
| Hyperlink
| Hyperlink
| Refers to a document providing an index for the current document.
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]
|
| 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-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

|}

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

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

|-
| in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube + 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]]
|-
|}

== 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.
* 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.

== 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}}