OSGeodata: Unterschied zwischen den Versionen
Aus Geoinformation HSR
Stefan (Diskussion | Beiträge) (→Overview) |
Stefan (Diskussion | Beiträge) |
||
Zeile 10: | Zeile 10: | ||
'''... for the [[OSGeodata Discovery| discovery of geodata]]''' . | '''... for the [[OSGeodata Discovery| discovery of geodata]]''' . | ||
− | For documentation an internal geodata management model is needed. | + | For '''documentation''' an internal geodata management model is needed. |
− | + | ||
− | + | Remarks: [[Geo-Metadata| Metadata]] is just data about data, so nothing special regarding modeling and encoding. [[Geo-Metadata| Metadata]] according to metadata exchange model should be strictly free (LGPL?). | |
+ | |||
+ | === Pleadings === | ||
* ''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) | * ''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) | ||
* [http://www.digitalearth.com.au/2006/06/23/lightweight-web-resource-catalogue/ Blog 1] - "Leight Weight Web Resource Catalogue" | * [http://www.digitalearth.com.au/2006/06/23/lightweight-web-resource-catalogue/ Blog 1] - "Leight Weight Web Resource Catalogue" | ||
Zeile 18: | Zeile 20: | ||
* [http://www.kralidis.ca/blog/2006/08/04/geospatial-catalog-development-brewing/ Blog 3]. | * [http://www.kralidis.ca/blog/2006/08/04/geospatial-catalog-development-brewing/ Blog 3]. | ||
* [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."). | * [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."). | ||
+ | |||
+ | === Building blocks for geometadata management === | ||
+ | Building blocks are: | ||
+ | # A geometadata management model ( e.g. internal to telascience) | ||
+ | # Tools to manage the geo-metadata | ||
+ | # A [[OSGeodata metadata exchange model| geometadata exchange model]] | ||
+ | # An encoding of the geometadata exchange model (probably XML) | ||
+ | # [[OSGeodata metadata exchange protocol| Geometadata exchange protocols]] (see chapter Discovery mechanisms and protocols) | ||
== Weblinks == | == Weblinks == |
Version vom 28. August 2006, 07:12 Uhr
Inhaltsverzeichnis
Overview
These are experimental pages originated from OSGeodata Mailing List on OSGeo.org.
Let's finally unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!
Therefore we need a
- geographic metadata exchange model as well as a
- geographic metadata exchange protocol (catalog service).
... for the discovery of geodata .
For documentation an internal geodata management model is needed.
Remarks: Metadata is just data about data, so nothing special regarding modeling and encoding. Metadata according to metadata exchange model should be strictly free (LGPL?).
Pleadings
- 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.
- 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.").
Building blocks for geometadata management
Building blocks are:
- A geometadata management model ( e.g. internal to telascience)
- Tools to manage the geo-metadata
- A geometadata exchange model
- An encoding of the geometadata exchange model (probably XML)
- Geometadata exchange protocols (see chapter Discovery mechanisms and protocols)
Weblinks
Information:
- Wiki at osgeo.org for requirements
- Geodata mailing list at osgeo.org for discussions