<?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: Dogster and Catster Local now Support hCard Microformat</title>
	<atom:link href="http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/</link>
	<description></description>
	<lastBuildDate>Wed, 11 Nov 2009 17:26:48 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Ted R.</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-19202</link>
		<dc:creator>Ted R.</dc:creator>
		<pubDate>Tue, 27 Mar 2007 00:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-19202</guid>
		<description>Thanks Michael.

I&#039;ve lowered the vcard class assignment into listingAddressAndAttributes and used the include pattern to pull in the org name from the outer div. Works like a charm.

I also added &#039;org&#039; along with the &#039;fn&#039; class assignment.

Finally, your Operator plugin has been invaluable for debugging. It has immediately joined WebDeveloper and Firebug as must-have development Add-Ons.

Anyone reading can download it here: https://addons.mozilla.org/en-US/firefox/addon/4106</description>
		<content:encoded><![CDATA[<p>Thanks Michael.</p>
<p>I&#8217;ve lowered the vcard class assignment into listingAddressAndAttributes and used the include pattern to pull in the org name from the outer div. Works like a charm.</p>
<p>I also added &#8216;org&#8217; along with the &#8216;fn&#8217; class assignment.</p>
<p>Finally, your Operator plugin has been invaluable for debugging. It has immediately joined WebDeveloper and Firebug as must-have development Add-Ons.</p>
<p>Anyone reading can download it here: <a href="https://addons.mozilla.org/en-US/firefox/addon/4106" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/4106</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kaply</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-18395</link>
		<dc:creator>Michael Kaply</dc:creator>
		<pubDate>Thu, 22 Mar 2007 17:51:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-18395</guid>
		<description>I&#039;m actually wrong. Using Firebug, I see that vcard would need to be on pageColCenterInner because your fn for your vcard is the first h1 (pagetitle)

I think is this an example of a PERFECT candidate for the include pattern (http://microformats.org/wiki/include-pattern)

Here&#039;s how it would work.

Add vcard to listingAddressAndAttributes.

Then add an id to the h1 that contains the name of the business (we&#039;ll use id=bus_title)

Then add this to the vcard:

&lt;a href=&quot;#bus_title&quot; class=&quot;include&quot;&gt;&lt;/a&gt;

and you have your hcard</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually wrong. Using Firebug, I see that vcard would need to be on pageColCenterInner because your fn for your vcard is the first h1 (pagetitle)</p>
<p>I think is this an example of a PERFECT candidate for the include pattern (<a href="http://microformats.org/wiki/include-pattern" rel="nofollow">http://microformats.org/wiki/include-pattern</a>)</p>
<p>Here&#8217;s how it would work.</p>
<p>Add vcard to listingAddressAndAttributes.</p>
<p>Then add an id to the h1 that contains the name of the business (we&#8217;ll use id=bus_title)</p>
<p>Then add this to the vcard:</p>
<p>&lt;a href=&#8221;#bus_title&#8221; class=&#8221;include&#8221;&gt;&lt;/a&gt;</p>
<p>and you have your hcard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted R.</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-18392</link>
		<dc:creator>Ted R.</dc:creator>
		<pubDate>Thu, 22 Mar 2007 16:51:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-18392</guid>
		<description>By the way everyone, Michael Kaply is the author of the amazing Operator plugin and a true Microformats expert. It&#039;s great to have him here. 

For example I just learned that Operator has a debug mode which give amazing visibility into exactly what is being extracted with your microformat and why.

Brizzziliant!</description>
		<content:encoded><![CDATA[<p>By the way everyone, Michael Kaply is the author of the amazing Operator plugin and a true Microformats expert. It&#8217;s great to have him here. </p>
<p>For example I just learned that Operator has a debug mode which give amazing visibility into exactly what is being extracted with your microformat and why.</p>
<p>Brizzziliant!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kaply</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-18389</link>
		<dc:creator>Michael Kaply</dc:creator>
		<pubDate>Thu, 22 Mar 2007 15:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-18389</guid>
		<description>Why did you guys choose to make the entire page content the vcard instead of just putting the vcard around the relevant data? For 

http://www.dogster.com/local/TX/Austin/Pet_Friendly_Restaurants/Whole_foods_market-58043

for instance, the vcard was added to a near toplevel div (pagecontent).

It could have been added as low as listingAddressAndAttributes and still worked, and then the label wouldn&#039;t be nested in the vcard.</description>
		<content:encoded><![CDATA[<p>Why did you guys choose to make the entire page content the vcard instead of just putting the vcard around the relevant data? For </p>
<p><a href="http://www.dogster.com/local/TX/Austin/Pet_Friendly_Restaurants/Whole_foods_market-58043" rel="nofollow">http://www.dogster.com/local/TX/Austin/Pet_Friendly_Restaurants/Whole_foods_market-58043</a></p>
<p>for instance, the vcard was added to a near toplevel div (pagecontent).</p>
<p>It could have been added as low as listingAddressAndAttributes and still worked, and then the label wouldn&#8217;t be nested in the vcard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted R.</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-18388</link>
		<dc:creator>Ted R.</dc:creator>
		<pubDate>Thu, 22 Mar 2007 15:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-18388</guid>
		<description>Thanks Michael,

That&#039;s the kind of community support I always hoped for! I&#039;ve been using Operator since I saw you speak at SXSW, but not for debugging, so that&#039;s a great tip.

The one issue I have is that &#039;label&#039; is a common class name we use on our site for 3 years now. It would be annoying to change. I&#039;m going to to have to go look for the way to indicate a certain class should NOT be considered part of the hCard.

And then I&#039;ll yank it out from the search results page. (And ad the org class ;)</description>
		<content:encoded><![CDATA[<p>Thanks Michael,</p>
<p>That&#8217;s the kind of community support I always hoped for! I&#8217;ve been using Operator since I saw you speak at SXSW, but not for debugging, so that&#8217;s a great tip.</p>
<p>The one issue I have is that &#8216;label&#8217; is a common class name we use on our site for 3 years now. It would be annoying to change. I&#8217;m going to to have to go look for the way to indicate a certain class should NOT be considered part of the hCard.</p>
<p>And then I&#8217;ll yank it out from the search results page. (And ad the org class ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kaply</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-18384</link>
		<dc:creator>Michael Kaply</dc:creator>
		<pubDate>Thu, 22 Mar 2007 14:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-18384</guid>
		<description>Great choice putting microformats on your website! I did find a few issues I wanted to point out.

1. When you do a Local Search, there is a microformat on that page that doesn&#039;t make sense. It&#039;s vcard with an fn of &quot;Local Search&quot;

2. the hCard for individual business when you click on them from local search does not contain &quot;org&quot; on the fn. This means that they are not actually marked as businesses, so the cards could get parsed incorrectly.

3. the hCard for individual businesses contains some erroneous label content related to the review. I think it&#039;s because the class &quot;label&quot; was used for something unrelated to the hCard, but it is nested in the hCard.

Incidentally, I found all these issues using Operator.

https://addons.mozilla.org/firefox/4106/</description>
		<content:encoded><![CDATA[<p>Great choice putting microformats on your website! I did find a few issues I wanted to point out.</p>
<p>1. When you do a Local Search, there is a microformat on that page that doesn&#8217;t make sense. It&#8217;s vcard with an fn of &#8220;Local Search&#8221;</p>
<p>2. the hCard for individual business when you click on them from local search does not contain &#8220;org&#8221; on the fn. This means that they are not actually marked as businesses, so the cards could get parsed incorrectly.</p>
<p>3. the hCard for individual businesses contains some erroneous label content related to the review. I think it&#8217;s because the class &#8220;label&#8221; was used for something unrelated to the hCard, but it is nested in the hCard.</p>
<p>Incidentally, I found all these issues using Operator.</p>
<p><a href="https://addons.mozilla.org/firefox/4106/" rel="nofollow">https://addons.mozilla.org/firefox/4106/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: microformatique - a blog about microformats and &#8220;data at the edges&#8221; : Dogster and Catster and microformats</title>
		<link>http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/comment-page-1/#comment-17659</link>
		<dc:creator>microformatique - a blog about microformats and &#8220;data at the edges&#8221; : Dogster and Catster and microformats</dc:creator>
		<pubDate>Tue, 20 Mar 2007 08:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogster.com/2007/03/19/dogster-and-catster-local-now-support-hcard-microformat/#comment-17659</guid>
		<description>[...] Dogster and Catster, the social networking sites for dog and cat owners and lovers have just announced support for hCard for pet related business listings, and promise upcoming hListings and hReviews. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dogster and Catster, the social networking sites for dog and cat owners and lovers have just announced support for hCard for pet related business listings, and promise upcoming hListings and hReviews. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
