<?xml version="1.0"?>
<feed xml:lang="en-GB" xmlns="http://www.w3.org/2005/Atom">
<title>WebOrganics</title>
<id>http://weborganics.co.uk/</id>
  <link href="http://weborganics.co.uk/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="http://weborganics.co.uk/" rel="alternate"/>
  <author>
    <name>Martin</name>
  </author>
<updated>2008-03-27T20:16:16+01:00</updated>
  <entry>

    <title>Extending hCard using RDFa</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2008-03-27T20:16:16+01:00</updated>
    <id>http://weborganics.co.uk/article/extending-hcard-using-rdfa</id>
    <link href="http://weborganics.co.uk/article/extending-hcard-using-rdfa" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>Mark Birbeck the Designer of RDFa has recently posted a couple of really good articles recently one about the first steps in <a href=" http://internet-apps.blogspot.com/2008/02/first-steps-in-rdfa-creating-foaf.html">adding Foaf to RDFa</a> and a second one about using <a href=" http://internet-apps.blogspot.com/2008/03/so-how-about-using-rdfa-in-microformats.html">RDFa and Microformats</a>. Both these articles has inspired me to write a little introduction about how to use the <a href="http://microformats.org/wiki/hcard">hcard microformat</a> and extend it using <a href="http://rdfa.info/wiki/RDFa_Wiki">RDFa</a>.</p>

<p>I am going to mark up this example of a hCard as RDFa:</p>

<pre>&lt;div class=&quot;vcard&quot; id=&quot;weborganics&quot;&gt;
&lt;p&gt;&lt;span class=&quot;fn&quot;&gt;Martin McEvoy&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;weborganics&quot; src=&quot;http://weborganics.co.uk/images/me.jpg&quot; class=&quot;photo&quot;&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a title=&quot;Email&quot; class=&quot;email&quot; href=&quot;mailto:info@weborganics.co.uk&quot;&gt;Email&lt;/a&gt;
Web: &lt;a rel=&quot;me&quot; class=&quot;url&quot; href=&quot;http://weborganics.co.uk/index.xhtml&quot;&gt;WebOrganics&lt;/a&gt;&lt;/p&gt;
&lt;div class=&quot;geo&quot;&gt;
	&lt;abbr title=&quot;53.7552&quot; class=&quot;latitude&quot;&gt;N 53.7552&lt;/abbr&gt;,
	&lt;abbr title=&quot;-2.3675&quot; class=&quot;longitude&quot;&gt;W -2.3675&lt;/abbr&gt;
&lt;/div&gt;
&lt;/div&gt;</pre>
 
<p>I have included the geo part of hcard because its useful for people, clients, or customers to know where you are yes?</p>

<p>First add the RDFa document type to your page:<br/>
&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML+RDFa 1.0//EN&quot; &quot;http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd&quot;&gt;</p>

<p>So far so good your page is now RDFa and you are ready to add some namespaces, a namespace is just a place where a set of names and definitions is stored.</p>

<p>I am going to use two namespaces in this example:</p>

<ul>
<li><p>1. Foaf, xmlns:foaf=&quot;http://xmlns.com/foaf/0.1/&quot;<br/>
Foaf Is primaraly used to define People, FOAF documents are machine-readable home pages.</p></li>
<li><p>2. Geo, xmlns:geo=&quot;http://www.w3.org/2003/01/geo/wgs84_pos#&quot;<br/>
Geo Is the RDF equivalent of the World Geodetic System or WGS84 and is used to represent Latitude/Longitude information about the location of things.</p></li>
</ul>

<p>There are two ways to add a namespace in RDFa one is In the &lt;html&gt; tag of your page or another way is in the page using say a &lt;div&gt; or a &lt;span&gt; I am going to add the namespace to the hcard markup itself:</p>

<pre>&lt;div class=&quot;vcard&quot; id=&quot;weborganics&quot;
		xmlns:foaf=&quot;http://xmlns.com/foaf/0.1/&quot; 
		typeof=&quot;foaf:Person&quot; 
		about=&quot;#weborganics&quot;&gt;</pre>

<p>@typeof is similar to a html &lt;div&gt; it describes a block of some thing, in this case Its a block of foaf:Person. @about means exactly as it says what this thing is about in this case Its about the foaf:Person weborganics.</p>

<p>Lets add a Name to this person:</p>
<pre>&lt;p&gt;&lt;span property=&quot;foaf:name&quot; class=&quot;fn&quot;&gt;Martin McEvoy&lt;/span&gt;&lt;/p&gt;</pre>

<p>Easy eh?, Properties are use to add information about the subject, in this case a person, the contents are usually just text.</p>

<p>Next you may want to add your picture:</p>

<pre>&lt;p rel=&quot;foaf:img&quot;&gt;
&lt;img alt=&quot;weborganics&quot; src=&quot;http://weborganics.co.uk/images/me.jpg&quot; class=&quot;photo&quot;/&gt;
&lt;/p&gt;</pre>

<p>@rel is used in the same way as a html rel to describe the relationships between things. The above example has a relationship of a foaf:img of the foaf:Person. In RDFa you can use @rel anywhere in your page not just in links, you may also want to add your email address and homepage url in the same way:</p>

<pre>&lt;p&gt;Contact: &lt;a rel=&quot;foaf:mbox&quot; title=&quot;Email&quot; class=&quot;email&quot; href=&quot;mailto:info@weborganics.co.uk&quot;&gt;Email&lt;/a&gt;
Web: &lt;a rel=&quot;foaf:weblog me&quot; class=&quot;url&quot; href=&quot;http://weborganics.co.uk/index.xhtml&quot;&gt;WebOrganics&lt;/a&gt;&lt;/p&gt;</pre>

<p>You can leave it there if you wanted which is great! but I am going to take this a little further and demonstrate how you can mark up the Geo bit of a hcard. All in one go this time using the same techniques as demonstrated above:</p>

<pre>&lt;div class=&quot;geo&quot; id=&quot;weblog&quot; rel=&quot;foaf:based_near&quot;
	xmlns:geo=&quot;http://www.w3.org/2003/01/geo/wgs84_pos#&quot;&gt;
    	&lt;span typeof=&quot;geo:Point&quot; about=&quot;#weblog&quot;&gt;
		&lt;abbr property=&quot;geo:lat&quot; content=&quot;53.7552&quot; title=&quot;53.7552&quot; class=&quot;latitude&quot;&gt;N 53.7552&lt;/abbr&gt;, 
		&lt;abbr property=&quot;geo:long&quot; content=&quot;-2.3675&quot; title=&quot;-2.3675&quot; class=&quot;longitude&quot;&gt;W -2.3675&lt;/abbr&gt;
    	&lt;/span&gt;
&lt;/div&gt;</pre>

<p>There Is one thing extra I have added I have used @content this works in the same way as the @title attribute in the <a href="http://microformats.org/wiki/abbr">abbr design pattern</a>, Its used to carry machine readable data without it interfering with the human content, If you think about that from an accessible point of view its actually better than the current abbr design pattern.</p>

<p>So there you have it a hCard marked up as RDFa in a few easy steps. I have created two examples to accompany this mini how-to. which you can simply just copy and paste with your own details.</p>
<ul>
<li>A Page marked up in <a href="http://weborganics.co.uk/demo/hcard.xhtml">just hcard</a></li>
<li>A Page marked up as a <a href="http://weborganics.co.uk/demo/hcard-RDFa.xhtml">hCard+RDFa</a></li>
<li>The <a href="http://rdfa.digitalbazaar.com/librdfa/rdfa2rdf.py?uri=http://weborganics.co.uk/demo/hcard-RDFa.xhtml">RDF output of hCard+RDFa</a> (uses <a href="http://rdfa.digitalbazaar.com/librdfa/">librdfa</a>)</li>
</ul>
<p>Microformats and RDFa work pretty well together I think, It adds Scope when previously there wasn't any, Microformats also make excellent building blocks for RDFa they give you hints on where everything should go. <em>Thanks.</em></p>
      </div>
    </content>
<category term="RDFa"/>
<category term="Microformats"/>
</entry>

  <entry>

    <title>hAudio 0.9</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2008-02-18T20:32:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-0-9</id>
    <link href="http://weborganics.co.uk/article/haudio-0-9" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>hAudio has reached a stately version 9.0 which I imagine will be the final proposal from the contributors of the hAudio Microformat.</p>
<p>Only one class name was changed, "fn" for "title" which doesn't seem so great but has been a hotly debated part of hAudio since <a href="http://microformats.org/discuss/mail/microformats-new/2007-May/000253.html">May 2007</a> when the issue about "title is already taken to mean something else" and "use fn instead" first came up. The Class Name "title" may yet change again because the fn/title issue is still being debated and I imagine will continue for some time yet.</p>

<p>In the meantime the <a href="http://grabb.it/">Grabb.it</a> guys became the first major implementer of hAudio 0.9 marking up thousands of tracks on their <a href="http://grabb.it/users/greg">userpages</a>, I would say that they are quite happy with the changes made to the microformat.</p>
<p>hAudio RSS also uses the new hAudio microformat in the V3 version of the hypertext playlist format. New for Version 3, is a new home page on The <a href="http://esw.w3.org/topic/FrontPage">ESW Wiki</a>,  <a href="http://esw.w3.org/topic/hAudioRSS">hAudioRSS</a> where you can download the entire source code and demo of the hAudio-RSS playlist.</p>
<p>If you are planning on marking up your pages in hAudio or hAudio-RSS let me know I will be more than happy to give you a shout for doing a good thing.</p>
      </div>
    </content>
<category term="hAudio"/>
<category term="Microformats"/>
</entry>

  <entry>

    <title>Talk about hAudio RSS</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2008-01-24T19:13:00+01:00</updated>
    <id>http://weborganics.co.uk/article/talk-about-haudio-rss</id>
    <link href="http://weborganics.co.uk/article/talk-about-haudio-rss" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>hAudio-RSS is causing a little flutter in the open media web community so much so that back in December it became part of a small discussion over at songbird nest called <a href="http://upcoming.yahoo.com/event/288711/">Portable Playlists and other POSH-ibilities</a> presented (amongst others) by Tantek which was kindly recorded to video by Citizen <a href="http://www.horsepigcow.com/">Tara Hunt</a>, so without any further rambling may I present Tantek's Demo.</p>
<object style="width: 437px; height: 370px;" type="application/x-shockwave-flash" id="viddler" data="http://www.viddler.com/player/165ed2d9/">
<param name="movie" value="http://www.viddler.com/player/165ed2d9/"/>
<param name="allowScriptAccess" value="always"/>
<param name="allowFullScreen" value="true"/>
</object>
      </div>
    </content>
<category term="hAudio"/>
<category term="hAudio-RSS"/>
<category term="Microformats"/>
</entry>

  <entry>

    <title>hAudio-RSS - Public Domain</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-12-31T01:19:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-rss---public-domain</id>
    <link href="http://weborganics.co.uk/article/haudio-rss---public-domain" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p><a title="hAudio-RSS" href="http://weborganics.co.uk/haudio-rss/"><img src="http://weborganics.co.uk/haudio-rss/img/haudio-rss.png" alt="hAudio0.8" class="photo"/></a> hAudio-RSS has been updated to version 2, the code has been modified and does not contain any suspected anti-patterns (info being scraped from the head not visible). The biggest change is that hAudio-RSS is now licensed under a Creative Commons <a href="http://creativecommons.org/licenses/publicdomain/deed.en_GB">Public Domain License</a>. This is because <a href="http://microformats.org/blog/2007/12/29/making-open-standards-as-open-as-possible/">microformats.org</a> have recently required all contributions on the microformats wiki have a public domain license, which personally I find is a smart move, Anybody can freely use microformats anywhere for anything and not have to worry about possible licensing or copyright infringements. hAudio-RSS is an extension of hAudio so I feel it should have the same license. There is also a free Template that you can download of the whole hAudio-RSS v2 markup also released into the Public domain which includes, XHTML 1.0 Strict document, CSS, Bookmarklet, Buttons and guidelines. <a href="http://weborganics.co.uk/files/hRSS-template.zip" title="Download hAudio-RSS Template">Download hRSS-template</a>.</p>
<p>The hAudio transformation service has been improved! Instead of data being just dumped onto the screen the service now saves the transformation in a store, the url that you are given when transformation is complete is a permanent url to a static xml file, every time you re-run the hAudio xslt service you will be given a new permanent url in the store, this makes it easy to keep versions, or archives of your files, you can download the xml files anytime you like, save them to your desktop, or if you like re-syndicate your xml files to <a href="http://www.feedburner.com/">feedburner</a>, add them to the <a href="http://www.podcast.net/">podcast.net</a> directory and pump them through another service like <a href="http://grabb.it/">Grabb.it</a>. do what you like its your data</p>
<p>Anyway lets not bore you anymore, <a href="http://weborganics.co.uk/files/hRSS-template.zip" title="Download Template">download the template</a> and have fun!</p>
      </div>
    </content>
<category term="hAudio"/>
<category term="hAudio-RSS"/>
</entry>

  <entry>

    <title>hAudio-RSS</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-12-13T23:15:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-rss</id>
    <link href="http://weborganics.co.uk/article/haudio-rss" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>hAudio-RSS is a way of embeding an RSS2 Podcast in XHTML or more accurately a way of extracting a podcast from
hAudio and XHTML using XSLT. Hypertext Podcasting if you like.</p>
<p>Its done by Embeding the <a href="http://microformats.org/wiki/haudio" rel="me">hAudio
Microformat</a> in Semantic HTML and transforming it using XSLT.</p>
<p>The resulting transformation can then be played in Amarok or
iTunes just like a podcast and (because the results are RSS2) you can read as
an Audio blog feed in your favorite news Aggregator.</p>
<p>Example:</p>
<ul>
  <li>Source File: <a href="http://weborganics.co.uk/haudio-rss/">http://weborganics.co.uk/haudio-rss/</a></li>
</ul>
<p> Because I am more a man of Science and not talk I have left
some notes in the source file to give hints on how it is done.</p>
<p>After feedback and positive testing I will shortly be
releasing all the source files and a transformation
service that you can just download and drop in the back end of any site
using PHP 5+ that will give publishers the ability to perform their own
server side transformations (which will be great to add into templates
just 6.3kb) and not have to use services like h2A and
x2v much like all the other services in the <a href="http://tools.weborganics.co.uk/">WebOrganics Toolbox</a></p>
<p>For anyone who may be intrested there is a very beta Just an
Idea kind of thing RDF site summary version of hAudio-RSS</p>
      </div>
    </content>
<category term="hAudio-RSS"/>
</entry>

  <entry>

    <title>hAudio Draft Specification</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-11-04T00:34:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-draft-specification</id>
    <link href="http://weborganics.co.uk/article/haudio-draft-specification" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>It was announced on Saturday 3rd of November by hAudio editor Manu Sporny, that on hAudio 0.8 has become a <a href="http://microformats.org/discuss/mail/microformats-new/2007-November/001244.html">Draft Specification</a></p>
<p>It was also announced that new Operator scripts would soon become available, combined with a new round of evangelism and rigorous testing for hAudio. The full hAudio Draft Specification can be read here <a href="http://microformats.org/wiki/haudio">http://microformats.org/wiki/haudio</a> and a new test page based on hAudio 0.8 can be found here <a href="http://weborganics.co.uk/haudio">http://weborganics.co.uk/haudio</a></p>
      </div>
    </content>
<category term="hAudio"/>
</entry>

  <entry>

    <title>Audio Microformat hAudio 0.8</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-11-02T00:41:00+01:00</updated>
    <id>http://weborganics.co.uk/article/audio-microformat-haudio</id>
    <link href="http://weborganics.co.uk/article/audio-microformat-haudio" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	 <p>This Halloween as well as that awful film Halloween being <a href="http://www.onthebox.com/program/663006/halloween.aspx" rel="nofollow">on the BBC again</a> they also promised Halloween II next week... dont worry I have plenty more repeats to chose from thanks to the miracle of <a href="http://www.sky.com/portal/site/skycom/tvguide" rel="nofollow">satelite tv</a>, something else not so scary happened the <a href="http://weborganics.co.uk/taggings/haudio" rel="directory">audio microformat hAudio</a> reached <a href="http://microformats.org/wiki/audio-info-proposal">version 0.8</a>. The general consensus on <a href="http://microformats.org/mailman/listinfo/microformats-new/">the list</a> is that hAudio 0.8 will be the final proposal, after a last round of talks, before hAudio gets moved on to Draft. hAudio will then become only the twelfth in a list of many <a href="http://microformats.org/wiki/exploratory-discussions">exploratory discussions</a>, to make it to <a href="http://microformats.org/wiki/Main_Page#Drafts">Microformat Draft</a>.</p>
<p><cite>Manu Sporny</cite>, Was the first to suggest a <a href="http://microformats.org/discuss/mail/microformats-new/2007-April/000117.html">hAudio Microformat</a> on Apr 6 2007, when he proposed that we... </p>
<blockquote cite="http://microformats.org/discuss/mail/microformats-new/2007-April/000117.html"><p>Create a very simple hAudio microformat, which can then be integrated into media-info</p></blockquote>
<p>...which was In response to <a href="http://microformats.org/discuss/mail/microformats-new/2007-April/000096.html" rel="me">my suggestion</a> a few days earlier on  Apr 4 2007 that the community could create a music download microformat using a combination of hAtom and hReview, a brave suggestion I thought, the Important thing was the discussion did not go stale.</p>
<p>Anyway check out the <a href="http://microformats.org/wiki/audio-info-proposal">microformats wiki</a> and find out what hAudio is, or have a look at <a href="http://microformats.org/discuss/mail/microformats-new/2007-April/000117.html">the discussion</a>, (7 months) and see what everyone got so worked up about. I have also updated the <a href="http://weborganics.co.uk/haudio">hAudio test page</a> for any of you who are interested in publishing and testing hAudio.</p>
      </div>
    </content>
<category term="hAudio"/>
</entry>

  <entry>

    <title>hAudio RDFa</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-08-24T10:56:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-rdfa</id>
    <link href="http://weborganics.co.uk/article/haudio-rdfa" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p><strong>hAudio</strong> has been creating quite a bit of exitement around the semantic web recently in particular the hAudio RDFa maping performed by David Lehn and Manu Sporny of <a href="http://www.digitalbazaar.com">Digital Bazaar, Inc.</a></p>
<p>The <cite>Creative Commons Tech Blog</cite> describes the proposal in its entry about <a href="http://techblog.creativecommons.org/2007/08/03/metadata-work-of-interest/">Metadata work of interest</a> as</p>
<blockquote cite="http://techblog.creativecommons.org/2007/08/03/metadata-work-of-interest/">
<p>...could turn out to be interesting for describing licensed content on the web, all rather interesting.</p>
</blockquote>
<p>The Proposed hAudio RDFa maping can be found on the Digital Bazaar Wiki <a href="http://wiki.digitalbazaar.com/en/HAudio_RDFa">http://wiki.digitalbazaar.com/en/HAudio_RDFa</a>
 a special well done to Manu Sporny because thanks to his efforts in the  Microformats community and the RDFa community has become an invited expert in the W3C RDFa task force exellent news for both hAudio and Manu.<br/>
If you want to see a working example of hAudio RDFa as always WebOrganics has Produced an example with one or two tools to work with which can be found at <a href="http://weborganics.co.uk/files/hAudio-RDFa.xhtml">http://weborganics.co.uk/files/hAudio-RDFa.xhtml</a>
 The example also uses Valid XHTML-RDFa 1.0, something else to talk about at a later date?</p>
      </div>
    </content>
<category term="hAudio"/>
<category term="RDFa"/>
</entry>

  <entry>

    <title>hAudio and Operator</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-08-07T03:38:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-and-operator</id>
    <link href="http://weborganics.co.uk/article/haudio-and-operator" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p>There Is now an Operator User Script created by David Lehn called hAudio.js which will help you to detect all the hAudio items available on WebOrganics.
<br/>You can either visit <a href="http://kaply.com/weblog/2007/07/20/operator-and-haudio/">Mike Kaply</a>'s (the creator of Operator) weblog and find out more about Operator and hAudio, or you can download hAudio.js directly from this site by <a href="http://weborganics.co.uk/files/js/haudio.js" title="hAudio Javascript">clicking here</a>.</p>
      </div>
    </content>
<category term="hAudio"/>
<category term="Operator"/>
</entry>

  <entry>

    <title>hAudio Microformat</title>
  <author>
    <name>Martin</name>
  </author>
    <updated>2007-06-27T22:22:00+01:00</updated>
    <id>http://weborganics.co.uk/article/haudio-microformat</id>
    <link href="http://weborganics.co.uk/article/haudio-microformat" rel="alternate"/>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">                
	<p><a href="http://microformats.org/wiki/audio-info-proposal" title="hAudio Proposal"><img src="http://weborganics.co.uk/images/haudio.png" alt="haudio"/></a></p>
<p>Well! what can I say, I'm honored to announce the birth of a new <a href="http://microformats.org/wiki/Main_Page" title="Microformats Wiki">microformat</a> that has managed to reach the status of <em>Proposal</em>, <a href="http://microformats.org/wiki/audio-info-proposal" title="hAudio Proposal"> hAudio</a>.</p>
<p>I say honored because for some bizarre reason I managed to become a contributor whilst I was a the quest to make our very own <a href="http://weborganics.co.uk/podcast">Podcast</a> more Organic and easier to share. I can honestly say that hAudio was one of the most hotly debated and well designed microformats since hAtom, and as a result the Format instead of taking the suggested 
eight weeks to complete, ended up finally taking twenty one contributors nearly twice as long.</p>
<p>The full proposal and full Schema can be found at <a href="http://microformats.org/wiki/audio-info-proposal">http://microformats.org/wiki/audio-info-proposal</a></p>
<p>The demo page used for testing, and created during the hAudio discussion can be found at <a href="http://weborganics.co.uk/haudio" title="WebOrganics hAudio">http://weborganics.co.uk/haudio</a></p>
<p>I would like to give a special "nod" to one or two of the guys who headed up the discussion and design of haudio, <a href="http://www.digitalbazaar.com/">Manu Sporny</a> who was the leader of the whole audio info discussion, without his guidance and Logic I doubt hAudio would ever been finished. <a href="http://suda.co.uk/">Brian Suda</a> and <a href="http://tantek.com/">Tantek &#199;elik</a> who kept us from straying too far beyond the "cow paths" <a href="http://makedatamakesense.com/">Scott Reynen</a>, <a href="http://blogmatrix.blogmatrix.com/">David Janes</a>, and <a href="http://www.pigsonthewing.org.uk/menu/index.htm">Andy Mabbett</a> all hot debaters and seasoned microformateers, who guided those of us who were not to sure where the cow path was. For my part well, my Ideas may have been a bit off the mark a little, Indeed most would say I found it hard keeping to the job at hand. In the end I think everyone that was involved helped create the most well designed microformat there is to date.</p>
      </div>
    </content>
<category term="hAudio"/>
<category term="Microformats"/>
</entry>
</feed>
