<?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: The problem with OGC support ..</title>
	<atom:link href="http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/</link>
	<description>Not another GIS blog</description>
	<lastBuildDate>Wed, 02 Jun 2010 04:13:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Geospatial &#187; Blog Archive &#187; Where art thou WCS clients?</title>
		<link>http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/comment-page-1/#comment-21755</link>
		<dc:creator>Geospatial &#187; Blog Archive &#187; Where art thou WCS clients?</dc:creator>
		<pubDate>Mon, 28 Jan 2008 15:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/09/07/the-problem-with-ogc-support/#comment-21755</guid>
		<description>[...] guess this kinda gets back to my previous rants on this issue. We’ve got Deegree, Geoserver, Mapserver and quite a few other notable suppliers [...]</description>
		<content:encoded><![CDATA[<p>[...] guess this kinda gets back to my previous rants on this issue. We’ve got Deegree, Geoserver, Mapserver and quite a few other notable suppliers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where art thou WCS clients? at Chris&#8217; GISmo&#8217;s</title>
		<link>http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/comment-page-1/#comment-21266</link>
		<dc:creator>Where art thou WCS clients? at Chris&#8217; GISmo&#8217;s</dc:creator>
		<pubDate>Sun, 30 Dec 2007 14:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/09/07/the-problem-with-ogc-support/#comment-21266</guid>
		<description>[...] guess this kinda gets back to my previous rants on this issue. We&#8217;ve got Deegree, Geoserver, Mapserver and quite a few other notable [...]</description>
		<content:encoded><![CDATA[<p>[...] guess this kinda gets back to my previous rants on this issue. We&#8217;ve got Deegree, Geoserver, Mapserver and quite a few other notable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taking it to &#8220;the man&#8221; at Chris&#8217; GISmo&#8217;s</title>
		<link>http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/comment-page-1/#comment-14913</link>
		<dc:creator>Taking it to &#8220;the man&#8221; at Chris&#8217; GISmo&#8217;s</dc:creator>
		<pubDate>Sat, 07 Apr 2007 14:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/09/07/the-problem-with-ogc-support/#comment-14913</guid>
		<description>[...] Paul has graciously asked people to send him some queries to raise before the OGC technical meeting in Ottawa. In somewhat of an irony, it has been exactly 7 months to the day that my rant on client support was first posted. [...]</description>
		<content:encoded><![CDATA[<p>[...] Paul has graciously asked people to send him some queries to raise before the OGC technical meeting in Ottawa. In somewhat of an irony, it has been exactly 7 months to the day that my rant on client support was first posted. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Perry</title>
		<link>http://blog.webmapper.com.au/2006/09/07/the-problem-with-ogc-support/comment-page-1/#comment-1637</link>
		<dc:creator>Matt Perry</dc:creator>
		<pubDate>Thu, 07 Sep 2006 16:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/09/07/the-problem-with-ogc-support/#comment-1637</guid>
		<description>Chris,

 This is a great set of best practices for w*s clients. 

Three more for wms:

- Ability to use your own styled layer descriptor (bonus points for implementing an sld editor using the existing styling/classification mechanism)

- Adding vendor specific parameters to the request

- Access to the layer abstracts ... the title and name of the layer are often not enough to really assess the content.

Thanks for a great article. It&#039;ll get lots of developers thinking.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p> This is a great set of best practices for w*s clients. </p>
<p>Three more for wms:</p>
<p>- Ability to use your own styled layer descriptor (bonus points for implementing an sld editor using the existing styling/classification mechanism)</p>
<p>- Adding vendor specific parameters to the request</p>
<p>- Access to the layer abstracts &#8230; the title and name of the layer are often not enough to really assess the content.</p>
<p>Thanks for a great article. It&#8217;ll get lots of developers thinking.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
