Hacker News Reader

Comment by akie | Hacker News Reader

The article mentions that JMAP does calendars as well. Anyone have a quick status update on how it compares to CalDav and if it's supported by any of the major calendar clients or servers? I did a quick google and looked at the JMAP site but couldn't find any info.

Background for this is that I implemented a calendar client and a calendar server (with SabreDAV) last year and I'm wondering if I should be adding support for JMAP anytime soon.

View on HN

Editor of the JMAP specs here. The JMAP calendar spec is currently just a draft, but now JMAP core and mail are (more or less) finalised and JSCalendar (https://tools.ietf.org/html/draft-ietf-calext-jscalendar-11) is in last call too, we will be looking to take the JMAP Calendar spec through the IETF process in the very near future. Since it is essentially just combing core with the JSCalendar data format, this should be reasonably straight forward.

I see, thank you so much for providing inside information. Looks like it'll be a while before I can ditch CalDav...

Current state of calendaring is horrible, it's basically not possible right now to create compatible and reliable library/application.

Calendaring truly is surprisingly difficult. Dates and times just are not defined with computers in mind.

Yep, they are extremely difficult. Timezones, group events, repeatable events. RFCs describing calendaring are very vague and miss a lot of important details. And exchange/outlook implementation adds a huge pile of incompatibility.

When I was working on calendaring project I've found lots of ways to create broken events in google calendar for example. They are completely valid according to RFC but absolutely not usable in apps.

Also there are working groups that STILL developing calendaring RFCs, they create tons of esoteric and cryptic documents every year.

P.S. When I write “RFC” I mean any well established standard.

Reply on news.ycombinator.com