I've scoured the terms and see no other date or accordingTo omissions for other terms.
At first I thought that the 30 days would be up on Friday around 11am Pacific Daylight Time and the term would pass into the ratified domain having passed scrutiny by the TAG, based on Peter's submission date, but, having never yet exercised the DwC ratification process, I neglected to take into account that the TAG is supposed to make the call for public comment and that should be open for 30 days if there is no dissenting opinion. Sorry for the oversight, Peter. I know you've been watching the clock for Friday.
Since this has to go to public comment, I think I should do the same with all of the pending terms to reach conclusion on them all simultaneously and put the ones that pass into the next release (version). I'll create a preamble about what I'm about to do, then create a thread for each of them, summarizing the status as I see it and open them each to final comments with the intention of ratifying the ones that have no apparent opposition. This will be in keeping with the semi-annual review of terms that was suggested in the TAG gathering at the last TDWG meeting.
Here is the list of terms still outstanding in the Issue tracker:
DigitalStillImage, which from the public discussion looks like it should be scrapped
Individual and IndividualRemarks, which went through a great deal of discussion without a clear conclusion
dcterms:source, which has not undergone public discussion
yearOfPublication to go with Taxon, which hasn't undergone public discussion
alive/dead status seems to have achieved the status of "dead"
geo:lat and geo:lng, the discussion for this began on tdwg-content and I entered it as an issue. It's unclear if the discussion has reached a definitive conclusion.
When the comment period is over, for all of the proposals for which there is no dissent, then I'll make the necessary changes to the standard and publish those, and make the announcement on tdwg-content.
Any dissent on this proposal? Doesn't matter, I'm going to do it anyway. ;-)
On Wed, Jun 1, 2011 at 2:10 PM, Jim Croft jim.croft@gmail.com wrote:
yes. Are there any other after-market actions that do not have dates (and people/agents) associated with them?
jim
On Thu, Jun 2, 2011 at 4:04 AM, John Wieczorek tuco@berkeley.edu wrote:
I completely agree with this proposal. It was an oversight not to have included it with the rest of the georeferencing terms in DwC at the outset. Now there are apps that need to include this, and it would be nice if it was an official term.
On Wed, Jun 1, 2011 at 10:52 AM, Peter Desmet peter.desmet@umontreal.ca wrote:
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
-- Peter Desmet Biodiversity Informatics Manager / Directeur de l'informatique de la biodiversité Biodiversity Centre / Centre sur la biodiversité de l'Université de Montréal Canadensys - www.canadensys.net
Institut de recherche en biologie végétale Université de Montréal 4101 rue Sherbrooke est Montréal, Québec, H1X2B2 Canada
Télé / Phone: 514-343-6111 #82354 Télécopie / Fax: 514-343-2288 Email: peter.desmet@umontreal.ca / peter.desmet.cubc@gmail.com Skype: anderhalv Public profile: http://www.linkedin.com/in/peterdesmet _______________________________________________ tdwg-tag mailing list tdwg-tag@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tag
tdwg-tag mailing list tdwg-tag@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tag
-- _________________ Jim Croft ~ jim.croft@gmail.com ~ +61-2-62509499 ~ http://about.me/jrc 'A civilized society is one which tolerates eccentricity to the point of doubtful sanity.' - Robert Frost, poet (1874-1963)
Please send URLs, not attachments: http://www.gnu.org/philosophy/no-word-attachments.html