Dating description definitions
This profile defines two ways of handling time zone offsets: Times are expressed in local time, together with a time zone offset in hours and minutes.
A time zone offset of " hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC.
For example it defines Basic Format, without punctuation, and Extended Format, with punctuation, and it allows elements to be omitted.
This profile defines a restricted range of formats, all of which are valid ISO 8601 dates and times.
A particular problem with ISO 8601 is that it allows the century to be omitted from years, which is likely to cause trouble as we approach the year 2000.Year: YYYY (eg 1997) Year and month: YYYY-MM (eg 1997-07) Complete date: YYYY-MM-DD (eg 1997-07-16) Complete date plus hours and minutes: YYYY-MM-DDThh:mm TZD (eg 1997-07-16T ) Complete date plus hours, minutes and seconds: YYYY-MM-DDThh:mm:ss TZD (eg 1997-07-16T ) Complete date plus hours, minutes, seconds and a decimal fraction of a second YYYY-MM-DDThh:mm:ss.s TZD (eg 1997-07-16T.45 ) YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) s = one or more digits representing a decimal fraction of a second TZD = time zone designator (Z or hh:mm or -hh:mm) This profile does not specify how many digits may be used to represent the decimal fraction of a second.An adopting standard that permits fractions of a second must specify both the minimum number of digits (a number greater than or equal to one) and the maximum number of digits (the maximum may be stated to be "unlimited").Therefore strings SHOULD always contain non-whitespace content There is no specified upper limit to the size of a binary, but systems will have to impose some implementation based limit to the size they support. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored at receiver discretion. Indicates that the value is taken from a set of controlled strings defined elsewhere (see Using codes for further discussion).This should be clearly documented, though there is no computable for this at this time An instant in time in the format YYYY-MM-DDThh:mm:zz:zz (e.g. The time SHALL specified at least to the second and SHALL include a time zone. Dates SHALL be valid dates A date, date-time or partial date (e.g. Technically, a code is restricted to a string which has at least one character and no leading or trailing whitespace, and where there is no whitespace other than single spaces in the contents Any combination of upper- or lower-case ASCII letters ('A'..'Z', and 'a'..'z', numerals ('0'..'9'), '-' and '.', with a length limit of 64 characters.