Re: TSTTime definition

[Paul Koning <pkoning@xxxxxxxxx>]

>>>>> "Denis" == Denis Pinkas <Denis.Pinkas@bull.net> writes:

 Denis> Since many applications will only use a time with a precision
 Denis> of a second , it makes sense to use GeneralizedTime only up to
 Denis> a precision of a second.

 Denis> Another argument is that using GeneralizedTime up to the
 Denis> millisecond, would not satisfy some people wishing to go
 Denis> beyond the millisecond.

 Denis> So we need an *additional* information to go under the
 Denis> millisecond, associated with a precision factor.

Why?  As I understand it, GeneralizedTime allows more than 3 digits
after the decimal point.  If you don't need them, don't look at them.
But I see no benefit in an arbitrary restriction that you must not go
beyond milliseconds.  Such a restriction modifies the standard
semantics of the datatype; it doesn't make any difference to an
application that only cares about seconds; and it introduces a problem 
for cases where you want better than milliseconds.  As Peter Gutmann
pointed out, why invent a new flat tire when an acceptable wheel
already exists?

	paul