<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Web 2.0 and the limits of owning your data</title>
	<link>http://www.econometa.com/archives/24</link>
	<description>The economy of stuff about stuff</description>
	<pubDate>Wed, 07 Jan 2009 02:15:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Good neighbors &#171; The gaping silence</title>
		<link>http://www.econometa.com/archives/24#comment-15866</link>
		<author>Good neighbors &#171; The gaping silence</author>
		<pubDate>Wed, 14 Nov 2007 21:51:43 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-15866</guid>
		<description>[...] I&#8217;d recently been reading this post on EconoMeta, in which Adam talks about our changing relationship with our personal data: one [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I&#8217;d recently been reading this post on EconoMeta, in which Adam talks about our changing relationship with our personal data: one [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob rowntree</title>
		<link>http://www.econometa.com/archives/24#comment-110</link>
		<author>rob rowntree</author>
		<pubDate>Sun, 30 Oct 2005 11:36:40 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-110</guid>
		<description>Independent of Web 2.0 developments, frameworks and specs. for Web services have also been addressing the problem of isolating the (meta)Data from the implementation. 

http://www-128.ibm.com/developerworks/library/specification/ws-resource/

Best practices dont seem to be saying that web20 implementations should be WebServices based. However, there is something to a framework that allows you to build things using a sort of template like:
1. tell me what you want to do
2. tell me where the WS-Resource compliant data is 
3. provide an implementation that can use any source for #2 but that in this particular instance will use the data at #2</description>
		<content:encoded><![CDATA[<p>Independent of Web 2.0 developments, frameworks and specs. for Web services have also been addressing the problem of isolating the (meta)Data from the implementation. </p>
<p><a href="http://www-128.ibm.com/developerworks/library/specification/ws-resource/" rel="nofollow">http://www-128.ibm.com/developerworks/library/specification/ws-resource/</a></p>
<p>Best practices dont seem to be saying that web20 implementations should be WebServices based. However, there is something to a framework that allows you to build things using a sort of template like:<br />
1. tell me what you want to do<br />
2. tell me where the WS-Resource compliant data is<br />
3. provide an implementation that can use any source for #2 but that in this particular instance will use the data at #2</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.econometa.com/archives/24#comment-105</link>
		<author>Adam</author>
		<pubDate>Wed, 26 Oct 2005 16:36:34 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-105</guid>
		<description>Dorrian, I couldn't agree more -- at least in copyright law, it seems to me that the root issue is that the nature of a "copy" has changed, and therefore so must the laws (although I'm not sure exactly in what way). I also agree with your first point, which to me says that yes, personal data such as identity and social networks have value to the user and so are subject to a demand by users for decoupling from apps; but even for data that has no such demand associated with it (e.g. for users that do everything within Yahoo or Google), decoupling is still important to avoid a potentially dangerous concentration of power. Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Dorrian, I couldn&#8217;t agree more &#8212; at least in copyright law, it seems to me that the root issue is that the nature of a &#8220;copy&#8221; has changed, and therefore so must the laws (although I&#8217;m not sure exactly in what way). I also agree with your first point, which to me says that yes, personal data such as identity and social networks have value to the user and so are subject to a demand by users for decoupling from apps; but even for data that has no such demand associated with it (e.g. for users that do everything within Yahoo or Google), decoupling is still important to avoid a potentially dangerous concentration of power. Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorrian Porter</title>
		<link>http://www.econometa.com/archives/24#comment-83</link>
		<author>Dorrian Porter</author>
		<pubDate>Fri, 21 Oct 2005 22:13:30 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-83</guid>
		<description>For me the debate has shifted a little from a point I was trying to make (less about data).  I was mostly concerned with elements of identity and social networks, and the impact on switching costs.  I'm most torn over the problem that a website or service is the holder of reputational, preference and identity data, and not the Internet itself.  Of course it is in the interest of any website or service to want to guard that data and create switching costs, but it just seems to be so damn inefficient.  I'm tired of hearing about any company that thinks it can get me to create a social network within its site.  Yet, the problem is even bigger when you think of the major players - where they believe, based on size, bredth and scale, that they are a natural fit for holding all of this information across all categories.  It's scary.  That's when I think the solution must lie in giving the individual more control.

The content creation/management side is a separate albeit equally interesting and challenging issue.  Lessig made probably the most compelling point to me for the reason CC exists in a recent post.  "If copyright regulates "copies," then while a tiny portion of the uses of culture off the net involves making "copies," every use of culture on the net begins by making a copy."  That sure made me stop and think just how troubling old laws applied to the new world might be.  Laws definitely need to change.</description>
		<content:encoded><![CDATA[<p>For me the debate has shifted a little from a point I was trying to make (less about data).  I was mostly concerned with elements of identity and social networks, and the impact on switching costs.  I&#8217;m most torn over the problem that a website or service is the holder of reputational, preference and identity data, and not the Internet itself.  Of course it is in the interest of any website or service to want to guard that data and create switching costs, but it just seems to be so damn inefficient.  I&#8217;m tired of hearing about any company that thinks it can get me to create a social network within its site.  Yet, the problem is even bigger when you think of the major players - where they believe, based on size, bredth and scale, that they are a natural fit for holding all of this information across all categories.  It&#8217;s scary.  That&#8217;s when I think the solution must lie in giving the individual more control.</p>
<p>The content creation/management side is a separate albeit equally interesting and challenging issue.  Lessig made probably the most compelling point to me for the reason CC exists in a recent post.  &#8220;If copyright regulates &#8220;copies,&#8221; then while a tiny portion of the uses of culture off the net involves making &#8220;copies,&#8221; every use of culture on the net begins by making a copy.&#8221;  That sure made me stop and think just how troubling old laws applied to the new world might be.  Laws definitely need to change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.econometa.com/archives/24#comment-67</link>
		<author>Adam</author>
		<pubDate>Fri, 21 Oct 2005 00:30:37 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-67</guid>
		<description>That's my first reaction as well; but then I think, what about authors who are depending upon income based on their writing on the web? Even if the feed is only excerpts, the entire article can always be screen scraped -- that's why I think the ongoing debate around *public* data is more about monetization and recognition for the content creator. 

In fact, I'd say it's really not a technology or business issue at all, it's a legal issue: if society wants authors (or musicians, artists, etc.) to be able to somehow profit from their public works in a digital world, legal restrictions have to be made on what is permissable. DRM, robot.txt mods, and similar tech doodads are just enforcement techniques, but they all only make repurposing more of a hassle, they'll never really prevent it. 

In the end, enforcement has to center around a clear idea of what everyone has decided is right and wrong, and right now, with so many new ways of repurposing data being created, no one is really sure.</description>
		<content:encoded><![CDATA[<p>That&#8217;s my first reaction as well; but then I think, what about authors who are depending upon income based on their writing on the web? Even if the feed is only excerpts, the entire article can always be screen scraped &#8212; that&#8217;s why I think the ongoing debate around *public* data is more about monetization and recognition for the content creator. </p>
<p>In fact, I&#8217;d say it&#8217;s really not a technology or business issue at all, it&#8217;s a legal issue: if society wants authors (or musicians, artists, etc.) to be able to somehow profit from their public works in a digital world, legal restrictions have to be made on what is permissable. DRM, robot.txt mods, and similar tech doodads are just enforcement techniques, but they all only make repurposing more of a hassle, they&#8217;ll never really prevent it. </p>
<p>In the end, enforcement has to center around a clear idea of what everyone has decided is right and wrong, and right now, with so many new ways of repurposing data being created, no one is really sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Russell</title>
		<link>http://www.econometa.com/archives/24#comment-59</link>
		<author>Seth Russell</author>
		<pubDate>Wed, 19 Oct 2005 22:07:56 +0000</pubDate>
		<guid>http://www.econometa.com/archives/24#comment-59</guid>
		<description>Over at Shelly's site you said "if you make your data public, you necessarily lose a great deal of control over it" ... which struck me as ooh so true.   Information is not like physical property.  It is fundamentally different.  The value of information lies in its ability to be repeated and still remain useful.  If it can be used in only one spot, in only in one context, then is its value is substantially diminished.

Now I certainly subscribe to the idea that people should be able to export\import their data between web services.  But the ability of an author to restrain the flow and interaction of the information that they generate when they write on the web is not, in general, something that is going to improve our culture.  In fact that ability is something that we would be better off if it were just forgotten.</description>
		<content:encoded><![CDATA[<p>Over at Shelly&#8217;s site you said &#8220;if you make your data public, you necessarily lose a great deal of control over it&#8221; &#8230; which struck me as ooh so true.   Information is not like physical property.  It is fundamentally different.  The value of information lies in its ability to be repeated and still remain useful.  If it can be used in only one spot, in only in one context, then is its value is substantially diminished.</p>
<p>Now I certainly subscribe to the idea that people should be able to export\import their data between web services.  But the ability of an author to restrain the flow and interaction of the information that they generate when they write on the web is not, in general, something that is going to improve our culture.  In fact that ability is something that we would be better off if it were just forgotten.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
