Closed mbjones closed 7 years ago
Original Redmine Comment Author Name: Matt Jones (Matt Jones) Original Date: 2003-10-28T20:39:45Z
Created a new group called BoundsDateGroup that allows the documentation and model to be different for date bounds than for numeric bounds. Now the date bounds are documented properly, and numeric bounds must be numbers (xsd:decimal) rather than strings (while date bounds are still string values).
FIXED.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:16:22Z
Original Bugzilla ID was 1155
Author Name: Matthew Brooke (Matthew Brooke) Original Redmine Issue: 1155, https://projects.ecoinformatics.org/ecoinfo/issues/1155 Original Date: 2003-09-25 Original Assignee: Matt Jones
within dateTimeDomainType (eg see eml:eml/dataset/dataTable/attributeList/attribute/measurementScale/datetime/date timeDomain), the documentation for the bounds/minimum and bounds/maximum elements is incorrect - it is currently the same documentation as for interval/numericDomain/bounds, which defines the min and max as numerical values. However, this is not appropriate for datetime, since the bounds can contain alphanumeric characters, not just numeric.
Note that the schema is correct - alphanumeric datetime bounds are validated OK - it appears to be just th edocumentation that's wrong.