http://microformats.org/wiki/api.php?action=feedcontributions&user=SamB&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-28T22:17:37ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=rel-registry&diff=44050rel-registry2011-06-06T23:01:31Z<p>SamB: /* How does the microformats rel registry compare to RFC and W3C options */</p>
<hr />
<div><entry-title>rel registry</entry-title><br />
<br />
The microformats wiki has the closest thing to a real-world rel value registry.<br />
We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.<br />
<br />
== stable rel values ==<br />
The [[existing-rel-values#formats|formats]] section of the [[existing-rel-values]] page can be used as a list of stable/dependable rel values.<br />
<br />
== draft rel values ==<br />
The [[existing-rel-values#proposals|proposals]] section of the [[existing-rel-values]] page can be used as a list of rel values with reasonably well written proposals.<br />
<br />
== provisional rel values ==<br />
The [[existing-rel-values#brainstorming|brainstorming]] section of the [[existing-rel-values]] page can be used as a list of ideas / simple proposals for rel values that merit further research and development (and possibly documentation as drafts) per the microformats [[process]]<br />
<br />
== additional rel values ==<br />
The [[existing-rel-values]] page contains additional sections/clusterings of rel values that have been documented in the wild. Some of these may merit brainstorming/provisional registration and further development.<br />
<br />
There is also documentation of dropped and rejected rel values for the sake of thoroughness and to hopefully avoid having them be unnecessarily re-proposed (without at least following up on why they failed in the first place.)<br />
<br />
== new rel values ==<br />
If you wish to develop a new rel value, please follow the microformats [[process]]. <br />
<br />
While you're following the [[process]], feel free to add your new rel value to the [[existing-rel-values#brainstorming|brainstorming section]] to indicate your interest and work in progress, but be sure to follow-up quickly with:<br />
* a page for the rel value itself clearly documenting it as a ''brainstorm proposal'', and explaining it in more detail, including documentation sections per the [[process]] (real world end user use cases, examples of content in the wild that would benefit, previous attempts at such a rel value or related format)<br />
* email to the microformats-new [[mailing-list]] stating your interest in developing the rel value<br />
* [[IRC]] (or email) asking help regarding anything in the [[process]] or general rel value questions that would help you to develop your new rel value.<br />
<br />
== FAQ ==<br />
<br />
=== Does the microformats rel registry reflect reality ===<br />
''Q: Does the microformats rel registry reflect reality?''<br />
<br />
A: In practice yes. The list of [[existing-rel-values]] very carefully documents which rel values are in well-accepted standards ([[existing-rel-values#formats|formats]]), which have well written microformats drafts ([[existing-rel-values#proposals|proposals]]), and which others are in development, sometimes on other sites ([[existing-rel-values#brainstorming|brainstorming]]). <br />
<br />
In addition, the microformats [[existing-rel-values]] reflects reality better than any other attempt at a registry, because it also explicitly documents which rel values have failed in the real world, or have otherwise been obsoleted or rejected.<br />
<br />
Finally, the barrier to entry for adding to and correcting the [[existing-rel-values]] is the lowest of any existing registry and thus the microformats community has best track record of keeping it up to date as compared to other attempts at registries.<br />
<br />
=== Can the microformats rel registry document HTML specific details ===<br />
''Q: Can the microformats rel registry document HTML-specific details? ''<br />
<br />
A: Currently the [[existing-rel-values]] are documented in a format-agnostic manner, though in practice most of the real world usage of existing rel values is in HTML.<br />
<br />
If there are specific real-world documented needs for capturing HTML-specific details, the [[existing-rel-values]] tables could be expanded with a column to describe those HTML-specific details.<br />
<br />
=== Can the microformats rel registry be used for provisional registration ===<br />
''Q: Can the microformats rel registry be used for provisionally registering new rel values?''<br />
<br />
A: Yes. See the [[rel-registry#provisional_rel_values|provisional rel values]] section.<br />
<br />
=== How do provisional values achieve full registration ===<br />
<br />
''Q: How do provisionally registered values achieve full registration?''<br />
<br />
A: The microformats [[process]] documents a number of steps to advance any microformats effort, including new rel values. In short, documenting specific real world use cases for a new rel value, and research into existing content that could benefit from it, as well as earlier/other attempts at such concepts help greatly. <br />
<br />
Also the microformats [[process]] has been updated this year (2011) to provide a more explicit path from draft, to specification, to standard. Those take additional steps such as documenting real world uses of a provisional rel value, implementations, test suites, test results.<br />
<br />
=== Is the microformats rel registry discoverable ===<br />
<br />
''Q: Is the microformats rel registry discoverable?''<br />
<br />
A: Yes. If you google for "rel registry" this page currently comes up on the first page of results, and may of the other results point to this page. Similarly a searching "rel values" returns results including [[existing-rel-values]] on the first page of results (in fact, the very ''first'' result as of 2011-091 on Google and Yahoo).<br />
<br />
=== How does the microformats rel registry compare to RFC and W3C options ===<br />
''Q: How does the microformats rel registry compare to RFC and W3C options?''<br />
<br />
A: The W3C doesn't currently have a rel registry. The closest thing to a W3C rel registry is the HTML4.01 Recommendation (which defines several rel values), and the HTML5 Working Draft. The latter is only edited/updated by a single editor, and thus all "registrations" must be committed by one individual. Such "registrations" are simultaneously published by the WHATWG in their "HTML" specification (see http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#linkTypes) which is available under the MIT license.<br />
<br />
Also note that the WHATWG spec presently [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types states]:<br />
<br />
<blockquote><br />
<dfn id="concept-rel-extensions" title="concept-rel-extensions">Extensions to the predefined set of link types</dfn> may be registered in the [http://microformats.org/wiki/existing-rel-values Microformats wiki existing-rel-values page].<br />
</blockquote> <br />
<br />
In comparison, the RFC/IETF/IANA method which appears to be at this URL:<br />
<br />
http://www.iana.org/assignments/link-relations/<br />
<br />
Provides no license, copyright or other statement of how it may be (re)used.<br />
<br />
Finally the microformats [[rel-registry]], and [[existing-rel-values]] as with the rest of the microformats wiki are published with a Creative Commons Public Domain License.<br />
<br />
Thus comparing these three (microformats, W3C/WHATWG, RFC/IETF/IANA) :<br />
<br />
# microformats has the most liberal (least private) availability as public domain<br />
# W3C HTML5 (via WHATWG's "HTML") has the effectively as liberal MIT license<br />
# RFC/IETF/IANA has no obvious license and thus it is unclear.<br />
<br />
=== Is there a machine processable version of the microformats rel registry ===<br />
''Q: Is there a machine processable version of the microformats rel registry? ''<br />
<br />
A: Yes. Each of the levels of rel values (formats, proposals, brainstorming) are in their own semantic HTML table, in order (1,2,3) on the [[existing-rel-values]] page. <br />
<br />
Machine processors may pick the table of their choosing by choosing the appropriate ordinal (1,2,3) and then parse it as well-formed markup, using the first column of the table as the rel value, the 2nd column as informative text, and the first hyperlink in the 3rd column of a row as the defining specification/draft/proposal where the rel value is further explained.</div>SamBhttp://microformats.org/wiki/index.php?title=existing-rel-values&diff=44038existing-rel-values2011-06-05T04:09:43Z<p>SamB: /* WCLR */ prod mediawiki into noticing paragraph breaks in blockquote...</p>
<hr />
<div><entry-title> existing rel values </entry-title><br />
<br />
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.<br />
<br />
<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]].<br />
<br />
== formats ==<br />
These rel values are defined formats from specifications (HTML 4, microformats) are thus are <strong>recommended for general use</strong>. Alphabetically ordered by value.<br />
<br />
Note:<br />
* <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]].<br />
* <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]].<br />
* <strong>Do not</strong> add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.<br />
<br />
<br />
Sources:<br />
* 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. <br />
* [[xfn]] and other [[microformats]]<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary<br />(from the relevant specification where possible)) !! defining specification<br />
<br />
|-<br />
| [[rel-acquaintance|acquaintance]] || the person represented by the current document considers the person represented by the referenced document to be an acquaintance || [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-child|child]] || the referenced person is a child of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-colleague|colleague]] || the referenced person is a colleague of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-contact|contact]] || the person represented by the current document considers the person represented by the referenced document to be a contact || [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-co-resident|co-resident]] || the referenced person lives in the same residence as the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-co-worker|co-worker]] || the referenced person is a co-worker of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-crush|crush]] || this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)|| [[XFN]]<br />
<br />
|-<br />
| [[rel-date|date]] || this person considers the referenced person to be a date (i.e. is dating the referenced person)|| [[XFN]]<br />
<br />
|-<br />
| [[rel-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-kin|kin]] || the referenced person is part of the extended family of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-license|license]] || &hellip;indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page. || [[rel-license]]<br />
<br />
|-<br />
| [[rel-me|me]] || the referenced document represents the same person as does the current document || [[XFN]]<br />
<br />
|-<br />
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]<br />
<br />
|-<br />
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-neighbor|neighbor]] || the referenced person lives nearby the person represented by the current document || [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]]<br />
<br />
|-<br />
| [[rel-parent|parent]] || the referenced person is a parent of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-previous|previous]] || Synonym of <code>prev</code> || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-sibling|sibling]] || the referenced person is a sibling of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[rel-spouse|spouse]] || the referenced person is a spouse of the person represented by the current document|| [[XFN]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]<br />
<br />
|-<br />
|[[rel-tag|tag]] || &hellip;indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]<br />
<br />
|-<br />
|[[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]<br />
<br />
|-<br />
| [[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] <br />
<br />
|-<br />
|}<br />
<br />
=== notes ===<br />
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as <br />
** <code>rel="alternate" lang="fr"</code> (French language version of this page)<br />
** <code>rel="alternate" media="print"</code> (printable version of this page)<br />
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)<br />
<br />
*Synonyms such as "previous", "toc" are not as widely supported as the main term.<br />
<br />
== proposals ==<br />
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.<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary !! proposed in !! external spec (if any)<br />
|-<br />
| [[rel-pronunciation|pronunciation]] || &hellip;indicates that the destination of the 'link' element is a document providing a pronunciation lexicon for speech-synthesis purposes. || [[rel-pronunciation]]<br />
|-<br />
| [[rel-directory|directory]] || &hellip;indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]<br />
|-<br />
| [[rel-enclosure|enclosure]] || &hellip;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]<br />
|-<br />
| [[rel-home|home]] || &hellip;indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]<br />
|-<br />
| [[rel-payment|payment]] || &hellip; || [[rel-payment]]<br />
|}<br />
<br />
== brainstorming ==<br />
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.<br />
<br />
You may list new proposed rel values here, and even better if you can list and link to POSH uses in the wild.<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary !! brainstormed in and usage in the wild<br />
<br />
|-<br />
| [[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 &lt;link&gt; tag in the head of the document.<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| [[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]]<br />
<br />
|-<br />
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]<br />
<br />
<br />
|-<br />
| <span id="longdesc">[[rel-longdesc|longdesc]]</span> || 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.<br />
<br />
|-<br />
| [[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)<br />
<br />
|-<br />
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]<br />
<br />
|-<br />
| [[rel-product|product]] || &hellip; || [[product-brainstorming]]<br />
<br />
|-<br />
| [[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]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|-<br />
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]<br />
|-<br />
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]<br />
|-<br />
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]<br />
<br />
|-<br />
| [[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]<br />
<br />
|}<br />
<br />
=== more brainstorming ===<br />
See also:<br />
* [[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)<br />
* [[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)<br />
<br />
== POSH usage ==<br />
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.<br />
<br />
Note: this list is incomplete, please help complete it from the following sources:<br />
<br />
External sources: <br />
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)<br />
* [http://wiki.mozilla.org/Microsummaries Microsummary]<br />
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)<br />
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991. <br />
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''<br />
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)<br />
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]<br />
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]<br />
<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary !! origin !! proposal(s)<br />
<br />
|-<br />
| [[rel-archive|archive]] || index of archived entrigs || unknown, perhaps Wordpress open source blogging software || WCLR<br />
<br />
|-<br />
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5<br />
<br />
|-<br />
|[[rel-author|author]]||&hellip;||unknown || DevMo / HTML5<br />
<br />
|-<br />
| [[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]<br />
<br />
<br />
|-<br />
| [[rel-comment|comment]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-contribution|contribution]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-EditURI|EditURI]] || &hellip; || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || &hellip;<br />
<br />
|-<br />
| [[rel-endorsed|endorsed]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || &hellip; || HTML5<br />
<br />
|-<br />
| [[rel-fan|fan]] || xxxx. || &hellip; || [[hcard-user-profile-authoring]]<br />
<br />
|-<br />
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || &hellip; || WCLR/ HTML5<br />
<br />
|-<br />
| [[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. || &hellip; || HTML5<br />
<br />
|-<br />
| [[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<br />
<br />
|-<br />
| [[rel-lightbox|lightbox]] || &hellip; || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || &hellip; <br />
<br />
|-<br />
| [[rel-made|made]] || &hellip; || &hellip; || LRdraft<br />
<br />
|-<br />
| [[rel-meta|meta]] || &hellip; || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF<br />
<br />
|-<br />
| [[rel-microsummary|microsummary]]|| &hellip; || &hellip; ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]<br />
<br />
|-<br />
| [[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<br />
<br />
|-<br />
| [[rel-openid-delegate|openid.delegate]] || &hellip; || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || &hellip;<br />
<br />
|-<br />
| [[rel-openid-server|openid.server]] || &hellip; || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || &hellip;<br />
<br />
|-<br />
| [[rel-permalink|permalink]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || &hellip; || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]<br />
<br />
|-<br />
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || &hellip; || WCLR/ HTML5<br />
<br />
|-<br />
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || &hellip; || HTML5<br />
<br />
|-<br />
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || &hellip; || [http://rasterweb.net/raster/2002/12/12/20021212072812/]<br />
<br />
|-<br />
| [[rel-referral|referral]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-related|related]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]<br />
<br />
|-<br />
| [[rel-resource|resource]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-search|search]] || &hellip; || unknown || unknown<br />
<br />
|-<br />
| [[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<br />
<br />
|-<br />
| [[rel-sponsor|sponsor]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-trackback|trackback]] || &hellip; || unknown, perhaps open source Movable Type blogging software || WCLR<br />
<br />
|-<br />
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || &hellip;|| HTML5<br />
<br />
|-<br />
| [[rel-user|user]] || &hellip; || &hellip; || WCLR<br />
<br />
|-<br />
| [[rel-via|via]] || &hellip; || &hellip; || WCLR<br />
<br />
|}<br />
<br />
=== WCLR ===<br />
<br />
The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:<br />
<br />
<blockquote><br />
<p>&hellip;now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.</p><br />
<br />
These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:<br />
<br />
* permalink -> bookmark<br />
* archive -> archives<br />
* feed<br />
* pingback<br />
* unendorsed -> nofollow<br />
<br />
The rest now seem unnecessary.<br />
</blockquote><br />
<br />
Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.<br />
<br />
== HTML5 link type extensions ==<br />
<br />
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]. 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.<br />
<br />
{| border="1"<br />
|+ <br />
! Keyword<br />
! Effect on <code>link</code><br />
! Effect on <code>a</code>, <code>area</code><br />
! Brief description<br />
! Link to specification<br />
! Synonyms<br />
! Status<br />
<br />
|-<br />
| apple-touch-icon<br />
| External Resource<br />
| Not allowed<br />
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).<br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]<br />
| probably redundant with rel=icon<br />
| proposed<br />
<br />
|-<br />
| apple-touch-icon-precomposed<br />
| External Resource<br />
| Not allowed<br />
| Specify a Webpage Icon for a “Web Clip”, or “touch icon”, for mobile devices (not limited to Apple devices).<br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]<br />
| probably redundant with rel=icon<br />
| proposed<br />
<br />
|-<br />
| apple-touch-startup-image <br />
| External Resource<br />
| Not allowed<br />
| Specify a splashscreen for Web apps on iOS Safari <br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safariwebcontent/configuringwebapplications/configuringwebapplications.html Apple's Safari Web Content Guide]<br />
| maybe redundant with rel=icon with the sizes attribute?<br />
| proposed<br />
<br />
|-<br />
| canonical<br />
| External Resource<br />
| Not allowed<br />
| Specifies the canonical URL for the current document in order to help avoid duplicate content.<br />
| [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]<br />
|<br />
| proposed<br />
<br />
|-<br />
| openid.delegate<br />
| External Resource<br />
| Not allowed<br />
| 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. <br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID Authentication 1.1]<br />
|<br />
| proposed<br />
<br />
|-<br />
| openid.server<br />
| External Resource<br />
| Not allowed<br />
| The OpenID server for the relying party to contact for OpenID 1.1 authentication<br />
| [http://openid.net/specs/openid-authentication-1_1.html#anchor4 OpenID Authentication 1.1]<br />
|<br />
| proposed<br />
<br />
|-<br />
| openid2.local_id<br />
| External Resource<br />
| Not allowed<br />
| 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. <br />
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]<br />
|<br />
| proposed<br />
<br />
|-<br />
| openid2.provider<br />
| External Resource<br />
| Not allowed<br />
| The OpenID server for the relying party to contact for OpenID 2.0 authentication<br />
| [http://openid.net/specs/openid-authentication-2_0.html#rfc.section.7.3.3 OpenID Authentication 2.0]<br />
|<br />
| proposed<br />
<br />
|-<br />
| shortcut<br />
| External Resource<br />
| Not allowed<br />
| Used as a companion for <code>icon</code> for compatibility with IE.<br />
| [http://msdn.microsoft.com/en-us/library/ms537656%28v=vs.85%29.aspx#Associate_the_Icon_with_Your_Web_Page Documentation on MSDN]<br />
|<br />
| proposed<br />
|}<br />
<br />
== non HTML rel values ==<br />
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.<br />
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]]<br />
<br />
Sources:<br />
* [[Atom]] [[RFC4287]] specification. <br />
* See http://www.iana.org/assignments/link-relations.html for more.<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary<br />(from the relevant specification where possible)) !! defining specification<br />
<br />
|-<br />
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]<br />
<br />
|-<br />
| in-reply-to || See http://code.google.com/apis/youtube/2.0/developers_guide_protocol_comments.html || YouTube + Atom<br />
<br />
|-<br />
| ... || ... || ...<br />
<br />
|}<br />
<br />
== dropped ==<br />
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.<br />
<br />
In general, you {{should not}} use any dropped values.<br />
<br />
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.<br />
<br />
Sources: <br />
* [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.)<br />
* [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 `e avoided.<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! summary !! defining specification !! why dropped <br />
|-<br />
|[[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<br />
|-<br />
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.<br />
|| HTML4dropped||unknown<br />
|-<br />
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown<br />
|-<br />
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown<br />
|-<br />
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown<br />
|-<br />
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown<br />
|-<br />
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown<br />
|-<br />
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown<br />
|-<br />
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown<br />
|-<br />
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown<br />
|-<br />
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown<br />
|-<br />
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown<br />
|-<br />
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown<br />
|-<br />
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown<br />
|-<br />
| [[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<br />
|-<br />
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown<br />
|-<br />
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown<br />
|-<br />
| [[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<br />
|-<br />
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown<br />
|-<br />
| [[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<br />
|-<br />
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown<br />
|-<br />
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown<br />
|-<br />
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown<br />
|-<br />
|[[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<br />
|-<br />
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown<br />
|-<br />
|}<br />
<br />
== rejected ==<br />
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.<br />
<br />
Source: [[rejected-formats]].<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !! origin / proposal !! why rejected <br />
|-<br />
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]<br />
|-<br />
|}<br />
<br />
== unspecified ==<br />
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.<br />
<br />
{| border="1"<br />
|+ <br />
! rel value !!"summary !! source<br />
|-<br />
| schema.DC || &hellip; || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]<br />
<br />
|-<br />
| schema.DCTERMS || &hellip; || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]<br />
|-<br />
|}<br />
<br />
Notes:<br />
* 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]. <br />
** '''examples from that search only use invisible <code>&lt;link href&gt;</code> element'''. At first glance it appears the results from the search show only uses with the invisible <code>&lt;link href&gt;</code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code>&lt;a href&gt;</code> are strongly preferred. <br />
*** [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>&lt;link href&gt;</code> appears to be more appropriate than <code>&lt;a href&gt;</code> for those that use Dublin Core metadata schemas.<br />
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code>&lt;a href&gt;</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.<br />
<br />
== tools ==<br />
See [[implementations]].<br />
<br />
== related ==<br />
{{rel-related-pages}}<br />
* [[elemental-microformats]]<br />
* [[existing-rev-values]]<br />
* [[existing-class-names]]<br />
<br />
== copyright ==<br />
<br />
{{cc-pd-license}}</div>SamBhttp://microformats.org/wiki/index.php?title=buttons&diff=44037buttons2011-06-05T03:32:48Z<p>SamB: </p>
<hr />
<div><h1>Microformats Buttons</h1><br />
<br />
There have been requests for buttons for various microformats. Either badges, or buttons that do something with the specific microformats. This page keeps a list of buttons, and requests as well. - [http://tantek.com/log/ Tantek]<br />
<br />
==Licensing==<br />
<br />
If you add <del>links to</del> buttons you have designed, '''please<br />
*'''upload them to this wiki''' to guard against ending up with tons of broken images on this page<br />
*'''also include a statement''' that you do one of the following:<br />
**release them into the public domain<br />
**hold copyright, but release all rights as to it use<br />
**license them under a specified free license, e.g. consider using a [http://creativecommons.org/ Creative Commons] license, such as [http://creativecommons.org/licenses/by/3.0 cc-by-3.0].<br />
<br />
Thank you.<br />
<br />
* Images below hosted at boogdesign.com are available under [http://creativecommons.org/licenses/by/2.0/ CC Attribution 2.0 License], see [http://www.boogdesign.com/buttons.html my buttons page] for the Photoshop files if you need them. - [[User:RobCrowther|Rob Crowther]]<br />
<br />
* Images below hosted at rbach.priv.at are available under [http://creativecommons.org/licenses/by/3.0 cc-by-3.0 license]. - [[User:RobertBachmann|Robert Bachmann]]<br />
<br />
* Images below hosted at hauntedpalace.net and flickr.com/photos.hauntedpalace (POSH logos and palette cheatsheet) are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license]. &#8212; [[:User:CarlaHufstedler|Carla Hufstedler]]<br />
<br />
__TOC__<br />
<br />
== Buttons ==<br />
<br />
=== Microformat Button ===<br />
I've made a button for microformats. Since there are so many microformats and with more to come, just indicating support/ use of might be a good generic approach. The image is free to use. Please copy it to your own hosting account and not link to it.<br />
<br />
http://www.crowley.nl/images/microformats.png<br />
<br />
I already have a "I use <br />
http://www.crowley.nl/images/microformats.png" on my blog: http://doncrowley.blogspot.com/<br />
<br />
- Don Crowley<br />
<br />
* http://www.boogdesign.com/images/buttons/microformat.png<br />
* http://www.boogdesign.com/images/buttons/microformat_enabled.png<br />
* http://www.boogdesign.com/images/buttons/emf_green.png<br />
* http://www.boogdesign.com/images/buttons/mfe_green.png<br />
* http://www.boogdesign.com/images/buttons/mwmf_green.png<br />
* http://www.boogdesign.com/images/buttons/smf_green.png<br />
* http://www.boogdesign.com/images/buttons/emf_white.png<br />
* http://www.boogdesign.com/images/buttons/mfe_white.png<br />
* http://www.boogdesign.com/images/buttons/mwmf_white.png<br />
* http://www.boogdesign.com/images/buttons/smf_white.png<br />
<br />
=== [[hcalendar|hCalendar]] ===<br />
* http://rbach.priv.at/2006/buttons/hcal.png<br />
* http://www.boogdesign.com/images/buttons/microformat_hcalendar.png<br />
* CSS-powered button from [http://www.midgard-project.org/community/events/ Midgard CMS - Event calendar]: <br />
<br />
<span class="badge" style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0; border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none; text-align: center;"><span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em; margin-right: 0.1em;">&#8250;&#8250;&#8250;</span> hCalendar</span><br />
<br />
<br />
Code (white space added for readability):<br />
<br />
<pre><nowiki><br />
<span class="badge" <br />
style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0;<br />
border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none;<br />
text-align: center;"><br />
<span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em; <br />
margin-right: 0.1em;"><br />
&amp;#8250;&amp;#8250;&amp;#8250;<br />
</span> <br />
hCalendar<br />
</span><br />
</nowiki></pre><br />
<br />
=== [[hcard|hCard]] ===<br />
* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)<br />
* http://rbach.priv.at/2006/buttons/hcard.png<br />
* http://www.boogdesign.com/images/buttons/microformat_hcard.png<br />
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]<br />
<br />
=== [[rel-license]] ===<br />
* http://rbach.priv.at/2006/buttons/license.png<br />
* http://www.boogdesign.com/images/buttons/microformat_rellicense.png<br />
<br />
=== [[rel-nofollow]] ===<br />
* http://rbach.priv.at/2006/buttons/nofollow.png<br />
* http://www.boogdesign.com/images/buttons/microformat_relnofollow.png<br />
<br />
=== [[rel-tag]] ===<br />
* http://rbach.priv.at/2006/buttons/rel-tag.png<br />
* http://rbach.priv.at/2006/buttons/tag.png<br />
* http://www.boogdesign.com/images/buttons/microformat_reltag.png<br />
<br />
=== [[vote-links|VoteLinks]] ===<br />
* http://rbach.priv.at/2006/buttons/votelinks.png<br />
* http://www.boogdesign.com/images/buttons/microformat_votelinks.png<br />
<br />
=== [http://gmpg.org/xfn/ XFN] ===<br />
* http://rbach.priv.at/2006/buttons/xfn.png<br />
* http://www.boogdesign.com/images/buttons/microformat_xfn.png<br />
<br />
=== [http://gmpg.org/xmdp/ XMDP] ===<br />
* http://rbach.priv.at/2006/buttons/xmdp.png<br />
* http://www.boogdesign.com/images/buttons/microformat_xmdp.png<br />
<br />
=== [[xoxo|XOXO]] ===<br />
* http://rbach.priv.at/2006/buttons/xoxo.png<br />
* http://www.boogdesign.com/images/buttons/microformat_xoxo.png<br />
<br />
===CSS Styles for microformats===<br />
I'm not sure wether this can be under buttons, but I don't know where else to put it. This is a stylesheet containing styles for most microformats. And, it's automatic. I release it under the cc by-sa. Please note that I am new to microformats, and if you can improve this, please do. [[User:Mac Lover|Mac Lover]] 13:25, 13 Apr 2007 (PDT)<br />
<br />
[http://creativecommons.org/licenses/by-sa/3.0/us/ License]<br />
[http://alyosha.bendebury.net/microformat-css.zip Zip]<br />
<br />
<br />
== CSS Buttons ==<br />
As there are new microformats happening all the time I set about making a CSS button that looks like the ''handmade'' versions. This is the result.<br />
<br />
The file with the CSS and the two images required (logo and background) can be downloaded from [http://thebeastlybeasts.co.uk/css/microformat_css.zip The Beastly Beasts].<br />
<br />
Extract the microformat directory and the files in it to /css so that you have:<br /><br />
/css/microformat/microformat.css<br /><br />
/css/microformat/background.png<br /><br />
/css/microformat/logo.png<br />
<br />
If your paths are different a bit of editing is needed.<br />
<br />
The XHTML to create a button is:<br />
<pre><tag class="microformat-button microformat-type"><span></span>microformat-type</tag></pre><br />
<br />
For example, an hCard button with a link to the spec:<br />
<pre><a href="http://microformats.org/wiki/hcard" title="Microformat enabled" class="microformat-button hcard"><span></span>hcard</a></pre><br />
<br />
== Buttons for draft formats ==<br />
<br />
These may be subject to change if the names of the formats change when they are released.<br />
<br />
=== [[adr]] ===<br />
* http://rbach.priv.at/2006/buttons/adr.png<br />
<br />
=== [[geo]] ===<br />
* http://rbach.priv.at/2006/buttons/geo.png<br />
<br />
=== [[hatom|hAtom]] ===<br />
* http://rbach.priv.at/2006/buttons/hatom.png<br />
<br />
=== [[hresume|hResume]] ===<br />
* http://rbach.priv.at/2006/buttons/hresume.png<br />
* http://www.boogdesign.com/images/buttons/microformat_hresume.png<br />
<br />
=== [[hreview|hReview]] ===<br />
* http://rbach.priv.at/2006/buttons/hreview.png<br />
<br />
=== [[rel-directory]] ===<br />
* http://rbach.priv.at/2006/buttons/directory.png<br />
<br />
=== [[rel-enclosure]] ===<br />
* http://rbach.priv.at/2006/buttons/enclosure.png<br />
<br />
=== [[rel-home]] ===<br />
* http://rbach.priv.at/2006/buttons/rel-home.png<br />
* http://rbach.priv.at/2006/buttons/home.png<br />
<br />
=== [[relpayment-research|rel-payment]] ===<br />
* http://rbach.priv.at/2006/buttons/payment.png<br />
<br />
=== [[robots-exclusion|Robots Exclusion]] ===<br />
* http://rbach.priv.at/2006/buttons/robots.png<br />
<br />
=== [[xfolk|xFolk]] ===<br />
* http://rbach.priv.at/2006/buttons/xfolk.png<br />
<br />
== Make your own buttons ==<br />
=== Style 1 ===<br />
<br />
Example: http://www.crowley.nl/images/hcard.png<br />
<br />
Use the [http://kalsey.com/tools/buttonmaker/ Kalsey Button Maker] with the following settings:<br />
* Outer border: #666666<br />
* Inner border: #ffffff<br />
* Bar position: 25 pixels from the left<br />
* Left box text: &gt;&gt;&gt;<br />
* Left box background: #000000<br />
* Left box text color: #ffffff<br />
* Left box text start: 7 pixels from the left<br />
* Right box text: (The name of the microformat goes here)<br />
* Right box background: #31757b<br />
* Right box text color: #ffffff<br />
* Right box text start: 3 pixels from the bar<br />
<br />
=== Style 2 ===<br />
<br />
Example: http://rbach.priv.at/2006/buttons/hcal.png<br />
<br />
# Get the font [http://www.kottke.org/plus/type/silkscreen/ Silkscreen]<br />
# Install [http://www.imagemagick.org/ ImageMagick]<br />
# Get the blank icon (http://rbach.priv.at/2006/buttons/blank.png)<br />
# Type: <br />
<pre>convert blank.png <br />
-fill white <br />
-font Silkscreen <br />
-pointsize 8 <br />
+antialias <br />
-draw "text 28,10 'button label'" <br />
output.png<br />
</pre><br />
<br />
= Microformats Logos =<br />
<br />
Rohit is a very poor CSS hacker, but gave it his best shot. He also [http://labs.commerce.net/~rohit/µf-logo.html rendered it at 72 and 18 points.] <br />
<br />
http://microformats.org/img/logo.gif<br />
<br />
<div style="position: relative; top:-46px; left:180px"><br />
<div style="background-color:#679A06; width:30px; height: 30px; left:1px; top:10px; position:absolute; -moz-border-radius:5pt;"></div><br />
<br />
<div style="background-color:#85BC07; width:22px; height: 22px; left:11.5px; top:6px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white; -moz-border-radius:4pt;"></div><br />
<br />
<div style="background-color:#AEE219; width:14px; height: 14px; left:22.5px; top:4px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white;-moz-border-radius:2pt;"></div><br />
<br />
<div style="font-family:Arial Narrow,Arial,sans-serif;font-size:17.5pt;letter-spacing:0px;color:#676767; position: absolute; left:44px; top: -6px"><br />
<span style="padding-left:9;color:#111111;vertical-align:40%">micro</span><span style="vertical-align:40%;padding-left:1pt">formats</span><br />
</div><br />
</div><br />
<br />
<br />
== Palette ==<br />
<br />
<br />
<div style="background-color:#AEE219; width:8em; height: 4ex;">#AEE219</div><br />
<br />
<div style="background-color:#85BC07; width:8em; height: 4ex;">#85BC07</div><br />
<br />
<div style="background-color:#679A06; width:8em; height: 4ex;">#679A06</div><br />
<br />
<br /><br />
I created a cheatsheet using [http://bighugelabs.com/flickr/ Big Huge Lab]'s Badgemaker:<br /><br />
[http://flickr.com/photos/hauntedpalace/1296783076/ http://farm2.static.flickr.com/1231/1296783076_1d6fe8a1f8_m_d.jpg]<br />
--[[User:CarlaHufstedler|Carla]] 12:11, 1 Sep 2007 (PDT)<br />
<br />
<br />
<br />
=Wiki buttons=<br />
For use on this wiki.<br />
*{{NewMarker}} - <nowiki>{{NewMarker}}</nowiki><br />
*{{SuccessMarker}} - <nowiki>{{SuccessMarker}}</nowiki><br />
*{{UpdateMarker}} - <nowiki>{{UpdateMarker}}</nowiki><br />
<br />
= Requests =<br />
<br />
* Logos for all microformats<br />
<br />
* When someone has time, these should be repeated on the page for each respective format.<br />
<br />
==See also==<br />
<br />
{{branding-see-also}}<br />
* <span class="POSH logos">[[posh#Spread_POSH|POSH logos and buttons]]</span></div>SamB