<?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: How Much Metadata is Enough: Is there a GIS &#8211; Neogeography Middle Ground?</title>
	<atom:link href="http://blog.geoiq.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.geoiq.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/</link>
	<description>News and updates from GeoIQ</description>
	<lastBuildDate>Sat, 05 May 2012 23:20:33 +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/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-130</link>
		<dc:creator>Sean Gorman</dc:creator>
		<pubDate>Thu, 21 Jun 2007 19:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-130</guid>
		<description>Good suggestions we will have to check them out. A formal structure that would allow us to link to traditional Metadata would be great. Hopefully we will get some more feedback and comments. It will be interesting to see if geoweb Metadata standards come out of the standards bodies or out of the community as with KML and GeoRSS.</description>
		<content:encoded><![CDATA[<p>Good suggestions we will have to check them out. A formal structure that would allow us to link to traditional Metadata would be great. Hopefully we will get some more feedback and comments. It will be interesting to see if geoweb Metadata standards come out of the standards bodies or out of the community as with KML and GeoRSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Thorp</title>
		<link>http://blog.geoiq.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-129</link>
		<dc:creator>Bill Thorp</dc:creator>
		<pubDate>Thu, 21 Jun 2007 15:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-129</guid>
		<description>Wow.  Where are all the other comments?

Virtually no one wants the public to be creating ISO or FGDC metadata.
On the other hand, we&#039;d all like to think that if Joe FortisOne wants to build something useful, that we can have some interoperability guidance, rather than unqualified criticism.</description>
		<content:encoded><![CDATA[<p>Wow.  Where are all the other comments?</p>
<p>Virtually no one wants the public to be creating ISO or FGDC metadata.<br />
On the other hand, we&#8217;d all like to think that if Joe FortisOne wants to build something useful, that we can have some interoperability guidance, rather than unqualified criticism.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Thorp</title>
		<link>http://blog.geoiq.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-128</link>
		<dc:creator>Bill Thorp</dc:creator>
		<pubDate>Wed, 20 Jun 2007 22:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/2007/06/20/how-much-metadata-is-enough-is-there-a-gis-neogeography-middle-ground/#comment-128</guid>
		<description>OSGeo came up with a DCLite4G spec (http://tinyurl.com/kfkyv).  Its hardly a standard, but its a decent fit for neo-geo.  You could use the dc:source tag to link to some beefy metadata, if that info existed.

Another option is the OGC_CORE minimum feilds for an OGC  Catalog Service.  Core queriables: subject, title, abstract, anytest, format, identifier, modified, type, boundingbox, crs, and association (target source relation).  Core returnables: title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage, and rights.  See section 6.3 of the spec:(http://portal.opengeospatial.org/files/?artifact_id=20555).

This section option might get you further into &quot;don&#039;t blame me&quot; territory, especially, again, if you allow linking to some beefy metadata record using &quot;source.&quot;</description>
		<content:encoded><![CDATA[<p>OSGeo came up with a DCLite4G spec (<a href="http://tinyurl.com/kfkyv" rel="nofollow">http://tinyurl.com/kfkyv</a>).  Its hardly a standard, but its a decent fit for neo-geo.  You could use the dc:source tag to link to some beefy metadata, if that info existed.</p>
<p>Another option is the OGC_CORE minimum feilds for an OGC  Catalog Service.  Core queriables: subject, title, abstract, anytest, format, identifier, modified, type, boundingbox, crs, and association (target source relation).  Core returnables: title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage, and rights.  See section 6.3 of the spec:(http://portal.opengeospatial.org/files/?artifact_id=20555).</p>
<p>This section option might get you further into &#8220;don&#8217;t blame me&#8221; territory, especially, again, if you allow linking to some beefy metadata record using &#8220;source.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

