<?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: Top Down vs. Bottom Up at GeoWeb 2009</title>
	<atom:link href="http://blog.geoiq.com/2009/08/07/top-down-vs-bottom-up-at-geoweb-2009/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.geoiq.com/2009/08/07/top-down-vs-bottom-up-at-geoweb-2009/</link>
	<description>News and updates from GeoIQ</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:02:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sean Gorman</title>
		<link>http://blog.geoiq.com/2009/08/07/top-down-vs-bottom-up-at-geoweb-2009/#comment-1097</link>
		<dc:creator>Sean Gorman</dc:creator>
		<pubDate>Mon, 10 Aug 2009 23:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1158#comment-1097</guid>
		<description>Hi Ian,

I really enjoyed your talk at GeoWeb and you make a very strong case.  I don&#039;t think it is an either or, and definitely plenty of room for both.  I&#039;m assuming business-B2B means the enterprise - fortune 1000 etc.  If so I&#039;m curious where the adoptions have been for GML+SOAP.  I might just be ignorant of it, but largely I don&#039;t see the majority of enterprises doing either (GML+SOAP or KML+REST).  Not convinced anyone has come up with the solution that makes a geospatial implemtnation palatable to the vast majority of enterprises.  A big greenfield that needs to be figured out no doubt.  Maybe GML+SOAP is the answer I&#039;ve just not seen a large market adoption of it or anything else for that matter in the enterprise.

best,
sean</description>
		<content:encoded><![CDATA[<p>Hi Ian,</p>
<p>I really enjoyed your talk at GeoWeb and you make a very strong case.  I don&#8217;t think it is an either or, and definitely plenty of room for both.  I&#8217;m assuming business-B2B means the enterprise &#8211; fortune 1000 etc.  If so I&#8217;m curious where the adoptions have been for GML+SOAP.  I might just be ignorant of it, but largely I don&#8217;t see the majority of enterprises doing either (GML+SOAP or KML+REST).  Not convinced anyone has come up with the solution that makes a geospatial implemtnation palatable to the vast majority of enterprises.  A big greenfield that needs to be figured out no doubt.  Maybe GML+SOAP is the answer I&#8217;ve just not seen a large market adoption of it or anything else for that matter in the enterprise.</p>
<p>best,<br />
sean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Painter</title>
		<link>http://blog.geoiq.com/2009/08/07/top-down-vs-bottom-up-at-geoweb-2009/#comment-1096</link>
		<dc:creator>Ian Painter</dc:creator>
		<pubDate>Mon, 10 Aug 2009 23:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1158#comment-1096</guid>
		<description>Sean,

I did a Top Down talk at GeoWeb and had the pleasure of defending SOAP in the SOAP vs REST vs PERR2PEER. Well the SOAP vrs REST was really quite fun at GeoWeb (it even got me my first appearance on Geek TV). Anyway, the Neogeographers were out in force defending REST at GeoWeb and their view seems to be if you can&#039;t access it in the browser its not in the GeoWeb, in my mind this doesn&#039;t hold up. What about B2B? Are people really saying the GeoWeb is not about B2B data exchange. This got me thinking that there are two distinct communities in the GeoWeb. Taking a mathematical approach I think the GeoWeb can be defined as: GeoWeb = B2B + B2C (the C being customer or citizen). Refining that further, GML over SOAP is best methodology to orchestra business data exchange and KML over REST is the simplest method to get data to the citizen. So I came up with this formula GeoWeb = (GML+SOAP) + (KML+REST). Now I do agree with you that the REST and Bottom Up solves about 80% of the use cases (and that this is only going to grow) but there are scenarios where Top Down and rigours of SOAP are the only option. Aviation is a  great example of this, an complex data model, safety critical, cross business and country data exchange. Its clear that strong standard bodies like ICAO need to set international standards from the top down in order to create safe environment. It maybe that the Top Down approach gets less popular but it will never go away.

Ian</description>
		<content:encoded><![CDATA[<p>Sean,</p>
<p>I did a Top Down talk at GeoWeb and had the pleasure of defending SOAP in the SOAP vs REST vs PERR2PEER. Well the SOAP vrs REST was really quite fun at GeoWeb (it even got me my first appearance on Geek TV). Anyway, the Neogeographers were out in force defending REST at GeoWeb and their view seems to be if you can&#8217;t access it in the browser its not in the GeoWeb, in my mind this doesn&#8217;t hold up. What about B2B? Are people really saying the GeoWeb is not about B2B data exchange. This got me thinking that there are two distinct communities in the GeoWeb. Taking a mathematical approach I think the GeoWeb can be defined as: GeoWeb = B2B + B2C (the C being customer or citizen). Refining that further, GML over SOAP is best methodology to orchestra business data exchange and KML over REST is the simplest method to get data to the citizen. So I came up with this formula GeoWeb = (GML+SOAP) + (KML+REST). Now I do agree with you that the REST and Bottom Up solves about 80% of the use cases (and that this is only going to grow) but there are scenarios where Top Down and rigours of SOAP are the only option. Aviation is a  great example of this, an complex data model, safety critical, cross business and country data exchange. Its clear that strong standard bodies like ICAO need to set international standards from the top down in order to create safe environment. It maybe that the Top Down approach gets less popular but it will never go away.</p>
<p>Ian</p>
]]></content:encoded>
	</item>
</channel>
</rss>

