<div>Carl,</div>
<div> </div>
<div>Thank you for the hints. I'm aware of most of theses documents except for the GML simple features profile (yet another one?). </div>
<div> </div>
<div>The background of these activities is that there is a growing malaise about how metadata is being approached by the specifications you mentioned. So, there grew up a felt need for a really simple metadata exchange protocol which is low barrier and lean to implement. See here
<a href="http://wiki.osgeo.org/index.php/Simple_Catalog_Interface">http://wiki.osgeo.org/index.php/Simple_Catalog_Interface</a> and below the reasons. These finally let me propose a harvesting protocol like OAI-PMH 2.0, together with a slightly specialized Dublin Core metadata model (still tbd).
<br> </div>
<div><span class="gmail_quote">2006/9/18, Carl Reed OGC Account <<a href="mailto:creed@opengeospatial.org">creed@opengeospatial.org</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div bgcolor="#ffffff">
<div>Stefan -</div>
<div> </div>
<div>I browsed the wiki sites mentioned in your email. A couple of questions/observations:</div>
<div> </div>
<div>1. I believe that WFS 1.1 supports both GML 2.1.2 and GML 3.1.1 (see outputFormat) and by restriction, the new GML simple features profile. The new GML app schema is only 61 pages long with 20 pages of examples.</div>
</div></div></blockquote>
<div> </div>
<div>Why do we need GML machinery just for the encoding of a bounding box? Dublin Core's dct:spatial or GeoRSS seem to be much more parsimounious. </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div bgcolor="#ffffff">
<div>2. I was wondering why OAI-PMH page compares OAI-PMH with WFS? WFS is not designed for harvesting or for being a Catalogue service. WFS is designed so that once a content resource has been discovered (and perhaps registered in a Catalogue/Registry) that source can then be queried and asked to return a set of features (as a GML payload).
</div></div></div></blockquote>
<div> </div>
<div>CAT/CSW is based on a distributed query architecture and there's redundant spec. (and therefore code) to WFS. Why another protocol when there is WFS? </div>
<div> </div>
<div>As explained in <a href="http://www.gis.hsr.ch/wiki/OAI-PMH">http://www.gis.hsr.ch/wiki/OAI-PMH</a> distributed query like in CAT/CSW means that search is at best limited to the slowest server and to a least denominator of implemented specs. That is because each server needs to implement exactly the same query functionality. OAI-PMH does harvesting and indexing before hand.
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div bgcolor="#ffffff">
<div>3. Was wondering if the new OGC Catalogue 2.0.1 19119/19115 Application Profile has been looked at.? Seems to me that there could be some real synergy between this Cat App Profile and OAI-PMH. <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://portal.opengeospatial.org/files/?artifact_id=8305" target="_blank">
https://portal.opengeospatial.org/files/?artifact_id=8305</a> . There are already quite a few implementations of this Application Profile.</div></div></div></blockquote>
<div> </div>
<div>You mentioned CSW implementations. To me it's like somebody who owns a truck saying "why don't all take trucks to move metadata around?" when bicycles would make the job. OAI-PMH is there since five years and even Google accepts it as alternative to Sitemaps.
</div></div>
<div> </div>
<div>
<div>From my experience, what you can expect at most from a data owner is nothing more than what's in Word/Visio (metadata) properties or what's mentioned in WMS GetCapabilities. So to me nothing more than Dublin Core is needed like the common returnable properties of Catalogue Services Specification
2.0.1, OGC 04-021r3, p.22 (as Josh mentioned) but extended by additional semantics which includes more URI for automation.</div>
<div> </div>
<div>I take ISO 19115, ISO 19119, ebRIM and all those forthcoming profiles as templates for the specification of information models internal to an organization. When talking about geodata discovery we are not talking about catalog services but search services on top of catalogs; see
<a href="http://www.gis.hsr.ch/wiki/OSGeodata_Discovery">http://www.gis.hsr.ch/wiki/OSGeodata_Discovery</a> and <a href="http://www.foss4g2006.org/contributionDisplay.py?contribId=234&sessionId=70&confId=1">http://www.foss4g2006.org/contributionDisplay.py?contribId=234&sessionId=70&confId=1
</a> .</div>
<div> </div>
<div><span class="sg"><font color="#000000">Stefan</font> </span></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div>
<div> </div></div>
<div>
<blockquote style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"></blockquote></div>
<div><span class="q">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><b>From:</b> <a title="sfkeller@gmail.com" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sfkeller@gmail.com" target="_blank">Stefan F. Keller</a> </div>
</span></div>
<div><span class="e" id="q_10dc2c9b1563945a_4">
<div style="FONT: 10pt arial"><b>To:</b> <a title="raj@rajsingh.org" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:raj@rajsingh.org" target="_blank">Raj Singh</a> </div>
<div style="FONT: 10pt arial"><b>Cc:</b> <a title="georss@lists.eogeo.org" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:georss@lists.eogeo.org" target="_blank">georss@lists.eogeo.org</a> </div>
<div style="FONT: 10pt arial"><b>Sent:</b> Tuesday, September 05, 2006 2:58 AM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re: [georss] Discovery of georss and other geographic information?</div>
<div><br> </div>
<div>Raj,</div>
<div> </div>
<div>I agree that encodings can differ as long there is a common understanding on the semantic level and as long 'best encoding practices' are fulfilled (what currently is the case in GeoRSS).</div>
<div> </div>
<div>But newly published encodings should consider established ones, which seems to not the case actually (in W3C draft?). I know that standardization is slow but programmers often don't care...</div>
<div> </div>
<div>But my initial question was not only targeted to adjust GeoRSS to be accepted as a Microformat. What I'm thinking about currently is (auto-)discovery of geodata and services as documented here <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.gis.hsr.ch/wiki/OSGeodata_Discovery" target="_blank">
http://www.gis.hsr.ch/wiki/OSGeodata_Discovery</a> .</div>
<div> </div>
<div>I'd like to discuss if GeoRSS icons are means to guide webcrawlers to xml-encoded content or if there is a need for a 'friend' attribute in a (yet to be re-defined ISO 19115) metadata as described in <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.openarchives.org/OAI/2.0/guidelines-static-repository.htm" target="_blank">
http://www.openarchives.org/OAI/2.0/guidelines-static-repository.htm</a> <br> </div>
<div>-- Stefan<br> </div>
<div><span class="gmail_quote">2006/9/4, Raj Singh <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:raj@rajsingh.org" target="_blank">raj@rajsingh.org</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If you have a hammmer, everything looks like a nail.<br><br>I say that because the hammer many people on this list have is information
<br>architecture. We try hard to make everything elegant in the information<br>model. I think interoperability occurs best at the programmer level, and<br>therefore we shouldn't try to hard to make all encodings of geography
<br>interoperable from an encoding standpoint. If it takes less time for<br>programmers to code with less elegant encodings, then that's the "right" way<br>to do it.<br><br>This is a long way to say that I agree that GeoRSS should stop with support
<br>for Atom and some other RSSes. If it's simpler to diverge from this encoding<br>to do microformats and/or XHTML, so be it.<br><br>My 2 cents,<br>Raj<br><br><br>On 8/30/06 10:38 AM, "Andrew Turner" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:georss@highearthorbit.com" target="_blank">
georss@highearthorbit.com</a>> wrote:<br><br>> Stefan F. Keller <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sfkeller@gmail.com" target="_blank">sfkeller@gmail.com</a>> wrote:<br>>>
<br>>> P.S. Still: Anyone who knows the status of GeoRSS (simple) as microformat? <br>>><br>><br>> What is the purpose of a GeoRSS microformat? Isn't Geo*RSS* targeted<br>> and meant for RSS/Atom? There already is a 'geo' and 'adr' Microformat
<br>> with widespread support. If you're just looking at adding line, <br>> polygon, etc. to a Microformat then expand on geo, but it doesn't seem<br>> worth it, or a good idea, to try and force GeoRSS into XHTML.
<br>><br>> There was a howto on possibilities of mixing RDF and GeoRSS: <br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.geospatialsemanticweb.com/2006/06/08/mixing-rdfa-with-georss" target="_blank">
http://www.geospatialsemanticweb.com/2006/06/08/mixing-rdfa-with-georss</a><br><br><br></blockquote></div><br></span></div>
<div>
<p>
<hr>
</p></div>
<div><span class="q">
<p></p>_______________________________________________<br>georss mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:georss@lists.eogeo.org" target="_blank">georss@lists.eogeo.org</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.eogeo.org/mailman/listinfo/georss" target="_blank">http://lists.eogeo.org/mailman/listinfo/georss</a><br></span></div>
<div>
<p></p>
<blockquote></blockquote></div></div></blockquote></div><br>