Those definitions in the DwC documetation are correct. Note that they are not implementation-specific. The caution here is that an ISO 8601 date time is much more expressive than an xs:datetime (a specific implementation), for example.
On Tue, Oct 19, 2010 at 12:16 PM, Steve Baskauf < steve.baskauf@vanderbilt.edu> wrote:
I was going by the definitions at http://rs.tdwg.org/dwc/terms/index.htm#eventDate and http://rs.tdwg.org/dwc/terms/index.htm#eventTime Going by these definitions, eventDate is an ISO 8601 encoded thing that can include both date and time (or only date at a lower resolution). eventTime appears to only refer to the time (at least based on the examples). If we are going to call these things dwc:eventDate and dwc:eventTime we have to go with the way they are defined in the Darwin Core standard. Steve
Mark Wilden wrote:
On Tue, Oct 19, 2010 at 10:12 AM, Richard Pyledeepreef@bishopmuseum.org deepreef@bishopmuseum.org wrote:
Yeah, I originally had it as eventDate, but then switched to eventTime. If Date can include time (and Time is assumed not to include date), then using eventDate is fine.
I would recommend using eventTime for a date + time-of-day. "Time" is more general than "date." This is the usage in the Ruby world.
///ark Web Applications Developer Center for Applied Biodiversity Informatics California Academy of Sciences
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: VU Station B 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 343-6707http://bioimages.vanderbilt.edu
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content