<?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: Let my plumber Jez build your SDI..</title>
	<atom:link href="http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/</link>
	<description></description>
	<lastBuildDate>Sat, 13 Mar 2010 13:52:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Antony Scott</title>
		<link>http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/comment-page-1/#comment-154007</link>
		<dc:creator>Antony Scott</dc:creator>
		<pubDate>Wed, 24 Jun 2009 09:13:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=921#comment-154007</guid>
		<description>I was at the session too, and found the water metaphor interesting, like all good metaphors it got me thinking about how far it could be stretched. My frustrations at the moment are around the range of data formats, standards and practices requiring converters before you can use them, and sources which make it impossible for you to get anything useful out of them by restricting you to one drip at a time! That&#039;s probably far enough, but there&#039;s clearly a need to open the flood gates (sorry!) and get more stuff in the cloud. Although I came away from the conference not being very much clearer about what an SDI was, I know that the &#039;D&#039;ata needs as much attention as the rest if we are to be able to get (as per last comment)  innovation and useful services.</description>
		<content:encoded><![CDATA[<p>I was at the session too, and found the water metaphor interesting, like all good metaphors it got me thinking about how far it could be stretched. My frustrations at the moment are around the range of data formats, standards and practices requiring converters before you can use them, and sources which make it impossible for you to get anything useful out of them by restricting you to one drip at a time! That&#8217;s probably far enough, but there&#8217;s clearly a need to open the flood gates (sorry!) and get more stuff in the cloud. Although I came away from the conference not being very much clearer about what an SDI was, I know that the &#8216;D&#8217;ata needs as much attention as the rest if we are to be able to get (as per last comment)  innovation and useful services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Barnes</title>
		<link>http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/comment-page-1/#comment-154006</link>
		<dc:creator>Peter Barnes</dc:creator>
		<pubDate>Wed, 24 Jun 2009 00:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=921#comment-154006</guid>
		<description>Two timely and well made points.  There has been a bit of disucussion around who or what neogeos are of late, and your post highlights a couple of the major philosophical differences.  I believe the first key differentiator is a strong customer and solution focus vs data and technology, the second an openness to web 2.0 concepts and an allied willingness to generate and use data and services with long and complex genealogy.  I&#039;m not suggesting that neogeos aren&#039;t interested in data and technology, it&#039;s that they regard them as the means to an end - solving a problem for real world citizens.  Cloud computing and the various tools offered by Google, Microsoft, Cloudmade etc. are extremely useful tools for achieving this goal, and significantly provide a low cost of entry route for innovation.</description>
		<content:encoded><![CDATA[<p>Two timely and well made points.  There has been a bit of disucussion around who or what neogeos are of late, and your post highlights a couple of the major philosophical differences.  I believe the first key differentiator is a strong customer and solution focus vs data and technology, the second an openness to web 2.0 concepts and an allied willingness to generate and use data and services with long and complex genealogy.  I&#8217;m not suggesting that neogeos aren&#8217;t interested in data and technology, it&#8217;s that they regard them as the means to an end &#8211; solving a problem for real world citizens.  Cloud computing and the various tools offered by Google, Microsoft, Cloudmade etc. are extremely useful tools for achieving this goal, and significantly provide a low cost of entry route for innovation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ewan</title>
		<link>http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/comment-page-1/#comment-153998</link>
		<dc:creator>Ewan</dc:creator>
		<pubDate>Mon, 22 Jun 2009 12:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=921#comment-153998</guid>
		<description>Interestinng observation around the demographic of the people attending the conference. There does seem to be plenty of discussion from within the &quot;GI Community&quot; but little engagement from those who would get real benefits from an SDI approach. I have recently undertaken an exercise to scope out an SDI, rather than looking at the technology the focus was very much on the people and process side.  After all, the technology is all avaliable, the trick is finding out requirements and getting &quot;users&quot; to change their behaviour and interact with an SDI, even if they dont now that. We actually found that some SDI components already existed and just needed a small tweak.  In some ways I think the term SDI is mis-leading and hard to explain exactly what it is.</description>
		<content:encoded><![CDATA[<p>Interestinng observation around the demographic of the people attending the conference. There does seem to be plenty of discussion from within the &#8220;GI Community&#8221; but little engagement from those who would get real benefits from an SDI approach. I have recently undertaken an exercise to scope out an SDI, rather than looking at the technology the focus was very much on the people and process side.  After all, the technology is all avaliable, the trick is finding out requirements and getting &#8220;users&#8221; to change their behaviour and interact with an SDI, even if they dont now that. We actually found that some SDI components already existed and just needed a small tweak.  In some ways I think the term SDI is mis-leading and hard to explain exactly what it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChrisW</title>
		<link>http://www.edparsons.com/2009/06/let-my-plumber-jez-build-your-sdi/comment-page-1/#comment-153989</link>
		<dc:creator>ChrisW</dc:creator>
		<pubDate>Sun, 21 Jun 2009 16:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.edparsons.com/?p=921#comment-153989</guid>
		<description>Good point about the absence of user perspectives on all this, and the point about &quot;plumbing&quot; geodata to the consumer is well-made.  But when you say that Google et al &quot;would be happy to host data on behalf of public sector bodies&quot;, you&#039;re straight back to the widespread problem of who owns &quot;public&quot; data in the UK.

Having spoken to some public sector GIS users recently, there still seems to be a lot of FUD (often encouraged by your former employers at the OS) surrounding the question of who owns OS data when it is mixed with Google data or even just passed through a Google mapping tool.  People are often ignorant and suspicious about the extent to which they &quot;own&quot; their own data or whether they may infringe draconian OS licences simply by using the term &quot;Google&quot; in the near vicinity of their spatial applications, and some believe that Google is out to claim ownership of their data.  Ironically, it seems the OS tacitly encourages this belief, even while asserting its own rights over &quot;derived&quot; spatial data.

Until there is greater clarity (and sense) around the licencing of &quot;public&quot; spatial data in the UK, I can&#039;t see many public sector organisations feeling brave enough to hand their data over for 3rd party hosting, least of all to Google.</description>
		<content:encoded><![CDATA[<p>Good point about the absence of user perspectives on all this, and the point about &#8220;plumbing&#8221; geodata to the consumer is well-made.  But when you say that Google et al &#8220;would be happy to host data on behalf of public sector bodies&#8221;, you&#8217;re straight back to the widespread problem of who owns &#8220;public&#8221; data in the UK.</p>
<p>Having spoken to some public sector GIS users recently, there still seems to be a lot of FUD (often encouraged by your former employers at the OS) surrounding the question of who owns OS data when it is mixed with Google data or even just passed through a Google mapping tool.  People are often ignorant and suspicious about the extent to which they &#8220;own&#8221; their own data or whether they may infringe draconian OS licences simply by using the term &#8220;Google&#8221; in the near vicinity of their spatial applications, and some believe that Google is out to claim ownership of their data.  Ironically, it seems the OS tacitly encourages this belief, even while asserting its own rights over &#8220;derived&#8221; spatial data.</p>
<p>Until there is greater clarity (and sense) around the licencing of &#8220;public&#8221; spatial data in the UK, I can&#8217;t see many public sector organisations feeling brave enough to hand their data over for 3rd party hosting, least of all to Google.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
