Microformats Wiki - User contributions [en]

distributed-conversation-brainstorming

2005-07-13T17:09:13Z

Skeltoac: /* rel="cite" / rev="cite" */

=citeRel brainstorming=
Various parties have proposed microformats related to citations and distributed conversations. Ryan King and Eran Globen started with hVia (which became citeVia and later citeRel :-)). You can see the conversation in these blog posts:

People already cite their sources in their blog posts and it would be great (and shouldn't be too difficult) to track that information. In that vein, read [http://theryanking.com/blog/archives/2005/05/06/hvia/ this post] which covers the initial thinking on the topic. ([http://theryanking.com/blog/archives/2005/05/09/citevia/ This] was a followup post).

Later, [http://hellononline.com Eran] [http://hellonline.com/blog/?p=18 expanded the idea] to encompass not just via citations, but replies and updates as well. Follow up post [http://hellonline.com/blog/?p=19 here].

==Problem==
The basic idea we're trying to solve here is the tracking of distributed conversation- more specifically, distributed conversation between blog posts– the scope is intentionally limited here, though other aspects of distributed conversation are certainly important and related.

:A smaller portion of the problem is in identifying the most authoritative sources in a web-wide thread. In researching anything, the ability to identify a primary source is invaluable. Adding this kind of ordinality would add value to any list of related links such as a tag page.

:Citing (quoting or refering to as an authoritative source or precedent) and hat-tipping (giving credit to a non-primary source for calling attention to a primary [authoritative] source) are certainly two different animals. Common etiquette suggests use of anchor tags because they can be actuated by the user.

:I dug around at [http://www.w3.org WC3] and found rel="cite" is ''already defined'' in the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-metaAttributes.html XHTML Metainformation Attributes Module]. In the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-hyperAttributes.html XHTML 2.0 Hypertext Attribute Collection], href and cite attributes are defined and may coexist but they behave differently: The href attribute "specifies a URI that is actuated when the element is activated." For the cite attribute, "User Agents MUST provide a means for the user to actuate the link."

:Whereas authors in general like their work to be cited with hyperlinks, and whereas users can be counted upon to cite primary and non-primary sources simultaneously without differentiating them, and whereas the only difference between a primary citation and a non-primary citation is the potential for skipped vias when considered across a distributed conversation, and whereas the use of existing specifications is preferred to the creation of redundant systems, and whereas increasing attributes is less severe than increasing nested elements, I propose that good definition and use of rel="cite" will resolve the problem of crediting sources via anchors. <cite>Andy Skelton</cite>

::I see the conclusion as quite the opposite. Because rel="cite" *is* defined in XHTML2 drafts, and microformats allow you add rel values to HTML4/XHTML1 *now*, adopting the same convention makes a lot of sense.

::If anything it bolsters the case for rel="cite" (as opposed to some other value like rel="source").

::In a relCite microformat, you would define the "cite" value by normatively referencing XHTML2, rather than redefining it (even copy/pasting the definition from the XHTML2 spec -- though one could do so "informatively"), just like in [[hcard|hCard]], we define the properties by normatively referencing vCard. <cite>Tantek</cite>

:::[http://www.w3.org/TR/2005/WD-xhtml2-20050527/ XHTML 2.0] states that it "should in no way be considered stable, and should not be normatively referenced for any purposes whatsoever." <cite>Andy Skelton</cite>

== Nested cite/anchor tags ==

== rel="cite" / rev="cite" ==

This could be a way to indicate a citation of linked content, typically web pages (or portions thereof, like blog posts) but inclusive of any kind of resource with a URL. "Cite" is defined as "to quote or refer to as a precedent or authority."

By adding <code>rel="cite"</code> to a hyperlink, an author could indicate that the destination of that hyperlink is an authoritative source or a precedent to the current page. rel="cite" would be used whether an author cites by quotation:
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite">
Thomas Jefferson</a></blockquote></pre>
or by reference only:
<pre><a href="http://example.com/joeschmoe/article/99/" rel="cite">
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre>

<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred by most authors because they afford the user easy access to the cited resource.

==Additional Resources==
* Thread Description Language - TDL is an RDF vocabulary for describing threaded discussions, such as Usenet, weblogs, bulletin boards, and e-mail conversations.
** http://www.eyrie.org/~zednenem/2002/web-threads/
** http://www.eyrie.org/~zednenem/2002/wtprofile/

User:Skeltoac

2005-07-13T16:42:11Z

Skeltoac:

===Andy Skelton===
I blog at [http://www.skeltoac.com skeltoac.com] and I maintain a WordPress blog directory called [http://blogsoftheday.com Blogs Of The Day].

User:Skeltoac/RelCite

2005-07-13T16:41:16Z

Skeltoac: /* rel="cite" */

distributed-conversation-brainstorming

2005-07-13T13:28:15Z

Skeltoac: /* citeRel brainstorming */

=citeRel brainstorming=
Various parties have proposed microformats related to citations and distributed conversations. Ryan King and Eran Globen started with hVia (which became citeVia and later citeRel :-)). You can see the conversation in these blog posts:

People already cite their sources in their blog posts and it would be great (and shouldn't be too difficult) to track that information. In that vein, read [http://theryanking.com/blog/archives/2005/05/06/hvia/ this post] which covers the initial thinking on the topic. ([http://theryanking.com/blog/archives/2005/05/09/citevia/ This] was a followup post).

Later, [http://hellononline.com Eran] [http://hellonline.com/blog/?p=18 expanded the idea] to encompass not just via citations, but replies and updates as well. Follow up post [http://hellonline.com/blog/?p=19 here].

==Problem==
The basic idea we're trying to solve here is the tracking of distributed conversation- more specifically, distributed conversation between blog posts– the scope is intentionally limited here, though other aspects of distributed conversation are certainly important and related.

:A smaller portion of the problem is in identifying the most authoritative sources in a web-wide thread. In researching anything, the ability to identify a primary source is invaluable. Adding this kind of ordinality would add value to any list of related links such as a tag page.

:Citing (quoting or refering to as an authoritative source or precedent) and hat-tipping (giving credit to a non-primary source for calling attention to a primary [authoritative] source) are certainly two different animals. Common etiquette suggests use of anchor tags because they can be actuated by the user.

:I dug around at [http://www.w3.org WC3] and found rel="cite" is ''already defined'' in the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-metaAttributes.html XHTML Metainformation Attributes Module]. In the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-hyperAttributes.html XHTML 2.0 Hypertext Attribute Collection], href and cite attributes are defined and may coexist but they behave differently: The href attribute "specifies a URI that is actuated when the element is activated." For the cite attribute, "User Agents MUST provide a means for the user to actuate the link."

:Whereas authors in general like their work to be cited with hyperlinks, and whereas users can be counted upon to cite primary and non-primary sources simultaneously without differentiating them, and whereas the only difference between a primary citation and a non-primary citation is the potential for skipped vias when considered across a distributed conversation, and whereas the use of existing specifications is preferred to the creation of redundant systems, and whereas increasing attributes is less severe than increasing nested elements, I propose that good definition and use of rel="cite" will resolve the problem of crediting sources via anchors. <cite>Andy Skelton</cite>

::I see the conclusion as quite the opposite. Because rel="cite" *is* defined in XHTML2 drafts, and microformats allow you add rel values to HTML4/XHTML1 *now*, adopting the same convention makes a lot of sense.

::If anything it bolsters the case for rel="cite" (as opposed to some other value like rel="source").

::In a relCite microformat, you would define the "cite" value by normatively referencing XHTML2, rather than redefining it (even copy/pasting the definition from the XHTML2 spec -- though one could do so "informatively"), just like in [[hcard|hCard]], we define the properties by normatively referencing vCard. <cite>Tantek</cite>

:::[http://www.w3.org/TR/2005/WD-xhtml2-20050527/ XHTML 2.0] states that it "should in no way be considered stable, and should not be normatively referenced for any purposes whatsoever." <cite>Andy Skelton</cite>

== Nested cite/anchor tags ==

== rel="cite" / rev="cite" ==

==Additional Resources==
* Thread Description Language - TDL is an RDF vocabulary for describing threaded discussions, such as Usenet, weblogs, bulletin boards, and e-mail conversations.
** http://www.eyrie.org/~zednenem/2002/web-threads/
** http://www.eyrie.org/~zednenem/2002/wtprofile/

User:Skeltoac

2005-07-12T19:19:24Z

Skeltoac:

===Andy Skelton===
I blog at [http://www.skeltoac.com skeltoac.com] and I maintain a WordPress blog directory called [http://blogsoftheday.com Blogs Of The Day].

Currently working on [[User:Skeltoac/RelCite|RelCite]]

User:Skeltoac

2005-07-12T19:19:14Z

Skeltoac:

User:Skeltoac

2005-07-12T19:18:16Z

Skeltoac:

===Andy Skelton===
I blog at [http://www.skeltoac.com skeltoac.com] and I maintain a WordPress blog directory called [http://blogsoftheday.com Blogs Of The Day].

User:Skeltoac/RelCite

2005-07-12T18:46:02Z

Skeltoac: /* Implementations */

= rel="cite" =
__TOC__

== Draft Specification 2005-07-12 ==
=== Editor/Author ===
[http://www.skeltoac.com/ Andy Skelton]

=== Concept ===
*[http://theryanking.com/blog Ryan King]
*[http://hellonline.com/ Eran Globen]
*[http://www.skeltoac.com/ Andy Skelton]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==

RelCite is one of several [[elemental-microformat|elemental microformats]]. By adding <code>rel="cite"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an authoritative source or a precedent to the current page. RelCite may be used whether an author cites by quotation:
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite">
Thomas Jefferson</a></blockquote></pre>
or by reference only:
<pre><a href="http://example.com/joeschmoe/article/99/" rel="cite">
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre>

RelCite is also reversible, i.e. the syntax <code>rev="cite"</code> indicates that the ''current page'' is an authoritative source or a precedent to the ''destination page''. This syntax may be useful when an author wishes link to off-site discussions of his own content.

The linked page MUST exist, and it is the linked page, rather than the link text that defines the citation.

RelCite is fully compatible with other microformats such as [[rel-nofollow|RelNoFollow]] and [[vote-links|VoteLinks]] to indicate a very specific relationship: <code>rel="cite vote-against nofollow"</code>

== Scope ==
rel="cite" is specifically designed for "citing" content, typically web pages (or portions thereof, like blog posts). "Cite" is defined as "to quote or refer to as a precedent or authority."

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<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.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referring page quotes or refers to
the referred page as a precedent or authority.</dd>
</dl>
</dd>
<dt id="rev">rev</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here is an additional value.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referred page quotes or refers to
the referring page as a precedent or authority.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Citations As Interactive Metadata ==
<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred because they afford the user easy access to the cited resource.

== Implementations ==
A theoretical implementation of RelCite could enable users and machines to determine the degree of separation of a given resource from a Primary resource in a "citation chain" where "Primary" denotes the first, original or most authoritative online resource for a unit of information or a discussion. By following <code>rel="cite"</code> links one can expect to converge on topical Primary sources; contratriwise, following <code>rev="cite"</code> links should bring one to resources of increasingly distant relation to one Primary while exposing other citation chains in the process.

It would be advantageous for implementations of automated linking systems such as Trackback and Pingback to generate <code>rev="cite"</code> links on cited resources.

== Normative References ==
* [http://gmpg.org/xmdp/ XMDP]

User:Skeltoac/RelCite

2005-07-12T18:44:38Z

Skeltoac: /* Implementations */

= rel="cite" =
__TOC__

== Draft Specification 2005-07-12 ==
=== Editor/Author ===
[http://www.skeltoac.com/ Andy Skelton]

=== Concept ===
*[http://theryanking.com/blog Ryan King]
*[http://hellonline.com/ Eran Globen]
*[http://www.skeltoac.com/ Andy Skelton]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==

RelCite is one of several [[elemental-microformat|elemental microformats]]. By adding <code>rel="cite"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an authoritative source or a precedent to the current page. RelCite may be used whether an author cites by quotation:
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite">
Thomas Jefferson</a></blockquote></pre>
or by reference only:
<pre><a href="http://example.com/joeschmoe/article/99/" rel="cite">
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre>

RelCite is also reversible, i.e. the syntax <code>rev="cite"</code> indicates that the ''current page'' is an authoritative source or a precedent to the ''destination page''. This syntax may be useful when an author wishes link to off-site discussions of his own content.

The linked page MUST exist, and it is the linked page, rather than the link text that defines the citation.

RelCite is fully compatible with other microformats such as [[rel-nofollow|RelNoFollow]] and [[vote-links|VoteLinks]] to indicate a very specific relationship: <code>rel="cite vote-against nofollow"</code>

== Scope ==
rel="cite" is specifically designed for "citing" content, typically web pages (or portions thereof, like blog posts). "Cite" is defined as "to quote or refer to as a precedent or authority."

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<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.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referring page quotes or refers to
the referred page as a precedent or authority.</dd>
</dl>
</dd>
<dt id="rev">rev</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here is an additional value.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referred page quotes or refers to
the referring page as a precedent or authority.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Citations As Interactive Metadata ==
<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred because they afford the user easy access to the cited resource.

== Implementations ==
A theoretical implementation of RelCite could enable users and machines to determine the degree of separation of a given resource from a Primary resource in a "citation chain" where "Primary" denotes the first, original or most authoritative online resource for a unit of information or a discussion. By following <code>rel="cite"</code> links one can expect to converge on topical Primary sources; contratriwise, following <code>rev="cite"</code> links should bring one to resources of increasingly distant relation to one Primary while exposing other citation chains in the process.

It would be advantageous for implementations of automated linking systems such as Trackback and Pingback to generate <code>rev="cite"</code> links on the target documents.

== Normative References ==
* [http://gmpg.org/xmdp/ XMDP]

User:Skeltoac/RelCite

2005-07-12T18:41:05Z

Skeltoac: /* rel="cite" */

= rel="cite" =
__TOC__

== Draft Specification 2005-07-12 ==
=== Editor/Author ===
[http://www.skeltoac.com/ Andy Skelton]

=== Concept ===
*[http://theryanking.com/blog Ryan King]
*[http://hellonline.com/ Eran Globen]
*[http://www.skeltoac.com/ Andy Skelton]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==

RelCite is one of several [[elemental-microformat|elemental microformats]]. By adding <code>rel="cite"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an authoritative source or a precedent to the current page. RelCite may be used whether an author cites by quotation:
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite">
Thomas Jefferson</a></blockquote></pre>
or by reference only:
<pre><a href="http://example.com/joeschmoe/article/99/" rel="cite">
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre>

RelCite is also reversible, i.e. the syntax <code>rev="cite"</code> indicates that the ''current page'' is an authoritative source or a precedent to the ''destination page''. This syntax may be useful when an author wishes link to off-site discussions of his own content.

The linked page MUST exist, and it is the linked page, rather than the link text that defines the citation.

RelCite is fully compatible with other microformats such as [[rel-nofollow|RelNoFollow]] and [[vote-links|VoteLinks]] to indicate a very specific relationship: <code>rel="cite vote-against nofollow"</code>

== Scope ==
rel="cite" is specifically designed for "citing" content, typically web pages (or portions thereof, like blog posts). "Cite" is defined as "to quote or refer to as a precedent or authority."

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<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.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referring page quotes or refers to
the referred page as a precedent or authority.</dd>
</dl>
</dd>
<dt id="rev">rev</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here is an additional value.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referred page quotes or refers to
the referring page as a precedent or authority.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Citations As Interactive Metadata ==
<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred because they afford the user easy access to the cited resource.

== Implementations ==
A theoretical implementation of RelCite could enable users and machines to determine the degree of separation of a given resource from a Primary resource in a "citation chain" where "Primary" denotes the first, original or most authoritative online resource for a unit of information or a discussion. By following <code>rel="cite"</code> links one can expect to converge on topical Primary sources; contratriwise, following <code>rev="cite"</code> links should bring one to resources of increasingly distant relation to one Primary while exposing other citation chains in the process.

== Normative References ==
* [http://gmpg.org/xmdp/ XMDP]

User:Skeltoac/RelCite

2005-07-12T18:18:04Z

Skeltoac:

= rel="cite" =
__TOC__

== Draft Specification 2005-07-12 ==
=== Editor/Author ===
[http://www.skeltoac.com/ Andy Skelton]

=== Concept ===
*[http://theryanking.com/blog Ryan King]
*[http://hellonline.com/ Eran Globen]
*[http://www.skeltoac.com/ Andy Skelton]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==

RelCite is one of several [[elemental-microformat|elemental microformats]]. By adding <code>rel="cite"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an authoritative source or a precedent to the current page. RelCite may be used whether an author cites by quotation:
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Thomas Jefferson</a></blockquote></pre>
or by reference only:
<pre><a href="http://someblog.com/article/99/" rel="cite">
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre>

RelCite is also reversible, i.e. the syntax <code>rev="cite"</code> indicates that the ''current page'' is an authoritative source or a precedent to the ''destination page''. This syntax may be useful when an author wishes link to off-site discussions of his own content.

The linked page MUST exist, and it is the linked page, rather than the link text that defines the citation.

RelCite is fully compatible with other microformats such as [[rel-nofollow|RelNoFollow]] and [[vote-links|VoteLinks]] to indicate a very specific relationship: <code>rel="cite vote-against nofollow"</code>

== Scope ==
rel="cite" is specifically designed for "citing" content, typically web pages (or portions thereof, like blog posts). "Cite" is defined as "to quote or refer to as a precedent or authority."

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<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.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referring page quotes or refers to
the referred page as a precedent or authority.</dd>
</dl>
</dd>
<dt id="rev">rev</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here is an additional value.
<dl>
<dt id="cite">cite</dt>
<dd>Indicates that the referred page quotes or refers to
the referring page as a precedent or authority.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Citations Are Visible Metadata ==
<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred because they afford the user easy access to the cited resource.

== Normative References ==
* [http://gmpg.org/xmdp/ XMDP]

== Related Work ==
* [http://technorati.com/help/tags.html Using Technorati Tags]
* [http://developers.technorati.com/wiki/attentionxml Attention.XML]
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags "Tag plugin for wordpress"]

Main Page

2005-07-12T02:55:26Z

Skeltoac: /* Exploratory discussions */

__NOTOC__
= Microformats Wiki =
Welcome to the microformats wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.

== But First... ==

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[presentations]] are also a good place for some background reading.

== Specifications ==
[[microformats|Microformats]] open standards specifications:
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license|RelLicense]]
* [[rel-nofollow|RelNoFollow]]
* [[rel-tag|RelTag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN]
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[hreview|hReview]]
* [[robots-exclusion|Robots Exclusion]]
* [[rel-enclosure]]
* [[xfolk]]

== Exploratory discussions ==
*[[comments-formats]]
*[[media-metadata-examples]]
*[[location-formats]]
*[[blog-post-formats]]
*[[wiki-formats]]
*[[other-formats]]
*[[citation-brainstorming]]

distributed-conversation-brainstorming

2005-07-12T02:54:03Z

Skeltoac: /* Problem */