rel-design-pattern: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
Line 23: Line 23:
* [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]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML 4.01 definition of the <code>rel</code> attribute]
* [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel HTML 4.01 definition of the <code>rel</code> attribute]
* Microformats: [[RelLicense]], [[RelNoFollow]], [[RelTag]]
* Microformats: [[rel-license]], [[rel-nofollow]], [[rel-tag]]
* Proposals: [[rel-directory]], [[rel-enclosure]]
* Proposals: [[rel-directory]], [[rel-enclosure]]

Revision as of 18:30, 10 October 2005

Rel design pattern

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 (A with href) within a micoformat and give it a name mf-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

Description

RelTag 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