<p>Hi Jo,</p>
<div>Thank you for giving feedback, especially also to INSPIRE: Delicious reading. </div>
<div> </div>
<div>These are some of my insights so far "towards a minimal metadata information model" - just to backup your "Reading the INSPIRE Metadata Draft":</div>
<div>* Attributes in general: cardinality? consider embedding URL.<br>* How to deal with data set, supersets and series?</div>
<div>* dc:subject: Prefer open taxonomies over hierarchical and/or fixed keyword lists.<br>* dc:relation: What to put into this important attribute? which relationships are allowed?<br>* dc:coverage and spatial specializations of it: how to encode extent and crs?
<br>* dc:identifier: Any policies? Is it an URN? I'm tending to say it points to metadata (not data access points).</div>
<div> </div>
<div>I thought about which of these attributes are essential metadata as part of any geodata and made a comparison between ArcCatalog, GeoMedia and OGRINFO (on Shapefiles). That's what you can expect to be extracted automatically from data resources:
</div>
<p>* dc:title........ <= File name and path <br>* dc:date/modified <= Modification date<br>* dc:description.. <= Layer names, feature count, source system (as concatenated strings)<br>* dc:coverage......<= Extent (bbox) and CRS
<br>* dc:type......... <= vector/raster (from Geometry types)</p>
<div>I think there is a potential to include data set language and to insist on modification date and CRS especially in databases. </div>
<div> </div>
<div>WxS/OxS getcapabilities (and FGDC inside ArcCatalog) go beyond these attribute values and include information not contained in the data resources like contact addresses. </div>
<div> </div>
<div>To me the question arises, if these attributes (contact, dc:publisher, etc.) are maintained best near the local data resource too or better in a webapplication? My current idea is to sync (one way) the metadata coming from data sets under the control of a webbased metadata editor.
<br> </div>
<div>-- Stefan<br><br> </div>
<div><span class="gmail_quote">2007/3/15, Jo Walsh <<a href="mailto:jo@frot.org">jo@frot.org</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">dear all at geodatacommons,<br><br>I come in peace from the OSGeo Geodata Committee. Collectively there<br>
has been some hard thinking about geospatial metadata, with a lot in<br>common with the position held in your MD whitepaper. We've also been<br>coordinating a FOSS community response to the draft profile for<br>metadata in Europe. It's more of a meta-profile, a very different beast
<br>from the new North American Profile guidelines based on ISO19115.<br><a href="http://wiki.osgeo.org/index.php/Reading_the_INSPIRE_Metadata_Draft">http://wiki.osgeo.org/index.php/Reading_the_INSPIRE_Metadata_Draft</a><br>
<br>If you read that page, there is a mention of wanting to connect with<br>the geodatacommons group on a response to the NAP Profile draft.<br>I sat down and read it, realised there is no way of modifying or<br>critiquing it without critiquing the whole ISO19115 model, and wrote
<br>this discussion draft: <a href="http://frot.org/terradue/minimal_metadata.html">http://frot.org/terradue/minimal_metadata.html</a><br><br>On the one hand I am starting to hear real world success stories from<br>people working, without other options, in an ebXML framework to carry
<br>metadata about OGC standard web services for geographic data around;<br>on the other, GeoRSS/FOAF/Dublin Core between them provide adequate<br>representation for a minimal model for 'non-expert' metadata to be
<br>published and collected. ISO19115 is falling between two stools, and I<br>fear that as it is currently framed it is going to have as little<br>utility to data producers and users, as the current FGDC core does.<br><br>
I want to know what I am overlooking, what I am taking for granted and<br>how the free and open source geospatial community could help out the<br>geodata/metadata user community by building simpler interfaces and<br>real use cases into cataloguing and search platforms...
<br><br>cheers, and best of luck,<br><br><br>jo<br>--<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>