<?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: Who reads the Terms of Service anyway..</title>
	<atom:link href="http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/</link>
	<description>The blog of Ed Parsons, Geographer.</description>
	<lastBuildDate>Mon, 06 Feb 2012 22:11:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Google Updates Terms of Service for the Google Maps API</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1600</link>
		<dc:creator>Google Updates Terms of Service for the Google Maps API</dc:creator>
		<pubDate>Mon, 15 Dec 2008 06:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1600</guid>
		<description>[...] can view the new terms of service here. Ed Parsons has a good summary of all of the changes, and there is a thread on Google Groups that had 45 comments at last [...] </description>
		<content:encoded><![CDATA[<p>[...] can view the new terms of service here. Ed Parsons has a good summary of all of the changes, and there is a thread on Google Groups that had 45 comments at last [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nearby.org.uk blog &#187; Blog Archive &#187; Between a rock and a hard place&#8230;</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1599</link>
		<dc:creator>nearby.org.uk blog &#187; Blog Archive &#187; Between a rock and a hard place&#8230;</dc:creator>
		<pubDate>Mon, 08 Dec 2008 02:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1599</guid>
		<description>[...] to issues brought up on the Mail group, and elsewhere. As a result of that edit there where many concerns raised - and a further edit was made. (note, only linked to some of the blogs etc - follow [...] </description>
		<content:encoded><![CDATA[<p>[...] to issues brought up on the Mail group, and elsewhere. As a result of that edit there where many concerns raised &#8211; and a further edit was made. (note, only linked to some of the blogs etc &#8211; follow [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everybody reads the Terms of Service.. &#124; edparsons.com</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1598</link>
		<dc:creator>Everybody reads the Terms of Service.. &#124; edparsons.com</dc:creator>
		<pubDate>Thu, 27 Nov 2008 08:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1598</guid>
		<description>[...] section 11 was an area of concern to the community, it is the section that balances legally what you as a map user submit and how [...] </description>
		<content:encoded><![CDATA[<p>[...] section 11 was an area of concern to the community, it is the section that balances legally what you as a map user submit and how [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Revises Their Update to the Google Maps API Terms of Service</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1597</link>
		<dc:creator>Google Revises Their Update to the Google Maps API Terms of Service</dc:creator>
		<pubDate>Thu, 27 Nov 2008 03:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1597</guid>
		<description>[...] to suggest that by using the API, you were giving Google a license to your data.  Ed Parsons blogged about the situation so you can follow more what the problems were there, but this latest update seems to remove that [...] </description>
		<content:encoded><![CDATA[<p>[...] to suggest that by using the API, you were giving Google a license to your data.  Ed Parsons blogged about the situation so you can follow more what the problems were there, but this latest update seems to remove that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yep Sport &#187; Blog Archive &#187; iFreeThePostcode</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1596</link>
		<dc:creator>Yep Sport &#187; Blog Archive &#187; iFreeThePostcode</dc:creator>
		<pubDate>Fri, 21 Nov 2008 21:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1596</guid>
		<description>[...] obvious on the ground - is a Good Thing, as the current row between Google and the OS (more, more) about derived data [...] </description>
		<content:encoded><![CDATA[<p>[...] obvious on the ground &#8211; is a Good Thing, as the current row between Google and the OS (more, more) about derived data [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ollie</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1595</link>
		<dc:creator>Ollie</dc:creator>
		<pubDate>Thu, 20 Nov 2008 21:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1595</guid>
		<description>So the new realisation is that data geolocated using an OS map (but not on the OS map itself) cannot be added as a layer on a Google map mashup...

But does this also apply the other way around, e.g. a feature which someone has visually geolocated using a Google map based on Teleatlas data (and so is thereon licensed to Google, but does not appear on the underlying Google/TeleAtlas tile) cannot be used in an OS OpenSpace mashup?

I couldn&#039;t find this scenario in the Google map terms, but then it is quite an intimidating document to read and understand!</description>
		<content:encoded><![CDATA[<p>So the new realisation is that data geolocated using an OS map (but not on the OS map itself) cannot be added as a layer on a Google map mashup&#8230;</p>
<p>But does this also apply the other way around, e.g. a feature which someone has visually geolocated using a Google map based on Teleatlas data (and so is thereon licensed to Google, but does not appear on the underlying Google/TeleAtlas tile) cannot be used in an OS OpenSpace mashup?</p>
<p>I couldn&#8217;t find this scenario in the Google map terms, but then it is quite an intimidating document to read and understand!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kev Winchcombe</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1594</link>
		<dc:creator>Kev Winchcombe</dc:creator>
		<pubDate>Mon, 17 Nov 2008 10:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1594</guid>
		<description>It&#039;s good to hear people discussing this as for me this Google v OS argument is ridiculous.
As a developer within local government I plan(ned) to implement Google Maps whereever I could and our FindMyNearest was just a start. But it uses data from our LLPG using the recently implemented Property Use Classification fieldsm as defined by central government. So the NLPG gives us fields that we can&#039;t tell anyone about using maps. Great.
I&#039;m reminded that our FindMyNearest will still be useful without maps and yes of course it will be but it&#039;ll be nowhere as nice to use.
Come on central goverment, SOCITM or someone, step in and sort this out.</description>
		<content:encoded><![CDATA[<p>It&#8217;s good to hear people discussing this as for me this Google v OS argument is ridiculous.<br />
As a developer within local government I plan(ned) to implement Google Maps whereever I could and our FindMyNearest was just a start. But it uses data from our LLPG using the recently implemented Property Use Classification fieldsm as defined by central government. So the NLPG gives us fields that we can&#8217;t tell anyone about using maps. Great.<br />
I&#8217;m reminded that our FindMyNearest will still be useful without maps and yes of course it will be but it&#8217;ll be nowhere as nice to use.<br />
Come on central goverment, SOCITM or someone, step in and sort this out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://www.edparsons.com/2008/11/who-reads-the-terms-of-service-anyway/#comment-1593</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Sun, 16 Nov 2008 23:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=590#comment-1593</guid>
		<description>All,

As this discussion has grown in scope, and to allow my colleagues back in the States to follow this important thread can I ask you continue posting comments at http://groups.google.com/group/Google-Maps-API/browse_thread/thread/3b0bd5922c7115f0</description>
		<content:encoded><![CDATA[<p>All,</p>
<p>As this discussion has grown in scope, and to allow my colleagues back in the States to follow this important thread can I ask you continue posting comments at <a href="http://groups.google.com/group/Google-Maps-API/browse_thread/thread/3b0bd5922c7115f0" rel="nofollow">http://groups.google.com/group/Google-Maps-API/browse_thread/thread/3b0bd5922c7115f0</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

