<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: hVia</title>
	<atom:link href="http://www.theryanking.com/entries/2005/05/06/hvia/feed/" rel="self" type="application/rss+xml" />
	<link>http://theryanking.com/entries/2005/05/06/hvia/</link>
	<description>Music and Technology, but NO TECHNO!</description>
	<pubDate>Thu, 09 Feb 2012 00:46:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Hellonline  &#187; Blog Archive   &#187; citeRel comments</title>
		<link>http://theryanking.com/entries/2005/05/06/hvia/#comment-504</link>
		<dc:creator>Hellonline  &#187; Blog Archive   &#187; citeRel comments</dc:creator>
		<pubDate>Tue, 28 Jun 2005 21:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/05/06/hvia/#comment-504</guid>
		<description>[...]  XHTMLâ€? and in discussions following that talk. You can read more about that on Ryanâ€™s early posts about the microformat. 	CITE A stands for citing the linked source well enough  [...]</description>
		<content:encoded><![CDATA[<p>[...]  XHTMLâ€? and in discussions following that talk. You can read more about that on Ryanâ€™s early posts about the microformat. 	CITE A stands for citing the linked source well enough  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the ryan king  &#187; Blog Archive   &#187; citeVia</title>
		<link>http://theryanking.com/entries/2005/05/06/hvia/#comment-350</link>
		<dc:creator>the ryan king  &#187; Blog Archive   &#187; citeVia</dc:creator>
		<pubDate>Tue, 10 May 2005 05:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/05/06/hvia/#comment-350</guid>
		<description>[...] 	&#8230; textually active since for a little while now. 	    	 				   	 		 			&#171; hVia 			 		 	 		 			citeVia 	 			 				Since I first wrote about  [...]</description>
		<content:encoded><![CDATA[<p>[...] 	&#8230; textually active since for a little while now. 	   </p>
<p> 			&laquo; hVia</p>
<p> 			citeVia</p>
<p> 				Since I first wrote about  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: limbo</title>
		<link>http://theryanking.com/entries/2005/05/06/hvia/#comment-348</link>
		<dc:creator>limbo</dc:creator>
		<pubDate>Mon, 09 May 2005 21:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/05/06/hvia/#comment-348</guid>
		<description>To clearly illustrate why we believe citeVia is necessary I want to talk a little bit about quoting in general. The following are my thoughts about citing and quoting, partially building on Tantekâ€™s comments. 

There are several reasons and ways for citing a reference.

A simple quote would usually be markuped as 
&lt;code&gt;&#60;cite&#62;source&#60;/cite&#62;
&#60;blockquote&#62;quote&#60;/blockquote&#62;&lt;/code&gt;

If we want to give a link to the source of the quote use the cite property of the blockquote tag:
&lt;code&gt;&#60;cite&#62;author&#60;/cite&#62;
&#60;blockquote cite=â€?source urlâ€?&#62;quote&#60;/blockquote&#62;&lt;/code&gt;

To just reference a source or person without actually quoting we use the cite tag alone. The more common case for this would be referencing a source (academic paper, journal article, book, etc.) in which case we use the following forms of mark up:

&lt;code&gt;&#60;cite&#62;author&#60;/cite&#62;&lt;/code&gt;
&lt;code&gt;&#60;a href="source or web page"&#62;&#60;cite&#62;author&#60;/cite&#62;&#60;/a&#62;&lt;/code&gt; to add a link.
&lt;code&gt;&#60;cite&#62;&#60;a href="source"&#62;author&#60;/a&#62;&#60;/cite&#62;&lt;/code&gt;

In the second case, the nesting means weâ€™re quoting a part of a work by said author and the link should lead to further information about the author or this work. The third case means weâ€™re citing the entire resource found at the linkâ€™s HREF attribute and this work was authored by the cited author. Note: this distinction comes directly from Tantekâ€™s comments on the subject.

With citeVia we wish to mark implicitly a specific sub-class of the above third case. Since via links carry specific importance and since there could be quotes of similar class (and hence similar markup) in the same document, we think that creating a specific class for via links is correct. 

Following is an example that, I hope, fully illustrates the need for specific via markup.

Blogger A (http://a.com/foo.html)
&lt;blockquote&gt;
&lt;code&gt;Foo.&lt;/code&gt;
&lt;/blockquote&gt;

Blogger B (http://b.com/on_foo.html)
&lt;blockquote&gt;
&lt;code&gt;&#60;a href="http://a.com/"&#62;&#60;cite&#62;a&#60;cite&#62;&#60;/a&#62;&#60;blockquote cite="http://a.com/foo.html"&#62;â€¦fooâ€¦&#60;/blockquote&#62;&lt;/code&gt;
&lt;/blockquote&gt;

Blogger C
&lt;blockquote&gt;
&lt;code&gt;&#60;cite&#62;&#60;a href="http://a.com/foo.html"&#62;A&#60;/a&#62;&#60;/cite&#62; says that foo 

is a interesting material
.
.
.
via: &#60;cite class=â€?viaâ€?&#62;&#60;a href="http://b.com/on_foo.html"&#62;B&#60;/a&#62;&#60;/cite&#62;&lt;/code&gt;
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>To clearly illustrate why we believe citeVia is necessary I want to talk a little bit about quoting in general. The following are my thoughts about citing and quoting, partially building on Tantekâ€™s comments. </p>
<p>There are several reasons and ways for citing a reference.</p>
<p>A simple quote would usually be markuped as<br />
<code>&lt;cite&gt;source&lt;/cite&gt;<br />
&lt;blockquote&gt;quote&lt;/blockquote&gt;</code></p>
<p>If we want to give a link to the source of the quote use the cite property of the blockquote tag:<br />
<code>&lt;cite&gt;author&lt;/cite&gt;<br />
&lt;blockquote cite=â€?source urlâ€?&gt;quote&lt;/blockquote&gt;</code></p>
<p>To just reference a source or person without actually quoting we use the cite tag alone. The more common case for this would be referencing a source (academic paper, journal article, book, etc.) in which case we use the following forms of mark up:</p>
<p><code>&lt;cite&gt;author&lt;/cite&gt;</code><br />
<code>&lt;a href="source or web page"&gt;&lt;cite&gt;author&lt;/cite&gt;&lt;/a&gt;</code> to add a link.<br />
<code>&lt;cite&gt;&lt;a href="source"&gt;author&lt;/a&gt;&lt;/cite&gt;</code></p>
<p>In the second case, the nesting means weâ€™re quoting a part of a work by said author and the link should lead to further information about the author or this work. The third case means weâ€™re citing the entire resource found at the linkâ€™s HREF attribute and this work was authored by the cited author. Note: this distinction comes directly from Tantekâ€™s comments on the subject.</p>
<p>With citeVia we wish to mark implicitly a specific sub-class of the above third case. Since via links carry specific importance and since there could be quotes of similar class (and hence similar markup) in the same document, we think that creating a specific class for via links is correct. </p>
<p>Following is an example that, I hope, fully illustrates the need for specific via markup.</p>
<p>Blogger A (http://a.com/foo.html)</p>
<blockquote><p>
<code>Foo.</code>
</p></blockquote>
<p>Blogger B (http://b.com/on_foo.html)</p>
<blockquote><p>
<code>&lt;a href="http://a.com/"&gt;&lt;cite&gt;a&lt;cite&gt;&lt;/a&gt;&lt;blockquote cite="http://a.com/foo.html"&gt;â€¦fooâ€¦&lt;/blockquote&gt;</code>
</p></blockquote>
<p>Blogger C</p>
<blockquote><p>
<code>&lt;cite&gt;&lt;a href="http://a.com/foo.html"&gt;A&lt;/a&gt;&lt;/cite&gt; says that foo </p>
<p>is a interesting material<br />
.<br />
.<br />
.<br />
via: &lt;cite class=â€?viaâ€?&gt;&lt;a href="http://b.com/on_foo.html"&gt;B&lt;/a&gt;&lt;/cite&gt;</code>
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tantek</title>
		<link>http://theryanking.com/entries/2005/05/06/hvia/#comment-346</link>
		<dc:creator>Tantek</dc:creator>
		<pubDate>Mon, 09 May 2005 08:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/05/06/hvia/#comment-346</guid>
		<description>Ryan, the example you gave is why I distinguished between a &#60;cite&#62; around an &#60;a href&#62;, and an &#60;a href&#62; around a &#60;cite&#62; (re-read my comment).  I would have marked up that example as the former if citing/quoting something Eric said in person, e.g. 

&lt;code&gt;&#60;a href="http://www.meyerweb.com"&#62;&#60;cite&#62;Eric Meyer&#60;/cite&#62;&#60;/a&#62;&lt;/code&gt;

But if citing/quoting something Eric said on meyerweb.com, then I would use the latter:

&lt;code&gt;&#60;cite&#62;&#60;a href="http://www.meyerweb.com"&#62;Eric Meyer&#60;/a&#62;&#60;/cite&#62;&lt;/code&gt;

which also expresses the exact meaning you are seeking to express with viaCite as far as I can tell, that you are quoting something you got from a particular website/blog.</description>
		<content:encoded><![CDATA[<p>Ryan, the example you gave is why I distinguished between a &lt;cite&gt; around an &lt;a href&gt;, and an &lt;a href&gt; around a &lt;cite&gt; (re-read my comment).  I would have marked up that example as the former if citing/quoting something Eric said in person, e.g. </p>
<p><code>&lt;a href="http://www.meyerweb.com"&gt;&lt;cite&gt;Eric Meyer&lt;/cite&gt;&lt;/a&gt;</code></p>
<p>But if citing/quoting something Eric said on meyerweb.com, then I would use the latter:</p>
<p><code>&lt;cite&gt;&lt;a href="http://www.meyerweb.com"&gt;Eric Meyer&lt;/a&gt;&lt;/cite&gt;</code></p>
<p>which also expresses the exact meaning you are seeking to express with viaCite as far as I can tell, that you are quoting something you got from a particular website/blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Del Vecchio</title>
		<link>http://theryanking.com/entries/2005/05/06/hvia/#comment-342</link>
		<dc:creator>Brian Del Vecchio</dc:creator>
		<pubDate>Mon, 09 May 2005 01:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/05/06/hvia/#comment-342</guid>
		<description>Ryan, I have wanted a formal way of lnking back to sources, both in blog posts and in Delicious posts.  Getting attribution right is a real sore point for me, and I think you're off to a good start here.  

I use this kind of backlinks in two different ways.  When there's a specific post that's relevant, I'll link to the post.  Otherwise I'll link back to the root of the site, if a specific link isn't available or appropriate.  

A via marker without a URL link back doesn't seem all that useful to me, since there's no way to disambiguate one &lt;a href="http://www.web-teams.co.uk/Player.asp?team=backwellunited&#38;player=Plyr15RyanKing.xml" rel="nofollow"&gt;Ryan King&lt;/a&gt; from &lt;a href="http://yalebulldogs.collegesports.com/sports/m-footbl/mtt/king_ryan00.html" rel="nofollow"&gt;another&lt;/a&gt;.
</description>
		<content:encoded><![CDATA[<p>Ryan, I have wanted a formal way of lnking back to sources, both in blog posts and in Delicious posts.  Getting attribution right is a real sore point for me, and I think you&#8217;re off to a good start here.  </p>
<p>I use this kind of backlinks in two different ways.  When there&#8217;s a specific post that&#8217;s relevant, I&#8217;ll link to the post.  Otherwise I&#8217;ll link back to the root of the site, if a specific link isn&#8217;t available or appropriate.  </p>
<p>A via marker without a URL link back doesn&#8217;t seem all that useful to me, since there&#8217;s no way to disambiguate one <a href="http://www.web-teams.co.uk/Player.asp?team=backwellunited&amp;player=Plyr15RyanKing.xml" rel="nofollow">Ryan King</a> from <a href="http://yalebulldogs.collegesports.com/sports/m-footbl/mtt/king_ryan00.html" rel="nofollow">another</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

