Simple Catalog Interface - Revision history

Neteler: /* Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.) */

2007-08-23T15:37:39Z

Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.)

Wiki-Sfkeller: /* Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.) */

2006-09-19T11:51:14Z

Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.)

Wiki-Sfkeller: /* Information model for metadata exchange */

2006-09-19T11:44:22Z

Information model for metadata exchange

Wiki-Sfkeller: /* Notes from Metadata + Catalog BOF at FOSS4G2006 */

2006-09-19T11:41:26Z

Notes from Metadata + Catalog BOF at FOSS4G2006

Wiki-Sfkeller: /* Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.) */

2006-09-19T11:39:08Z

Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.)

Wiki-Sfkeller: /* Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.) */

2006-09-19T11:38:10Z

Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.)

Wiki-Sfkeller: /* Metadata information model (proposal) */

2006-09-19T11:24:00Z

Metadata information model (proposal)

Wiki-Sfkeller: /* Metadata information model (proposal) */

2006-09-19T09:29:03Z

Metadata information model (proposal)

Wiki-Sfkeller: /* Metadata information model (proposal) */

2006-09-19T09:26:48Z

Metadata information model (proposal)

Wiki-Sfkeller: /* Metadata information model (proposal) */

2006-09-19T09:26:34Z

Metadata information model (proposal)

← Older revision		Revision as of 15:37, 23 August 2007
Line 125:		Line 125:

	An information model for exchange of geographical metadata like the following at [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Geodata_Metadata_Requirements] would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info]. --[[User:Sfkeller\|SFK]] 11:06, 19 September 2006 (CEST)		An information model for exchange of geographical metadata like the following at [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Geodata_Metadata_Requirements] would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info]. --[[User:Sfkeller\|SFK]] 11:06, 19 September 2006 (CEST)
		+
		+	[[Category:Public Geospatial Data Committee]]

@@ Line 122: / Line 122: @@
 ==  Notes from Metadata + Catalog BOF at FOSS4G2006 (ff.) ==
-Thank you, Jo, for the notes. I hope you are all safe back home from Switzerland! I uploaded my slides at [http://www.foss4g2006.org/contributionDisplay.py?contribId=234&sessionId=70&confId=1 FOSS4G2006]. I took again some time to define an minimal metadata information model regarding to a metadata exchange protocol. --[[User:Sfkeller|SFK]] 11:06, 19 September 2006 (CEST)
+Thank you, Jo, for the notes. I hope you are all safe back home from Switzerland! I uploaded my slides at [http://www.foss4g2006.org/contributionDisplay.py?contribId=234&sessionId=70&confId=1 FOSS4G2006]. I took again some time to define an minimal metadata information model regarding to a metadata exchange protocol.
-An information model for exchange of geographical metadata like the following would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info].
+An information model for exchange of geographical metadata like the following at [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Geodata_Metadata_Requirements] would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info]. --[[User:Sfkeller|SFK]] 11:06, 19 September 2006 (CEST)

← Older revision		Revision as of 11:44, 19 September 2006
Line 126:		Line 126:
	An information model for exchange of geographical metadata like the following would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info].		An information model for exchange of geographical metadata like the following would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info].

−	~~=== Information model for metadata exchange ===~~

−	~~Some design considerations:~~
−	* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed)
−	* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
−	* Dublin Core need refined semantics of some properties/attributes.
−	* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
−	* All properties/attributes have cardinality 1 except where really needed for automation!
−	* Take all information one can in an automated manner, e.g. from data set resource.
−
−	~~Table:~~
−	~~{\| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"~~
−	\|-
−	~~\| '''Attr. name''' \|\| '''Cardinality''' \|\| '''Attr. type''' \|\| '''Explanation''' \|\| Status~~
−	\|-
−	~~\|dc:identifier \|\| [1] \|\| string \|\| Unique id to identify a resource (URI); see UUID but also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH]! \|\| tbd.~~
−	\|-
−	~~\|dc:title \|\| [1] \|\| string \|\| Title of the resource. \|\| Ok~~
−	\|-
−	~~\|dc:description \|\| [1] \|\| string \|\| A description of the resource (why dct:abstract?) \|\| Ok~~
−	\|-
−	~~\|dc:subject \|\| [1] \|\| string \|\| Could be ISO 19115 classification or keyw., comma separated?? \|\| tbd.~~
−	\|-
−	~~\|dc:relation \|\| [unbounded] \|\| URI \|\| Reference to other data providers or to ‘friends’ as indicated [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm here]. \|\| tbd.~~
−	\|-
−	~~\|dct:type \|\| [1] \|\| string \|\| Type of original resource, like vector, raster, grid geodata. \|\| tbd.~~
−	\|-
−	~~\|dct:format \|\| [unbounded] \|\| URI \|\| enum of‘http, ftp, WMS, WFS’ (= Well known data access services), ‘Filter Service’ else ‘WSDL’. \|\| tbd.~~
−	\|-
−	~~\|dct:modified \|\| [1] \|\| date \|\| Date of last (published) change of resource. (Automated sync. from dataset) \|\| Ok~~
−	\|-
−	~~\|dct:spatial \|\| [1] \|\| dcmiBox:Box with CRS \|\| (Automated sync. from dataset) \|\| Ok?~~
−	\|-
−	~~\|dc:language \|\| [1] \|\| enum \|\| RFC 1766 (ISO 639, followed optionally by country ISO 3166) \|\| Ok~~
−	\|-
−	~~\|dc:source \|\| [1] \|\| URL (preferred) or string \|\| Lineage information about the resource \|\| Ok?~~
−	\|-
−	~~\|dc:rights \|\| [1] \|\| URL (preferred) or string \|\| License information about the resource \|\| Ok?~~
−	\|-
−	~~\|dc:publisher \|\| [1] \|\| structure (refinement of string) \|\| Civic Address or URI to point to (xAL/KML?) \|\| tbd.~~
−	\|}
−
−
−	~~Remarks:~~
−	* DC attributes/properties left as they are...: Audience; Contributor; Creator.
−	* All attributes/properties have cardinality 1 except dc:relation and dct:format.
−	* No additinal DC attributes/properties required; few them needed to be specialized (see dct:...); still some attributes/properties need some specialized recommended meaning (see tbd.).
−	* dct:modified and dct:spatial can be sync'ed from dataset.
−	* Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
−	* See for some general explanations about dc/dct: http://cicharvest.grainger.uiuc.edu/qualifieddc.asp
−	* Note that OAM-PMH puts a XML enveloppe around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
−	* Assume metadata (as opposite to geodata) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
−	* An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?

	=== Example ===		=== Example ===

← Older revision		Revision as of 11:41, 19 September 2006
Line 44:		Line 44:


−	stefan - ISO issues - need to describe services - being merged with ebRIM - ~~compulsory~~ core is 300 attributes - this is overkill for user+producer requirements	+	stefan - ISO issues - need to describe services - being merged with ebRIM - core is 300 attributes - this is overkill for user+producer requirements

	* has a vision of how to overcome the problem		* has a vision of how to overcome the problem

@@ Line 124: / Line 124: @@
 Thank you, Jo, for the notes. I hope you are all safe back home from Switzerland! I uploaded my slides at [http://www.foss4g2006.org/contributionDisplay.py?contribId=234&sessionId=70&confId=1 FOSS4G2006]. I took again some time to define an minimal metadata information model regarding to a metadata exchange protocol. --[[User:Sfkeller|SFK]] 11:06, 19 September 2006 (CEST)
-This information model for exchange of geographical metadata would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info].
+An information model for exchange of geographical metadata like the following would already by sufficient combined with [[OAI-PMH]]! There exist already [http://www.openarchives.org/tools/ tools, libs and validation sites], Google eats it like [http://www.google.com/webmasters/sitemaps Sitemaps] (DC only) and we very soon will have GIS related implementations, like Open Source [http://geonetwork-opensource.org/ GeoNetwork] as well as e.g. this [http://www.gis.hsr.ch/gmdb/oai_pmh_data_provider/ geometa-data provider] and a related search engine [http://geometa.info].
 === Information model for metadata exchange ===

@@ Line 175: / Line 175: @@
 * See for some general explanations about dc/dct: http://cicharvest.grainger.uiuc.edu/qualifieddc.asp
 * Note that OAM-PMH puts a XML enveloppe around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
-* Assume metadata (as opposite to geodata) is always free and open information.
+* Assume metadata (as opposite to geodata) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
 * An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?

@@ Line 127: / Line 127: @@
 Some design considerations:
 * Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
 * Dublin Core need refined semantics of some properties/attributes.

@@ Line 131: / Line 131: @@
 * Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
 * All properties/attributes have cardinality 1 except where really needed for automation!
-* Take all information one can in an automated manner, e.g. from data set.
+* Take all information one can in an automated manner, e.g. from data set resource.
 Table:

@@ Line 131: / Line 131: @@
 * Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
 * All properties/attributes have cardinality 1 except where really needed for automation!
-* Take all information one can in an automated manner, e.g. from geodata data sets.
+* Take all information one can in an automated manner, e.g. from data set.
 Table:
 {| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
 |-
-| '''Attr. name''' || '''Attr. type''' || '''Explanation''' || Status
+| '''Attr. name''' || '''Cardinality''' || '''Attr. type''' || '''Explanation''' || Status
 |-
-|dc:identifier[1]  || string  || Unique id to identify a resource (URI); see UUID but also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH]! || tbd.
+|dc:identifier  || [1] || string  || Unique id to identify a resource (URI); see UUID but also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH]! || tbd.
 |-
-|dc:title[1]       || string  || Title of the resource. || Ok
+|dc:title       || [1] || string  || Title of the resource. || Ok
 |-
-|dc:description[1] || string  || A description of the resource (why dct:abstract?) || Ok
+|dc:description || [1] || string  || A description of the resource (why dct:abstract?) || Ok
 |-
-|dc:subject[1]     || string  || Could be ISO 19115 classification or keyw., comma separated?? || tbd.
+|dc:subject     || [1] || string  || Could be ISO 19115 classification or keyw., comma separated?? || tbd.
 |-
-|dc:relation[unbounded] || URI || Reference to other data providers or to ‘friends’ as indicated [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm here]. || tbd.
+|dc:relation    || [unbounded] || URI || Reference to other data providers or to ‘friends’ as indicated [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm here]. || tbd.
 |-
-|dct:type[1]       || string   || Type of original resource, like vector, raster, grid geodata. || tbd.
+|dct:type       || [1] || string   || Type of original resource, like vector, raster, grid geodata. || tbd.
 |-
-|dct:format[unbounded] || URI || enum of‘http, ftp, WMS, WFS’ (= Well known data access services),  ‘Filter Service’ else ‘WSDL’. || tbd.
+|dct:format     || [unbounded] || URI || enum of‘http, ftp, WMS, WFS’ (= Well known data access services),  ‘Filter Service’ else ‘WSDL’. || tbd.
 |-
-|dct:modified[1]   || date    || Date of last (published) change of resource. (Automated sync. from dataset) || Ok
+|dct:modified   || [1] || date    || Date of last (published) change of resource. (Automated sync. from dataset) || Ok
 |-
-|dct:spatial[1]    || dcmiBox:Box with CRS ||  (Automated sync. from dataset)  || Ok?
+|dct:spatial    || [1] || dcmiBox:Box with CRS ||  (Automated sync. from dataset)  || Ok?
 |-
-|dc:language[1]    || enum    || RFC 1766 (ISO 639, followed optionally by country ISO 3166) || Ok
+|dc:language    || [1] || enum    || RFC 1766 (ISO 639, followed optionally by country ISO 3166) || Ok
 |-
-|dc:source[1]      || URL (preferred) or string || Lineage information about the resource || Ok?
+|dc:source      || [1] || URL (preferred) or string || Lineage information about the resource || Ok?
 |-
-|dc:rights[1]      || URL (preferred) or string || License information about the resource || Ok?
+|dc:rights      || [1] || URL (preferred) or string || License information about the resource || Ok?
 |-
-|dc:publisher[1]   || structure (refinement of string) || Civic Address or URI to point to (xAL/KML?)  || tbd.
+|dc:publisher   || [1] || structure (refinement of string) || Civic Address or URI to point to (xAL/KML?)  || tbd.
 |}
@@ Line 168: / Line 168: @@
 Remarks:
 * DC attributes/properties left as they are...: Audience; Contributor; Creator.
-* No additinal DC attributes/properties required; only two of them needed to be specialized (see dct:...); still some attributes/properties need some specialized recommended meaning (see tbd.).
+* All attributes/properties have cardinality 1 except dc:relation and dct:format.
 * dct:modified and dct:spatial can be sync'ed from dataset.
 * Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.