<?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: The Trouble With hCard and Microformats in General</title>
	<atom:link href="http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/feed/" rel="self" type="application/rss+xml" />
	<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/</link>
	<description>Web Standards, Web Culture, Web Everything.™</description>
	<pubDate>Thu, 21 Aug 2008 20:01:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Sarven Capadisli</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-40599</link>
		<dc:creator>Sarven Capadisli</dc:creator>
		<pubDate>Tue, 20 May 2008 07:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-40599</guid>
		<description>I've written about the microformats misconceptions and the common criticisms here: http://www.csarven.ca/microformats-misconceptions

I don't believe that the whole microformats concept is faulty or useless if localisation is an issue. Keep in mind that microformats is adopting *existing* standards (e.g., vCard) for most common patterns. The root of the problem is outside of microformats and it would be great if it could be solved easily.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve written about the microformats misconceptions and the common criticisms here: <a href="http://www.csarven.ca/microformats-misconceptions" rel="nofollow">http://www.csarven.ca/microformats-misconceptions</a></p>
<p>I don&#8217;t believe that the whole microformats concept is faulty or useless if localisation is an issue. Keep in mind that microformats is adopting *existing* standards (e.g., vCard) for most common patterns. The root of the problem is outside of microformats and it would be great if it could be solved easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ara Pehlivanian</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-39891</link>
		<dc:creator>Ara Pehlivanian</dc:creator>
		<pubDate>Tue, 15 Apr 2008 15:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-39891</guid>
		<description>@Nathan: Yes, but you never see a "p" tag in clear text. It's under the hood. Microformats require that "tel" or "home" be in the clear.

@Ian: I didn't think much about i18n either till I got hit with a scenario that required it.</description>
		<content:encoded><![CDATA[<p>@Nathan: Yes, but you never see a &#8220;p&#8221; tag in clear text. It&#8217;s under the hood. Microformats require that &#8220;tel&#8221; or &#8220;home&#8221; be in the clear.</p>
<p>@Ian: I didn&#8217;t think much about i18n either till I got hit with a scenario that required it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Smith</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-39890</link>
		<dc:creator>Nathan Smith</dc:creator>
		<pubDate>Tue, 15 Apr 2008 14:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-39890</guid>
		<description>While I'm all for internationalization, is not HTML itself a bit too English-centric? A paragraph tag, for instance, derives the "P" from the English word for paragraph. So it is with DIV, for division, etc. We have to draw the line somewhere, if only for the sake of being able to support parsers. :)</description>
		<content:encoded><![CDATA[<p>While I&#8217;m all for internationalization, is not HTML itself a bit too English-centric? A paragraph tag, for instance, derives the &#8220;P&#8221; from the English word for paragraph. So it is with DIV, for division, etc. We have to draw the line somewhere, if only for the sake of being able to support parsers. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-39888</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Tue, 15 Apr 2008 14:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-39888</guid>
		<description>Any ideas on how to do it better? 

I personally don't have a huge amount of experience with localization, and I have a feeling many of the people in the MicroFormats community might be in the same boat. I didn't even realize that the formats wouldn't work for other languages. I believe that the type can be any value, though I may be mistaken.

In all honesty, I wouldn't mind if Microsoft embraced Microformats. It would be better than using a more proprietary format and it would give Microformats some visiblity. If MicroFomats were natively supported in IE8, or even added to IE7 through a patch, that would likely make a lot more developers take notice.</description>
		<content:encoded><![CDATA[<p>Any ideas on how to do it better? </p>
<p>I personally don&#8217;t have a huge amount of experience with localization, and I have a feeling many of the people in the MicroFormats community might be in the same boat. I didn&#8217;t even realize that the formats wouldn&#8217;t work for other languages. I believe that the type can be any value, though I may be mistaken.</p>
<p>In all honesty, I wouldn&#8217;t mind if Microsoft embraced Microformats. It would be better than using a more proprietary format and it would give Microformats some visiblity. If MicroFomats were natively supported in IE8, or even added to IE7 through a patch, that would likely make a lot more developers take notice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Snook</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-39885</link>
		<dc:creator>Jonathan Snook</dc:creator>
		<pubDate>Tue, 15 Apr 2008 13:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-39885</guid>
		<description>The interesting thing here is that Microformats are less likely to receive browser endorsement if it can't support i18n. What you'll end up with is a company like Microsoft embracing and extending the format.</description>
		<content:encoded><![CDATA[<p>The interesting thing here is that Microformats are less likely to receive browser endorsement if it can&#8217;t support i18n. What you&#8217;ll end up with is a company like Microsoft embracing and extending the format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://arapehlivanian.com/2008/04/15/the-trouble-with-hcard-and-microformats-in-general/#comment-39880</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Tue, 15 Apr 2008 12:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=380#comment-39880</guid>
		<description>I think the challenge comes down to the limitations of the markup. The advantage of a vCard is that it doesn't adhere to any standards other than it's own. An hCard tries to accomplish the same functionality, but is constrained to html standards.

I personally think that MicroFormats are a great idea, but they don't really have enouhg adoption by vendors to make it worthwhile in many cases. Once browsers start natively recognizing and supporting MicroFormats, there will likely be some additional work put into localization and some of the other technical issues.</description>
		<content:encoded><![CDATA[<p>I think the challenge comes down to the limitations of the markup. The advantage of a vCard is that it doesn&#8217;t adhere to any standards other than it&#8217;s own. An hCard tries to accomplish the same functionality, but is constrained to html standards.</p>
<p>I personally think that MicroFormats are a great idea, but they don&#8217;t really have enouhg adoption by vendors to make it worthwhile in many cases. Once browsers start natively recognizing and supporting MicroFormats, there will likely be some additional work put into localization and some of the other technical issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
