http://microformats.org/wiki/api.php?action=feedcontributions&user=Rafael+Gaspar&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-28T21:13:55ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=15670rel-product-brainstorming2006-06-11T03:28:21Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product brainstorming </h1><br />
<br />
__TOC__<br />
<br />
== What rel-product will change in your life ==<br />
<br />
With rel-product it would be easier to go to some product website by just searching for its name, for instance you want to go the iPod website, so you go to some microformat search engine that could suport rel-product and search for iPod. if some site has linked http://www.apple.com/iPod/iPod.html with rel-product you will find it.<br />
<br />
== Proposals ==<br />
<br />
=== Draft Proposal for rel-product 2006-06-10 ===<br />
==== Author ====<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
'''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]<br />
<br />
==== Copyright ====<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
==== Patents ====<br />
{{MicroFormatPatentStatement}}<br />
<br />
==== Abstract ====<br />
[[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 Product Website. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Product Website.<br />
<br />
The linked page SHOULD be the Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
=== Scope ===<br />
rel=&quot;product&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;product&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.<br />
<br />
=== XMDP profile ===<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
=== Encoding issues ===<br />
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]. <br />
<br />
=== Implementations ===<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
=== References ===<br />
==== Normative References ====<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
=== Discussion and Issues ===<br />
* This needs broader discussion on the [http://microformats.org/discuss microformats-discuss list] and proper following of the microformats [[process]] before proceeding any further.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6574rel-product-brainstorming2006-06-11T03:28:05Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product brainstorming </h1><br />
<br />
__TOC__<br />
<br />
== What rel-product will change in your life ==<br />
<br />
With rel-product it would be easier to go to some product website by just searching for its name, for instance you want to go the iPod website, so you go to some microformat search engine that could suport rel-product and search for iPod. if some site has linked http://www.apple.com/iPod/iPod.html with rel-product you will find it.<br />
<br />
== Proposals ==<br />
<br />
=== Draft Proposal for rel-product 2006-06-10 ===<br />
==== Author ====<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
'''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]<br />
<br />
==== Copyright ====<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
==== Patents ====<br />
{{MicroFormatPatentStatement}}<br />
<br />
==== Abstract ====<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Product Website.<br />
<br />
The linked page SHOULD be the Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
=== Scope ===<br />
rel=&quot;product&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;product&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.<br />
<br />
=== XMDP profile ===<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
=== Encoding issues ===<br />
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]. <br />
<br />
=== Implementations ===<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
=== References ===<br />
==== Normative References ====<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
=== Discussion and Issues ===<br />
* This needs broader discussion on the [http://microformats.org/discuss microformats-discuss list] and proper following of the microformats [[process]] before proceeding any further.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6573rel-product-brainstorming2006-06-11T03:27:34Z<p>Rafael Gaspar: /* Scope */</p>
<hr />
<div><h1> rel-product brainstorming </h1><br />
<br />
__TOC__<br />
<br />
== What rel-product will change in your life ==<br />
<br />
With rel-product it would be easier to go to some product website by just searching for its name, for instance you want to go the iPod website, so you go to some microformat search engine that could suport rel-product and search for iPod. if some site has linked http://www.apple.com/iPod/iPod.html with rel-product you will find it.<br />
<br />
== Proposals ==<br />
<br />
=== Draft Proposal for rel-product 2006-06-10 ===<br />
==== Author ====<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
'''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]<br />
<br />
==== Copyright ====<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
==== Patents ====<br />
{{MicroFormatPatentStatement}}<br />
<br />
==== Abstract ====<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
=== Scope ===<br />
rel=&quot;product&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;product&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.<br />
<br />
=== XMDP profile ===<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
=== Encoding issues ===<br />
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]. <br />
<br />
=== Implementations ===<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
=== References ===<br />
==== Normative References ====<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
=== Discussion and Issues ===<br />
* This needs broader discussion on the [http://microformats.org/discuss microformats-discuss list] and proper following of the microformats [[process]] before proceeding any further.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6572rel-product-brainstorming2006-06-11T03:26:33Z<p>Rafael Gaspar: /* Problem Description */</p>
<hr />
<div><h1> rel-product brainstorming </h1><br />
<br />
__TOC__<br />
<br />
== What rel-product will change in your life ==<br />
<br />
With rel-product it would be easier to go to some product website by just searching for its name, for instance you want to go the iPod website, so you go to some microformat search engine that could suport rel-product and search for iPod. if some site has linked http://www.apple.com/iPod/iPod.html with rel-product you will find it.<br />
<br />
== Proposals ==<br />
<br />
=== Draft Proposal for rel-product 2006-06-10 ===<br />
==== Author ====<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
'''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]<br />
<br />
==== Copyright ====<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
==== Patents ====<br />
{{MicroFormatPatentStatement}}<br />
<br />
==== Abstract ====<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
=== Scope ===<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.<br />
<br />
=== XMDP profile ===<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
=== Encoding issues ===<br />
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]. <br />
<br />
=== Implementations ===<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
=== References ===<br />
==== Normative References ====<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
=== Discussion and Issues ===<br />
* This needs broader discussion on the [http://microformats.org/discuss microformats-discuss list] and proper following of the microformats [[process]] before proceeding any further.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=Main_Page&diff=29213Main Page2006-06-10T19:31:12Z<p>Rafael Gaspar: /* Drafts */</p>
<hr />
<div>__NOTOC__<br />
__NOTOC__<br />
= Microformats Wiki =<br />
<br />
'''Please read [[how-to-play]] before making any edits.'''<br />
<br />
'''Please read [[process]] before proposing any new microformats.'''<br />
<br />
== Introduction ==<br />
<br />
[[what-are-microformats|What are microformats]]? And [[what-can-you-do-with-microformats|what can you do with them]]? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also a good place for some background reading/listening. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]]<br />
* [[hcard|hCard]]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]] {{NewMarker}}<br />
* [[rel-product]] {{NewMarker}}<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''<br />
<br />
* [[abbr-design-pattern]]<br />
* [[class-design-pattern]]<br />
* [[datetime-design-pattern]]<br />
* [[existing-classes|class names defined across all microformats]]<br />
* [[include-pattern]] {{NewMarker}}<br />
* [[rel-design-pattern]]<br />
<br />
== Exploratory discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*[[attention]]<br />
*[[blog-description-examples]]<br />
*[[blog-info-examples]]<br />
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])<br />
*[[book-examples]], [[book-formats]], [[book-brainstorming]]<br />
*[[chat-examples]], [[chat-formats]]<br />
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]<br />
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])<br />
*[[directions-examples]] {{NewMarker}}<br />
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])<br />
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]<br />
*[[forms-examples]]<br />
*[[genealogy-formats]]<br />
*[[hash-examples]]<br />
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]<br />
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}<br />
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]<br />
*[[location-formats]]. (see also [[adr]] and [[geo]])<br />
*[[media-info-examples]]<br />
*[[meeting-minutes-examples]], [[meeting-minutes-formats]], [[meeting-minutes-brainstorming]]<br />
*[[mfo-examples]]<br />
*[[music-examples]]<br />
*[[other-formats]]<br />
*[[photo-note-examples]]<br />
*[[recipe-examples]]<br />
*[[requirements-testing]], [[requirements-testing-examples]]<br />
*[[rest-examples]]<br />
*[[resume-brainstorming]], [[resume-formats]]<br />
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)<br />
*[[search-results-example]]<br />
*[[show-brainstorming]]<br />
*[[showroll-brainstorming]]<br />
*[[table-examples]]<br />
*[[tagspeak-examples]]<br />
*[[transit-table-examples]]<br />
*[[uid]]<br />
*[[widget-examples]], [[widget-brainstorming]]<br />
*[[wiki-formats]]<br />
*[[work-of-art]] {{NewMarker}}<br />
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]] {{NewMarker}}<br />
<br />
<br />
== Tools & Test Cases & Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository]<br />
*[[vcard-implementations]], [[vcard-errata]]<br />
*[[icalendar-implementations]]<br />
*[[faqs-for-rdf]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in <del>many different</del> other languages<br />
<br />
=== microformats wiki languages with over 2 articles ===<br />
<br />
* [[Main_Page-fr|Français (French)]]<br />
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}<br />
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=Main_Page&diff=29212Main Page2006-06-10T19:30:54Z<p>Rafael Gaspar: /* Drafts */</p>
<hr />
<div>__NOTOC__<br />
__NOTOC__<br />
= Microformats Wiki =<br />
<br />
'''Please read [[how-to-play]] before making any edits.'''<br />
<br />
'''Please read [[process]] before proposing any new microformats.'''<br />
<br />
== Introduction ==<br />
<br />
[[what-are-microformats|What are microformats]]? And [[what-can-you-do-with-microformats|what can you do with them]]? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also a good place for some background reading/listening. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]]<br />
* [[hcard|hCard]]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]] {{NewMarker}}<br />
* [[rel-product]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''<br />
<br />
* [[abbr-design-pattern]]<br />
* [[class-design-pattern]]<br />
* [[datetime-design-pattern]]<br />
* [[existing-classes|class names defined across all microformats]]<br />
* [[include-pattern]] {{NewMarker}}<br />
* [[rel-design-pattern]]<br />
<br />
== Exploratory discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*[[attention]]<br />
*[[blog-description-examples]]<br />
*[[blog-info-examples]]<br />
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])<br />
*[[book-examples]], [[book-formats]], [[book-brainstorming]]<br />
*[[chat-examples]], [[chat-formats]]<br />
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]<br />
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])<br />
*[[directions-examples]] {{NewMarker}}<br />
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])<br />
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]<br />
*[[forms-examples]]<br />
*[[genealogy-formats]]<br />
*[[hash-examples]]<br />
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]<br />
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}<br />
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]<br />
*[[location-formats]]. (see also [[adr]] and [[geo]])<br />
*[[media-info-examples]]<br />
*[[meeting-minutes-examples]], [[meeting-minutes-formats]], [[meeting-minutes-brainstorming]]<br />
*[[mfo-examples]]<br />
*[[music-examples]]<br />
*[[other-formats]]<br />
*[[photo-note-examples]]<br />
*[[recipe-examples]]<br />
*[[requirements-testing]], [[requirements-testing-examples]]<br />
*[[rest-examples]]<br />
*[[resume-brainstorming]], [[resume-formats]]<br />
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)<br />
*[[search-results-example]]<br />
*[[show-brainstorming]]<br />
*[[showroll-brainstorming]]<br />
*[[table-examples]]<br />
*[[tagspeak-examples]]<br />
*[[transit-table-examples]]<br />
*[[uid]]<br />
*[[widget-examples]], [[widget-brainstorming]]<br />
*[[wiki-formats]]<br />
*[[work-of-art]] {{NewMarker}}<br />
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]] {{NewMarker}}<br />
<br />
<br />
== Tools & Test Cases & Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository]<br />
*[[vcard-implementations]], [[vcard-errata]]<br />
*[[icalendar-implementations]]<br />
*[[faqs-for-rdf]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in <del>many different</del> other languages<br />
<br />
=== microformats wiki languages with over 2 articles ===<br />
<br />
* [[Main_Page-fr|Français (French)]]<br />
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}<br />
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6564rel-product-brainstorming2006-06-10T19:27:28Z<p>Rafael Gaspar: /* Scope */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6561rel-product-brainstorming2006-06-10T19:26:29Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the product name.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6560rel-product-brainstorming2006-06-10T19:26:09Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6559rel-product-brainstorming2006-06-10T19:25:51Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the OFFICIAL Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6558rel-product-brainstorming2006-06-10T19:25:35Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to OFFICIAL Product Website.<br />
<br />
The linked page SHOULD be the Official Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6557rel-product-brainstorming2006-06-10T19:25:08Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[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 Offical Product Website. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Official Product Website.<br />
<br />
The linked page SHOULD be the Official Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6556rel-product-brainstorming2006-06-10T19:24:29Z<p>Rafael Gaspar: /* Abstract */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[rel-product]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;product&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is the Offical Product Website. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Official Product Website.<br />
<br />
The linked page SHOULD be the Official Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6555rel-product-brainstorming2006-06-10T19:23:16Z<p>Rafael Gaspar: /* Draft Specification 2005-01-10 */</p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2006-06-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[Rel-Product]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;product&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is the Offical Product Website. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Official Product Website.<br />
<br />
The linked page SHOULD be the Official Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gasparhttp://microformats.org/wiki/index.php?title=rel-product-brainstorming&diff=6554rel-product-brainstorming2006-06-10T19:22:47Z<p>Rafael Gaspar: </p>
<hr />
<div><h1> rel-product </h1><br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-01-10 ==<br />
=== Editor/Author ===<br />
[http://www.eucomomaca.vocepod.com/ Rafael Gaspar]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[Rel-Product]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;product&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is the Offical Product Website. <br />
<br />
e.g. by placing this link on a page,<br />
<br />
<pre><nowiki><a href=&quot;http://www.apple.com/ipod/ipod.html&quot; rel=&quot;product&quot;>iPod</a></nowiki></pre><br />
<br />
the author indicates that the link points to Official Product Website.<br />
<br />
The linked page SHOULD be the Official Website, And the text of the hyperlink SHOULD be the Product Name.<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for referencing the OFFICIAL website of the product; content, typically hosted on its own company website.<br />
<br />
rel=&quot;tag&quot; is NOT designed for referencing arbitrary URLs or Shopping Websites with this product. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;product&quot;>product</dt><br />
<dd>Indicates that the referred resource is the OFFICIAL website of the product specified into the hyperlink text.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Encoding issues ==<br />
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]. <br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
By now there is no rel-product implementation.<br />
<br />
My idea is a search engine like [http://kitchen.technorati.com/contact/search/ Technorati Contact Search]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
<br />
== Discussions ==<br />
* Feedback is encouraged on the [[rel-product-feedback]] page.<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-product-issues|rel-product issues]] document.</div>Rafael Gaspar