XML Schema follows the ISO 8601 standard for its lexical representation. Some other examples of this application of dates and times include:ġ.2 Identifying Time Zones and Zone Offsets As with incremental time, the event happens in the same instant around the globe and meaning of the value depends on the offset from UTC. For example, if you tell someone that you will make a telephone call to them at 14:00 from Paris, if that person is in London they'll expect the phone to ring at 13:00. Time Zone Dependent Field-Based Time In other cases, field-based dates and times are supposed to represent values linked to a particular location or time zone. Some other examples of this application of dates and times include: For example, various kinds of "anniversary date" such as a person's birthdate or an employee hire date would normally fall into this category, partly because time is not expressed, and partly because the actual time of the start and end of the day for a given geographic location may not be considered important. One application for this type of representation is for values that are time zone independent, representing a logical event divorced from a particular location on the Earth. Time Zone Independent Field-Based Time The human representation of computer times is more complicated, and represents time using various separate field values, such as hour, minute, month, or year. Recording actual process start or stop times Labeling log file entries with a timestamp Values of this type are commonly used in applications as "time stamps", showing when an event occured. Date and time values based on a construct of this type (which we'll call computer time) are time-zone-independent, since at any given moment it is the same time in UTC everywhere on Earth: the values can be transformed for display for any particular time zone offset, but the value itself is not tied to a specific location. Other systems use other units and epochs. For example, the Java type is a long (integer) value for the number of milliseconds since 00:00 (midnight) on Januin UTC (Universal Coordinated Time, sometimes also called GMT). Incremental or Computer Time Most programming languages and development environments provide data types for handling time which are based on a numeric value: units of some specific length measured from a specific point in time (called the epoch). There are three main applications of date, time, or dateTime data types in applications.
#Utc time offset meaning archive
See W3C mailing list and archive usageĪs of this publication, the Working Group expects thisĭocument to become a W3C Working Group Note. List dedicated to discussion associated with the Internationalization Core Your feedback is welcome, especially regarding the open issues This document has been produced as part of the W3C Internationalization Activity, following the procedures set out for the W3C Process. Inappropriate to cite this document as other than work in Replaced or obsoleted by other documents at any time. This is a draft document and may be updated, Publication as Working Draft does not imply endorsement by the This is the first public Working Draft of the Internationalization Core Working Group for review by interested parties.
This technical report can be found in the W3C technical reports Other documents may supersede this document.Ī list of current W3C publications and the latest revision of This section describes the status of this document at the time This document is an editors' copy that has
0 kommentar(er)
