Difference between revisions of "rel-product-brainstorming"

From Microformats Wiki
rel-product-brainstorming
Jump to navigation Jump to search
(changed text of rel-product to be more of a brainstorming page (since process was not followed))
Line 1: Line 1:
<h1> rel-product </h1>
+
<h1> rel-product brainstorming </h1>
  
 
__TOC__
 
__TOC__
  
== Draft Specification 2006-06-10 ==
+
== Problem Description ==
=== Editor/Author ===
+
 
 +
What is the problem that a rel-product microformat is trying to solve?
 +
 
 +
Per the microformats [[process]], there needs to first be
 +
# A proper specific problem statement
 +
# Research and documentation of [[examples]] in a [[rel-product-examples]] page
 +
# Research and documentation of any preexisting formats in a [[rel-product-formats]] page
 +
 
 +
 
 +
== Proposals ==
 +
 
 +
=== Draft Proposal for rel-product 2006-06-10 ===
 +
==== Author ====
 
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]
 
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]
  
=== Copyright ===
+
'''Rafael, please read 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|xFolk]] or [[hreview|hReview]]. - [http://tantek.com Tantek]
 +
 
 +
==== Copyright ====
 
{{MicroFormatCopyrightStatement2004}}
 
{{MicroFormatCopyrightStatement2004}}
  
=== Patents ===
+
==== Patents ====
 
{{MicroFormatPatentStatement}}
 
{{MicroFormatPatentStatement}}
  
== Abstract ==
+
==== Abstract ====
[[rel-product]] is one of several [[MicroFormats]].  By adding <code>rel=&quot;product&quot;</code> to an hyperlink indicates that the destination of that hyperlink is the OFFICIAL Product Website.  
+
[[rel-product]] is a proposal for a microformat.  By adding <code>rel=&quot;product&quot;</code> to an hyperlink indicates that the destination of that hyperlink is the OFFICIAL Product Website.  
  
 
e.g. by placing this link on a page,
 
e.g. by placing this link on a page,
Line 24: Line 38:
 
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.
 
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.
  
== Scope ==
+
=== Scope ===
 
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.
 
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.
  
 
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.
 
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.
  
== XMDP profile ==
+
=== XMDP profile ===
 
<pre><nowiki>
 
<pre><nowiki>
 
<dl class=&quot;profile&quot;>
 
<dl class=&quot;profile&quot;>
Line 45: Line 59:
 
</nowiki></pre>
 
</nowiki></pre>
  
== Encoding issues ==
+
=== Encoding issues ===
 
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986].  
 
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986].  
  
== Implementations ==
+
=== Implementations ===
 
This section is '''informative'''.
 
This section is '''informative'''.
  
Line 55: Line 69:
 
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]
 
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]
  
== References ==
+
=== References ===
=== Normative References ===
+
==== Normative References ====
 
* [http://www.w3.org/TR/REC-html40/ HTML 4]
 
* [http://www.w3.org/TR/REC-html40/ HTML 4]
 
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
 
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
Line 63: Line 77:
  
  
== Discussions ==
+
=== Discussion and Issues ===
* Feedback is encouraged on the [[rel-product-feedback]] page.
+
* This needs broader discussion on the [http://microformats.org/discuss microformats-discuss list] and proper following of the microformats [[process]] before proceeding any further.
 
 
=== Issues ===
 
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.
 

Revision as of 21:13, 10 June 2006

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


Proposals

Draft Proposal for rel-product 2006-06-10

Author

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

Copyright

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.

Patents

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

Abstract

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="http://www.apple.com/ipod/ipod.html" 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.

Scope

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>
 <dd><p>
   <a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
     HTML4 definition of the 'rel' attribute.</a>  
   Here is an additional value.</p>
  <dl>
   <dt id="product">product</dt>
   <dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd>
  </dl>
 </dd>
</dl>

Encoding issues

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

Implementations

This section is informative.

By now there is no rel-product implementation.

My idea is a search engine like Technorati Contact Search

References

Normative References

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


Discussion and Issues