<?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: People Writing about RDFa</title>
	<atom:link href="http://rdfa.info/2006/05/29/people-writing-about-rdfa/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdfa.info/2006/05/29/people-writing-about-rdfa/</link>
	<description>Interoperable Web Metadata</description>
	<pubDate>Sat, 22 Nov 2008 00:16:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Ben</title>
		<link>http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-7</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 31 May 2006 19:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-7</guid>
		<description>Evan,

Thanks for your comments and blog posting about RDFa. Absolutely microformats need to be taken into consideration. My vision is that, a year or two from now, folks who want to express "just calendar events", or "just business cards" will be using microformats. People who want to mix and match properties, make up their own, or express metadata about embedded images, page fragments, and the like, will be using RDFa.

My true hope is that, since RDFa is a superset of what can be expressed with Microformats (semantically, not syntactically), we'll all be using the same tools to parse them. That's what we're aiming for with the &lt;a href="http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Apr/0069.html" rel="nofollow"&gt;hGRDDL proposal&lt;/a&gt;. You should really take a look at it, because it shows that we've been thinking quite hard about how to include microformats, and still address the numerous other use cases that microformats don't cover.

The most important thing, if you're using microformats, is to add that profile URL in the head of your document. Without it, building parsing tools for microformats is going to be come very difficult.</description>
		<content:encoded><![CDATA[<p>Evan,</p>
<p>Thanks for your comments and blog posting about RDFa. Absolutely microformats need to be taken into consideration. My vision is that, a year or two from now, folks who want to express &#8220;just calendar events&#8221;, or &#8220;just business cards&#8221; will be using microformats. People who want to mix and match properties, make up their own, or express metadata about embedded images, page fragments, and the like, will be using RDFa.</p>
<p>My true hope is that, since RDFa is a superset of what can be expressed with Microformats (semantically, not syntactically), we&#8217;ll all be using the same tools to parse them. That&#8217;s what we&#8217;re aiming for with the <a href="http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Apr/0069.html" rel="nofollow">hGRDDL proposal</a>. You should really take a look at it, because it shows that we&#8217;ve been thinking quite hard about how to include microformats, and still address the numerous other use cases that microformats don&#8217;t cover.</p>
<p>The most important thing, if you&#8217;re using microformats, is to add that profile URL in the head of your document. Without it, building parsing tools for microformats is going to be come very difficult.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Linksvayer &#187; Long tail of metadata</title>
		<link>http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-5</link>
		<dc:creator>Mike Linksvayer &#187; Long tail of metadata</dc:creator>
		<pubDate>Tue, 30 May 2006 05:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-5</guid>
		<description>[...] Ben Adida notes that people are writing about RDFa, which is great, and envisioning conflict with microformats, which is not. As Ben says: Microformats are useful for expressing a few, common, well-defined vocabularies. RDFa is useful for letting publishers mix and match any vocabularies they choose. Both are useful. [...]</description>
		<content:encoded><![CDATA[<p>[...] Ben Adida notes that people are writing about RDFa, which is great, and envisioning conflict with microformats, which is not. As Ben says: Microformats are useful for expressing a few, common, well-defined vocabularies. RDFa is useful for letting publishers mix and match any vocabularies they choose. Both are useful. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: evan</title>
		<link>http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-4</link>
		<dc:creator>evan</dc:creator>
		<pubDate>Mon, 29 May 2006 23:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://rdfa.info/2006/05/29/people-writing-about-rdfa/#comment-4</guid>
		<description>Ben: how do you see microformats.org and RDFa interrelating a year from now? Two years? Five years? Considering that microformats.org is semantic HTML effort with the most traction right now, don't you think that it's worthwhile taking it into consideration?

Is there any value to Web developers and Web users in having both RDFa and microformats?</description>
		<content:encoded><![CDATA[<p>Ben: how do you see microformats.org and RDFa interrelating a year from now? Two years? Five years? Considering that microformats.org is semantic HTML effort with the most traction right now, don&#8217;t you think that it&#8217;s worthwhile taking it into consideration?</p>
<p>Is there any value to Web developers and Web users in having both RDFa and microformats?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
