<?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>Cantorva Limited &#187; News</title>
	<atom:link href="http://cantorva.com/blog/category/news/feed/" rel="self" type="application/rss+xml" />
	<link>http://cantorva.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 11 Jan 2010 20:36:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Search Monkey Event Standard Object</title>
		<link>http://cantorva.com/blog/2009/07/17/search-monkey-event-standard-object/</link>
		<comments>http://cantorva.com/blog/2009/07/17/search-monkey-event-standard-object/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 19:37:22 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[search monkey]]></category>

		<guid isPermaLink="false">http://cantorva.com/blog/?p=85</guid>
		<description><![CDATA[I located the Search Monkey event standard object. Yahoo doing this makes it the de-facto standard markup, though its a shame it differs at the namespace level from their previous recommendation. The difference of two characters makes FIL incompatible!
Of course, my SM plugin &#8211; which is a more basic version of the same thing, is [...]]]></description>
			<content:encoded><![CDATA[<p>I located the Search Monkey <a href="http://developer.search.yahoo.com/help/objects/event" target="_blank">event standard object</a>. Yahoo doing this makes it the de-facto standard markup, though its a shame it differs at the namespace level from their previous recommendation. The difference of two characters makes FIL incompatible!</p>
<p>Of course, my <a href="http://cantorva.com/blog/about/generic-event-info/">SM plugin</a> &#8211; which is a more basic version of the same thing, is now completely redundant. I&#8217;m actually quite pleased by that, it did seem like Mission Impossible.</p>
]]></content:encoded>
			<wfw:commentRss>http://cantorva.com/blog/2009/07/17/search-monkey-event-standard-object/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Moving forward on Search Monkey</title>
		<link>http://cantorva.com/blog/2009/05/11/moving-forward-on-search-monkey/</link>
		<comments>http://cantorva.com/blog/2009/05/11/moving-forward-on-search-monkey/#comments</comments>
		<pubDate>Mon, 11 May 2009 22:15:56 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[hcalendar]]></category>
		<category><![CDATA[rdfa]]></category>
		<category><![CDATA[search monkey]]></category>

		<guid isPermaLink="false">http://cantorva.com/blog/?p=47</guid>
		<description><![CDATA[I've moved forward marginally with my Search Monkey presentation app, and backwards a little as well.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve moved forward marginally with my Search Monkey presentation app, and backwards a little as well.</p>
<p>The backward step was that some of the DataRSS content in the Yahoo Index appears to have vanished, this broke the examples in the <a href="http://cantorva.com/blog/2009/04/03/vcal-rdfa-and-search-monkey/" target="_blank">previous post</a> and on <a href="http://gallery.search.yahoo.com/application?smid=WCi.s" target="_blank">the Search Monkey site</a>. I don&#8217;t think there is a lot a lowly web site operator like me can do to recover that, but I hope coverage will continue to be at least patchy.  I look forward to the day they just make the RDF available directly, I can see this being much more scalable for them and certainly easier for me.</p>
<p>At the same time I have made a little progress with adding hCalendar support. The level of adoption for hCalendar makes this compelling, though the lack of precision does mean its fundamentally restricted.  I will not, for example, be able to enhance results for pages that mention more than one event, even if one event is clearly (to a human) the primary topic of the page, choosing meaningful graphics is also circuitous.</p>
<p>On the topic of graphics, it is often not possible to depict an event that has not yet occurred. You might choose a graphic for purely aesthetic reasons, use an inconsistent rationale that is difficult to capture, or may abstract away the reasoning into another software module making it unavailable to the UI (as in my case).  This scenario seems to require a specific predicate which I will coin and document as I get around to it. A microformats equivalent is a non-starter as I do not have the inclination to make official representations to standards bodies for work of speculative value (see below).</p>
<p>In total then, the roadmap will be something like this (in order of priority):</p>
<ol>
<li>Basic support for hCalendar (actually tested on <a href="http://upcoming.yahoo.com/event/2488827/" target="_blank">upcoming</a>), with simple safeguards for the ambiguous cases.</li>
<li>Support for RDFa enhanced pages mentioning multiple events, using foaf:primaryTopic to disambiguate.</li>
<li>Support for cases where the event itself can be previewed as a commercial proposition without requiring excess detail in the data, using the new predicate unless I can find one.</li>
<li>Support for event ontology actor and factor and associated foaf:depiction triples such that a factor or actor can be reliably depicted in the result.</li>
<li>Support for the organiser and logo <a href="http://microformats.org/wiki/hcalendar" target="_blank">hCalendar</a> and <a href="http://microformats.org/wiki/hcard" target="_blank">hCard</a> properties. This is useless to me as the interesting entity for music events is almost never the organiser and never the attendees [ unless you are on a date <img src='http://cantorva.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  ], but its feasible so deserves a modicum of attention. I don&#8217;t think photo is worth supporting as that would immediately break on conferences.</li>
</ol>
<p>I&#8217;m realistic about the importance of this project for making money as there is no predictable way to ensure large scale adoption of the plugin and the difference in click though rates is also unpredictable. As a result, I&#8217;ll be moving this forward primarily as a hackspace project rather than a commercial one, albeit commercially motivated. Doing it on hack evenings is a simple way to box off an amount of time.</p>
<p>Progress will be slow for other reasons, I have to locate implementations of the relevent vocabularies, trawl the Yahoo Index for fully crawled examples and possibly establish some test cases. This will all take time and much of it will be out of my control.</p>
]]></content:encoded>
			<wfw:commentRss>http://cantorva.com/blog/2009/05/11/moving-forward-on-search-monkey/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UK Gov shares its data cheaply, avoiding change</title>
		<link>http://cantorva.com/blog/2009/04/24/uk-gov-shares-its-data-cheaply-avoiding-change/</link>
		<comments>http://cantorva.com/blog/2009/04/24/uk-gov-shares-its-data-cheaply-avoiding-change/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 14:41:22 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[cheap]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[rdfa]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[sharing]]></category>

		<guid isPermaLink="false">http://cantorva.com/blog/?p=43</guid>
		<description><![CDATA[No, not a story of intrusion and data-loss, this is data the government should be sharing &#8211; job adverts.
While apparently being in a position to know,  Mark Birkbeck &#8220;speculates&#8221; publicly that the UK Gov are using RDFa because:
by using RDFa to mark-up vacancies on each individual government site, it&#8217;s possible to allow each department to [...]]]></description>
			<content:encoded><![CDATA[<p>No, not a story of intrusion and data-loss, this is data the government should be sharing &#8211; job adverts.</p>
<p>While apparently being in a position to know,  <a href="http://webbackplane.com/mark-birbeck/blog/2009/04/23/more-rdfa-goodness-from-uk-government-web-sites" target="_blank">Mark Birkbeck</a> &#8220;speculates&#8221; publicly that the UK Gov are using RDFa because:</p>
<blockquote><p>by using RDFa to mark-up vacancies on each individual government site, it&#8217;s possible to allow each department to publish jobs however it sees fit. Many companies want to have some centralised information, not just government, but this usually involves imposing on each department some new database system or workflow. By using RDFa as the interface, each department merely needs to have the ability to publish HTML, and then they can share their data.</p>
<p>The second[reason] is that by publishing vacancies using RDFa, it&#8217;s easy for <em>third-parties</em> to &#8217;scrape&#8217; the data into their own databases, in a reliable way.</p>
<p>For example, some external company could import all vacancies for a particular region or of a particular type, and then show them on their own site.</p></blockquote>
<p>Of course, all the benefits he mentioned a provably true &#8211; just <a href="http://www.w3.org/2007/08/pyRdfa/extract?uri=http%3A%2F%2Fwww.civilservice.gov.uk%2Fjobs%2Fcareers-detail.aspx%3FJobId%3D2832&amp;format=pretty-xml&amp;warnings=false&amp;parser=lax&amp;host=xhtml&amp;space-preserve=true&amp;submit=Go!">run a page through a distiller</a> &#8211; this is not bleeding edge technology any longer, it&#8217;s merely cutting edge.</p>
]]></content:encoded>
			<wfw:commentRss>http://cantorva.com/blog/2009/04/24/uk-gov-shares-its-data-cheaply-avoiding-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
