From Microformats Wiki
rel-product-brainstorming /
Revision as of 21:13, 10 June 2006 by Tantek (talk | contribs) (changed text of rel-product to be more of a brainstorming page (since process was not followed))
Jump to navigation Jump to search

rel-product brainstorming

Problem Description

What is the problem that a rel-product microformat is trying to solve?

Per the microformats The microformats process, there needs to first be

  1. A proper specific problem statement
  2. Research and documentation of Best Practices for Examples Pages in a rel-product-examples page
  3. Research and documentation of any preexisting formats in a rel-product-formats page


Draft Proposal for rel-product 2006-06-10


Rafael Gaspar

Rafael, please read the microformats The microformats process and please join the microformats-discuss list so we can help walk you through the steps in the process in order to best develop your idea for a microformat. E.g. there may better names, as what you are focusing on for this is the OFFICIALness rather than the PRODUCTness of the destination of the link. In addition, what you are describing is not really a relationship FROM the source TO the destination (please read rel-faq), what you are describing is more something "about" the destination, which is perhaps better done by tagging the destination link as "OFFICIAL" either via xFolk or hReview. - Tantek


This specification is (C) 2004-2020 by the authors. However, the authors intend to submit (or already have submitted, see details in the spec) this specification to a standards body with a liberal copyright/licensing policy such as the GMPG, IETF, and/or W3C. Anyone wishing to contribute should read their copyright principles, policies and licenses (e.g. the GMPG Principles) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 and later), before contributing.


This specification is subject to a royalty free patent policy, e.g. per the W3C Patent Policy, and IETF RFC3667 & RFC3668.


rel-product is a proposal for a microformat. By adding rel="product" to an hyperlink indicates that the destination of that hyperlink is the OFFICIAL Product Website.

e.g. by placing this link on a page,

<a href="" rel="product">iPod</a>

the author indicates that the link points to OFFICIAL Product Website.

The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.


rel="tag" is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.

rel="tag" is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.

XMDP profile

<dl class="profile">
 <dt id="rel">rel</dt>
   <a rel="help" href="">
     HTML4 definition of the 'rel' attribute.</a>  
   Here is an additional value.</p>
   <dt id="product">product</dt>
   <dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd>

Encoding issues

Spaces can be encoded either as + or %20. Unicode characters are encoded as specified in RFC 3986.


This section is informative.

By now there is no rel-product implementation.

My idea is a search engine like Technorati Contact Search


Normative References

  • HTML 4
  • XHTML 1
  • XMDP
  • RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

Discussion and Issues