<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: An Old Idea</title>
	<link>http://smackman.com/2006/06/01/an-old-idea/</link>
	<description>Putting the smack down, one smack at a time</description>
	<pubDate>Wed, 10 Mar 2010 05:37:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: steve</title>
		<link>http://smackman.com/2006/06/01/an-old-idea/#comment-14</link>
		<pubDate>Thu, 01 Jun 2006 05:56:27 +0000</pubDate>
		<guid>http://smackman.com/2006/06/01/an-old-idea/#comment-14</guid>
					<description>Scott,

The point is not that the document can or cannot be parsed with a schema.  The point is that the schema allows parsers to be generated automatically rather than hand-code them for each microformat and for each programming language.

As for collisions, it's not that you couldn't write a parser that knew that an email address inside a vcard was different than an email address inside an hreview, or that hreviews might contain vcards which, in turn, might contain email addresses that should be associated with the latter.  The point is that if there is a clear grammar, then one doesn't have to worry about whether their hand parser will misread a microformat when another, unexpected microformat is nested inside it.</description>
		<content:encoded><![CDATA[<p>Scott,</p>
<p>The point is not that the document can or cannot be parsed with a schema.  The point is that the schema allows parsers to be generated automatically rather than hand-code them for each microformat and for each programming language.</p>
<p>As for collisions, it&#8217;s not that you couldn&#8217;t write a parser that knew that an email address inside a vcard was different than an email address inside an hreview, or that hreviews might contain vcards which, in turn, might contain email addresses that should be associated with the latter.  The point is that if there is a clear grammar, then one doesn&#8217;t have to worry about whether their hand parser will misread a microformat when another, unexpected microformat is nested inside it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Scott Reynen</title>
		<link>http://smackman.com/2006/06/01/an-old-idea/#comment-13</link>
		<pubDate>Thu, 01 Jun 2006 01:32:24 +0000</pubDate>
		<guid>http://smackman.com/2006/06/01/an-old-idea/#comment-13</guid>
					<description>It's not clear to me what problem this would solve. It doesn't appear to solve the problem of collision, as knowing that vcard contains email doesn't tell you that email can also be part of hreview.

Can you give a specific example of a document that could be parsed automatically with a schema, and couldn't be parsed automatically without?</description>
		<content:encoded><![CDATA[<p>It&#8217;s not clear to me what problem this would solve. It doesn&#8217;t appear to solve the problem of collision, as knowing that vcard contains email doesn&#8217;t tell you that email can also be part of hreview.</p>
<p>Can you give a specific example of a document that could be parsed automatically with a schema, and couldn&#8217;t be parsed automatically without?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: hans.gerwitz&#187; Blog Archive &#187;</title>
		<link>http://smackman.com/2006/06/01/an-old-idea/#comment-12</link>
		<pubDate>Thu, 01 Jun 2006 00:53:16 +0000</pubDate>
		<guid>http://smackman.com/2006/06/01/an-old-idea/#comment-12</guid>
					<description>[...] Microformat schema are sorely needed. Parsing for microformats presently feels&amp;#8230;clunky. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Microformat schema are sorely needed. Parsing for microformats presently feels&#8230;clunky. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
