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

[Carsten Bormann <[e-mail]>]

On Feb 14, 2019, at 09:31, Richter, Jörg <[e-mail]> wrote:
> 
> Here is a proposal to assign tags to date, time of day and time zone designator:
> https://j-richter.github.io/CBOR/date.html

I think it is interesting to compare this approach with that of tag 1001.

Tag 1001 tries to combine necessary information (to identify a point in time) into a single data structure.

Your proposal differs in two ways:
(1) the date/time-of-day/timezone information is unbundled into separate tags.
(2) the relation to time zones is implicit (contextual).

Specifically:
— the “date” seems to stand for the entire 24-hour interval of the given day in some timezone taken from the context
— the “time” (really time of day) stands for any point in time that corresponds to that time of day (again in a time zone taken from the context)
— the “time zone” stands alone, i.e., is useful without such contextual information.

All of these would make good fields in a 1001-style map (which would provide the context), except that “date” really is an interval (which ) and “time” (time of day) really is a recurring event.

> For the tags I have chosen values between 24 and 255. For date and time I could imagine
> to use smaller tags, because the encoded payload is very short.
>  
> Do you have better suggestions for the tags?

I think the tags proposed are fine.  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).

Grüße, Carsten