Hi,
Following the Darwin Core Term Change Policy (http://rs.tdwg.org/dwc/terms/namespace/index.htm#classesofchanges), I am hereby submitting a request for the addition of a new Darwin Core term: georeferencedDate. I've also submitted this request as an issue on the Darwin Core Google Code site: http://code.google.com/p/darwincore/issues/detail?id=104
Term Name: georeferencedDate Identifier: http://rs.tdwg.org/dwc/terms/georeferencedDate Namespace: http://rs.tdwg.org/dwc/terms/ Label: georeferencedDate Definition: The date on which the georeference of the Location was determined. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). Comment: Example: "2011-03-01T13:59-0500" is 1 Mar 2011 1:59pm in the time zone five hours earlier than UTC. Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property Refines: http://purl.org/dc/terms/date Status: Date Issued: 2011-06-01 Date Modified: Member Of: Has Domain: Has Range: Decision: Version: Replaces: Is Replaced By: Class: http://purl.org/dc/terms/Location ABCD 2.06: not in ABCD
Submitter: Peter Desmet
Justification: A georeferencing date allows chronological sorting of multiple georeferences for one location, identification of the most recent georeference, etc. This term is already used at georeferencing workshops (based on the GBIF 2006 Guide to best practices for georeferencing) and in numerous collection databases. It will also become one of the outputs of the new BioGeomancer. It's justification is similar to the one for dateIdentified. The term could be called "dateGeoreferenced" (cf. "dateIdentified"), "georeferenceDate" (cf. "georeferenceProtocol" and "eventDate") or "georeferencedDate" (cf. "georeferencedBy").
Thank you for reviewing this request.
Peter