OSGeodata metadata exchange model - Versionsgeschichte

Stefan: /* Status of geographic metadata models */

2009-06-16T06:08:55Z

Status of geographic metadata models

← Nächstältere Version		Version vom 16. Juni 2009, 06:08 Uhr
Zeile 18:		Zeile 18:

	* ISO 19115/19 The model behind many current GIS initiatives (even core too complex and lacking service descriptions)		* ISO 19115/19 The model behind many current GIS initiatives (even core too complex and lacking service descriptions)
	* ~~cws~~:record behind OGC's CSW (CSW was also labeled 'painfull', yet another encoding)		* csw:record behind OGC's CSW (CSW was also labeled 'painfull', yet another encoding)
	* unqualified default Dublin Core - too simple, no own proper encoding		* unqualified default Dublin Core - too simple, no own proper encoding
	* [http://iesr.ac.uk/metadata/mappings/oaidcmap.html IESR's Extension to OAI-PMH Dublin Core] (see also [http://epub.mimas.ac.uk/papers/dlsr200603/iesr-dlsr200603_summary.html Introduction to the IESR: A Registry of Collections and Services], by Hill and Ann Apps, MIMAS, Univ. of Manchester, 2006).		* [http://iesr.ac.uk/metadata/mappings/oaidcmap.html IESR's Extension to OAI-PMH Dublin Core] (see also [http://epub.mimas.ac.uk/papers/dlsr200603/iesr-dlsr200603_summary.html Introduction to the IESR: A Registry of Collections and Services], by Hill and Ann Apps, MIMAS, Univ. of Manchester, 2006).

Stefan: /* Weblinks */

2006-10-29T10:14:33Z

Weblinks

← Nächstältere Version		Version vom 29. Oktober 2006, 10:14 Uhr
Zeile 65:		Zeile 65:


	[[Kategorie: English]]		[[Kategorie: English]] [[Kategorie: Metadaten]]

Geonick: /* Dublin Core and its interpretation in geographic metadata */

2006-09-26T17:53:26Z

Dublin Core and its interpretation in geographic metadata

← Nächstältere Version		Version vom 26. September 2006, 17:53 Uhr
Zeile 38:		Zeile 38:
	=== Dublin Core and its interpretation in geographic metadata ===		=== Dublin Core and its interpretation in geographic metadata ===

	~~Proposal~~ '''~~Dublin Core lite for Geo''' (DClite4G)~~ [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange ~~here at OSGeo~~].		There sis now a proposal out called '''[http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Dublin Core lite for Geo (DClite4G)]'''.

	This is the list of attributes of DClite4G which defines the minimal information model for metadata exchange, harvesting and discovery ( *) Manual input required from somewhere):		This is the list of attributes of DClite4G which defines the minimal information model for metadata exchange, harvesting and discovery ( *) Manual input required from somewhere):

Geonick: Attributes to be discussed in detail deleted

2006-09-26T05:14:09Z

Attributes to be discussed in detail deleted

← Nächstältere Version		Version vom 26. September 2006, 05:14 Uhr
Zeile 46:		Zeile 46:
	Other links:		Other links:
	* As a blueprint, here is a [http://iesr.ac.uk/metadata/mappings/oaidcmap.html OAI-PMH Dublin Core Mapping] (Version 2005-09-06) from Information Environment Service Registry (IESR).		* As a blueprint, here is a [http://iesr.ac.uk/metadata/mappings/oaidcmap.html OAI-PMH Dublin Core Mapping] (Version 2005-09-06) from Information Environment Service Registry (IESR).

	~~=== Attributes to be discussed in detail ===~~

	~~(Most are probably enums):~~

	* Relation (specialized): 'Relates to': Identifier of (other) data resource. Note that this may be hierarchical
	* Relation (specialized for data): 'See also': URL as hint to other metadata data resource (valid XML). Note this is an important feature for crawlers if there exists not (yet) a harvesting protocol.
	* Type (specialized): Protocol type: URL to WKS (WxS, WMS, WFS), WSDL, etc.
	* Identifier (specialized): URL (not URN as in DC)
	* Coverage (specialized): Coverage.box and Coverage.name
	* Subject (specialized for data): c.f. above.
	* Format (specialized for data): Not clear in unqualified DC how to point to original resource
	* Creator and Publisher (specialized): structured adress including webpage and/or mail and phone
	* Resource accepted (new for processing services): In case of a service: Information about the kind of data (e.g. schemas) it can process - unless there exists a GetCapabilities for every kind of service. Note that metadata about filter services are stand alone records.

	=== Example ===		=== Example ===
Zeile 68:		Zeile 54:

	Encodings:		Encodings:
	* Use ~~GeoRSS (simple)~~?		* Use RDF or qualified DC or?

	Notes:		Notes:

Geonick: /* Dublin Core and its interpretation in geographic metadata */

2006-09-26T05:12:50Z

Dublin Core and its interpretation in geographic metadata

← Nächstältere Version		Version vom 26. September 2006, 05:12 Uhr
Zeile 38:		Zeile 38:
	=== Dublin Core and its interpretation in geographic metadata ===		=== Dublin Core and its interpretation in geographic metadata ===

	~~As a blueprint, here is a~~ [http://~~iesr~~.ac.uk/~~metadata~~/~~mappings/oaidcmap.html OAI-PMH Dublin Core Mapping~~] ~~(Version 2005-09-06) from Information Environment Service Registry (IESR)~~.		Proposal '''Dublin Core lite for Geo''' (DClite4G) [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].

	~~There~~ is ~~actually a proposal [http~~:~~//wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].~~		This is the list of attributes of DClite4G which defines the minimal information model for metadata exchange, harvesting and discovery ( *) Manual input required from somewhere):
			* dc:identifier, dc:title, dc:description, dc:type, dc:format, dct:spatial, dct:modified, dc:subject, cld:isAccessedVia, dcterms:hasPart, dc:source,
			* Remaining (optional) DC elements: dc:publisher, dc:language, dc:rights, dc:relation*,

	~~This is list of attributes of current entity which defines the minimal information model for metadata exchange, harvesting and discovery~~:		Other links:
	* ~~'Core'~~: ~~'''identifier, title, description, subject, relation, type, format, modified, spatial, language, source, rights, publisher, fees, scalehint, harvestinterval~~.~~'''~~		* As a blueprint, here is a [http://iesr.ac.uk/metadata/mappings/oaidcmap.html OAI-PMH Dublin Core Mapping] (Version 2005-09-06) from Information Environment Service Registry (IESR).
	* 'Core of Core~~' (* = manual input required): '''identifier, title, description, relation~~(s), type, format(s), modified, spatial, rights, publisher*.~~'''~~

	=== Attributes to be discussed in detail ===		=== Attributes to be discussed in detail ===

Geonick: /* Dublin Core and its interpretation in geographic metadata */

2006-09-21T04:46:11Z

Dublin Core and its interpretation in geographic metadata

← Nächstältere Version		Version vom 21. September 2006, 04:46 Uhr
Zeile 43:		Zeile 43:

	This is list of attributes of current entity which defines the minimal information model for metadata exchange, harvesting and discovery:		This is list of attributes of current entity which defines the minimal information model for metadata exchange, harvesting and discovery:
	* 'Core': identifier, title, description, subject, relation, type, format, modified, spatial, language, source, rights, publisher, fees, scalehint, harvestinterval.		* 'Core': '''identifier, title, description, subject, relation, type, format, modified, spatial, language, source, rights, publisher, fees, scalehint, harvestinterval.'''
	* 'Core of Core': identifier, title, description, relation(s), type, format(s), modified, spatial, rights, publisher. ~~( = manual input required).~~		* 'Core of Core' (* = manual input required): '''identifier, title, description, relation(s), type, format(s), modified, spatial, rights, publisher*.'''

	=== Attributes to be discussed in detail ===		=== Attributes to be discussed in detail ===

Geonick: /* Proposal of an information model to exchange spatial metadata */

2006-09-21T04:45:29Z

Proposal of an information model to exchange spatial metadata

← Nächstältere Version		Version vom 21. September 2006, 04:45 Uhr
Zeile 36:		Zeile 36:
	But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.		But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.

	~~There is a new proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].~~		=== Dublin Core and its interpretation in geographic metadata ===

	~~===~~ Dublin Core ~~and its interpretation in geographic metadata ===~~		As a blueprint, here is a [http://iesr.ac.uk/metadata/mappings/oaidcmap.html OAI-PMH Dublin Core Mapping] (Version 2005-09-06) from Information Environment Service Registry (IESR).

	~~This~~ is ~~the full list of attributes from DC together with its proposed semantic interpretation and~~/~~or enumeration list (needs probably an own XML namespace)~~. ~~If not indicated 'multivalued' all attributes are non-repeatable (i~~.e. ~~have cardinality 1 to 1):~~		There is actually a proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].

	* '''Relation''': URL (multivalued) - Reference to other metadata ~~records - also useful for map service types (WxS) pointing to data service types (= file~~, ~~database?)~~		This is list of attributes of current entity which defines the minimal information model for metadata exchange, harvesting and discovery:
	* '~~''Type''~~': ~~URL (preferred) or enum (multivalued) - Either 'WPS' (= processing/filter services) or Protocol~~ type ~~(for data services)~~, ~~e.g. 'file'~~, ~~Well known data access services: 'WxS' (WMS layer~~, ~~WFS feature set)~~, ~~'WSDL' (SOAP)~~. ~~'''IMPORTANT FOR SERVICE DISCOVERY'''~~		* 'Core': identifier, title, description, subject, relation, type, format, modified, spatial, language, source, rights, publisher, fees, scalehint, harvestinterval.
	* ''~~'Identifier''': string - Unique id to identify an metadata record (use a URI for dc~~:identifier).		* 'Core of Core': identifier, title, description, relation(s), type, format(s), modified, spatial, rights, publisher. ( = manual input required).
	* ~~'''Title''': string - Title~~
	* ~~'''Coverage.box''': - Rectangular box~~ (~~mandatory~~) ~~in WGS84 (e.g. encoded as georss:box)~~
	* ~~'''Coverage.name''': String - (optionally) a geographic name~~
	* '''Description''': string (multivalued) - Some free text
	* '''Subject''': enum - Classification from ISO 19115 as enum type ~~(original: The topic of the resource. Typically~~, ~~subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemas is encouraged.)~~
	* '''Language''': enum - ISO Code
	* '''Format''': enum (~~preferred~~) ~~or string - File type or name of originating source system~~
	* '''Source''': URL (preferred) or string - Lineage information
	* '''Date''': date - Publication date or date of last change of metadata record
	* '''Creator''': structure - Address (person or organization name, ~~e-mail) of data owner~~, ~~else of data capturer. (Note: OASIS has a standard called eXtensible Address Language (xAL) for civic/civil addresses and KML uses that to).~~
	* ~~'''Publisher''': structure - Address~~, ~~Distribution information (person or organization name, e-mail)~~
	* ~~'''Contributor''': structure - Address~~ (~~see publisher) Leave unused?~~
	* ~~'''Rights''': URL (preferred~~) ~~or string - License information about the data~~
	* '''Audience''': string - Not used or 'GIS' as a constant

	=== Attributes to be discussed in detail ===		=== Attributes to be discussed in detail ===

Geonick: /* Example */

2006-09-21T04:43:28Z

Example

@@ Zeile 76: / Zeile 76: @@
 === Example ===
-These are preliminary thoughts... There is actually a proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].
+See proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].
 === Toughts about encoding and links ===

Geonick: /* Proposal of an information model to exchange spatial metadata */

2006-09-19T11:36:56Z

Proposal of an information model to exchange spatial metadata

← Nächstältere Version		Version vom 19. September 2006, 11:36 Uhr
Zeile 36:		Zeile 36:
	But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.		But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.

	There is a proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].		There is a new proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].

	=== Dublin Core and its interpretation in geographic metadata ===		=== Dublin Core and its interpretation in geographic metadata ===

Geonick: /* Proposal of an information model to exchange spatial metadata */

2006-09-19T11:36:44Z

Proposal of an information model to exchange spatial metadata

← Nächstältere Version		Version vom 19. September 2006, 11:36 Uhr
Zeile 35:		Zeile 35:

	But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.		But there is also a need to describe services on its own, also called filter - finally as own metadata records: Normally you feed some data in and get data out. For these kinds of services it’s interesting to know what kind of data you can feed in and get back. Examples are format conversion or coordinate transformation services.

			There is a proposal [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange here at OSGeo].

	=== Dublin Core and its interpretation in geographic metadata ===		=== Dublin Core and its interpretation in geographic metadata ===