Microformats Wiki - User contributions [en]

rel-longdesc

2010-09-03T04:20:26Z

Komputist: /* The longdesc microformat, as described in W3 bug 10434 */

{{stub}}

Proposed by John Foliot in a [http://www.brucelawson.co.uk/2009/alternate-text-in-html-5/#comment-614001 comment on Bruce Lawson's blog].

...

== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed in that bug, will be taken into this microformat.

Here is a summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

== see also ==
* [[existing-rel-values]]

rel-longdesc

2010-09-03T04:20:06Z

Komputist: /* The longdesc microformat, as described in W3 bug 10434 */

{{stub}}

Proposed by John Foliot in a [http://www.brucelawson.co.uk/2009/alternate-text-in-html-5/#comment-614001 comment on Bruce Lawson's blog].

...

== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed in that bug, will be taken into this microformat.

Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

== see also ==
* [[existing-rel-values]]

rel-longdesc

2010-09-03T04:19:39Z

Komputist: /* see also */ Added pointer to W3 bug 10434

{{stub}}

Proposed by John Foliot in a [http://www.brucelawson.co.uk/2009/alternate-text-in-html-5/#comment-614001 comment on Bruce Lawson's blog].

...

== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed that bug, will be taken into this microformat.

Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

== see also ==
* [[existing-rel-values]]

existing-rel-values

2010-08-25T23:09:53Z

Komputist: Added <span id="longdesc"></span>

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

<span id="usage">usage</span>: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding <span id="rev">rev</span>, 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 <strong>recommended for general use</strong>. Alphabetically ordered by value.

Note:
* <strong>Do not</strong> 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]].
* <strong>Do not</strong> 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]].
* <strong>Do not</strong> add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

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

{| border="1"
|+
! rel value !! summary<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-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [[rel-stylesheet|stylesheet]] || a style sheet for the current document<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-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]

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

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

|-
|}

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

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

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You <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 !! external spec (if any)
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, <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-accessibility|accessibility]] || indicate[s] that the destination of that hyperlink contains accessibility information for the current page. || [http://www.brucelawson.co.uk/2009/rel-accessibility/ blog post]

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

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

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

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

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

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

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

|-
| [[rel-shortlink|shortlink]] || the referenced document represents the current document but with a shorter URL || [http://samj.net/2009/04/introducing-relshort-better-alternative.html blog post]

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

|-
| [[rel-status|status]] || the referenced document represents the status (or source of status updates) for the author of this document || [http://www.monkinetic.com/2009/11/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: this list is incomplete, please help complete it from the following sources:

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

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

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

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

|-
|[[rel-author|author]]||…||unknown || DevMo / 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-details|details]] || … || (seen on w3c.org news log in a "read more" permalink) || …

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

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

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

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

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

|-
| [[rel-first|first]] || Indicates that the current document is a part of a series, and that the first document in the series is the referenced document. || … || HTML5

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

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

|-
| <span id="longdesc">[[rel-longdesc|longdesc]]</span> || Alternative to @longdesc || ([http://www.google.com/search?q=rel%3D%22longdesc%22 Google search for rel=longdesc in the wild]) || …

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|}

=== WCLR ===

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

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

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

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

The rest now seem unnecessary.
</blockquote>

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

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

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.

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

|-
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]

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

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research <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.

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

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

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

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped
|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown
|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown
|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown
|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown
|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown
|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown
|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown
|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown
|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown
|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown
|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown
|-
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown
|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown
|-
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown
|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown
|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown
|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown
|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown
|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown
|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown
|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown
|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown
|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||HTML3||unknown, but proposed for re-introduction in HTML5
|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown
|-
|}

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

Source: [[rejected-formats]].

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

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

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

|-
| schema.DCTERMS || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.

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

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

html5-profile-issues

2010-02-22T00:10:06Z

Komputist: /* 2010 */

<entry-title>HTML5 profile attribute issues </entry-title>
__TOC__
These are externally raised issues about the [[html5-profile|HTML5 Profile Attribute]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[html5-profile-faq|HTML5 Profile Attribute FAQ]] and the [[html5-profile-issues-resolved|HTML5 Profile Attribute resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [[User:Tantek|Tantek]]

== closed issues ==
See: [[html5-profile-issues-closed]]

== resolved issues ==
See: [[html5-profile-issues-resolved]]

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list below by copy and pasting the [[#template|template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2010===
* Copyright statement - 2010-02-19

This is a request for clarification.

This document is in the public domain. If the W3C HTML Working Group accepts to take on the proposal as a deliverable, should contributions from the Working Group participants expected to be in the public domain as well, or can they remain under the W3C Document license? As owner of [http://www.w3.org/html/wg/tracker/actions/29 ACTION-29] in the WG, I'm interested in gathering rationals in both approaches. -PLH.
<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-20</span>
raised by <span class="fn">Krzysztof Maczyński</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Should sections 2 and 3 be normative?</strong>
The [http://lists.w3.org/Archives/Public/public-html/2010Feb/0683.html message announcing the draft] indicates that sections 2 (“listing known HTML 4.01 errata regarding the profile attribute on the head element”) and 3 (“describing how this specification could be applied to both previous versions of HTML and XHTML, and other markup languages”) would be informative. I propose that the HTML WG consider making them normative.
** other [http://lists.w3.org/Archives/Public/public-html/2010Feb/0685.html relevant] [http://lists.w3.org/Archives/Public/public-html/2010Feb/0690.html messages]
</div>
</div>

<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-21</span>
raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title"><code>data-foo=""</code> should be in (subsequent) scope of @profile.</strong> An <code> <element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify optional or required data-foo attributes. <strong>Example:</strong> <code> <element class="classname" data-profileprefix-attribute="value"></element></code> In other words, it should be possible to specify required/optional <code>data-foo=""</code> attributes together with specific ''element@class'' combinations.
;Related info and messages:
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0692 Message from Toby Inkster in support of a html5 profile spec],
:[http://lists.w3.org/Archives/Public/public-html/2010Jan/0618 The original profile based distributed extensibility idea of Toby Inkster],
:[http://dev.w3.org/html5/spec/dom.html#attr-data data-foo="" in HTML5, including the ''space ship element'' example]: <div class="spaceship" data-ship-id="92432" data-weapons="laser 2" [ etc ]
:For scripting libraries, then HTML5 recommends using a prefix (<code>data-prefx-attribute=""</code> to avoid clashes and should be considered for the HTML5 profile specification also.

</div>
</div>

<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-21</span>
raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title">ARIA attributes and <code>role=""</code> should be in (subsequent) scope of @profile.</strong> An <code> <element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify recommended ARIA and role attribtues. <strong>Example:</strong> <code> <element class="classname" role="button"></element></code>
;Related info and messages:
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://www.w3.org/mid/83960F12C8BA4EB2AD7753AAF13C38E1@joe1446a4150a8 Question from Joe D Williams (comment to Toby Inksters Distributed Extensibility proposal]

</div>
</div>

== template ==
{{issues-format}}

== related pages ==
* [[html5-profile]]
* [[html5]]
* [[xmdp]]

html5-profile-issues

2010-02-22T00:05:45Z

Komputist: /* 2010 */ added 2 issues

<entry-title>HTML5 profile attribute issues </entry-title>
__TOC__
These are externally raised issues about the [[html5-profile|HTML5 Profile Attribute]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[html5-profile-faq|HTML5 Profile Attribute FAQ]] and the [[html5-profile-issues-resolved|HTML5 Profile Attribute resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [[User:Tantek|Tantek]]

== closed issues ==
See: [[html5-profile-issues-closed]]

== resolved issues ==
See: [[html5-profile-issues-resolved]]

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list below by copy and pasting the [[#template|template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2010===
* Copyright statement - 2010-02-19

This is a request for clarification.

This document is in the public domain. If the W3C HTML Working Group accepts to take on the proposal as a deliverable, should contributions from the Working Group participants expected to be in the public domain as well, or can they remain under the W3C Document license? As owner of [http://www.w3.org/html/wg/tracker/actions/29 ACTION-29] in the WG, I'm interested in gathering rationals in both approaches. -PLH.
<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-20</span>
raised by <span class="fn">Krzysztof Maczyński</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Should sections 2 and 3 be normative?</strong>
The [http://lists.w3.org/Archives/Public/public-html/2010Feb/0683.html message announcing the draft] indicates that sections 2 (“listing known HTML 4.01 errata regarding the profile attribute on the head element”) and 3 (“describing how this specification could be applied to both previous versions of HTML and XHTML, and other markup languages”) would be informative. I propose that the HTML WG consider making them normative.
** other [http://lists.w3.org/Archives/Public/public-html/2010Feb/0685.html relevant] [http://lists.w3.org/Archives/Public/public-html/2010Feb/0690.html messages]
</div>
</div>

<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-21</span>
raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title"><code>data-foo=""</code> should be in (subsequent) scope of @profile.</strong> An <code> <element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify optional or required data-foo attributes. <strong>Example:</strong> <code> <element class="classname" data-profileprefix-attribute="value"></element></code> In other words, it should be possible to specify required/optional <code>data-foo=""</code> attributes together with specific ''element@class'' combinations.
;Related info and messages:
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0692 Message from Toby Inkster in support of a html5 profile spec],
:[http://lists.w3.org/Archives/Public/public-html/2010Jan/0618 The original profile based distributed extensibility idea of Toby Inkster],
:[http://dev.w3.org/html5/spec/dom.html#attr-data data-foo="" in HTML5, including the ''space ship element'' example]: <div class="spaceship" data-ship-id="92432" data-weapons="laser 2" [ etc ]
:For scripting libraries, then HTML5 recommends using a prefix (<code>data-prefx-attribute=""</code> to avoid clashes - this should be considered for the HTML5 profile specification also.

</div>
</div>

<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2010-02-21</span>
raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title">ARIA attributes and <code>role=""</code> should be in (subsequent) scope of @profile.</strong> An <code> <element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify recommended ARIA and role attribtues. <strong>Example:</strong> <code> <element class="classname" role="button"></element></code>
;Related info and messages:
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://www.w3.org/mid/83960F12C8BA4EB2AD7753AAF13C38E1@joe1446a4150a8 Question from Joe D Williams (comment to Toby Inksters Distributed Extensibility proposal]

</div>
</div>

== template ==
{{issues-format}}

== related pages ==
* [[html5-profile]]
* [[html5]]
* [[xmdp]]