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.
As different standards have their own requirements regarding granularity and flexibility, this profile offers a number of options.
An adopting standard must specify which of these options it permits.
This profile avoids the problem by expressing the year as four digits in all cases.
This profile may be adopted by standards which require an unambiguous representation of dates and times.
Note: This is intended for when precisely observed times are required (typically system logs etc.), and not human-reported times - for those, use date or date Time (which can be as precise as A date, or partial date (e.g. just year or year month) as used in human communication. (This might be an integer, an un-prefixed OID, UUID or any other identifier pattern that meets these constraints.) All elements using these primitive types may have one or more of a value as described above, an internal identity (e.g. For an example, take an element of name "count" and type "integer".
just year or year month) as used in human communication. The format is YYYY, YYYY-MM, YYYY-MM-DD or YYYY-MM-DDThh:mm:ss zz:zz, e.g. XML The value is represented in XML as an attribute named "value": For additional details, see the XML, JSON and Turtle format definitions.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.Comments on this document should be sent to [email protected] document defines a profile of ISO 8601, the International Standard for the representation of dates and times.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).