<?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: Ordered lists and the START attribute</title>
	<atom:link href="http://www.maxdesign.com.au/articles/ordered-lists/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maxdesign.com.au</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 22:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: David Hucklesby</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1378</link>
		<dc:creator>David Hucklesby</dc:creator>
		<pubDate>Mon, 07 Dec 2009 02:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1378</guid>
		<description>Interesting dilemma. Speaking personally, I make good use of both spell-checker and validator during development. A strict DOCTYPE makes most sense to me. But just as I&#039;d note, but not correct some spelling &quot;errors,&quot; the same goes for HTML &quot;deprecated&quot; items where the alternatives are poor, such as this case.

In other words, checking against a strict DOCTYPE is invaluable; avoiding flagged items like a plague seems less useful...</description>
		<content:encoded><![CDATA[<p>Interesting dilemma. Speaking personally, I make good use of both spell-checker and validator during development. A strict DOCTYPE makes most sense to me. But just as I&#8217;d note, but not correct some spelling &#8220;errors,&#8221; the same goes for HTML &#8220;deprecated&#8221; items where the alternatives are poor, such as this case.</p>
<p>In other words, checking against a strict DOCTYPE is invaluable; avoiding flagged items like a plague seems less useful&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1376</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Thu, 03 Dec 2009 09:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1376</guid>
		<description>I should really thank you for the post because it has been presented in an impressive manner, its  been very useful to me and i am really looking forward for more of this sort, thank you.</description>
		<content:encoded><![CDATA[<p>I should really thank you for the post because it has been presented in an impressive manner, its  been very useful to me and i am really looking forward for more of this sort, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1374</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Tue, 01 Dec 2009 23:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1374</guid>
		<description>An interesting idea...  :)</description>
		<content:encoded><![CDATA[<p>An interesting idea&#8230;  <img src='http://www.maxdesign.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1373</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 01 Dec 2009 22:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1373</guid>
		<description>@Russ I just realised I forgot to escape my HTML syntax in the example I was trying to give - it was this: 

&lt;ol id=&quot;list1&quot;&gt; &#8230; &lt;ol continues=&quot;list1&quot;&gt;

Hopefully that works :)</description>
		<content:encoded><![CDATA[<p>@Russ I just realised I forgot to escape my HTML syntax in the example I was trying to give &#8211; it was this: </p>
<p>&lt;ol id=&#8221;list1&#8243;&gt; &hellip; &lt;ol continues=&#8221;list1&#8243;&gt;</p>
<p>Hopefully that works <img src='http://www.maxdesign.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1372</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Tue, 01 Dec 2009 21:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1372</guid>
		<description>@Brain, an interesting question. I suppose some people would argue that there are times - maybe if the numbering is more presentational... but I would find it hard to justify using a technique that disappears if CSS is turned off  :)</description>
		<content:encoded><![CDATA[<p>@Brain, an interesting question. I suppose some people would argue that there are times &#8211; maybe if the numbering is more presentational&#8230; but I would find it hard to justify using a technique that disappears if CSS is turned off  <img src='http://www.maxdesign.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1371</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 01 Dec 2009 21:06:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1371</guid>
		<description>@Russ I guess my view is that if you *have* to number ordered list items continuously throughout a document then that goes beyond the semantics that HTML can express - especially with the &quot;start&quot; attribute, which is prone to author error. Maybe a better way would be something like the &quot;for&quot; attribute for LABELs that would link two discrete OLs together so that the browser can treat them as a single list - e.g  ... .

HTML5&#039;s undeprecation of the &quot;start&quot; and &quot;type&quot; attributes seems to me to be another example of the &quot;paving the cowpaths&quot; and fits with my overall feeling about the spec that it&#039;s &quot;two steps forward, one step back&quot;.

As an aside - is there actually a valid use case for CSS Counters, given that they don&#039;t degrade gracefully?</description>
		<content:encoded><![CDATA[<p>@Russ I guess my view is that if you *have* to number ordered list items continuously throughout a document then that goes beyond the semantics that HTML can express &#8211; especially with the &#8220;start&#8221; attribute, which is prone to author error. Maybe a better way would be something like the &#8220;for&#8221; attribute for LABELs that would link two discrete OLs together so that the browser can treat them as a single list &#8211; e.g  &#8230; .</p>
<p>HTML5&#8242;s undeprecation of the &#8220;start&#8221; and &#8220;type&#8221; attributes seems to me to be another example of the &#8220;paving the cowpaths&#8221; and fits with my overall feeling about the spec that it&#8217;s &#8220;two steps forward, one step back&#8221;.</p>
<p>As an aside &#8211; is there actually a valid use case for CSS Counters, given that they don&#8217;t degrade gracefully?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jermayn</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1368</link>
		<dc:creator>Jermayn</dc:creator>
		<pubDate>Thu, 26 Nov 2009 04:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1368</guid>
		<description>Always always wanted to know how to do this, so thank you...</description>
		<content:encoded><![CDATA[<p>Always always wanted to know how to do this, so thank you&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Bunt</title>
		<link>http://www.maxdesign.com.au/articles/ordered-lists/comment-page-1/#comment-1367</link>
		<dc:creator>Stephen Bunt</dc:creator>
		<pubDate>Thu, 26 Nov 2009 00:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2009/11/24/ordered-lists/#comment-1367</guid>
		<description>I agree, Russ. This used to frustrate &amp; infuriate me (do I need to get a life?), because of the &quot;â€¦documents must be able to work with and without presentation&quot; requirement. It just didn&#039;t make sense that the document would have different &#039;content&#039; without styling. CSS counters just don&#039;t have the same _meaning_.

I often had to mark up terms &amp; conditions for many of the promotional events at KCA. These are legal documents and are very much numbered points rather than paragraphs. 

Because I had control over the code, I (grudgingly) used option 2, but I agree that option 5 is probably the best going forward.</description>
		<content:encoded><![CDATA[<p>I agree, Russ. This used to frustrate &amp; infuriate me (do I need to get a life?), because of the &#8220;â€¦documents must be able to work with and without presentation&#8221; requirement. It just didn&#8217;t make sense that the document would have different &#8216;content&#8217; without styling. CSS counters just don&#8217;t have the same _meaning_.</p>
<p>I often had to mark up terms &amp; conditions for many of the promotional events at KCA. These are legal documents and are very much numbered points rather than paragraphs. </p>
<p>Because I had control over the code, I (grudgingly) used option 2, but I agree that option 5 is probably the best going forward.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

