<div>Jody - Thanks for the enlightening answers. I like chicken-and-eggs: You have 'your' (Geo)Tools and some discovery services - say that's the chicken - and I can finally release my eggs, namely GMDB (not the music db!) as open source metadata editor and
<a href="http://geometa.info">geometa.info</a> as a discovery portal (nice term). AND we got OAI-PMH! :-O<br> </div>
<div><span class="gmail_quote">2006/9/26, Jody Garnett <<a href="mailto:jgarnett@refractions.net">jgarnett@refractions.net</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Stefan F. Keller wrote:<br>><br>> As you know, I am trying to reach consensus about a minimal<br>> information metadata model (to all: I'm still awaiting comments or
<br>> counter proposals to <a href="http://tinyurl.com/kfkyv">http://tinyurl.com/kfkyv</a>). So I like to give my<br>> 0.25 pennies to this open problem:<br>><br>Okay finally managed to read that page ... not seeing any obvious
<br>problems right now.</blockquote>
<div> </div>
<div>Fine; so I now finalized the model and put all field status on "Ok?" in order to ask for confirmation (or perdition...)</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">For dc:identifier we used the following convention:<br>- service:<br><a href="http://localhost:8080/geoserver/wfs?REQUEST=GetCapabilities+SERVICE=WFS+VERSION=1.0">
http://localhost:8080/geoserver/wfs?REQUEST=GetCapabilities+SERVICE=WFS+VERSION=1.0</a><br>- georesource:<br><a href="http://localhost:8080/geoserver/wfs?REQUEST=GetCapabilities+SERVICE=WFS+VERSION=1.0#my_roads">http://localhost:8080/geoserver/wfs?REQUEST=GetCapabilities+SERVICE=WFS+VERSION=1.0#my_roads
</a><br>- we also made use of "jdbc" as a URI to identify database resources ...<br>did not see database in your list?</blockquote>
<div> </div>
<div>Added database. But I don't see any (local) uniqueness behind the dc:identifier you mention?</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Do you want to consider multi lingual support on the human readable<br>fields at this time?</blockquote>
<div> </div>
<div>Ok; added encoding hints to the model for strings (for URI it should be clear).</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Looking into your question about "description" vs. "abstract"... (for<br>Service)<br>- abstract - abstract from WFS capabilities
<br>- description - quick human readable string</blockquote>
<div> </div>
<div>Confuses me: Why don't you say that the abstract text out of WFS capabilities goes into dc:description?</div><br>-- Stefan</div>