<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">Jo wrote:</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> This is an implementation of</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> <a href="http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements">http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements
</a></font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> which in turn is an attempt to extract the 'simplest useful thing'</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> from FGDC metadata, and bolt on some Dublin Core properties and also</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> expressions about OGC web services interfaces. This was put together</font></p>
<div class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> over a couple of longish discussions at IRC meetings in April/May. It </font><font size="2"><font face="Courier New">[...]</font>
</font></div>
<div class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font size="2"><font face="Courier New"></font></font> </div>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">To my knowledge FGDC strongly influenced - if not formed the base of - ISO19115. So on one hand, this means that chances are high that there are similarities to ISO19115, but I think, that on the other hand FGDC (as a namespace) would be not so accepted in
Europe. </font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> Why not OAI-PMH, i would say 1/ because none of us really knew it.</font>
</font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> <a href="http://www.oaforum.org/tutorial/english/page3.htm">http://www.oaforum.org/tutorial/english/page3.htm</a> outlines a</font>
</p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> nice simple worldview - 6 http based requests -</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2"> </font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">OAI-PMH with the basic 6 functions needs at least being extended by the 'output content model' (
i.e. the metadata schema).</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> But we'll *definitely* need to extend beyond this</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> - I want to be able to send spatial and temporal bounding boxes to a</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> <span style="mso-spacerun: yes"> </span>RESTful interfaces and get back data sets constrained by this.
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">Temporal constraints are included in OAI-PMH. Spatial constraints have also been suggested by Tom in the following answer and I accept that. But keep in mind: To me the difference between an online-query and a harvesting protocol is, that the latter only needs to gather a complete and perhaps a differential set of records (that's what OAI-PMH obviously offers). This does not exclude that the OAI-PMH (search) service providers can offer spatial constraints.
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> I guess being able to say 'OAI-PMH compatible' is a win?</font></font></span>
</p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">Yes, definitively: Google accepts it and work seems to be done in spec. and implementations since years in this information retrieval area.
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> I've always thought of this as a data-driven not "metadata-driven"
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font size="2"><font face="Courier New"><span lang="EN-GB" style="mso-ansi-language: EN-GB">> activity - thus 'ListMetadataFormats' doesn't make tha</span>t much sense to
</font></font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font size="2"><font face="Courier New">> me. Model first, format is syntactic sugar almost? ;)</font></font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span style="COLOR: black"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">Yeah! I have waited for years to hear such words in ISO/OGC standardization... (keep in mind that every second content model of ISO/OGC is still crafted by hand in XML schema instead of being model-driven).
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">I agree that it should be data-driven, but look closer: 'ListMetadataFormats' is used with similar semantics like GetCapabilities in the sense that the OAI-PMH data provider is requested to respond the metadata schemas it knows. I'd expect that in our context it responds that it knows Dublin Core ('oai_dc' as mandatory default) as well some geospatial metadata schemas, where one is the one we have to sketch here (I'd say Dublin Core plus...).
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> I guess I'd envisioned results coming out mainly in RSS1.0 (RDF)</font>
</font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font size="2"><font face="Courier New"><span lang="EN-GB" style="mso-ansi-language: EN-GB">> with GeoRSS expressions - cf <a href="http://georss.org/">http://georss.org/
</a><span style="mso-spacerun: yes"> </span>- and a</span>lso optionally</font></font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> in that lovely tab-delimited FGDC format :) - and FGDC xml if people</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> really want that too.</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2"> </font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">GeoRSS would be nice for syndicating new entries (as Tom suggested) but not for exchanging 'output content model'. BTW: There exists another spec. proposal for exchanging search engine results, which is RSS like, called OpenSearch.
</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">For votes against FGDC (as a namespace or encoding) see above. </font></font>
</span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">[...]</font></font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">> > > My motivation is to avoid the CSW-ebRim profile</font></font>
</span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> </font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> Definitely, it sounds painful.</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> ></font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> > Regarding the protocol I see three choices: 1. CSW 2, 2. WFS and 3.</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> > OAI-PMH.</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> </font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> +1 on using the very basic OAI-PMH 6 functions, seeing if they're all</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> useful to us, and extending them, and then arguing about it via the</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2">> medium of bots.</font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><font face="Courier New" size="2"> </font></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">OAI-PMH using the basic 6 functions is exactly what I meant. </font>
</font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font face="Courier New" size="2"> </font></span></p>
<p class="MsoPlainText" style="MARGIN: 0cm 0cm 0pt"><span lang="EN-GB" style="COLOR: black; mso-ansi-language: EN-GB"><font size="2"><font face="Courier New">-- Stefan</font></font></span></p>