<div>Norman, good proposal. </div>
<div> </div>
<div>Use cases area always good for bringing users and programmers as well as implementors and implementors together. Because I have the impression that no so many users are following these threads I would extend your proposal: I think that visions would also help to focus and to get a common understanding. It's now about half a year ago when I 'blogged' down my metadata network visions: see
<a href="http://gis.hsr.ch/wiki/OSGeodata_Discovery">http://gis.hsr.ch/wiki/OSGeodata_Discovery</a>.<br> </div>
<div>
<div>Jody also had an excellent idea: One could organize a 'metadata exchange code sprint' at FOSS4G'07 and hack down some software components (e.g. for uDig, GeoNetwork etc.)! Still others (like me) can't wait another couple of months... :->
</div><br>-- Stefan</div>
<div> </div>
<div> </div>
<div><span class="gmail_quote">2007/3/16, Norman Barker <<a href="mailto:norman.barker@gmail.com">norman.barker@gmail.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>having been trying to do this catalog thing for a while now (both the<br>minimal metadata and the ebRIM model) and I am slightly concerned that
<br>as a geodata group we don't know what we want, and perhaps there is a<br>certain amount of Java/OGC/ISO/Python/REST/SOAP/OAI bashing (pick your<br>camp depending on your persuasion!)<br><br>We have requirements for minimal metadata (dclite4g) which is great,
<br>we also have the concept that we want this catalog to be 'out there' -<br>also great. I like the general discussion as well.<br><br>However I don't see use cases, the kind of thing I am looking for is<br>
(simplistic example)<br><br>I want to use a catalog and I want to do the following<br><br>1) search on bbox<br>2) search on keywords<br>3) discover services offering data matching (1) and (2)<br><br>I think if we could come up with evaluation criteria / use cases we
<br>could get past some of the implementation specifics when it comes to<br>saying if something is right or not or whether it matches needs (since<br>'right or not' is a bit stark). If these could go on the wiki then
<br>great; I am a developer I shouldn't be providing use cases, these<br>should come from users. If I provide a use case then it is going to<br>centred around my expertise bias. I am sitting here now thinking my<br>
catalog is kind of cool, geonetwork is also kind of cool, however<br>others (rightly) are saying I don't think so, and there is no use case<br>benchmark.<br><br>Just my thoughts, flame me if you want, it's gmail :-)
<br><br>Norman<br>_______________________________________________<br>Geodata mailing list<br><a href="mailto:Geodata@lists.osgeo.org">Geodata@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/geodata">
http://lists.osgeo.org/mailman/listinfo/geodata</a><br></blockquote></div><br>