679Re: Pure ISO 8601 or varied for popular formats
- Sep 1, 2003The human-readable numeric formats should be:
2000-06-14T23:59:59Z or 2000-06-14T19:59:59-04:00
2000-06-14 23:59:59 (UTC) or 2000-06-14 19:59:59 (UTC-04:00)
The latter should be default and the former should be for the
internal code of programs.
The example with "Wednesday, August 2003-08-13T18:00:00+01:00 CEST"
isn't a very good example as the month is in two places and can
confuse a reader.. Something like "2003-08-13 (Wed) 18:00:00
(UTC+01:00)" would work much better. The "1999/12/31 (Friday)
23:59:59" format has been in use in China & Japan for a LONG time
so, it may be a good alternative. Modernising it to "1999-12-31
(Fri) 23:59:59" may be the best bet. For worded longhand dates in
English, something like "Saturday, 1 January 2000" (used in the UK)
or "2000 January 1 (Saturday)" (used in the Chinese, Hangul &
Japanese languages for thousands of years and by astronomers in the
form of "1999 Dec 31.ddd..." (decimal part of day) for a few
centuries) would work well.
I hope any of this helped...
--- In ISO8601@yahoogroups.com, Tex Texin <tex@i...> wrote:
> My suggestion would be to have at least a "pure ISO 8601" mode
> exactly and then offer the forms that you think are more natural
or popular as
> options or alternatives so you satisfy both worlds.
> I don't think the ISO community will complain unless you
> that are close to 8601, but not defined in 8601, as 8601
conformant. It might
> help to warn your users that the 8601 format is best for data
> the non 8601 variations are (perhaps) better for readability.
> That's my 2 cents. But check with your (potential) user community
> hjwoudenberg@a... wrote:
> > In a message dated 8/13/2003 5:25:01 PM Central Daylight Time,
> > writes:
> > Should be with blank before time
> > > to = "Wednesday, August 2003-08-13 18:00:00+01:00 CEST"
> > Subject: To Tex Texin
> > Date: Wed, 13 Aug 2003 18:25:01 EDT
> > From: HJWOUDENBERG@a...
> > My date and time conversion for anywhere in the world to
anywhere in the
> > world is just about completed.
> > I support the ISO to the letter, but would like you advice about
> > practices
> > The ISO to the letter requires the "T" as the designator for
> > No zero suppression.
> > No names of day or month
> > Does do not permit truncation.
> > Only permits reduced precision on time.
> > It supports all combinations of date, time, fraction of
> > (hours,minutes,seconds[ fraction of days]),and Coordinate
> > offset and conversion for calendar dates, ordinal dates and week-
> > It does not support Time Intervals (As you have pointed
> > problems).
> > The general practices supports:
> > 'That the "T" is replace with a blank.
> > The name of the day and month can be prefixed to the date.
> > The text abbreviation for the time zone may be suffixed
> > offset.
> > Tex, you know the ISO community. How much criticism can I
> > general practices are the real world, how do you think they
> > handled? Should I say these are not ISO dates? The market
> > features.
> > Examples of the use of the function (.fr is ISO two letter code
> > to = ADT(.fr:2003-08-13T12:00:00-05:00)
> > (;CEST is Central Eruopean Summer Time)
> > to = ADT(;CET:2003-08-13T12:00:00-05:00)
> > to= "2003-08-13T18:00:00+01:00"
> > to = ADT(*I&=.fr|L|!TZA:2003-08-13T12:00:00-05:00)
> > to = "Wednesday, August 2003-08-13T18:00:00+01:00 CEST"
> Tex Texin cell: +1 781 789 1898 mailto:Tex@X...
> Xen Master http://www.i18nGuy.com
> XenCraft http://www.XenCraft.com
> Making e-Business Work Around the World
- << Previous post in topic Next post in topic >>