<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: The need for clear data licenses</title>
	<atom:link href="http://highearthorbit.com/the-need-for-clear-data-licenses/feed/" rel="self" type="application/rss+xml" />
	<link>http://highearthorbit.com/the-need-for-clear-data-licenses/</link>
	<description>Transmitting ideas, observations, and images from 42,000 km.</description>
	<lastBuildDate>Wed, 17 Mar 2010 20:25:51 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jorge</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-283904</link>
		<dc:creator>Jorge</dc:creator>
		<pubDate>Sun, 29 Nov 2009 00:32:44 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-283904</guid>
		<description>Hello

I Send you a link of a post about spatial data license in Infrastructure for Spatial Information in the European Community (INSPIRE) 

http://www.orbemapa.com/2008/11/inspire-y-las-licencias-de-uso-de-los.html

I hope it´ s useful for discussion.</description>
		<content:encoded><![CDATA[<p>Hello</p>
<p>I Send you a link of a post about spatial data license in Infrastructure for Spatial Information in the European Community (INSPIRE) </p>
<p><a href="http://www.orbemapa.com/2008/11/inspire-y-las-licencias-de-uso-de-los.html" rel="nofollow">http://www.orbemapa.com/2008/11/inspire-y-las-licencias-de-uso-de-los.html</a></p>
<p>I hope it´ s useful for discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikel</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-281250</link>
		<dc:creator>Mikel</dc:creator>
		<pubDate>Tue, 10 Nov 2009 03:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-281250</guid>
		<description>Richard Fairhurst lays out some arguments about modules in this comment ..

http://highearthorbit.com/does-the-opendatabase-license-need-cc-style-modules/#comment-213522

Response?</description>
		<content:encoded><![CDATA[<p>Richard Fairhurst lays out some arguments about modules in this comment ..</p>
<p><a href="http://highearthorbit.com/does-the-opendatabase-license-need-cc-style-modules/#comment-213522" rel="nofollow">http://highearthorbit.com/does-the-opendatabase-license-need-cc-style-modules/#comment-213522</a></p>
<p>Response?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Turner</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-281179</link>
		<dc:creator>Andrew Turner</dc:creator>
		<pubDate>Mon, 09 Nov 2009 17:29:42 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-281179</guid>
		<description>Bad me for writing a weighty post and then traveling for 3 weeks. 

Thank you for the insightful feedback. My point here was less about potential shortcomings of the ODbL. I&#039;m aware of the very hard work that went into making it. Momentum is forward moving with the license and it will be a great shake-out of issues and open data applications.

My goal was to raise the issue that the ODbL is a specific use-case, and one that doesn&#039;t apply to other options for how data is opened. Organizations need various ways and mechanisms to open data. 

Open-Source licenses are varied, and wild, but at least there is a corpus of well understood licenses. So nominally users of the software know what GPL implies vs. Apache. This isn&#039;t the case with data licenses that are unique each and every time.

So even with ODbL, we&#039;ll still see data being released under unique licenses if it, for example, doesn&#039;t need to be share-alike, or can only be used &quot;non-commercial&quot;, etc.</description>
		<content:encoded><![CDATA[<p>Bad me for writing a weighty post and then traveling for 3 weeks. </p>
<p>Thank you for the insightful feedback. My point here was less about potential shortcomings of the ODbL. I&#8217;m aware of the very hard work that went into making it. Momentum is forward moving with the license and it will be a great shake-out of issues and open data applications.</p>
<p>My goal was to raise the issue that the ODbL is a specific use-case, and one that doesn&#8217;t apply to other options for how data is opened. Organizations need various ways and mechanisms to open data. </p>
<p>Open-Source licenses are varied, and wild, but at least there is a corpus of well understood licenses. So nominally users of the software know what GPL implies vs. Apache. This isn&#8217;t the case with data licenses that are unique each and every time.</p>
<p>So even with ODbL, we&#8217;ll still see data being released under unique licenses if it, for example, doesn&#8217;t need to be share-alike, or can only be used &#8220;non-commercial&#8221;, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikel</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-279641</link>
		<dc:creator>Mikel</dc:creator>
		<pubDate>Fri, 30 Oct 2009 12:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-279641</guid>
		<description>Open Source software licenses, and Creative Commons licenses, were the result of a large and long interactive process, which required a lot of legal knowledge capacity building among communities that are not at all lawyers.

Try just reading the GPL or Apache License and tell me if it would make sense without the cultural context and years of experience in open source software.

CC have done a great job at making licensing accessible to non-experts, kudos. 


The OKFN is actually doing a great job of engaging the community, answering questions, clarifying confusing points. The most simple human readable view of the license is below.

http://www.opendatacommons.org/licenses/odbl/summary/

As you point out, CC offer one extreme for open data. ODbL offers another. As for modularization, there are compelling arguments against this, due to the differences in data. But yes, we&#039;ll see, all part of an evolutionary process that has already made pretty great strides.</description>
		<content:encoded><![CDATA[<p>Open Source software licenses, and Creative Commons licenses, were the result of a large and long interactive process, which required a lot of legal knowledge capacity building among communities that are not at all lawyers.</p>
<p>Try just reading the GPL or Apache License and tell me if it would make sense without the cultural context and years of experience in open source software.</p>
<p>CC have done a great job at making licensing accessible to non-experts, kudos. </p>
<p>The OKFN is actually doing a great job of engaging the community, answering questions, clarifying confusing points. The most simple human readable view of the license is below.</p>
<p><a href="http://www.opendatacommons.org/licenses/odbl/summary/" rel="nofollow">http://www.opendatacommons.org/licenses/odbl/summary/</a></p>
<p>As you point out, CC offer one extreme for open data. ODbL offers another. As for modularization, there are compelling arguments against this, due to the differences in data. But yes, we&#8217;ll see, all part of an evolutionary process that has already made pretty great strides.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo Walsh</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-279191</link>
		<dc:creator>Jo Walsh</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-279191</guid>
		<description>dear Andrew,

It looked like much care was taken to make it clear the extent to which &quot;Produced Works&quot; are not subject to any &quot;viral&quot; style ShareAlike conditions; only when using the entire database in public in a systematic way does one become obliged to contribute improvements to the data. 

From the ODbL text at http://www.opendatacommons.org/licenses/odbl/1.0/ : 
&quot;Notice for using output (Contents). Creating and Using a Produced Work does not require the notice in Section 4.2 [conveying the license and indicating compliance with its terms]. However, if you Publicly Use a Produced Work, You must include a notice associated with the Produced Work reasonably calculated to make any Person that uses, views, accesses, interacts with, or is otherwise exposed to the Produced Work aware that Content was obtained from the Database, Derivative Database, or the Database as part of a Collective Database, and that it is available under this License.&quot;

A long time was taken to hit the balance between public domain and ShareAlike advocates, many rounds of consultation with the OSM community in particular. ODbL holds up. It fits the Open Definition - http://opendefinition.org/1.0/ . Nothing is perfect, but it looks like a good candidate license.</description>
		<content:encoded><![CDATA[<p>dear Andrew,</p>
<p>It looked like much care was taken to make it clear the extent to which &#8220;Produced Works&#8221; are not subject to any &#8220;viral&#8221; style ShareAlike conditions; only when using the entire database in public in a systematic way does one become obliged to contribute improvements to the data. </p>
<p>From the ODbL text at <a href="http://www.opendatacommons.org/licenses/odbl/1.0/" rel="nofollow">http://www.opendatacommons.org/licenses/odbl/1.0/</a> :<br />
&#8220;Notice for using output (Contents). Creating and Using a Produced Work does not require the notice in Section 4.2 [conveying the license and indicating compliance with its terms]. However, if you Publicly Use a Produced Work, You must include a notice associated with the Produced Work reasonably calculated to make any Person that uses, views, accesses, interacts with, or is otherwise exposed to the Produced Work aware that Content was obtained from the Database, Derivative Database, or the Database as part of a Collective Database, and that it is available under this License.&#8221;</p>
<p>A long time was taken to hit the balance between public domain and ShareAlike advocates, many rounds of consultation with the OSM community in particular. ODbL holds up. It fits the Open Definition &#8211; <a href="http://opendefinition.org/1.0/" rel="nofollow">http://opendefinition.org/1.0/</a> . Nothing is perfect, but it looks like a good candidate license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Richardson</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-279154</link>
		<dc:creator>Jim Richardson</dc:creator>
		<pubDate>Tue, 27 Oct 2009 07:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-279154</guid>
		<description>For arguments in favour of the CC0 or PDDL approach in the particular case of  publicly funded scientific research data, see John Wilbanks&#039; commentary at http://scienceblogs.com/commonknowledge/2009/05/a_breakthrough_in_data_licensi.php on the &quot;Panton Principles&quot;, developed by Cameron Neylon, Peter Murray-Rust and Rufus Pollock (there are links in John&#039;s posting).

Problems with assertion of any kind of licence rights for research data include incompatibility between different licence formulations preventing data from being combined or mashed up; and the irony that restrictions to non-commercial uses may hinder retention of data in cases where eventual preservation approaches have a commercial component.

Relying on community norms rather than a legal tack can achieve fair attribution without tying the data up.  See also http://sciencecommons.org/projects/publishing/open-access-data-protocol/ which I&#039;ll quote (section 4.1):

&quot;The conflict between simplicity and legal certainty can be best resolved by a twofold measure: 1) a reconstruction of the public domain and 2) the use of scientific norms to express the wishes of the data provider.

&quot;Reconstructing the public domain can be achieved through the use of a legal tool (waiving the relevant rights on data and asserting that the provider makes no claims on the data).

&quot;Requesting behavior, such as citation, through norms rather than as a legal requirement based on copyright or contracts, allows for different scientific disciplines to develop different norms for citation. This allows for legal certainty without constraining one community to the norms of another.&quot;</description>
		<content:encoded><![CDATA[<p>For arguments in favour of the CC0 or PDDL approach in the particular case of  publicly funded scientific research data, see John Wilbanks&#8217; commentary at <a href="http://scienceblogs.com/commonknowledge/2009/05/a_breakthrough_in_data_licensi.php" rel="nofollow">http://scienceblogs.com/commonknowledge/2009/05/a_breakthrough_in_data_licensi.php</a> on the &#8220;Panton Principles&#8221;, developed by Cameron Neylon, Peter Murray-Rust and Rufus Pollock (there are links in John&#8217;s posting).</p>
<p>Problems with assertion of any kind of licence rights for research data include incompatibility between different licence formulations preventing data from being combined or mashed up; and the irony that restrictions to non-commercial uses may hinder retention of data in cases where eventual preservation approaches have a commercial component.</p>
<p>Relying on community norms rather than a legal tack can achieve fair attribution without tying the data up.  See also <a href="http://sciencecommons.org/projects/publishing/open-access-data-protocol/" rel="nofollow">http://sciencecommons.org/projects/publishing/open-access-data-protocol/</a> which I&#8217;ll quote (section 4.1):</p>
<p>&#8220;The conflict between simplicity and legal certainty can be best resolved by a twofold measure: 1) a reconstruction of the public domain and 2) the use of scientific norms to express the wishes of the data provider.</p>
<p>&#8220;Reconstructing the public domain can be achieved through the use of a legal tool (waiving the relevant rights on data and asserting that the provider makes no claims on the data).</p>
<p>&#8220;Requesting behavior, such as citation, through norms rather than as a legal requirement based on copyright or contracts, allows for different scientific disciplines to develop different norms for citation. This allows for legal certainty without constraining one community to the norms of another.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Fairhurst</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-278652</link>
		<dc:creator>Richard Fairhurst</dc:creator>
		<pubDate>Fri, 23 Oct 2009 23:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-278652</guid>
		<description>You don&#039;t actually say what your problem is with ODbL, other than some vague hand-wavy stuff.

Data licensing is hard. When you say you want licences &quot;that would allow anyone to easily demarcate the terms of the data they are releasing&quot;, yeah, I agree. I also want a pony. Try actually writing that in a way that applies both to Rural vs Feist and sweat-of-the-brow jurisdictions...</description>
		<content:encoded><![CDATA[<p>You don&#8217;t actually say what your problem is with ODbL, other than some vague hand-wavy stuff.</p>
<p>Data licensing is hard. When you say you want licences &#8220;that would allow anyone to easily demarcate the terms of the data they are releasing&#8221;, yeah, I agree. I also want a pony. Try actually writing that in a way that applies both to Rural vs Feist and sweat-of-the-brow jurisdictions&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miten sampat</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-278630</link>
		<dc:creator>miten sampat</dc:creator>
		<pubDate>Fri, 23 Oct 2009 21:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-278630</guid>
		<description>Andrew: you have definitely highlighted a large issue here.

in the online advertising world, similar challenges exist for data sharing, reporting, revenue attribution et al. 

from my perspective, this will continue to grow into a larger challenge with companies trying to build more and more semantic technologies. if you recall the speech given by Tim-Berners-Lee at TED in 2009, he is inviting the next set of companies and technologies to exploit semantic data and build meaning.

to allow this next wave of innovation, the hurdles for new ideas to get access to data have to be minimized.

would love to work on a framework, and contribute ideas</description>
		<content:encoded><![CDATA[<p>Andrew: you have definitely highlighted a large issue here.</p>
<p>in the online advertising world, similar challenges exist for data sharing, reporting, revenue attribution et al. </p>
<p>from my perspective, this will continue to grow into a larger challenge with companies trying to build more and more semantic technologies. if you recall the speech given by Tim-Berners-Lee at TED in 2009, he is inviting the next set of companies and technologies to exploit semantic data and build meaning.</p>
<p>to allow this next wave of innovation, the hurdles for new ideas to get access to data have to be minimized.</p>
<p>would love to work on a framework, and contribute ideas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jusitn C. Houk</title>
		<link>http://highearthorbit.com/the-need-for-clear-data-licenses/comment-page-1/#comment-278613</link>
		<dc:creator>Jusitn C. Houk</dc:creator>
		<pubDate>Fri, 23 Oct 2009 18:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/the-need-for-clear-data-licenses/#comment-278613</guid>
		<description>I totally agree with you on this Andrew.  From my perspective working in government, licensing is a total mess.  There are a wide array of data types at different levels of sensitivity to the public.  One size fits all is a very crude solution.  As communities follow the moves of Portland, San Francisco, DC, and others in opening data I can see a some big challenges forming.  Portland is basically just figuring out what their resolution means for everyone working in city bureaus.  Having a toolbox of choices for licensing data would make the process much easier and perhaps encourage other communities to follow suite.

JH</description>
		<content:encoded><![CDATA[<p>I totally agree with you on this Andrew.  From my perspective working in government, licensing is a total mess.  There are a wide array of data types at different levels of sensitivity to the public.  One size fits all is a very crude solution.  As communities follow the moves of Portland, San Francisco, DC, and others in opening data I can see a some big challenges forming.  Portland is basically just figuring out what their resolution means for everyone working in city bureaus.  Having a toolbox of choices for licensing data would make the process much easier and perhaps encourage other communities to follow suite.</p>
<p>JH</p>
]]></content:encoded>
	</item>
</channel>
</rss>
