Project

General

Profile

Bug #1155

Documentation incorrect for dateTimeDomainType bounds

Added by Matthew Brooke almost 17 years ago. Updated almost 17 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
eml - general bugs
Target version:
Start date:
09/25/2003
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1155

Description

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.

History

#1 Updated by Matt Jones almost 17 years ago

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.

#2 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 1155

Also available in: Atom PDF