<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: HTML5 Microdata Fantasy</title>
	<atom:link href="http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/</link>
	<description>Don Park's Personal Blog</description>
	<lastBuildDate>Sun, 21 Aug 2011 19:05:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: none</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-981</link>
		<dc:creator><![CDATA[none]]></dc:creator>
		<pubDate>Fri, 29 Jul 2011 17:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-981</guid>
		<description><![CDATA[&quot;There are lots of wholes in this sketch which is why it’s a fantasy.&quot;
I first read that as &quot;There are lots of whores in this sketch which is why it’s a fantasy.&quot;

Which didn&#039;t make sense in the context (but makes sense otherwise). I then realised you meant &quot;There are lots of holes in this sketch which is why it’s a fantasy.&quot;

Curse that double-you!]]></description>
		<content:encoded><![CDATA[<p>&#8220;There are lots of wholes in this sketch which is why it’s a fantasy.&#8221;<br />
I first read that as &#8220;There are lots of whores in this sketch which is why it’s a fantasy.&#8221;</p>
<p>Which didn&#8217;t make sense in the context (but makes sense otherwise). I then realised you meant &#8220;There are lots of holes in this sketch which is why it’s a fantasy.&#8221;</p>
<p>Curse that double-you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lun0</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-600</link>
		<dc:creator><![CDATA[lun0]]></dc:creator>
		<pubDate>Thu, 04 Jun 2009 23:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-600</guid>
		<description><![CDATA[hehehe awesome stuff]]></description>
		<content:encoded><![CDATA[<p>hehehe awesome stuff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Gibbs</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-591</link>
		<dc:creator><![CDATA[Simon Gibbs]]></dc:creator>
		<pubDate>Thu, 14 May 2009 19:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-591</guid>
		<description><![CDATA[If you were to put city state, zip and street elements in a namespace and use CSS3 selectors then you wouldn&#039;t need any syntax transformation in the page, or anywhere else. 

Once the elements are in a namespace and the markup is valid XML getting to RDF (via GRDLL) or unmarshalling objects (XPath, JAX-B) is easy - everyone is happy. Most intelligent people are able to grok XML namespaces given a few days of exposure to them.

Given CSS3 rather than a def element there is very little missing from standards and tools, so this is not especially fantastic.]]></description>
		<content:encoded><![CDATA[<p>If you were to put city state, zip and street elements in a namespace and use CSS3 selectors then you wouldn&#8217;t need any syntax transformation in the page, or anywhere else. </p>
<p>Once the elements are in a namespace and the markup is valid XML getting to RDF (via GRDLL) or unmarshalling objects (XPath, JAX-B) is easy &#8211; everyone is happy. Most intelligent people are able to grok XML namespaces given a few days of exposure to them.</p>
<p>Given CSS3 rather than a def element there is very little missing from standards and tools, so this is not especially fantastic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donpark</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-590</link>
		<dc:creator><![CDATA[donpark]]></dc:creator>
		<pubDate>Wed, 13 May 2009 16:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-590</guid>
		<description><![CDATA[If it&#039;s done on client-side, only that I think this is easier to learn than XSLT. If XSLT transform is server-side, this is easier to use as well. I find XSLT learning curve rather steep for average HTML jockey.]]></description>
		<content:encoded><![CDATA[<p>If it&#8217;s done on client-side, only that I think this is easier to learn than XSLT. If XSLT transform is server-side, this is easier to use as well. I find XSLT learning curve rather steep for average HTML jockey.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Taylor</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-589</link>
		<dc:creator><![CDATA[Philip Taylor]]></dc:creator>
		<pubDate>Wed, 13 May 2009 08:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-589</guid>
		<description><![CDATA[How would your idea differ from simply defining all the data in a separate machine-readable XML file and then using XSLT (or some other templating language) to construct the HTML from it?]]></description>
		<content:encoded><![CDATA[<p>How would your idea differ from simply defining all the data in a separate machine-readable XML file and then using XSLT (or some other templating language) to construct the HTML from it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donpark</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-588</link>
		<dc:creator><![CDATA[donpark]]></dc:creator>
		<pubDate>Wed, 13 May 2009 07:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-588</guid>
		<description><![CDATA[Yeah, I know. I was there when IE core guys explained how the IE worked during a W3C DOM WG meeting. If I could, I would bury W3C in the sand then build an out house over it.]]></description>
		<content:encoded><![CDATA[<p>Yeah, I know. I was there when IE core guys explained how the IE worked during a W3C DOM WG meeting. If I could, I would bury W3C in the sand then build an out house over it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Hineline</title>
		<link>http://blog.docuverse.com/2009/05/12/html5-microdata-fantasy/#comment-587</link>
		<dc:creator><![CDATA[Douglas Hineline]]></dc:creator>
		<pubDate>Wed, 13 May 2009 06:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.docuverse.com/?p=276#comment-587</guid>
		<description><![CDATA[You can&#039;t stop a stampede my man.  The general html semantics has too much momentum to change direction too much, besides we&#039;re just now starting to get browsers that act somewhat similar.  In the end it is all just XML nodes, but try telling that to IE.]]></description>
		<content:encoded><![CDATA[<p>You can&#8217;t stop a stampede my man.  The general html semantics has too much momentum to change direction too much, besides we&#8217;re just now starting to get browsers that act somewhat similar.  In the end it is all just XML nodes, but try telling that to IE.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

