cite-rel - Revision history

Brian: Reverted edits by CooloAlacl (Talk) to last version by Tantek

2009-01-03T19:05:04Z

Reverted edits by CooloAlacl (Talk) to last version by Tantek

← Older revision		Revision as of 19:05, 3 January 2009
Line 1:		Line 1:
	~~eltchic4tde~~		= Cite-rel Draft Specification 2006–02–21 =
	= Cite-rel Draft Specification ~~2006â02â21~~ =

	=== Authors ===		=== Authors ===
Line 7:		Line 6:

	=== Acknowledgements ===		=== Acknowledgements ===
	Thanks to Tantek ~~Ãelik~~ for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.		Thanks to Tantek Çelik for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.

	=== Copyright ===		=== Copyright ===
Line 45:		Line 44:
	</blockquote>		</blockquote>

	The intended semantic meaning of the above structure is ~~âthis~~ document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.		The intended semantic meaning of the above structure is “this document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.

	===Relationship values===		===Relationship values===
	Cite-rel covers the following possible relationships between documents:		Cite-rel covers the following possible relationships between documents:
	* Via ~~â~~ a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.		* Via – a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.
	* Reply ~~â~~ a reply, as one might see in Email or Usenet discussions.		* Reply – a reply, as one might see in Email or Usenet discussions.
	* Forward ~~â~~ repeating a post or part of a post as one might forward an Email message.		* Forward – repeating a post or part of a post as one might forward an Email message.
	* Update ~~â~~ an updated version as one might see in published standards.		* Update – an updated version as one might see in published standards.

	All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.		All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.

CooloAlacl: chilili

2009-01-03T09:03:40Z

chilili

← Older revision		Revision as of 09:03, 3 January 2009
Line 1:		Line 1:
	= Cite-rel Draft Specification ~~2006–02–21~~ =		eltchic4tde
			= Cite-rel Draft Specification 2006â02â21 =

	=== Authors ===		=== Authors ===
Line 6:		Line 7:

	=== Acknowledgements ===		=== Acknowledgements ===
	Thanks to Tantek ~~Çelik~~ for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.		Thanks to Tantek Ãelik for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.

	=== Copyright ===		=== Copyright ===
Line 44:		Line 45:
	</blockquote>		</blockquote>

	The intended semantic meaning of the above structure is ~~“this~~ document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.		The intended semantic meaning of the above structure is âthis document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.

	===Relationship values===		===Relationship values===
	Cite-rel covers the following possible relationships between documents:		Cite-rel covers the following possible relationships between documents:
	* Via – a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.		* Via â a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.
	* Reply – a reply, as one might see in Email or Usenet discussions.		* Reply â a reply, as one might see in Email or Usenet discussions.
	* Forward – repeating a post or part of a post as one might forward an Email message.		* Forward â repeating a post or part of a post as one might forward an Email message.
	* Update – an updated version as one might see in published standards.		* Update â an updated version as one might see in published standards.

	All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.		All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.

Tantek: Reverted edit of RolalOlomo, changed back to last version by Tantek

2008-02-01T08:22:10Z

Reverted edit of RolalOlomo, changed back to last version by Tantek

← Older revision		Revision as of 08:22, 1 February 2008
Line 1:		Line 1:
	~~vardroncnage~~		= Cite-rel Draft Specification 2006–02–21 =
	= Cite-rel Draft Specification ~~2006â02â21~~ =

	=== Authors ===		=== Authors ===
Line 7:		Line 6:

	=== Acknowledgements ===		=== Acknowledgements ===
	Thanks to Tantek ~~Ãelik~~ for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.		Thanks to Tantek Çelik for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.

	=== Copyright ===		=== Copyright ===
Line 45:		Line 44:
	</blockquote>		</blockquote>

	The intended semantic meaning of the above structure is ~~âthis~~ document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.		The intended semantic meaning of the above structure is “this document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.

	===Relationship values===		===Relationship values===
	Cite-rel covers the following possible relationships between documents:		Cite-rel covers the following possible relationships between documents:
	* Via ~~â~~ a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.		* Via – a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.
	* Reply ~~â~~ a reply, as one might see in Email or Usenet discussions.		* Reply – a reply, as one might see in Email or Usenet discussions.
	* Forward ~~â~~ repeating a post or part of a post as one might forward an Email message.		* Forward – repeating a post or part of a post as one might forward an Email message.
	* Update ~~â~~ an updated version as one might see in published standards.		* Update – an updated version as one might see in published standards.

	All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.		All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.

RolalOlomo: c4tacelliget

2008-02-01T07:34:32Z

c4tacelliget

← Older revision		Revision as of 07:34, 1 February 2008
Line 1:		Line 1:
	= Cite-rel Draft Specification ~~2006–02–21~~ =		vardroncnage
			= Cite-rel Draft Specification 2006â02â21 =

	=== Authors ===		=== Authors ===
Line 6:		Line 7:

	=== Acknowledgements ===		=== Acknowledgements ===
	Thanks to Tantek ~~Çelik~~ for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.		Thanks to Tantek Ãelik for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.

	=== Copyright ===		=== Copyright ===
Line 44:		Line 45:
	</blockquote>		</blockquote>

	The intended semantic meaning of the above structure is ~~“this~~ document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.		The intended semantic meaning of the above structure is âthis document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.

	===Relationship values===		===Relationship values===
	Cite-rel covers the following possible relationships between documents:		Cite-rel covers the following possible relationships between documents:
	* Via – a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.		* Via â a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.
	* Reply – a reply, as one might see in Email or Usenet discussions.		* Reply â a reply, as one might see in Email or Usenet discussions.
	* Forward – repeating a post or part of a post as one might forward an Email message.		* Forward â repeating a post or part of a post as one might forward an Email message.
	* Update – an updated version as one might see in published standards.		* Update â an updated version as one might see in published standards.

	All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.		All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.

Tantek: Reverted edit of CarlaHufstedler, changed back to last version by EranGloben

2007-09-02T06:33:03Z

Reverted edit of CarlaHufstedler, changed back to last version by EranGloben

← Older revision		Revision as of 06:33, 2 September 2007
Line 110:		Line 110:
	=== Commentary ===		=== Commentary ===
	For discussion of cite-rel see [[distributed-conversation-brainstorming]] and [[distributed-conversation]].		For discussion of cite-rel see [[distributed-conversation-brainstorming]] and [[distributed-conversation]].

	~~[[Category:Specific Microformats]]~~

CarlaHufstedler: added category

2007-09-01T16:45:28Z

added category

← Older revision		Revision as of 16:45, 1 September 2007
Line 110:		Line 110:
	=== Commentary ===		=== Commentary ===
	For discussion of cite-rel see [[distributed-conversation-brainstorming]] and [[distributed-conversation]].		For discussion of cite-rel see [[distributed-conversation-brainstorming]] and [[distributed-conversation]].

			[[Category:Specific Microformats]]

EranGloben: updated link to XMDP profile

2006-02-21T21:43:28Z

updated link to XMDP profile

← Older revision		Revision as of 21:43, 21 February 2006
Line 92:		Line 92:

	== XMDP profile ==		== XMDP profile ==
	see [[~~CiteRelXmdpProfile~~\|XMDP Profile]]		see [[cite-rel-profile\|XMDP Profile]]

	== Implementations ==		== Implementations ==

EranGloben: created first draft version of cite-rel spec

2006-02-21T21:16:32Z

created first draft version of cite-rel spec

New page

= Cite-rel Draft Specification 2006–02–21 =

=== Authors ===
* EranGloben
* RyanKing

=== Acknowledgements ===
Thanks to Tantek Çelik for his inspiration and help with the original [http://theryanking.com/blog/archives/2005/05/06/hvia/ hVia specification] which eventually evolved into this.

=== Copyright ===
This specification is (C) 2005-2006 by the authors. However, the authors intend to submit this specification to a standards body with a liberal copyright/licensing policy such as the GMPG (http://gmpg.org/), IETF (http://ietf.org/), and/or W3C (http://w3.org). Anyone wishing to contribute should read their copyright principles, policies and licenses (e.g. the GMPG Principles (http://gmpg.org/principles)) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 (http://creativecommons.org/licenses/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 (http://www.w3.org/Consortium/Patent-Policy-20040205/), and IETF RFC3667 (http://www.ietf.org/rfc/rfc3667.txt) & RFC3668 (http://www.ietf.org/rfc/rfc3668.txt).

== Abstract ==
This document is the initial draft for the proposed cite-rel microformat. The author(s) wish to encourage anyone reading this document to offer their feedback, critique or opinion regarding the proposed microformat. You may do so on the distributed-discussion-issues page.

cite-rel is one of several microformats. By adding rel values to an XHTML CITE tag, a blog post (for example) can indicate its place in a distributed conversation.

Sample Simon said in
<cite class="rev-reply">
<a href="http://example.com/blog/?p=1">Example post</a>
</cite>

The author indicates that the post containing the above markup is in reply to the post at http://example.com/blog/?p=1
This assertion will typically apply to a single blog post (or other such element in an online discussion forum).

Other relationships between pages or posts are also possible, for example via links, updates of previous versions and re-blogging (or forwarding) of content.

== Scope ==
Cite-rel is specifically designed for tracking distributed conversations carried out over several online discussion forums.

This document does not cover issues related to describing blogs, defining the exact scope of a blog post and other meta-data related to it or proper formats for citation.

== Format ==
===In general===

The general structure of cite-rel is based on simple XHTML building blocks:

<cite id="ID" class="RELATION"><a href="SOURCE">source</a></cite>
<blockquote cite="#ID">
quoted text
</blockquote>

The intended semantic meaning of the above structure is “this document cites the document referenced in the link. The relationship between is as described by RELATION. The authors believe that this is a good general format for simple HTML citations. Optionally you may express the connection between the quoted text and the cited source by using the "cite" attribute in the quote/blockquote element.

===Relationship values===
Cite-rel covers the following possible relationships between documents:
* Via – a hat-tip or via link, commonly used by bloggers to give credit to someone for providing the information to the blogger.
* Reply – a reply, as one might see in Email or Usenet discussions.
* Forward – repeating a post or part of a post as one might forward an Email message.
* Update – an updated version as one might see in published standards.

All the above relationships (besides via) can be used on both original and follow-up post. To make the relationship explicitly clear we use rel and rev prefixes on those relationships in the same manner that one might use a rel or rev attribute. The resulting relationship class names are as follows.
* via
* rev-reply (this document is in reply to the cited document)
* rel-reply (the cited document is in reply to this one)
* rev-forward
* rel-forward
* rev-update
* rel-update

== Examples ==
Via: <cite class="via">
<a href="http://example.com/blog/post=17"> Mr. Example </a>
</cite>

In reply to <cite class="rev-reply">
<a href="http://Example.com/your-blog-annoys-me">
this post</a></cite>
by <a href="http://theRyanKing.com/"> Ryan King </a>.
*INSERT FLAME HERE*

This is an update to my
<cite id="cow_cite" class="rev-update">
<a href="http://Example.com/blog/?post=17">previous post</a>
</cite>
on this topic where I claimed that:
<blockquote cite="#cow_cite">
Cows can fly.
</blockquote>
Well, I now have proof!

Ryan had some
<cite class="rel-reply">
<a href="http://theryanking.com/blog/?post=1">
additional ideas
</a>
</cite>
about the format.

== XMDP profile ==
see [[CiteRelXmdpProfile|XMDP Profile]]

== Implementations ==
This section is informative. The following implementations have been developed which either generate or parse cite-rel. If you have a cite-rel implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.
* ...

=== References ===
Normative References
* HTML 4 (http://www.w3.org/TR/REC-html40/)
* XHTML (http://www.w3.org/TR/xhtml1/)
* XMDP (http://gmpg.org/xmdp/)
Informative References
* This document was originally cloned from the rel-directory specification.
* Distributed-conversation-examples
* Distributed-conversation-brainstorming

=== Commentary ===
For discussion of cite-rel see [[distributed-conversation-brainstorming]] and [[distributed-conversation]].