Microformats Wiki - User contributions [en]

xfn-implementations

2007-10-04T16:50:45Z

Makacow: added new implementation item "MeetListen now supports XFN on profile pages."

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the '''top''' of this list.

* [http://meetlisten.com MeetListen] now supports [http://gmpg.org/xfn XFN] on profile pages. (e.g. [http://meetlisten.com/home/friends.php?id=6 MAKACOW-Brazil's]).
* XFN is implemented on [http://couchsurfing.com CouchSurfing] profiles (e.g. [http://www.couchsurfing.com/people/guaka Guaka's]).
* [http://xfngraph.sourceforge.net XFN Graph] — a multi-platform Java-based tool which creates spider diagrams of XFN relationships from any given starting URL.
* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.
* [http://www.zaadz.com Zaadz] uses [[hcard|hCard]] and [http://gmpg.org/xfn XFN] for friends on a user's profile page.
* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.
* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.
* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])
* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.
* [http://xfnsearch.joshpeek.com/ XFN Search]
* [http://ma.gnolia.com/ Ma.gnolia] [http://ma.gnolia.com/blog/2006/08/21/a-microadvance-in-our-microformats supports relMe]
* [http://wink.com Wink] supports rel-me (see [http://wink.com/beach--profile])
* [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- XFN visualization] example at IBM's Many Eyes

== XFN Validators ==

[http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] by [[User:DrewMcLellan|Drew McLellan]] will validate existence of XFN attributes.

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]

xfn-implementations

2007-10-04T16:22:48Z

Makacow: deleted broken link, this pt-BR translation does not exist in the linked page

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the '''top''' of this list.

* XFN is implemented on [http://couchsurfing.com CouchSurfing] profiles (e.g. [http://www.couchsurfing.com/people/guaka Guaka's]).
* [http://xfngraph.sourceforge.net XFN Graph] — a multi-platform Java-based tool which creates spider diagrams of XFN relationships from any given starting URL.
* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.
* [http://www.zaadz.com Zaadz] uses [[hcard|hCard]] and [http://gmpg.org/xfn XFN] for friends on a user's profile page.
* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.
* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.
* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])
* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.
* [http://xfnsearch.joshpeek.com/ XFN Search]
* [http://ma.gnolia.com/ Ma.gnolia] [http://ma.gnolia.com/blog/2006/08/21/a-microadvance-in-our-microformats supports relMe]
* [http://wink.com Wink] supports rel-me (see [http://wink.com/beach--profile])
* [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- XFN visualization] example at IBM's Many Eyes

== XFN Validators ==

[http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] by [[User:DrewMcLellan|Drew McLellan]] will validate existence of XFN attributes.

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]

existing-rel-values

2007-10-01T17:38:38Z

Makacow: rel='details'

<h1> existing rel values </h1>
{{TOC-right}}

This page contains tables of known 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.

Note: these lists may be incompleete, please help complete them from the referenced sources.

== usage ==
See [[rel-faq#How_is_rel_used]]. Regarding <span id="rev">rev</span>, see: [[rel-faq#Should_rev_even_be_used]].

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

Sources:
* [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4 link type]
* [[xfn]] and other [[microformats]]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [[rel-details|details]] || (seen on w3c.org news log in a "read more" permalink) || ???

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

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

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

|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]

|-
| [[rel-index|index]] || Refers to a document providing an index for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

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

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

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

|-
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]

|-
| [[rel-meta|meta]] || (seen on w3c.org) || ???

|-
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]

|-
| [[rel-transformation|transformation]] || Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. (Used in [[grddl|GRDDL]]) || [http://www.w3.org/2003/g/data-view#transformation GRDDL spec]

|-
|[[rel-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]
|-
|[[rel-toc|toc]] || Synonym of <code>contents</code> (from "Table Of Contents") || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]
|-
|}

=== 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 <strong>may use these values</strong>, 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
|-
| [[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]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

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

{| border="1"
|+
! rel value !! summary !! brainstormed in
|-
| [[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-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-product|product]] || … || [[product-brainstorming]]

|-
| [[rel-profile|profile]] || … || [[xmdp-brainstorming]]

|-
| (various) || XFN values for family relationships || [[genealogy-brainstorming#Relationships]]

|}

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

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

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''

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

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

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

|-
|[[rel-author|author]]||…||unknown || DevMo

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

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

|-
| [[rel-EditURI|EditURI]] || … || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || …

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

|-
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || … || HTML5

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

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

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

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

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

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

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

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

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

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

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

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

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

|-
| [[rel-sidebar |sidebar ]] || Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). || || HTML5

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

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

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

|-
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || …|| HTML5

|-
| [[rel-user|user]] || … || … || WCLR

|-
| [[rel-via|via]] || … || … || WCLR

|}

=== WCLR ===

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

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

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

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

The rest now seem unnecessary.
</blockquote>

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

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research <em>why</em> such values were omitted from latter specifications before using them. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

Sources: [http://www.w3.org/MarkUp/html3/ HTML3 (expired!)] - (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.)

{| 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).||[http://www.w3.org/MarkUp/html3/dochead.html HTML 3]||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||[http://www.w3.org/MarkUp/html3/dochead.html HTML 3]||unknown, but proposed for re-introduction in HTML5
|-
|}

== rejected ==
Some rel values have been proposed and rejected. These are <strong>not recommended</strong> for use, and listed here to make that explicit.

Source: [[rejected-formats]].

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

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

{| border="1"
|+
! rel value !! summary !! possible source
|-
| schema.DC || … || [http://dublincore.org/ Dublin Core]

|-
| schema.DCTERMS || … || [http://dublincore.org/ 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]. 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. Unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical.

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

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

existing-rel-values

2007-09-23T18:50:00Z

Makacow: /* formats */

<h1> existing rel values </h1>

== formats ==
These rel values are defined formats from specifications (HTML4, microformats). Alphabetically ordered by value.

Note: this list is incomplete, please help complete it from the following sources:
* [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]
* [[xfn]] and other [[microformats]]

{| border="1"
|+
! rel value !! summary !! defining specification
|-
|[[rel-friend|friend]] || the person represented by the current document considers the person represented by the refrenced document to be a friend || [[XFN]]
|-
|[[rel-me|me]]||the referenced document represents the same person as the current document||[[XFN]]
|-
|[[rel-home|home]]||the referenced document is the homepage of the site in which the current page appears.||[[rel-home]]
|-
|[[rel-license|license]]||the referenced document is license information for the current page.||[[rel-license]]
|-
|[[rel-next|next]]||the next document in a navigation order||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]
|-
|[[rel-prev|prev]]||the previous document in a navigation order||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]
|-
|[[rel-stylesheet|stylesheet]]||a style sheet for the current document||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]
|-
|[[rel-tag|tag]]||the referenced document represents a "tag", which is like a keyword or category label, for the current document||[[rel-tag]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here.

Sources: [[group-brainstorming]], ...

{| border="1"
|+
! rel value !! summary !! proposed in
|-
|[[rel-group|group]]||the referenced document represents a group that the person represented by the current document belongs to||[[group-brainstorming]]
|-
|[[rel-member|member]]||the referenced document represents a member of the group represented by the current document||[[group-brainstorming]]
|}

== POSH usage ==
There are numerous rel values used as [[POSH]] in the wild, their origins are not necessarily known, nor are their meanings consistent, but it may still be useful to document their existence and summarize their implied meanings/usage intent.

{| border="1"
|+
! rel value !! summary !! origin
|-
|[[rel-archive|archive]]||an archive document for the current blog||unknown origin
|}

== related ==
* [[elemental-microformats]]
* [[rel-faq]]
* [[existing-class-names]]