OSGeodata: Unterschied zwischen den Versionen

Aus Geoinformation HSR
Wechseln zu: Navigation, Suche
K (Goal for a lean and mean geographic metadata protocol)
(Weblinks)
 
(137 dazwischenliegende Versionen von 4 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
Experimental pages for OSGeodata Mailing List on [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata&by=date&paged=false OSGeo.org].
+
== Overview ==
  
== Goal for a lean and mean geographic metadata protocol ==
+
These are experimental pages ([[OSGeodata Discovery|1]],[[OSGeodata metadata exchange model|2]],[[OSGeodata metadata exchange protocol|3]],[[OAI-PMH|4]]) originated from OSGeodata Mailing List on [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata&by=date&paged=false OSGeo.org].
  
Citation from Jo Walsh: "Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata...".
+
Let's unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!
  
Appropriate name sought:
+
Allow to '''[[OSGeodata Discovery| discover geodata]]'''! Let's make metadata 'sexy' again.
* geographic metadata protocol
 
* geographic metadata harvesting protocol
 
* ?
 
  
See also: [[OSGeodataMetadataModel]].
+
For the '''[[OSGeodata Discovery| discovery of geodata]]''' we need a
 +
* '''[[OSGeodataMetadataModel| Geographic metadata exchange model]]''' as well as a
 +
* '''[[OSGeodataMetadataProtocol| Geographic metadata exchange protocol]]''' (catalog service).  
  
== Comparison between WFS and OAI-PMH ==
+
For '''documentation''' an internal geodata management model is needed. For the '''metadata metadata exchange model''' a proposal was made called  '''[http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Dublin Core lite for Geo (DClite4G)]'''.
  
Relative (biased?) comparison:
+
Remarks: '''Metadata''' is just data about data. There is nothing special regarding its modeling and encoding. Metadata according to metadata exchange model should be strictly free (LGPL?).
* OAI-PMH is a set of simple harvesting protocols based on Dublin Core (since 1995) whereas WFS allows a client to retrieve geospatial data encoded in GML (since 2000).
 
* WFS though originated in GIS could cover a smaller community than OAI-PMH which today probably has a larger user base and is supported even by Google.
 
* Both have in common that they can be made (WFS) or are (OAI-PMH) RESTful and both can be profiled to respond an 'output content model' - which has yet to be defined (see [[OSGeodataMetadataModel]]).
 
* WFS needs to be profiled (spec. size is > 140 p.) whereas OAI-PMH needs probably to be extended (spec. size is < 50 p.) - so WFS seems more complex and more costly to implement.
 
  
=== WFS ===
+
== Pleadings for metadata (models) and adequate protocols ==
* WFS is short for 'Web Feature Service'.  
+
* ''Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata...''. (Citation from Jo Walsh)
* Spec. size: About 100 pages plus at least refernce to Filter spec. of about 40 pages, plus ??.
+
* [http://www.digitalearth.com.au/2006/06/23/lightweight-web-resource-catalogue/ Blog 1] - "Leight Weight Web Resource Catalogue"
* Background: A de-facto standard in GIS world owned by OGC
+
* [http://geotips.blogspot.com/2006/02/more-simple-web-services-catalogues.html Blog 2] - More Simple Web Services Catalogues...", and  
* Request operations (Basic WFS, read only WFS):
+
* [http://www.kralidis.ca/blog/2006/08/04/geospatial-catalog-development-brewing/ Blog 3] - geospatial-catalog-development-brewing.
** ''GetCapabilities'' - describes service capabilities;  
+
* [http://home.badc.rl.ac.uk/lawrence/blog/all Bryan's Blog]: "To extend or not to extend ..." ("In practice, we can exchange any derivative of the ISO19139 profiles using OAI and store them in xml databases.").
** ''DescribeFeatureType'' - descibes structure of a feature type
+
* Paper "Are Geospatial Catalogues Reaching their Goals?" from [http://www.agile2006.hu/papers/Larson_Siliceo_etal.pdf Larson et al.].
** ''GetFeature'' - retrieves feature instances
 
* Query:
 
** Standard query includes spatial constraints (but no temporal?)
 
* Peculiarities:
 
** Knows version negotiation (which isn't implemented yet...)
 
** Uses URN as unique identifier
 
* Availability and outreach of services, tools and (open source) software:
 
** Open source software see [http://www.freegis.org freegis.org]
 
* Expected changes to spec. (profile or extension):
 
** Profile to KVP binding
 
** Profile Filter to Boolean and Wildcard matches as well as 'within'
 
** ...
 
  
=== OAI-PMH ===
+
== Building blocks for metadata management ==
* OAI is short for [http://en.wikipedia.org/wiki/Open_Archives_Initiative 'Open Archives Initiative'], PMH is short for 'Protocol for Metadata Harvesting'.  
+
Building blocks are:
* Spec. size: < 50 pages(!) plus??
+
# A geometadata '''management model''' (e.g. internal to each organisation)
* Background: Was initiated by libraries, universities, museums and galleries to 'open access' (OA) free online availability of digital content.
+
# '''Tools''' to manage the geometadata
* Request operations:
+
# A geometadata '''[[OSGeodata metadata exchange model| exchange model]]'''
** ''Identify'' - describe an archive (similar to WFS' GetCapabilities)
+
# An '''encoding''' of the geometadata exchange model (probably XML)
** ''ListMetadataFormats'' - retrieve available metadata formats from archive
+
# Geometadata '''[[OSGeodata metadata exchange protocol| exchange protocols]]''' (like [[OAI-PMH]], see [[OSGeodata_Discovery]])
** ''ListSets'' - retrieve set structure of a repository
 
** ''ListIdentifiers'' - abbreviated form of ListRecords, retrieving only headers
 
** ''ListRecords'' - harvest records from a repository (similar to WFS' GetFeature)
 
** ''GetRecord'' - retrieve individual metadata record from a repository (also similar to WFS' GetFeature)
 
* Query:
 
** Standard query includes temporal constraints (but no spatial).
 
* Peculiarities:
 
** Uses identifier mechanism (numbers) from digital archives.
 
** Has no version negotiation
 
* Availability and outreach of services, tools and (open source) software:
 
** Open source software see [http://www.openarchives.org/tools/tools.html OAI-PMH tools]
 
** Gateways available from publishing files to others 
 
** Google reads it as a Sitemaps file ([http://www.google.com/support/webmasters/bin/answer.py?answer=34655 how to submit]) and Internet Archive uses it among others.
 
* Expected changes to spec. (profile or extension):
 
** special treatment of ID's?
 
** Need to be extended if spatial constraints are needed here
 
** Add version negotiation?
 
** ...?
 
  
 
== Weblinks ==
 
== Weblinks ==
* OGC's CSW 2.0
+
 
* OGC's WFS
+
Information:
* [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] - Open Archives Initiative Protocol for Metadata Harvesting 2.0
+
* [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Discovery Wiki at osgeo.org] for requirements
 +
* [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata Geodata mailing list at osgeo.org] for discussions
 +
 
 +
 
 +
<!-- Kategorien und ev. Koordinaten -->
 +
[[Kategorie: Geodaten]] [[Kategorie: Metadaten]] [[Kategorie: English]]

Aktuelle Version vom 29. Oktober 2006, 12:15 Uhr

Overview

These are experimental pages (1,2,3,4) originated from OSGeodata Mailing List on OSGeo.org.

Let's unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!

Allow to discover geodata! Let's make metadata 'sexy' again.

For the discovery of geodata we need a

For documentation an internal geodata management model is needed. For the metadata metadata exchange model a proposal was made called Dublin Core lite for Geo (DClite4G).

Remarks: Metadata is just data about data. There is nothing special regarding its modeling and encoding. Metadata according to metadata exchange model should be strictly free (LGPL?).

Pleadings for metadata (models) and adequate protocols

  • Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata.... (Citation from Jo Walsh)
  • Blog 1 - "Leight Weight Web Resource Catalogue"
  • Blog 2 - More Simple Web Services Catalogues...", and
  • Blog 3 - geospatial-catalog-development-brewing.
  • Bryan's Blog: "To extend or not to extend ..." ("In practice, we can exchange any derivative of the ISO19139 profiles using OAI and store them in xml databases.").
  • Paper "Are Geospatial Catalogues Reaching their Goals?" from Larson et al..

Building blocks for metadata management

Building blocks are:

  1. A geometadata management model (e.g. internal to each organisation)
  2. Tools to manage the geometadata
  3. A geometadata exchange model
  4. An encoding of the geometadata exchange model (probably XML)
  5. Geometadata exchange protocols (like OAI-PMH, see OSGeodata_Discovery)

Weblinks

Information: