<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Quoting Tables; a Question of Semantics</title>
	<atom:link href="http://leftjustified.net/journal/2005/01/07/table-q/feed/" rel="self" type="application/rss+xml" />
	<link>http://leftjustified.net/journal/2005/01/07/table-q/</link>
	<description>In a few words, explain what this weblog is about.</description>
	<lastBuildDate>Thu, 09 Dec 2010 01:02:44 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen Mailer</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-1383</link>
		<dc:creator>Glen Mailer</dc:creator>
		<pubDate>Sun, 13 Mar 2005 21:32:40 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-1383</guid>
		<description>Hate to be picky, but might I point out that of the three, only the first is actually valid. Unless I&#039;m mistaken you must either use thead, tfoot &lt;strong&gt;and&lt;/strong&gt; tbody, or none of the three at all.</description>
		<content:encoded><![CDATA[<p>Hate to be picky, but might I point out that of the three, only the first is actually valid. Unless I&#8217;m mistaken you must either use thead, tfoot <strong>and</strong> tbody, or none of the three at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel Mihalache</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-395</link>
		<dc:creator>Gabriel Mihalache</dc:creator>
		<pubDate>Thu, 20 Jan 2005 22:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-395</guid>
		<description>No idea, but I just wanted to say that I really love your obsession with the semantics of it all... you managed the record of raising an issue with completly non-rendered information! Wow!
This is the kind of attitude that will push XHTML2.0 and the semnatic web forward. Keep up the good/obsessive work!</description>
		<content:encoded><![CDATA[<p>No idea, but I just wanted to say that I really love your obsession with the semantics of it all&#8230; you managed the record of raising an issue with completly non-rendered information! Wow!<br />
This is the kind of attitude that will push XHTML2.0 and the semnatic web forward. Keep up the good/obsessive work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Thomas Rasmussen</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-381</link>
		<dc:creator>Seth Thomas Rasmussen</dc:creator>
		<pubDate>Fri, 07 Jan 2005 15:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-381</guid>
		<description>My favorite number: #2!

You left a comment using the &lt;code&gt;cite&lt;/code&gt; attribute in the manner of #3 on my site not too long ago, I recall. ;) I&#039;m pretty sure I&#039;ve done the same thing at least at one point or another.

These are good details to cover, so I&#039;m glad you can be arsed to use your blog-space for it.

When you use the &lt;code&gt;cite&lt;/code&gt; attribute properly, it fascilitates some useful functionality. On my site, for instance, I use a function that reads the attribute, and if it has a value, automatically appends a link to the source within&#039; the quote.

I want to publish the function for others, but I&#039;ve yet to iron out the details with auto-linking &lt;code&gt;&lt;q /&gt;&lt;/code&gt; elements. The same function handles both.</description>
		<content:encoded><![CDATA[<p>My favorite number: #2!</p>
<p>You left a comment using the <code>cite</code> attribute in the manner of #3 on my site not too long ago, I recall. <img src='http://leftjustified.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  I&#8217;m pretty sure I&#8217;ve done the same thing at least at one point or another.</p>
<p>These are good details to cover, so I&#8217;m glad you can be arsed to use your blog-space for it.</p>
<p>When you use the <code>cite</code> attribute properly, it fascilitates some useful functionality. On my site, for instance, I use a function that reads the attribute, and if it has a value, automatically appends a link to the source within&#8217; the quote.</p>
<p>I want to publish the function for others, but I&#8217;ve yet to iron out the details with auto-linking <code>&#60;q /&#62;</code> elements. The same function handles both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: heretic</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-380</link>
		<dc:creator>heretic</dc:creator>
		<pubDate>Fri, 07 Jan 2005 00:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-380</guid>
		<description>Hmm. I&#039;d go for option two, but only since option three relies on the cite attribute which is for a URI rather than conversational text. As a result, the plain text paragraph wins out in my mind. 

Plus... personally I am wary of quoting something and not being clear enough about what is a quote and what is my own content. Since I&#039;m not sure the average user knows about semantics, I wouldn&#039;t feel comfortable relying on an attribute to make the soure clear.</description>
		<content:encoded><![CDATA[<p>Hmm. I&#8217;d go for option two, but only since option three relies on the cite attribute which is for a URI rather than conversational text. As a result, the plain text paragraph wins out in my mind. </p>
<p>Plus&#8230; personally I am wary of quoting something and not being clear enough about what is a quote and what is my own content. Since I&#8217;m not sure the average user knows about semantics, I wouldn&#8217;t feel comfortable relying on an attribute to make the soure clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-379</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 06 Jan 2005 23:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-379</guid>
		<description>I knew number three would be tempting -- looks like it caught three people before being exposed ;-). Number three does make more sense though, and since a physical publication (esp. one which is out of print) can&#039;t be expected to have a URI, surely some leverage is needed.

Paul: thanks for the photomatt link -- I missed that one first time &#039;round

Rob: The penguin was delicious!</description>
		<content:encoded><![CDATA[<p>I knew number three would be tempting &#8212; looks like it caught three people before being exposed <img src='http://leftjustified.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> . Number three does make more sense though, and since a physical publication (esp. one which is out of print) can&#8217;t be expected to have a URI, surely some leverage is needed.</p>
<p>Paul: thanks for the photomatt link &#8212; I missed that one first time &#8217;round</p>
<p>Rob: The penguin was delicious!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoffrey Sneddon</title>
		<link>http://leftjustified.net/journal/2005/01/07/table-q/#comment-378</link>
		<dc:creator>Geoffrey Sneddon</dc:creator>
		<pubDate>Thu, 06 Jan 2005 18:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2005/01/07/table-q/#comment-378</guid>
		<description>I&#039;d say 2, as the cite attribute is for URIs, and it also put&#039;s it outside the table, which IMO it has no reason to be in...</description>
		<content:encoded><![CDATA[<p>I&#8217;d say 2, as the cite attribute is for URIs, and it also put&#8217;s it outside the table, which IMO it has no reason to be in&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

