<?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: BBC Rejects hCalendar Microformat Because Of Accessibility Concerns</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Tue, 02 Dec 2008 04:01:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: PatrickSamphire</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-754566</link>
		<dc:creator>PatrickSamphire</dc:creator>
		<pubDate>Wed, 02 Jul 2008 09:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-754566</guid>
		<description>Excellent post. I've been frustrated about hCalendar over this issue for ages. I would love to use the hCalendar microformat, but not when it inconveniences some of my users. That the microformat community hasn't bothered to deal with this serious issue that has been known for a long time is undermining what is basically a fantastic idea.</description>
		<content:encoded><![CDATA[<p>Excellent post. I&#8217;ve been frustrated about hCalendar over this issue for ages. I would love to use the hCalendar microformat, but not when it inconveniences some of my users. That the microformat community hasn&#8217;t bothered to deal with this serious issue that has been known for a long time is undermining what is basically a fantastic idea.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: brothercake</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751400</link>
		<dc:creator>brothercake</dc:creator>
		<pubDate>Fri, 27 Jun 2008 00:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751400</guid>
		<description>Agreed - pretend XHTML is just HTML, so no advantage over HTML.  But real XHTML is XML, and can use namespaces.  

And it's the same markup.

It is worth using XHTML, even if it's only error-handled HTML for some browsers, because for other browsers it can be used as XML. 

And even where it's only HTML, namespaced information can still be set and extracted programatically (albeit in a mangled way); as a principle, that appears to be working nicely for ARIA, don't see why it couldn't work for UF too. And even if the bottom line is semantic information that IE can't use, I still think that's better than what's happening now.</description>
		<content:encoded><![CDATA[<p>Agreed - pretend XHTML is just HTML, so no advantage over HTML.  But real XHTML is XML, and can use namespaces.  </p>
<p>And it&#8217;s the same markup.</p>
<p>It is worth using XHTML, even if it&#8217;s only error-handled HTML for some browsers, because for other browsers it can be used as XML. </p>
<p>And even where it&#8217;s only HTML, namespaced information can still be set and extracted programatically (albeit in a mangled way); as a principle, that appears to be working nicely for ARIA, don&#8217;t see why it couldn&#8217;t work for UF too. And even if the bottom line is semantic information that IE can&#8217;t use, I still think that&#8217;s better than what&#8217;s happening now.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AutisticCuckoo</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751273</link>
		<dc:creator>AutisticCuckoo</dc:creator>
		<pubDate>Thu, 26 Jun 2008 18:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751273</guid>
		<description>&lt;blockquote&gt;The whole point though is that maybe if more people did use ‘pretend XHTML’, it would cause the browser manufacturers to but proper XHTML support higher up on their priority list, so it isn’t entirely useless.&lt;/blockquote&gt;
Why would they? Pretend-XHTML doesn't benefit from XHTML support, since it's HTML.

Just look at the millions of pretend-XHTML sites on the 'Net today. They don't seem to have swayed Microsoft into making an effort, have they?

Now, if lots of important sites were to use &lt;em&gt;real&lt;/em&gt; XHTML, thus barring IE users from access, &lt;em&gt;that&lt;/em&gt; might provide an incentive for Mr Ballmer et al. But of course that's not going to happen. Catch-22. Chicken and egg.</description>
		<content:encoded><![CDATA[<blockquote><p>The whole point though is that maybe if more people did use ‘pretend XHTML’, it would cause the browser manufacturers to but proper XHTML support higher up on their priority list, so it isn’t entirely useless.</p></blockquote>
<p>Why would they? Pretend-XHTML doesn&#8217;t benefit from XHTML support, since it&#8217;s HTML.</p>
<p>Just look at the millions of pretend-XHTML sites on the &#8216;Net today. They don&#8217;t seem to have swayed Microsoft into making an effort, have they?</p>
<p>Now, if lots of important sites were to use <em>real</em> XHTML, thus barring IE users from access, <em>that</em> might provide an incentive for Mr Ballmer et al. But of course that&#8217;s not going to happen. Catch-22. Chicken and egg.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: RyanR</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751245</link>
		<dc:creator>RyanR</dc:creator>
		<pubDate>Thu, 26 Jun 2008 17:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751245</guid>
		<description>@Stormrider

How would that help, you're not using any XML features so the browser vendors would carry on as normal. If people used proper XHTML as XML then maybe that would have changed things, but due to IE and the excessive XML error handling people won't go near proper XHTML.</description>
		<content:encoded><![CDATA[<p>@Stormrider</p>
<p>How would that help, you&#8217;re not using any XML features so the browser vendors would carry on as normal. If people used proper XHTML as XML then maybe that would have changed things, but due to IE and the excessive XML error handling people won&#8217;t go near proper XHTML.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stormrider</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751211</link>
		<dc:creator>Stormrider</dc:creator>
		<pubDate>Thu, 26 Jun 2008 14:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751211</guid>
		<description>"If, instead of using pretend-XHTML, authors had put pressure on browser vendors (one in particular, you know who) to support real XHTM"

The whole point though is that maybe if more people did use 'pretend XHTML', it would cause the browser manufacturers to but proper XHTML support higher up on their priority list, so it isn't entirely useless.</description>
		<content:encoded><![CDATA[<p>&#8220;If, instead of using pretend-XHTML, authors had put pressure on browser vendors (one in particular, you know who) to support real XHTM&#8221;</p>
<p>The whole point though is that maybe if more people did use &#8216;pretend XHTML&#8217;, it would cause the browser manufacturers to but proper XHTML support higher up on their priority list, so it isn&#8217;t entirely useless.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: RyanR</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751154</link>
		<dc:creator>RyanR</dc:creator>
		<pubDate>Thu, 26 Jun 2008 12:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751154</guid>
		<description>AutisticCuckoo is correct, faux XHTML (sent as text/html) is invalid HTML not XHTML. So a namespace would be useless.

However people are free to use true XHTML as XML, but they don't because IE can't handle it (not to mention the error handling).</description>
		<content:encoded><![CDATA[<p>AutisticCuckoo is correct, faux XHTML (sent as text/html) is invalid HTML not XHTML. So a namespace would be useless.</p>
<p>However people are free to use true XHTML as XML, but they don&#8217;t because IE can&#8217;t handle it (not to mention the error handling).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AutisticCuckoo</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-751082</link>
		<dc:creator>AutisticCuckoo</dc:creator>
		<pubDate>Thu, 26 Jun 2008 08:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-751082</guid>
		<description>Lots of people agree with you that Hixie is wrong (he isn't), and &lt;em&gt;that&lt;/em&gt; is the main reason we're not using XHTML today – and that we probably never will.

Pretend-XHTML is just invalid HTML, and HTML doesn't support namespaces. If, instead of using pretend-XHTML, authors had put pressure on browser vendors (one in particular, you know who) to support real XHTML, then we might have been able to use XML namespaces by now.

Anyway, isn't it a bit ironic that proponents of microformats (who claim to care about semantics) so blatantly disregard semantics in abusing &lt;code&gt;abbr&lt;/code&gt; this way?</description>
		<content:encoded><![CDATA[<p>Lots of people agree with you that Hixie is wrong (he isn&#8217;t), and <em>that</em> is the main reason we&#8217;re not using XHTML today – and that we probably never will.</p>
<p>Pretend-XHTML is just invalid HTML, and HTML doesn&#8217;t support namespaces. If, instead of using pretend-XHTML, authors had put pressure on browser vendors (one in particular, you know who) to support real XHTML, then we might have been able to use XML namespaces by now.</p>
<p>Anyway, isn&#8217;t it a bit ironic that proponents of microformats (who claim to care about semantics) so blatantly disregard semantics in abusing <code>abbr</code> this way?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tyssen</title>
		<link>http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/#comment-750397</link>
		<dc:creator>Tyssen</dc:creator>
		<pubDate>Wed, 25 Jun 2008 03:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2579#comment-750397</guid>
		<description>I think RDFa is probably the way forward too so am looking forward to the developments in that space.</description>
		<content:encoded><![CDATA[<p>I think RDFa is probably the way forward too so am looking forward to the developments in that space.</p>]]></content:encoded>
	</item>
</channel>
</rss>
