createDateTime
RIXML 2.5 Attribute
Definition
Used consistently as `dateTime` (required)
CoverageUpdates dateTime |
This marks the date/time at which this research bundle was formed. It is expressed using ISO 8601 as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime. In addition, RIXML requires the use of Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. required |
Research dateTime |
This marks the date/time at which this research bundle was formed. It is expressed using ISO 8601 as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime. In addition, RIXML requires the use of Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. required |
RosterUpdates dateTime |
This marks the date/time at which this research bundle was formed. It is expressed using ISO 8601 as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime. In addition, RIXML requires the use of Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. required |
Documentation
This marks the date/time at which this research bundle was formed. It is expressed using ISO 8601 as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime. In addition, RIXML requires the use of Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time.
Version History
Business Rules
Date and time values must be expressed using ISO 8601 format with Zulu time (GMT +/- offset) rather than relative time
DateTime values must be expressed using ISO 8601 format as refined by the W3C specification and must use Zulu time (GMT with timezone offset) rather than relative time representations
DateTime values for coverage updates must be expressed using ISO 8601 format with Zulu time representation
Years in date/time values must be expressed using exactly four digits
Months in date/time values must be expressed using exactly two digits with leading zeros when necessary
Days in date/time values must be expressed using exactly two digits with leading zeros when necessary
Time conversion to UTC should only be done if the time is actually converted, not just the time zone indicator changed
Hour values in time components must use 00-23 format, not 24:00:00
The 'T' separator between date and time components must not be omitted
Additional punctuation or spaces must not be added to date/time values beyond ISO 8601 format
Date/time values should include a time zone indicator
Time components should not be omitted from date/time values or defaulted to midnight (00:00:00)
Time values should not be set to one second before midnight (23:59:59)
Design Decisions
DateTime attributes must use absolute time with Zulu time format rather than relative time representations
Absolute times are easier to compute and process compared to relative time formats like 08:30 +5
RIXML Research Data Dictionary v2.5.1, p.135
Semantic Relationships
Constrains1 relationship
xs:dateTimeMUSTDate/time attributes must conform to ISO 8601 standard with specific formatting requirements including 4-digit years, 2-digit months and days, and time zone indicators
RIXML Implementation Guide v2.5.1, p.30— Date/time