Re: [Cbor] Proposal for Date, Time and Time Zones

[Richter, Jörg <[e-mail]>]

The main motivation for date and time of day is to just represent 
the semantic information.  Without a need to assign one or more points in time.

No one cares whether his birthday was 23, 24 or 25 hours long.  
Opening hours of stock exchanges are also just represented as a pair of clock times.
Of course, deriving concrete points in time requires always context information 
like the time zone of the stock exchange. But this information should not be 
part of the clock time.

As I see it, tag 1001 is useful for points in time.  I find it particularly 
good that decimal fractions can also be used. I am unsure about the negative
keys. Don't they do the same as a decimal fraction? And unusual scaling like 10^-7
cannot be used as is.  (Which is as it happens our internal resolution of
points in time and time of day)

I can't quite imagine how the concepts could be unified. Do you have an 
idea in mind?  All 4 types (timestamp, date, time of day, time zone) are used 
separately in our code.  To me it makes sense to represent them distinctly in CBOR.

About leap seconds: Now that I think about it, is tag 0 defined with leap seconds 
or without?  This might pose a problem (for us).  Anybody know what other 
encoders/decoders do?

> I’m interested in where the two
> different approaches would be used (and how to get the interval/periodic
> event function into tag 1001-1003).

I think I understand 1001.  And I think the two are different semantic concepts.
But I cannot find anything about tags 1002 and 1003.  The draft for 1001
does not contain much information about it.  Is there another document somewhere?

- Jörg