<?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: Cui bono? The problem with opening up data</title>
	<atom:link href="http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 23:05:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Guardian OpenPlatform DataStore &#8211; Just a Toy, or a Trusted Resource? &#171; OUseful.Info, the blog&#8230;</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4840</link>
		<dc:creator>The Guardian OpenPlatform DataStore &#8211; Just a Toy, or a Trusted Resource? &#171; OUseful.Info, the blog&#8230;</dc:creator>
		<pubDate>Mon, 08 Jun 2009 09:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4840</guid>
		<description>[...] Steph Gray says in Cui bono? The problem with opening up data: Here’s my thought: open data needs a new breed of data gardeners &#8211; not necessarily civil [...]</description>
		<content:encoded><![CDATA[<p>[...] Steph Gray says in Cui bono? The problem with opening up data: Here’s my thought: open data needs a new breed of data gardeners &#8211; not necessarily civil [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plug&#8217;n&#8217;Play Public Data &#171; OUseful.Info, the blog&#8230;</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4660</link>
		<dc:creator>Plug&#8217;n&#8217;Play Public Data &#171; OUseful.Info, the blog&#8230;</dc:creator>
		<pubDate>Mon, 01 Jun 2009 11:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4660</guid>
		<description>[...] started there, as well as thoughtful response on Steph Gray&#8217;s Helpful Technology blog (Cui bono? The problem with opening up data) which picks up on &#8220;some more fundamental problems than whether we publish the data in JSON [...]</description>
		<content:encoded><![CDATA[<p>[...] started there, as well as thoughtful response on Steph Gray&#8217;s Helpful Technology blog (Cui bono? The problem with opening up data) which picks up on &#8220;some more fundamental problems than whether we publish the data in JSON [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feargal Hogan</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4583</link>
		<dc:creator>Feargal Hogan</dc:creator>
		<pubDate>Sat, 30 May 2009 19:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4583</guid>
		<description>@Steph
I agree entirely that personal data such as NI numbers should not be published. But I think that type of issue should never be called &#039;clean up&#039;. The 4 precursors to publication you seem to mention above are:
*Cleaning up data for publication
*documenting it
*checking it for errors or personal details
*reformating it
Of those there is only ½ that I would allow, i.e. checking it for ... personal details

The rest can wait. You may even find that joe public do much of the rest for you, post publication.

And the personal details issue needs to be addressed much further back up the chain. What good reason is there for personal data to be in most civil service datasets? Prevention is much better than cure.</description>
		<content:encoded><![CDATA[<p>@Steph<br />
I agree entirely that personal data such as NI numbers should not be published. But I think that type of issue should never be called &#8216;clean up&#8217;. The 4 precursors to publication you seem to mention above are:<br />
*Cleaning up data for publication<br />
*documenting it<br />
*checking it for errors or personal details<br />
*reformating it<br />
Of those there is only ½ that I would allow, i.e. checking it for &#8230; personal details</p>
<p>The rest can wait. You may even find that joe public do much of the rest for you, post publication.</p>
<p>And the personal details issue needs to be addressed much further back up the chain. What good reason is there for personal data to be in most civil service datasets? Prevention is much better than cure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4567</link>
		<dc:creator>Steph</dc:creator>
		<pubDate>Sat, 30 May 2009 10:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4567</guid>
		<description>@Feargal

&lt;blockquote&gt;I understand that the data may not be 100%, but most of us who want the datasets are quite happy to work with - and around - the imperfections. I certainly don’t want our civil servants to be tasked with cleaning-up the data before publishing it. I’m pretty sure that will be used as an excuse to delay it&lt;/blockquote&gt;

I know what you&#039;re saying, and Jeremy&#039;s said much the same too over on Richard&#039;s post. But &#039;clean up&#039; could just involve important but slightly laborious tasks like confirming a dataset doesn&#039;t reveal citizen&#039;s personal data (e.g. names + postcodes, NI numbers or whatever), combining three messy spreadsheets into one, or putting in titles and basic notes so someone coming to the data &#039;cold&#039; understands how it&#039;s structured.

So while I agree that there&#039;s a risk it will be an excuse to delay and needlessly polish, if civil servants start just publishing the content of their hard drives, the ICO and others will justifiably get upset.</description>
		<content:encoded><![CDATA[<p>@Feargal</p>
<blockquote><p>I understand that the data may not be 100%, but most of us who want the datasets are quite happy to work with &#8211; and around &#8211; the imperfections. I certainly don’t want our civil servants to be tasked with cleaning-up the data before publishing it. I’m pretty sure that will be used as an excuse to delay it</p></blockquote>
<p>I know what you&#8217;re saying, and Jeremy&#8217;s said much the same too over on Richard&#8217;s post. But &#8216;clean up&#8217; could just involve important but slightly laborious tasks like confirming a dataset doesn&#8217;t reveal citizen&#8217;s personal data (e.g. names + postcodes, NI numbers or whatever), combining three messy spreadsheets into one, or putting in titles and basic notes so someone coming to the data &#8216;cold&#8217; understands how it&#8217;s structured.</p>
<p>So while I agree that there&#8217;s a risk it will be an excuse to delay and needlessly polish, if civil servants start just publishing the content of their hard drives, the ICO and others will justifiably get upset.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4566</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sat, 30 May 2009 10:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4566</guid>
		<description>Government should do much as the Guardian has done with the expenses: publish data in its raw format to allow people to do what the hell they like with it.  Mash it up, stick it on their fridge or move house to a postcode served by better schools.  Government can itself be a &quot;customer&quot; of that data, doing whatever analysis it chooses, but by putting the data out there, the onus is on individuals and the private sector to add value by turning it into information, from which individuals can garner knowledge.</description>
		<content:encoded><![CDATA[<p>Government should do much as the Guardian has done with the expenses: publish data in its raw format to allow people to do what the hell they like with it.  Mash it up, stick it on their fridge or move house to a postcode served by better schools.  Government can itself be a &#8220;customer&#8221; of that data, doing whatever analysis it chooses, but by putting the data out there, the onus is on individuals and the private sector to add value by turning it into information, from which individuals can garner knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4516</link>
		<dc:creator>Noel</dc:creator>
		<pubDate>Fri, 29 May 2009 07:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4516</guid>
		<description>Alex, at Kent we&#039;ve prioritised getting the citizens involved in the design as well more than building a localised version of data.gov.

What people create for themselves can benefit others and it also harnesses their creativity and energy - being able to &quot;build stuff that matters&quot; (to paraphrase Tim O&#039;Reilly). It also can provide a great way for us to find out what different services (don&#039;t just mean our ones!) our residents try and connect to for any given need they have (customer insight!).

We now get people coming to us saying &quot;we just built a microsite with the other local partners to engage on x issue, but we had worked with you, we could have just used your mashup hub&quot; 

I know the PoI taskforce produced some really good recommendations for local government, but those are still organisation focused - we need PoI to talk to the people setting the &quot;place shaping&quot; agenda...mind u if Kent &amp; Edinburgh are just getting on with it anyway, maybe that&#039;s not so important?</description>
		<content:encoded><![CDATA[<p>Alex, at Kent we&#8217;ve prioritised getting the citizens involved in the design as well more than building a localised version of data.gov.</p>
<p>What people create for themselves can benefit others and it also harnesses their creativity and energy &#8211; being able to &#8220;build stuff that matters&#8221; (to paraphrase Tim O&#8217;Reilly). It also can provide a great way for us to find out what different services (don&#8217;t just mean our ones!) our residents try and connect to for any given need they have (customer insight!).</p>
<p>We now get people coming to us saying &#8220;we just built a microsite with the other local partners to engage on x issue, but we had worked with you, we could have just used your mashup hub&#8221; </p>
<p>I know the PoI taskforce produced some really good recommendations for local government, but those are still organisation focused &#8211; we need PoI to talk to the people setting the &#8220;place shaping&#8221; agenda&#8230;mind u if Kent &amp; Edinburgh are just getting on with it anyway, maybe that&#8217;s not so important?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4511</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Fri, 29 May 2009 05:47:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4511</guid>
		<description>Noel

You explain it well with a practical example.

With Edinburgh we are looking at involving the citizen in the design. There might be an &quot;app&quot; for moving into a new area ; searching for somethingetc.....

The intention is to build an AnywhereCouncil app. set, since the act of moving is the same from John o Groats to Penzance.

This will be a possible UK first, as I don&#039;t remember any government initiative asking the citizen to design their services before. That is why Job Centre Pro Plus may actually work !

We have public servants, but they may not often serve the name in their title.

As far as mashing the data, people are planning for it all to be released in &quot; as-is &quot; state, together with early years school and nursery information, including e.g. post-code. Of course, the Ordnance Survey continues to play a 19th century apprach to this. Unlike Denmark or other sensible countries where collaboration is actually encouraged.

Then the coders, and technical folk, together with the citizend, council officials and members can get on with designing what they need for the people who live here.

Public services that add value to the individual</description>
		<content:encoded><![CDATA[<p>Noel</p>
<p>You explain it well with a practical example.</p>
<p>With Edinburgh we are looking at involving the citizen in the design. There might be an &#8220;app&#8221; for moving into a new area ; searching for somethingetc&#8230;..</p>
<p>The intention is to build an AnywhereCouncil app. set, since the act of moving is the same from John o Groats to Penzance.</p>
<p>This will be a possible UK first, as I don&#8217;t remember any government initiative asking the citizen to design their services before. That is why Job Centre Pro Plus may actually work !</p>
<p>We have public servants, but they may not often serve the name in their title.</p>
<p>As far as mashing the data, people are planning for it all to be released in &#8221; as-is &#8221; state, together with early years school and nursery information, including e.g. post-code. Of course, the Ordnance Survey continues to play a 19th century apprach to this. Unlike Denmark or other sensible countries where collaboration is actually encouraged.</p>
<p>Then the coders, and technical folk, together with the citizend, council officials and members can get on with designing what they need for the people who live here.</p>
<p>Public services that add value to the individual</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Williams</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4492</link>
		<dc:creator>Neil Williams</dc:creator>
		<pubDate>Thu, 28 May 2009 21:03:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4492</guid>
		<description>Well said indeed. Where do we start and how do we know that&#039;s the right place? We could spend a lot of effort and hard cash on exposing data that turns out to have little or no value. 

You almost need to think of the apps first and work backwards, though that goes directly against the hacker spirit.</description>
		<content:encoded><![CDATA[<p>Well said indeed. Where do we start and how do we know that&#8217;s the right place? We could spend a lot of effort and hard cash on exposing data that turns out to have little or no value. </p>
<p>You almost need to think of the apps first and work backwards, though that goes directly against the hacker spirit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4472</link>
		<dc:creator>Noel</dc:creator>
		<pubDate>Thu, 28 May 2009 10:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4472</guid>
		<description>Couldn&#039;t put it better myself Steph and this is certainly what we have found through developing our Pic &amp; Mix project down in Kent.  

All the questions you mention are interlinked - Which data? Who decides whether to publish? Who benefits? Who pays? For how long?

Given the infinite sets of data across a council or government dept, let alone across all public sector, you would need a diktat to make sure that all publicly available data was released in a re-usable way.

Let&#039;s take a very specific example of the benefits of opening up data to be mashed together. You&#039;ve got a family moving to a new area - father&#039;s been relocated, mother needs to find new job, their 16 yr old kid wants to start an apprenticeship and the three yr old needs some kind of childcare arrangements - oh yeah and throw in good public transport connections and after school activities for the teenager.

There is a lot of work going on around making services adapted to needs of people and place than aligned to departmental processes - just look at Every Child Matters, CAA and MAAs.

If we start opening up data in line with these areas, then service managers (and data owners!) would see it as part of the toolkit to making it easier to achieve specific outcomes they have?</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t put it better myself Steph and this is certainly what we have found through developing our Pic &amp; Mix project down in Kent.  </p>
<p>All the questions you mention are interlinked &#8211; Which data? Who decides whether to publish? Who benefits? Who pays? For how long?</p>
<p>Given the infinite sets of data across a council or government dept, let alone across all public sector, you would need a diktat to make sure that all publicly available data was released in a re-usable way.</p>
<p>Let&#8217;s take a very specific example of the benefits of opening up data to be mashed together. You&#8217;ve got a family moving to a new area &#8211; father&#8217;s been relocated, mother needs to find new job, their 16 yr old kid wants to start an apprenticeship and the three yr old needs some kind of childcare arrangements &#8211; oh yeah and throw in good public transport connections and after school activities for the teenager.</p>
<p>There is a lot of work going on around making services adapted to needs of people and place than aligned to departmental processes &#8211; just look at Every Child Matters, CAA and MAAs.</p>
<p>If we start opening up data in line with these areas, then service managers (and data owners!) would see it as part of the toolkit to making it easier to achieve specific outcomes they have?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feargal Hogan</title>
		<link>http://blog.helpfultechnology.com/2009/05/cui-bono-the-problem-with-opening-up-data/comment-page-1/#comment-4466</link>
		<dc:creator>Feargal Hogan</dc:creator>
		<pubDate>Thu, 28 May 2009 07:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.helpfultechnology.com/?p=281#comment-4466</guid>
		<description>Great post Steph. Just one little thing.

I&#039;m not sure you are necessarily correct about the cleanup requirements associated with publishing data.

I understand that the data may not be 100%, but most of us who want the datasets are quite happy to work with - and around - the imperfections. I certainly don&#039;t want our civil servants to be tasked with cleaning-up the data before publishing it. I&#039;m pretty sure that will be used as an excuse to delay it. 

Get it out there warts and all.</description>
		<content:encoded><![CDATA[<p>Great post Steph. Just one little thing.</p>
<p>I&#8217;m not sure you are necessarily correct about the cleanup requirements associated with publishing data.</p>
<p>I understand that the data may not be 100%, but most of us who want the datasets are quite happy to work with &#8211; and around &#8211; the imperfections. I certainly don&#8217;t want our civil servants to be tasked with cleaning-up the data before publishing it. I&#8217;m pretty sure that will be used as an excuse to delay it. </p>
<p>Get it out there warts and all.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
