<?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: The Three Laws of Open Data</title>
	<atom:link href="http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/</link>
	<description>Design by Ben Crothers of Catch Media</description>
	<lastBuildDate>Wed, 10 Mar 2010 06:21:37 +1100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Three Laws of Open Data (International Edition) &#124; eaves.ca</title>
		<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/comment-page-1/#comment-4993</link>
		<dc:creator>Three Laws of Open Data (International Edition) &#124; eaves.ca</dc:creator>
		<pubDate>Mon, 30 Nov 2009 04:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://gov2.net.au/?p=1190#comment-4993</guid>
		<description>[...] When I published the Three Laws of Open Data post back on September 30, 2009 I was pleasantly surprised by how much traffic it garnered. In addition, a number of people emailed me positive feedback about the post (including some who read a revised version on the Australian Governments Web 2.0 Taskforce blog). [...]</description>
		<content:encoded><![CDATA[<p>[...] When I published the Three Laws of Open Data post back on September 30, 2009 I was pleasantly surprised by how much traffic it garnered. In addition, a number of people emailed me positive feedback about the post (including some who read a revised version on the Australian Governments Web 2.0 Taskforce blog). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simonfj</title>
		<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/comment-page-1/#comment-2562</link>
		<dc:creator>simonfj</dc:creator>
		<pubDate>Wed, 21 Oct 2009 23:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://gov2.net.au/?p=1190#comment-2562</guid>
		<description>David,

I&#039;m not sure how silly this is going to stike you. I have this problem in not being able to dstinguish betwen what is happening in the Open Governmental Data area (.gov) and what has been happening for the past 10 years in &lt;a href=&quot;http://en.wikipedia.org/wiki/Open_educational_resources&quot; rel=&quot;nofollow&quot;&gt;Open Educational Resources&lt;/a&gt; (.edu). Can you explain the differences?

I like the rightt0know conference. Can you tell us the url for where you&#039;re streaming and recording it, and taking questions and comments?

Lastly, could you explain the title &quot;interim commissioner&quot;?</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>I&#8217;m not sure how silly this is going to stike you. I have this problem in not being able to dstinguish betwen what is happening in the Open Governmental Data area (.gov) and what has been happening for the past 10 years in <a href="http://en.wikipedia.org/wiki/Open_educational_resources" rel="nofollow">Open Educational Resources</a> (.edu). Can you explain the differences?</p>
<p>I like the rightt0know conference. Can you tell us the url for where you&#8217;re streaming and recording it, and taking questions and comments?</p>
<p>Lastly, could you explain the title &#8220;interim commissioner&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Cox</title>
		<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/comment-page-1/#comment-2555</link>
		<dc:creator>Kevin Cox</dc:creator>
		<pubDate>Wed, 21 Oct 2009 18:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://gov2.net.au/?p=1190#comment-2555</guid>
		<description>The reason why government data is valued highly is that it is trusted. 

Kerry makes an excellent point. Data needs to be understood and that requires meta data which must also include &quot;how the data came into existence&quot;, &quot;a measure of trust in the accuracy&quot;, &quot;who is permitted to access the data&quot;,  &quot;who is permitted to modify it&quot;, etc.

When government data is released the answers to these meaning and meta questions are implied by the fact that it has been released by a known government body. For government data to be released &quot;electronically&quot; rules and information that can be embodied in meta data or by the fact it can be seen must be established so that the trust can be maintained.

Perhaps there needs to be another law that tries to encapsulate this. Maybe something like

&quot;Only data that can be understood and trusted should be open&quot;  or in the words of David Eaves
&quot;Only data that can be understood and trusted should exist&quot;</description>
		<content:encoded><![CDATA[<p>The reason why government data is valued highly is that it is trusted. </p>
<p>Kerry makes an excellent point. Data needs to be understood and that requires meta data which must also include &#8220;how the data came into existence&#8221;, &#8220;a measure of trust in the accuracy&#8221;, &#8220;who is permitted to access the data&#8221;,  &#8220;who is permitted to modify it&#8221;, etc.</p>
<p>When government data is released the answers to these meaning and meta questions are implied by the fact that it has been released by a known government body. For government data to be released &#8220;electronically&#8221; rules and information that can be embodied in meta data or by the fact it can be seen must be established so that the trust can be maintained.</p>
<p>Perhaps there needs to be another law that tries to encapsulate this. Maybe something like</p>
<p>&#8220;Only data that can be understood and trusted should be open&#8221;  or in the words of David Eaves<br />
&#8220;Only data that can be understood and trusted should exist&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Grace</title>
		<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/comment-page-1/#comment-2529</link>
		<dc:creator>Gordon Grace</dc:creator>
		<pubDate>Wed, 21 Oct 2009 00:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://gov2.net.au/?p=1190#comment-2529</guid>
		<description>I think the &#039;optimized to be crawled&#039; caveat described here definitely deserves further investigation.  Given that the recommendations in the linked page (&quot;Do You See Spiders&quot;) include:

&lt;blockquote&gt;# Make use of clear and logical metadata such as Title, Description and Canonical tags to ensure that both search engines and your prospective searchers can make sense of the results. Nothing worse than publishing a record with an HTML title like “32432-43A”. Nobody is going to click on that!&lt;/blockquote&gt;

Dedicated &#039;vertical search&#039; providers (not unlike those provided by ASDD) then have a chance to slice and dice a data registry in several meaningful ways.  Publishing a dataset&#039;s metadata in a structured, standardised fashion on the web could conceivably allow &lt;strong&gt;anyone&lt;/strong&gt; to create a &#039;dataset search&#039; engine to answer queries such as:

&quot;Find me a crime-themed dataset for my new suburb from the last 2 years.&quot;

Of course, within the metadata (or landing page for that dataset), a link to that dataset&#039;s &quot;More Documentation&quot; / &quot;More Metadata&quot; / &quot;Data Dictionary&quot; resource would be enormously valuable, once you&#039;ve determined that a given set is suitable to your requirements.</description>
		<content:encoded><![CDATA[<p>I think the &#8216;optimized to be crawled&#8217; caveat described here definitely deserves further investigation.  Given that the recommendations in the linked page (&#8221;Do You See Spiders&#8221;) include:</p>
<blockquote><p># Make use of clear and logical metadata such as Title, Description and Canonical tags to ensure that both search engines and your prospective searchers can make sense of the results. Nothing worse than publishing a record with an HTML title like “32432-43A”. Nobody is going to click on that!</p></blockquote>
<p>Dedicated &#8216;vertical search&#8217; providers (not unlike those provided by ASDD) then have a chance to slice and dice a data registry in several meaningful ways.  Publishing a dataset&#8217;s metadata in a structured, standardised fashion on the web could conceivably allow <strong>anyone</strong> to create a &#8216;dataset search&#8217; engine to answer queries such as:</p>
<p>&#8220;Find me a crime-themed dataset for my new suburb from the last 2 years.&#8221;</p>
<p>Of course, within the metadata (or landing page for that dataset), a link to that dataset&#8217;s &#8220;More Documentation&#8221; / &#8220;More Metadata&#8221; / &#8220;Data Dictionary&#8221; resource would be enormously valuable, once you&#8217;ve determined that a given set is suitable to your requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerry Webb</title>
		<link>http://gov2.net.au/blog/2009/10/20/the-three-laws-of-open-data/comment-page-1/#comment-2526</link>
		<dc:creator>Kerry Webb</dc:creator>
		<pubDate>Tue, 20 Oct 2009 22:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://gov2.net.au/?p=1190#comment-2526</guid>
		<description>What about metadata?

An Excel spreadsheet with no documentation but column headings may meet all the criteria, but it&#039;s essentially unusable.</description>
		<content:encoded><![CDATA[<p>What about metadata?</p>
<p>An Excel spreadsheet with no documentation but column headings may meet all the criteria, but it&#8217;s essentially unusable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
