<?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: Semantic Weighted Lists</title>
	<atom:link href="http://ma.tt/2005/01/semantic-weighted-lists/feed/" rel="self" type="application/rss+xml" />
	<link>http://ma.tt/2005/01/semantic-weighted-lists/</link>
	<description>Unlucky in Cards</description>
	<lastBuildDate>Sat, 26 May 2012 13:00:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta4-20941</generator>
	<item>
		<title>By: david gouch</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14867</link>
		<dc:creator>david gouch</dc:creator>
		<pubDate>Sat, 05 Feb 2005 03:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14867</guid>
		<description>Two comments.

1. It&#039;s an alphabetically &lt;em&gt;ordered&lt;/em&gt; list. I wish Clark would explain why his (&quot;the best&quot;) solution uses an unordered list.

2. Nested &lt;code&gt;em&lt;/code&gt; tags!? If we can nest &lt;code&gt;em&lt;/code&gt; tags, why do we have the &lt;code&gt;strong&lt;/code&gt; tag?

The spec:

EM: indicates emphasis.
STRONG: indicates stronger emphasis.</description>
		<content:encoded><![CDATA[<p>Two comments.</p>
<p>1. It&#8217;s an alphabetically <em>ordered</em> list. I wish Clark would explain why his (&#8220;the best&#8221;) solution uses an unordered list.</p>
<p>2. Nested <code>em</code> tags!? If we can nest <code>em</code> tags, why do we have the <code>strong</code> tag?</p>
<p>The spec:</p>
<p>EM: indicates emphasis.<br />
STRONG: indicates stronger emphasis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Firas</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14793</link>
		<dc:creator>Firas</dc:creator>
		<pubDate>Fri, 04 Feb 2005 20:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14793</guid>
		<description>dave: here&#039;s a &lt;a href=&quot;http://firasd.org/weblog/2005/02/demo/index.php?style=basic&quot;&gt;demo&lt;/a&gt; of what I think you meant.

(I realize that a pingback already showed up, but just wanted to make clear that there&#039;s a CSS example just not discussion.)</description>
		<content:encoded><![CDATA[<p>dave: here&#8217;s a <a href="http://firasd.org/weblog/2005/02/demo/index.php?style=basic">demo</a> of what I think you meant.</p>
<p>(I realize that a pingback already showed up, but just wanted to make clear that there&#8217;s a CSS example just not discussion.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: firasd.org &#187; Semantics in Markup of Ranked Tag Lists</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14790</link>
		<dc:creator>firasd.org &#187; Semantics in Markup of Ranked Tag Lists</dc:creator>
		<pubDate>Fri, 04 Feb 2005 20:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14790</guid>
		<description>replaceable with with the &lt;em&gt; tag. 	So when Matt linked to Joe Clark&#8217;s post I chimed in with a rationale for using &lt;big&gt;, saying that it&#8217;s a [...]</description>
		<content:encoded><![CDATA[<p>replaceable with with the &lt;em&gt; tag. 	So when Matt linked to Joe Clark&#8217;s post I chimed in with a rationale for using &lt;big&gt;, saying that it&#8217;s a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14573</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Thu, 03 Feb 2005 02:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14573</guid>
		<description>I also wonder why the list is not ordered, but perhaps more disturbingly - suggest that the information conveyed in the weighted list by nested em tag solution is soupy at the expense of hiding a relevant piece of data (the popularity itself). I am not disputing the styled presentation but attempting html gymnastics in the name of semantics.

I fail to see how these semantics (so many nests of ems) are of benefit to man or machine and turning off CSS reveals a list with equally emphasized items, the nesting does not reveal the relevant info.

The only solution I see is to properly mark up  a table with columns for tag and popularity ,semanticly linking the two pieces of data (and exposing the popularity to client side manipulation- the part that interests me) with the scope of each row. The rows and cells can be displayed inline to create the block of text effect and the weights/size controlled with classes and the display of the numeric value set to none(I would leave it in though and just make it less prominent).</description>
		<content:encoded><![CDATA[<p>I also wonder why the list is not ordered, but perhaps more disturbingly &#8211; suggest that the information conveyed in the weighted list by nested em tag solution is soupy at the expense of hiding a relevant piece of data (the popularity itself). I am not disputing the styled presentation but attempting html gymnastics in the name of semantics.</p>
<p>I fail to see how these semantics (so many nests of ems) are of benefit to man or machine and turning off CSS reveals a list with equally emphasized items, the nesting does not reveal the relevant info.</p>
<p>The only solution I see is to properly mark up  a table with columns for tag and popularity ,semanticly linking the two pieces of data (and exposing the popularity to client side manipulation- the part that interests me) with the scope of each row. The rows and cells can be displayed inline to create the block of text effect and the weights/size controlled with classes and the display of the numeric value set to none(I would leave it in though and just make it less prominent).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Firas</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14564</link>
		<dc:creator>Firas</dc:creator>
		<pubDate>Wed, 02 Feb 2005 19:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14564</guid>
		<description>Isn&#039;t this list ordered? The tags are in alphabetical order.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t this list ordered? The tags are in alphabetical order.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tantek</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14560</link>
		<dc:creator>Tantek</dc:creator>
		<pubDate>Wed, 02 Feb 2005 17:31:14 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14560</guid>
		<description>&lt;a href=&quot;http://tantek.com/log/2005/02.html#d02t0800&quot;&gt;Joe Clark is right&lt;/a&gt; that the markup can be improved.  But I came to a slightly different markup conclusion. See http://tantek.com/log/2005/02.html#d02t0800 for details.</description>
		<content:encoded><![CDATA[<p><a href="http://tantek.com/log/2005/02.html#d02t0800">Joe Clark is right</a> that the markup can be improved.  But I came to a slightly different markup conclusion. See <a href="http://tantek.com/log/2005/02.html#d02t0800" rel="nofollow">http://tantek.com/log/2005/02.html#d02t0800</a> for details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-14265</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Thu, 27 Jan 2005 13:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-14265</guid>
		<description>You&#039;re saying that &lt;code&gt;big&lt;/code&gt; and &lt;code&gt;small&lt;/code&gt; aren&#039;t semantic? That&#039;s clearly untrue in the context of a visual graphing system like a weighted list.</description>
		<content:encoded><![CDATA[<p>You&#8217;re saying that <code>big</code> and <code>small</code> aren&#8217;t semantic? That&#8217;s clearly untrue in the context of a visual graphing system like a weighted list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david gouch</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-13948</link>
		<dc:creator>david gouch</dc:creator>
		<pubDate>Mon, 24 Jan 2005 22:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-13948</guid>
		<description>Firas:
&lt;code&gt;&lt;Big&gt;&lt;/code&gt; and &lt;code&gt;&lt;small&gt;&lt;/code&gt; mean nothing semantically: they mean &lt;code&gt;&lt;font size=&quot;+1&quot;&gt;&lt;/code&gt; and &lt;code&gt;&lt;font size=&quot;-1&quot;&gt;&lt;/code&gt;. That is no better than the current markup with inline styles on every link.

You are right that classifying all the &lt;code&gt;&lt;li&gt;&lt;/code&gt;s doesn&#039;t convey the popularity rating. Really, I had written off even being able to convey that information with markup, but now I think you can if you use &lt;code&gt;title&lt;/code&gt;s.

&lt;pre&gt;&lt;code&gt;
&lt;ol&gt;
    &lt;li class=&quot;pop-48&quot; title=&quot;this is the 48th most popular tag&quot;&gt;Bicycles&lt;/li&gt;
    &lt;li class=&quot;pop-2&quot; title=&quot;This is the 2nd most popular tag&quot;&gt;Cars&lt;/li&gt;
&lt;/ol&gt;
&lt;/code&gt;&lt;/pre&gt;

That solves everything.</description>
		<content:encoded><![CDATA[<p>Firas:<br />
<code>&lt;Big&gt;</code> and <code>&lt;small&gt;</code> mean nothing semantically: they mean <code>&lt;font size="+1"&gt;</code> and <code>&lt;font size="-1"&gt;</code>. That is no better than the current markup with inline styles on every link.</p>
<p>You are right that classifying all the <code>&lt;li&gt;</code>s doesn&#8217;t convey the popularity rating. Really, I had written off even being able to convey that information with markup, but now I think you can if you use <code>title</code>s.</p>
<pre><code>
&lt;ol&gt;
    &lt;li class="pop-48" title="this is the 48th most popular tag"&gt;Bicycles&lt;/li&gt;
    &lt;li class="pop-2" title="This is the 2nd most popular tag"&gt;Cars&lt;/li&gt;
&lt;/ol&gt;
</code></pre>
<p>That solves everything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Firas</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-13939</link>
		<dc:creator>Firas</dc:creator>
		<pubDate>Mon, 24 Jan 2005 22:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-13939</guid>
		<description>David, classifying the li&#039;s and stopping there removes the whole point of the linked post. The point is that since the larger words are not necessarily emphasized (are they?), there should be a way to convey that they are &#039;higher ranked&#039; without misusing &lt;em&gt; or &lt;strong&gt;. And hence &lt;big&gt; and &lt;small&gt; come in service.

These are the edge cases in which semantics becomes meaningless. Unless you can decide exactly what making a word larger in the tag list is actually supposed to mean. Is it more important? Is it stressed? Is it stressed in the way that &lt;em&gt; stresses words in a sentence?

Big and Small mean something that &#039;List Item&#039; doesn&#039;t.

Matt&#039;s title is somewhat misleading, because we&#039;re trying to convey meaning without conveying semantics, at least the not semantics defined in HTML. Why does a blue whale seem more majestic than a school of tuna? It&#039;s not more important, or more &#039;emphasized&#039;, but there&#039;s definitely something that&#039;s triggering a sense of comparitive significance. It&#039;s that sort of significance that a larger word in a weighted list conveys: big.

(You can, I suppose, argue that a larger tag emphasized over the surrounding ones. Which leads me to wonder whether &lt;em&gt; should have a &#039;rank&#039; attribute.)</description>
		<content:encoded><![CDATA[<p>David, classifying the li&#8217;s and stopping there removes the whole point of the linked post. The point is that since the larger words are not necessarily emphasized (are they?), there should be a way to convey that they are &#8216;higher ranked&#8217; without misusing &lt;em&gt; or &lt;strong&gt;. And hence &lt;big&gt; and &lt;small&gt; come in service.</p>
<p>These are the edge cases in which semantics becomes meaningless. Unless you can decide exactly what making a word larger in the tag list is actually supposed to mean. Is it more important? Is it stressed? Is it stressed in the way that &lt;em&gt; stresses words in a sentence?</p>
<p>Big and Small mean something that &#8216;List Item&#8217; doesn&#8217;t.</p>
<p>Matt&#8217;s title is somewhat misleading, because we&#8217;re trying to convey meaning without conveying semantics, at least the not semantics defined in HTML. Why does a blue whale seem more majestic than a school of tuna? It&#8217;s not more important, or more &#8216;emphasized&#8217;, but there&#8217;s definitely something that&#8217;s triggering a sense of comparitive significance. It&#8217;s that sort of significance that a larger word in a weighted list conveys: big.</p>
<p>(You can, I suppose, argue that a larger tag emphasized over the surrounding ones. Which leads me to wonder whether &lt;em> should have a &#8216;rank&#8217; attribute.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david gouch</title>
		<link>http://ma.tt/2005/01/semantic-weighted-lists/#comment-13804</link>
		<dc:creator>david gouch</dc:creator>
		<pubDate>Mon, 24 Jan 2005 04:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2005/01/23/semantic-weighted-lists/#comment-13804</guid>
		<description>And recommends bad markup to take its place.

Joe Clark&#039;s right about the list being an ordered one, but &lt;code&gt;big&lt;/code&gt; and &lt;code&gt;small&lt;/code&gt; tags? They don&#039;t add anything semantically. 

Just classify the &lt;code&gt;li&lt;/code&gt;s and be done with it.</description>
		<content:encoded><![CDATA[<p>And recommends bad markup to take its place.</p>
<p>Joe Clark&#8217;s right about the list being an ordered one, but <code>big</code> and <code>small</code> tags? They don&#8217;t add anything semantically. </p>
<p>Just classify the <code>li</code>s and be done with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

