<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MaisonBisson.com &#187; microformats</title>
	<atom:link href="http://maisonbisson.com/blog/post/tag/microformats/feed/" rel="self" type="application/rss+xml" />
	<link>http://maisonbisson.com</link>
	<description>A bunch of stuff I would have emailed you about.</description>
	<lastBuildDate>Sat, 14 Nov 2009 20:14:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Yelp: A Poster Child For Semantic Markup</title>
		<link>http://maisonbisson.com/blog/post/14078/yelp-a-poster-child-for-semantic-markup/</link>
		<comments>http://maisonbisson.com/blog/post/14078/yelp-a-poster-child-for-semantic-markup/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 16:48:24 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[semantic markup]]></category>
		<category><![CDATA[semantic web]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/?p=14078</guid>
		<description><![CDATA[
Search Engine Land.com:
Yelp&#8230;is&#8230;essentially a poster-child for semantic markup. This spring, Google’s introduction of rich snippets has allowed Yelp’s listings in the SERPs to stand out more, attracting consumers to click more due to the “bling” decorating the listings in the form of the star ratings.
There are now some very good reasons why sites with ratings [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-14078"><!-- &nbsp; --></abbr>
<p><a href="http://searchengineland.com/brave-new-world-for-yellow-pages-google-nabs-marketshare-strangles-local-directories-25492">Search Engine Land.com</a>:</p>
<blockquote><p>Yelp&#8230;is&#8230;essentially a poster-child for semantic markup. This spring, Google’s introduction of rich snippets has allowed Yelp’s listings in the SERPs to stand out more, attracting consumers to click more due to the “bling” decorating the listings in the form of the star ratings.</p>
<p>There are now some very good reasons why sites with ratings and reviews should be adopting microformats, and it’s not that hard to do! For a more detailed explanation, read my recap on the subject, <a href="http://www.semclubhouse.com/why-use-microformats/">Why Use Microformats</a>?</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/14078/yelp-a-poster-child-for-semantic-markup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>hNews Might Not Be So Bad</title>
		<link>http://maisonbisson.com/blog/post/14008/hnews-might-not-be-so-bad/</link>
		<comments>http://maisonbisson.com/blog/post/14008/hnews-might-not-be-so-bad/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 15:29:37 +0000</pubDate>
		<dc:creator>Casey</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[hNews]]></category>
		<category><![CDATA[markup]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[news]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/?p=14008</guid>
		<description><![CDATA[
The AP&#8217;s diagram of their Protect, Point, Pay “news DRM” scheme looked like a joke, then I saw the parody.
Despite all the smoke and hype, Ed Felton explains that it&#8217;s underwhelming, at most. Still, hNews might be an interesting format for some blogs to adopt. Most of what the AP is rattling their saber about [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-14008"><!-- &nbsp; --></abbr>
<p>The <a href="http://www.ap.org/media/images/APnewsregistry.jpg">AP&#8217;s diagram</a> of their <a href="http://www.ap.org/pages/about/pressreleases/pr_072309a.html">Protect, Point, Pay “news DRM” scheme</a> looked like a joke, then <a href="http://imgur.com/DzZdf.jpg">I saw the parody</a>.</p>
<p>Despite all the smoke and hype, Ed Felton explains that <a title="AP's DRM Announcement: Much Ado About Nothing | Freedom to Tinker" href="http://freedom-to-tinker.com/blog/felten/aps-drm-announcement-much-ado-about-nothing">it&#8217;s underwhelming, at most</a>. Still, <a title="Value Added News" href="http://www.valueaddednews.org/technical/techspec">hNews</a> might be an interesting format for some blogs to adopt. Most of what the AP is rattling their saber about is in the <a title="Value Added News" href="http://www.valueaddednews.org/technical/techspec#Rights">rights</a> (containing <a href="http://wiki.creativecommons.org/images/d/d6/Ccrel-1.0.pdf">ccREL</a> declarations). Felton thinks the dependence on ccREL may extend derivative usage rights, rather than limit them. ccREL, after all, “states unequivocally that it does not limit users&#8217; rights already granted by copyright and can only convey further rights to the user.”</p>
<p>Okay, so hNews mightn&#8217;t be so bad, but what&#8217;s good about it? It brings together a number of pieces that we all expect in a news story (and many other stories). It makes it easy to identify the <a title="4.3.2 Dateline" href="http://www.valueaddednews.org/technical/techspec#Dateline">dateline</a> and <a title="4.3.3 Geo" href="http://www.valueaddednews.org/technical/techspec#Geo">geocoding</a> of a particular story, as well as the <a title="4.3.1 Source Organization" href="http://www.valueaddednews.org/technical/techspec#Source_Organization">publisher</a> and its <a title="4.3.5 Principles" href="http://www.valueaddednews.org/technical/techspec#Principles">principles</a>.</p>
<p>Oddly, the format doesn&#8217;t appear to address media within the content, but perhaps they expect us to leverage <a title="Media RSS - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Media_RSS">Media RSS</a> and <a title="» Facebook’s Favorite Metadata MaisonBisson.com" href="http://maisonbisson.com/blog/post/13726/facebooks-favorite-metadata/"><code>rel=image_src</code> links</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/14008/hnews-might-not-be-so-bad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Recommends Microformats and RDFa</title>
		<link>http://maisonbisson.com/blog/post/13988/google-recommends-microformats-and-rdfa/</link>
		<comments>http://maisonbisson.com/blog/post/13988/google-recommends-microformats-and-rdfa/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 19:11:24 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[rdfa]]></category>
		<category><![CDATA[structured data]]></category>
		<category><![CDATA[webmaster tools]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/?p=13988</guid>
		<description><![CDATA[
Google&#8217;s own webmasters help site recommends microformats and RDFa structured data to improve indexing and usefulness of the data. Review metadata appears to have full support, while people, product, and business data are in beta.
]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-13988"><!-- &nbsp; --></abbr>
<p>Google&#8217;s own <a title="Webmasters/Site owners Help" href="http://www.google.com/support/webmasters/">webmasters help site</a> recommends <a title="About microformats - Webmasters/Site owners Help" href="http://www.google.com/support/webmasters/bin/answer.py?answer=146897">microformats</a> and <a title="About RDFa - Webmasters/Site owners Help" href="http://www.google.com/support/webmasters/bin/answer.py?answer=146898">RDFa</a> structured data to improve indexing and usefulness of the data. <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=146645">Review metadata</a> appears to have full support, while <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=146646">people</a>, <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=146750">product</a>, and <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=146861">business</a> data are in beta.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/13988/google-recommends-microformats-and-rdfa/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>OpenSearch Progress</title>
		<link>http://maisonbisson.com/blog/post/11397/opensearch-progress/</link>
		<comments>http://maisonbisson.com/blog/post/11397/opensearch-progress/#comments</comments>
		<pubDate>Wed, 02 Aug 2006 00:18:27 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Blink]]></category>
		<category><![CDATA[Libraries & Networked Information]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[extensions]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[opensearch]]></category>
		<category><![CDATA[OpenSearch referrer extension]]></category>
		<category><![CDATA[search suggestions]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/post/11397/</guid>
		<description><![CDATA[
I really need to keep better tabs on Michael Fagan, as his June 11 OpenSearch Update is full of goodies.
OpenSearch, OpenSearch referrer extension, extensions, microformats, search suggestions
]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-11397"><!-- &nbsp; --></abbr>
<p>I really need to keep better tabs on <a href="http://www.faganfinder.com/">Michael Fagan</a>, as his June 11 <a href="http://www.faganfinder.com/wp/2006/06/11/791/" title="Puzzlepieces – OpenSearch Update (June 11, 2006)">OpenSearch Update</a> is full of goodies.</p>
<p><tags>OpenSearch, OpenSearch referrer extension, extensions, microformats, search suggestions</tags></p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/11397/opensearch-progress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IdM Takes Lessons From the Microformats Crowd</title>
		<link>http://maisonbisson.com/blog/post/11233/idm-takes-lessons-from-the-microformats-crowd/</link>
		<comments>http://maisonbisson.com/blog/post/11233/idm-takes-lessons-from-the-microformats-crowd/#comments</comments>
		<pubDate>Fri, 31 Mar 2006 02:46:07 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Libraries & Networked Information]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[identity architecture]]></category>
		<category><![CDATA[identity assertion]]></category>
		<category><![CDATA[identity management]]></category>
		<category><![CDATA[identity verification]]></category>
		<category><![CDATA[idm]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[microid]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/post/11233/</guid>
		<description><![CDATA[A tip from <a href="http://blog.ryaneby.com/">Ryan</a> sent me <a href="http://identityfuture.com/story/idm-microformats-microid/">looking</a> at <a href="http://microid.org/">MicroID</a>:

<blockquote>a new Identity layer to the web and <a href="http://microformats.org/">Microformats</a> that allows anyone to simply claim verifiable ownership over their own pages and content hosted anywhere.</blockquote>

The idea is to hash a user's email address (or other identifier) with the name of the site it will be published on, giving a string that can be inserted -- in true Microformats style -- as an element of the html on the site.]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-11233"><!-- &nbsp; --></abbr>
<p>A tip from <a href="http://blog.ryaneby.com/">Ryan</a> sent me <a href="http://identityfuture.com/story/idm-microformats-microid/">looking</a> at <a href="http://microid.org/">MicroID</a>:</p>
<blockquote><p>a new Identity layer to the web and <a href="http://microformats.org/">Microformats</a> that allows anyone to simply claim verifiable ownership over their own pages and content hosted anywhere.</p></blockquote>
<p>The idea is to hash a user&#8217;s email address (or other identifier) with the name of the site it will be published on, giving a string that can be inserted &#8212; in true Microformats style &#8212; as an element of the html on the site.</p>
<p>Examples:</p>
<blockquote><p>To verify a user&#8217;s home page or ownership of any page:</p>
<p><code style="display:block; overflow:scroll;">&lt;head&gt;... &lt;meta name=“microid” content=“a9993e364706816aba3e25717850c26c9cd0d89d” /&gt; ... &lt;/head&gt;</code></p>
<p>To verify a user&#8217;s membership in (or content/microformat published on) any (trusted) 3rd party site:</p>
<p><code style="display:block; overflow:scroll;">&lt;div class=“agent vcard microid-a9993e364706816aba3e25717850c26c9cd0d89d”&gt;<br />
&lt;a class=“email fn” href=“mailto:jfriday@host.com”&gt;Joe Friday&lt;/a&gt;<br />
&lt;div class=“tel”&gt;+1-919-555-7878&lt;/div&gt;<br />
&lt;div class=“title”&gt;Area Administrator, Assistant&lt;/div&gt;<br />
&lt;/div&gt;</code></p>
<p>To validate a user&#8217;s feedback or reputation on any moderated system (slashdot, digg, etc):</p>
<p><code style="display:block; overflow:scroll;">&lt;span class=“score microid-a9993e364706816aba3e25717850c26c9cd0d89d”&gt;5&lt;/span&gt;</code></p></blockquote>
<p>I&#8217;ve gotta admit that it seems too simple to work and I&#8217;m gonna have to think about this a while.</p>
<blockquote><p>Once this [MicroID] is published via one of the number of different ways or as part of a microformat on any page or site, they appear as opaque strings, but unique to a particular ID on that site. When the owner of the communication identifier forms a relationship with a new site, and (critical) that new site validates the communication identifier, they can then immediately validate the MicroID published on any other site for that given communication identifier.</p>
<p>MicroID also allows any third party to crawl and index these microformats and provide a web service that may return a weighted response (for reputations), list of references, etc. This index is anonymous and queries into it may simply provide the hashed version of a validated user-provided communication identifier.</p>
<p>While it may seem that spoofing would be an issue due to the nature of using communication idenitifers and how widely they are sometimes shared or published, the assertion of ownership must always originate from the owner, the MicroID simply allows anyone to validate that relationship very simply.</p></blockquote>
<p><tags>identity, identity architecture, identity assertion, identity management, identity verification, idm, microformats, microid, identity, identity architecture, identity assertion, identity management, identity verification, idm, microformats, microid</tags></p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/11233/idm-takes-lessons-from-the-microformats-crowd/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Microformats</title>
		<link>http://maisonbisson.com/blog/post/10729/microformats/</link>
		<comments>http://maisonbisson.com/blog/post/10729/microformats/#comments</comments>
		<pubDate>Thu, 08 Dec 2005 15:14:24 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Libraries & Networked Information]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[data standards]]></category>
		<category><![CDATA[libraries]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[microformat]]></category>
		<category><![CDATA[microformats]]></category>
		<category><![CDATA[networked information]]></category>
		<category><![CDATA[semantic web]]></category>

		<guid isPermaLink="false">http://www.maisonbisson.com/blog/?p=10729</guid>
		<description><![CDATA[
Oliver Brown introduced me to microformats a while ago, the Ryan Eby got excited about them, then COinS-PMH showed how useful they could be for libraries, but I still haven&#8217;t done anything with them myself (other than beg Peter Binkley to release his COinS-PMH WordPress Plugin).
What are microformats? Garrett Dimon explains the theory:
When writing markup [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-10729"><!-- &nbsp; --></abbr>
<p><a href="http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/">Oliver Brown</a> introduced me to <a href="http://microformats.org/wiki/microformats" title="microformats">microformats</a> a while ago, the <a href="http://blog.ryaneby.com/archives/microformats-and-standardized-markup/">Ryan Eby</a> got excited about them, then <a href="http://libdev.plymouth.edu/post/21" title="libdev » COinS-PMH and Microformats">COinS-PMH</a> showed how useful they could be for libraries, but I still haven&#8217;t done anything with them myself (other than beg Peter Binkley to release his <a href="http://www.wallandbinkley.com/quaedam/?p=48">COinS-PMH WordPress Plugin</a>).</p>
<p>What are microformats? <a href="http://www.digital-web.com/articles/microformats_primer/">Garrett Dimon explains the theory</a>:</p>
<blockquote><p>When writing markup against deadlines and priorities, it’s easy to forget that somebody else will eventually have to maintain it. Conveniently, some of the central ideas behind microformats revolve around the fact that they are designed for humans first and created with simplicity in mind. This means you’ll have markup that is easy to understand and maintain for everyone, including:</p>
<ul>
<li>The engineer integrating your code next week</li>
<li>You updating your code next month</li>
<li>The new guy taking over your job when you get promoted next year</li>
</ul>
</blockquote>
<p>Basically, microformats suggest the use of common class names for various XHTML elements. As it turns out, the <a href="http://www.microformats.org/wiki/hcard">hCard microformat</a> is a convenient way of representing the data from <a href="http://en.wikipedia.org/wiki/Vcard">vCards</a> in XHTML. The convenience is by design, of course. Here&#8217;s an example:</p>
<blockquote><p><code>&lt;div class=“vcard”&gt;<br />
&lt;a class=“url fn” href=“http://maisonbisson.com/”&gt;Casey Bisson&lt;/a&gt;<br />
&lt;div class=“org”&gt;MaisonBisson&lt;/div&gt;<br />
&lt;/div&gt;</code></p></blockquote>
<p>By standardizing the class names for this content, it&#8217;s easier to share and maintain stylesheets, re-use content, and read the content programatically. Perhaps most importantly, it offers valuable tips to search engines crawling your site about what the data is, making it more findable.</p>
<p>The principles of microformats are such:</p>
<ul>
<li>solve a specific problem</li>
<li>design for humans first, machines second</li>
<li>reuse building blocks from widely adopted standards</li>
<li>modularity / embeddability</li>
<li>enable and encourage decentralized and distributed development, content, services</li>
</ul>
<p>The potential here for libraries is huge, but we should take seriously <a href="http://tantek.com/log/2003/0813t1158.html#handauthoring">the caution that microformats be easy to use</a> and the <a href="http://microformats.org/wiki/process">design rule</a> that it be simple.</p>
<p><tags>microformat, networked information, semantic web, microformats, library, libraries, metadata, data standards</tags></p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/10729/microformats/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>