Difference between revisions of "DCLite4G"

From OSGeo
Jump to navigation Jump to search
Line 15: Line 15:
== TODO ==
== TODO ==
* extract more of the specifics from [[Geodata Metadata Requirements]]. (This has changed a lot from the original version in the history & current version which has data sets differentiated from data sources, which may be files or databases or services)
* extract more of the specifics from [[Geodata Metadata Requirements]]. (This has changed a lot from the original version in the history
* update docs on [[Geodata Metadata Model]]
* draw some UML to appease people?
= Information Model =
== Core Model ==
=== Dublin Core ===
[http://dublincore.org/ The Dublin Core Metadata Initiative] is an open organization engaged in the development of interoperable online metadata standards that support a broad range of purposes and business models. An introduction to the topic can be read in the [http://dublincore.org/documents/usageguide/ Usage Guide].
=== ISO19115 ===
=== FGDC ===
== Namespace ==
The '''dclite4g''' namespace provides a common naming scheme for properties specific to geographic data sets and services which are not covered by the existing Dublin Core or GeoRSS standards.
The namespace will come to live at http://xmlns.com/2006/dclite4g/ .
* extents
* accuracy
* scale
''' fill in here from [[Geodata Metadata Requirements]] '''
== References ==
* [http://geometa.info/rappiinfo/wiki/index.php/DClite4G Dublin Core lite for Geo]
* [http://portal.opengeospatial.org/files/?artifact_id=5929&version=2 OGC Catalog Services 2 Specification] '''6.3.3''', ''Core returnable properties''
* [http://portal.opengeospatial.org/files/?artifact_id=12604&version=1&format=pdf OGC ebRIM profile of CSW specification], '''Appendix B.5, Table B.3''' - ''Slots defined in the Basic package''
* [http://udig.refractions.net/docs/api-udig/net.refractions.udig.catalog/net/refractions/udig/catalog/IGeoResourceInfo.html  iGeoResourceInfo class in uDig]
* [http://www.geodatacommons.umaine.edu/wpapers/CGD%20Metadata%20White%20Paper%20v2.pdf GeodataCommons Metadata Whitepaper]
= Query Interface =
== OAI-PMH ==
[http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
Following are specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):
* Only '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.
Additional bounding box query property for ListRecords.
== Others ==
== References ==
* [http://devgeo.cciw.ca/owscat/docs/index.html OWSCat]
* [[Simple Catalog Interface]] - links to articles, etc
= See Also =
* http://www.geometa.info/ - German geospatial data search service using dclite4g + OAI-PMH.

Revision as of 15:51, 10 April 2007

DCLite4G is an effort to

  • establish a common information model with mappings to well known formats for geospatial metadata
  • provide a vocabulary/recommendations for spatial extensions to Dublin Core
  • support simple interfaces for collecting and querying geospatial metadata

Getting involved

To get involved first of all subscribe to the Mailing List (see below). Then read all corresponding pages of this Wiki. If you find that something is missing or incorrect, correct or add it as required. To do this you need to create an account for this Wiki. Sorry, still working on Single Sign On...

Once you get the hang of it and feel like needing more involvement you can join any interest group or project and contribute to the process. This can happen from many perspectives - as a user, portal operator, developer, decision maker or name it.

Mailing List

Feel welcome to join the discussion and development mailing list: