https://developers.google.com/google-apps/calendar/caldav/v2...
It also supports a richer API, for features that don't fit into CalDAV:
https://developers.google.com/google-apps/calendar/overview
While I tend to agree with what I think is your point, it's all well and good to say that there's a standard and one should use it (which I support, and have worked on many throughout my career), but standards aren't a panacea either, especially since many of best standards are ones that standardize a previously proprietary (but working!) design.
(No relationship with the calendar team, but I'm pretty sure they'll read this thread if you have comments for them.)
CalDAV is a standardization of a previously proprietary but working design (apple's icalendar work) that most all other vendors support except for Google.
"We have not yet provided a full implementation of all of the relevant specifications, however for many clients such as Apple iCal™ the CalDAV protocol should interoperate correctly."[0]
[0]: https://developers.google.com/google-apps/calendar/caldav/v2...
Every time I see "google calendar" in our issue tracker, I die a little inside.
We have a dozen known vulnerabilities in common software packages every year, and these devices are using IP for communicating often confidential information. It can be disastrous for your toaster to be hijacked, especially if it can be remoted no and burn your house down.
This whole IoT disaster should have been predicated on free software, with some protocol support for authorized local network updates and maintenance. You know damn well that if Samsung cannot be bothered to update the OS on a four year old phone anymore, your Samsung Fridge or TV or futon is a lost cause.
The only solution I could think of from a security standpoint would be to limit functionality on the device itself to such a level that there is not much need for updating, i.e., ideally the fridge becomes a dumb device that essentially offers a vnc-style connection to a central FridgeCo data center, so that the fridge itself would never deal with your passwords etc. other than sending them somewhere in an encrypted connection. This basic layer of functionality (and even that would be a lot to keep secure) would be more reasonable to maintain and keep secure than having separate apps for Google Cal etc. Of course, this would cause many more problems, be a single point of failure etc., but I think that's the way it's most likely going to go.
How much vendors are willing to use something like this remains to be seen. Personally I resist buying things that I think will have a poor security update record. I'd like to see more pressure on vendors to do the right thing here, especially because there is at least one reasonable solution available.
Disclosure: I work for Canonical, but am not associated with the IoT work in Ubuntu.
I believe Canonical have a grand plan but have just focused on phones first. Since to my knowledge the Ubuntu TV hasn't happened yet, how can it be a flop?
Rather than being built in, this "calendar" should be android/iOS tablet that's attached to the refrigerator with magnets. It should be thrown in the trash every couple years and replaced with a new one. According to the interests of Google/Apple (as evidenced by their software updates).
Same thing with "Smart TVs". Just put some extra powered USB ports on the back next to the HDMI port and bundle it with a TV stick.
I have GPS and internet radio on my phone that I upgrade every few years, why would I want it in my car that I upgrade maybe every 10 years?
I think we're building a shitty internet of shitty things.
By the way, do you know that you can send an email to a server running software that hasn't been updated since the 1960's?
I repeat.
The problem here is not the refrigerator!
We're building a shitty internet, not an internet of shitty things. If integrating with an online calendar means having to have a software team at the ready at all times for the whim's of some service's API updates.. we have failed society in a deep way.
The API that Google should be releasing for Google calendar is CalDAV, because it's a standard that people can depend on. Google - by choosing to not use that standard AND to not get a different one standardized with their peers, shows they don't want to be part of an Internet.