rel-design-pattern: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) (→See Also: existing-rel-values) |
|||
| (12 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
= Rel design pattern = | = Rel design pattern = | ||
'''There is no need for the notion of "rel design pattern". Simply using the rel attribute as it is defined in the HTML spec is not a "design pattern". It's not a "design". It's not a "pattern". It's just using a single feature as it is defined in a spec.''' | |||
[[to-do]]: | |||
# go through all the [[Special:WhatLinksHere/rel-design-pattern|pages that link to this one]] and edit them to not depend on this page, they should simply refer to a [[rel]] attribute page if anything. | |||
# delete most of the content of this page, and leave in place a warning to avoid creating unnecessary "-design-pattern" pages which are simply restatements of using a single feature as already defined in another spec. | |||
[[User:Tantek|Tantek]] 23:43, 30 September 2009 (UTC) | |||
== Purpose == | == Purpose == | ||
| Line 30: | Line 38: | ||
== See Also == | == See Also == | ||
* | * {{rel-related-pages}} | ||
* [[Main_Page#Design_Patterns|All microformat design patterns]] | * [[Main_Page#Design_Patterns|All microformat design patterns]] | ||
* [http://www.w3.org/TR/REC-html40/struct/links.html#edef-A HTML 4.01 definition of the <code>A</code> element] | * [http://www.w3.org/TR/REC-html40/struct/links.html#edef-A HTML 4.01 definition of the <code>A</code> element] | ||
| Line 36: | Line 44: | ||
* Microformats: [[rel-license]], [[rel-nofollow]], [[rel-tag]] | * Microformats: [[rel-license]], [[rel-nofollow]], [[rel-tag]] | ||
* Proposals: [[rel-directory]], [[rel-enclosure]] | * Proposals: [[rel-directory]], [[rel-enclosure]] | ||
* [[votelinks-faq|VoteLinks FAQ]] Discusses issues with rel v. rev | * [[votelinks-faq|VoteLinks FAQ]] Discusses issues with rel v. rev | ||
Latest revision as of 04:58, 7 April 2013
Rel design pattern
There is no need for the notion of "rel design pattern". Simply using the rel attribute as it is defined in the HTML spec is not a "design pattern". It's not a "design". It's not a "pattern". It's just using a single feature as it is defined in a spec.
- go through all the pages that link to this one and edit them to not depend on this page, they should simply refer to a rel attribute page if anything.
- delete most of the content of this page, and leave in place a warning to avoid creating unnecessary "-design-pattern" pages which are simply restatements of using a single feature as already defined in another spec.
Tantek 23:43, 30 September 2009 (UTC)
Purpose
Use the rel-design-pattern to indicate the meaning of a link (i.e. a href) in an XHTML document
How to use it
- define the semantic meaning of a link (
Awithhref) within a microformat and give it a namemf-rel-value- this definition may also extend to the value of elements and text enclosed by the link
- add
rel="mf-rel-value"to hyperlinks that have that semantic meaning within that microformat. - simple microformats that use only the rel-design-pattern are typically named after the rel-value
Examples
rel="bookmark"
The HTML4 spec describes a bookmark as "a link to a key entry point within an extended document". By convention (citation needed), this entry point also captures the notion of a "permalink".
<a href="archive/entry.html" rel="bookmark">A Document Entry</a>
rel="tag"
rel-tag defines semantic meaning for by the URI and enclosed elements using rel="tag"
<a href="http://technorati.com/tag/tech" rel="tag">tech</a>
See Also
- rel
- existing rel values
- rel examples
- rel FAQ
- rel design pattern
- rel values issues
- rel-registry
- All microformat design patterns
- HTML 4.01 definition of the
Aelement - HTML 4.01 definition of the
relattribute - Microformats: rel-license, rel-nofollow, rel-tag
- Proposals: rel-directory, rel-enclosure
- VoteLinks FAQ Discusses issues with rel v. rev