Journal Articles
| Browse in : |
All
> Journals
> CVu
> 124
(22)
All > Topics > Programming (877) Any of these categories - All of these categories |
Note: when you create a new publication type, the articles module will automatically use the templates user-display-[publicationtype].xt and user-summary-[publicationtype].xt. If those templates do not exist when you try to preview or display a new article, you'll get this warning :-) Please place your own templates in themes/yourtheme/modules/articles . The templates will get the extension .xt there.
Title: ISO 8601: A Standard You Should Know About
Author: Administrator
Date: 03 July 2000 13:15:38 +01:00 or Mon, 03 July 2000 13:15:38 +01:00
Summary:
Body:
Have you ever been annoyed with the confusion between the British DD/MM/YYYY and American MM/DD/YYYY in user interfaces and web pages? Using the name of the month can help, but it's more to type and it commits you to a language (like English or French) rather than a purely numerical representation. One solution is for programmers to use
YYYY-MM-DD
This is the convention in the Far East and some other countries, and has been adopted as an international standard, ISO 8601. Besides avoiding confusion, it makes dates easy to sort, and this still holds if you append the time in ISO 8601 format (24-hour HH:MM[:SS] with 00:00 for midnight). Colons and dashes are optional (but they do make things more readable).
ISO 8601 defines a suffix of "Z" ("Zero-meridian", aka "Zulu time") to mean UTC (the 1972 atomic replacement for GMT). "+HH" or "+HH:MM" means local time that is ahead of UTC and "-HH" or "-HH:MM" means local time that is behind. Hence, to find out the UTC equivalent of a local time, you need to INVERT the +/- operator.
Notes:
More fields may be available via dynamicdata ..