<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.2" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>shimenawa - Latest comments on Open data isn't</title>
		<link>http://blogs.lib.berkeley.edu/shimenawa.php?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.2"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: Open data isn't</title>
			<pubDate>Mon, 28 Jul 2008 19:42:24 +0000</pubDate>
			<dc:creator>Samuel Generoux [Visitor]</dc:creator>
			<guid isPermaLink="false">c57541@http://blogs.lib.berkeley.edu/</guid>
			<description>I actually think that this is an excellent and highly relevant observation.  In terms of Google maps and Google books, we might be looking at different types of things, but the pattern is similar.  In terms of access to content, this is really looking more like an issue of degree or maybe type of access.  Google is indeed providing more access to material than was previously available, but there are costs and trade-offs.    There is certainly no harm in saying and discussing this point.  The solution might be to continue to work towards mapping and articulating these types of issues and promoting discussion as a way of understanding how information and culture can be and should be shared in a networked digital environment.  In order to make the most informed decisions, libraries, archives, museums and holders of public information need to understand the ramifications of these partnerships and the terms and conditions that come with them.   &lt;br /&gt;
Additionally, we need to understand what is being provided by Google and the limitations of what is being provided in order for our public institutions to create and adjust their policies, priorities and actions.&lt;br /&gt;
&lt;br /&gt;
I just finished reading Jonathan Zittrain&amp;#8217;s Future of the Internet and I think that his book does an amazing job of parsing out a lot of these issues.  He uses the term &amp;#8220;generative&amp;#8221; to refer to the degree of openness in being able to innovate, experiment and hack on content and technology in order to create new things.  Services like Google Books allows us to search across vast amounts of content for free and it provides citation, snippet and some full text access for free.  A powerful and highly useful service.  However, users are quite limited in how they can hack up and riff on this mass of data.  It is open to search, open to read (to various degrees according to copyright), but not completely open to do R&amp;amp;D and other experimenting.  Google is providing an API platform for others to develop and play with the data, but as Zittrain points out, this openness is contingent.  Services and tools built on open APIs can be withdrawn at anytime by the owner of the API (in this case Google).  &lt;br /&gt;
&lt;br /&gt;
I think a good perspective on all of this is that it is not an either-or debate.  Not completely open or completely locked down.  There are and will continue to be degrees of openness, but it is important for libraries, archives and museums to make decisions about how they share content based on an understanding of the networked digital environment and the degrees and types of access.&lt;br /&gt;</description>
			<content:encoded><![CDATA[I actually think that this is an excellent and highly relevant observation.  In terms of Google maps and Google books, we might be looking at different types of things, but the pattern is similar.  In terms of access to content, this is really looking more like an issue of degree or maybe type of access.  Google is indeed providing more access to material than was previously available, but there are costs and trade-offs.    There is certainly no harm in saying and discussing this point.  The solution might be to continue to work towards mapping and articulating these types of issues and promoting discussion as a way of understanding how information and culture can be and should be shared in a networked digital environment.  In order to make the most informed decisions, libraries, archives, museums and holders of public information need to understand the ramifications of these partnerships and the terms and conditions that come with them.   <br />
Additionally, we need to understand what is being provided by Google and the limitations of what is being provided in order for our public institutions to create and adjust their policies, priorities and actions.<br />
<br />
I just finished reading Jonathan Zittrain&#8217;s Future of the Internet and I think that his book does an amazing job of parsing out a lot of these issues.  He uses the term &#8220;generative&#8221; to refer to the degree of openness in being able to innovate, experiment and hack on content and technology in order to create new things.  Services like Google Books allows us to search across vast amounts of content for free and it provides citation, snippet and some full text access for free.  A powerful and highly useful service.  However, users are quite limited in how they can hack up and riff on this mass of data.  It is open to search, open to read (to various degrees according to copyright), but not completely open to do R&amp;D and other experimenting.  Google is providing an API platform for others to develop and play with the data, but as Zittrain points out, this openness is contingent.  Services and tools built on open APIs can be withdrawn at anytime by the owner of the API (in this case Google).  <br />
<br />
I think a good perspective on all of this is that it is not an either-or debate.  Not completely open or completely locked down.  There are and will continue to be degrees of openness, but it is important for libraries, archives and museums to make decisions about how they share content based on an understanding of the networked digital environment and the degrees and types of access.<br />]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/25/open_data_isn_t#c57541</link>
		</item>
				<item>
			<title>In response to: Open data isn't</title>
			<pubDate>Thu, 26 Jun 2008 14:20:02 +0000</pubDate>
			<dc:creator>Raymond Yee [Visitor]</dc:creator>
			<guid isPermaLink="false">c54631@http://blogs.lib.berkeley.edu/</guid>
			<description>What does Thomas Lord suggest that we who would otherwise use a commercial service like Google maps to do?  Not create mashups at all?  Create mashups that involve no commercial services?  (I'm writing as someone interested in both mashups and helping people make sense of public data.)&lt;br /&gt;
&lt;br /&gt;
</description>
			<content:encoded><![CDATA[What does Thomas Lord suggest that we who would otherwise use a commercial service like Google maps to do?  Not create mashups at all?  Create mashups that involve no commercial services?  (I'm writing as someone interested in both mashups and helping people make sense of public data.)<br />
<br />
]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/25/open_data_isn_t#c54631</link>
		</item>
				<item>
			<title>In response to: Open data isn't</title>
			<pubDate>Thu, 26 Jun 2008 10:24:58 +0000</pubDate>
			<dc:creator>Paul Courant [Visitor]</dc:creator>
			<guid isPermaLink="false">c54629@http://blogs.lib.berkeley.edu/</guid>
			<description>The choice between well-funded, far-seeing, wise, intelligent government and the world that we live in is a false choice.  We never had such a government. Neither did ancient Athens.  &lt;br /&gt;
&lt;br /&gt;
It has always been the case that private entities (R.H. Polk, for example) have used public data and reused them to provide detailed geographic information to those who were willing to pay for it.  Is that better or worse than the example with Google maps?  I would argue the old way was less democratic, and less open, although we are still, alas, short of being able to get our news from the brow of the philosopher-monarch.&lt;br /&gt;
&lt;br /&gt;
More generally, if private entities can add value (preferably not by monopolizing something, but by actually adding value) to public data, that's capitalism at its best. Along these lines, I have an entry on my blog (Au Courant at paulcourant.net) that explains why I choose to have an attribution only Creative Commons license on the blog.  I may, of course, be wrong about this, but my position derives from the notion that we want date to be used in ways that people value. &lt;br /&gt;
&lt;br /&gt;
Again, the choice is between levels of imperfection, not between the ideal and something less.  </description>
			<content:encoded><![CDATA[The choice between well-funded, far-seeing, wise, intelligent government and the world that we live in is a false choice.  We never had such a government. Neither did ancient Athens.  <br />
<br />
It has always been the case that private entities (R.H. Polk, for example) have used public data and reused them to provide detailed geographic information to those who were willing to pay for it.  Is that better or worse than the example with Google maps?  I would argue the old way was less democratic, and less open, although we are still, alas, short of being able to get our news from the brow of the philosopher-monarch.<br />
<br />
More generally, if private entities can add value (preferably not by monopolizing something, but by actually adding value) to public data, that's capitalism at its best. Along these lines, I have an entry on my blog (Au Courant at paulcourant.net) that explains why I choose to have an attribution only Creative Commons license on the blog.  I may, of course, be wrong about this, but my position derives from the notion that we want date to be used in ways that people value. <br />
<br />
Again, the choice is between levels of imperfection, not between the ideal and something less.  ]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/25/open_data_isn_t#c54629</link>
		</item>
			</channel>
</rss>
