Yet more on time

Trying to unify everything by making time of day a recurring time instance
just makes things more complex.

Basically, what I would like to see is:

time (that is time of day) as a fundamental type with a representation like
T11:00:00-05:00.

date as a fundamental type with a representation like 1999-11-08.

dateTime as an aggregate of these two types with a representation like
1999-11-08T11:00:00-05:00.

timeDuration as a fundamental type with a representation like P nnn
(Y|M|D|W|H|M|S).  This would allow things like a 120 day return policy that
could not be represented using the dateTime like formulation.  Not allowing
combination (like 1M5D) would eliminate the ambiguity that would occur when
the order of addition would result in different dates.

Time Periods, repeating time instances, repeating time periods, etc, should
have no built-in datatypes but should be represented in the schema by
combinations of dateTimes and/or timeDurations.

Received on Monday, 8 November 1999 18:37:53 UTC