<?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: The (Failing) Semantic Web</title>
	<atom:link href="http://www.orangeninja.com/2007/05/12/the-failing-semantic-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.orangeninja.com/2007/05/12/the-failing-semantic-web/</link>
	<description>Life, the Universe, and Everything In It</description>
	<lastBuildDate>Wed, 31 Mar 2010 09:09:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Justin Smith</title>
		<link>http://www.orangeninja.com/2007/05/12/the-failing-semantic-web/#comment-12</link>
		<dc:creator>Justin Smith</dc:creator>
		<pubDate>Tue, 10 Jul 2007 23:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.orangeninja.com/2007/05/09/the-failing-semantic-web/#comment-12</guid>
		<description>I think you hit the nail on the head when you say that there&#039;s no perceived benefit for 99% of the population to add syntactically correct markup.  Sure, that one percent of sites out there who can count a blind user as one of their patrons might see a benefit to ensuring that their product can be sold to him/her too, but when at least half of all sites (note I say sites, and not pages) are Joe Smith in his parent&#039;s basement raging against the machine about why he&#039;s grounded, there&#039;s never going to be a mass exodus to proper markup.

The other part of the problem is, as you said, the WYSIWYG editors that already add scores of useless markup as it is.  I don&#039;t think it&#039;s due to the lack of context, but rather the fact that there really isn&#039;t a single &quot;standard&quot;.  Sure there&#039;s HTML 4.01/XHTML 1.1, but they are notoriously out of date, and as such, the separate browser developers like Microsoft, Mozilla, and Opera have taken it upon themselves to build upon them.

The whole scenario is really a whole catch-22: how do the WYSIWYG editors add features if each browser has its own set of &quot;quirks&quot;, how do the browser developers get rid of the quirks if there&#039;s no set standard, and how does a standard get implemented if no one who uses the WYSIWYG editors care anyways?

I guess it&#039;s anyone&#039;s guess how we get ourselves out of this mess.</description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head when you say that there&#8217;s no perceived benefit for 99% of the population to add syntactically correct markup.  Sure, that one percent of sites out there who can count a blind user as one of their patrons might see a benefit to ensuring that their product can be sold to him/her too, but when at least half of all sites (note I say sites, and not pages) are Joe Smith in his parent&#8217;s basement raging against the machine about why he&#8217;s grounded, there&#8217;s never going to be a mass exodus to proper markup.</p>
<p>The other part of the problem is, as you said, the WYSIWYG editors that already add scores of useless markup as it is.  I don&#8217;t think it&#8217;s due to the lack of context, but rather the fact that there really isn&#8217;t a single &#8220;standard&#8221;.  Sure there&#8217;s HTML 4.01/XHTML 1.1, but they are notoriously out of date, and as such, the separate browser developers like Microsoft, Mozilla, and Opera have taken it upon themselves to build upon them.</p>
<p>The whole scenario is really a whole catch-22: how do the WYSIWYG editors add features if each browser has its own set of &#8220;quirks&#8221;, how do the browser developers get rid of the quirks if there&#8217;s no set standard, and how does a standard get implemented if no one who uses the WYSIWYG editors care anyways?</p>
<p>I guess it&#8217;s anyone&#8217;s guess how we get ourselves out of this mess.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
