Google Developers Blog: caldav
COLLECTED BY
Organization:
Internet Archive
The Internet Archive discovers and captures web pages through many different web crawls.
At any given time several distinct crawls are running, some for months, and some every day or longer.
View the web archive through the
Wayback Machine .
Web wide crawl number 16
The seed list for Wide00016 was made from the join of the top 1 million domains from CISCO and the top 1 million domains from Alexa.
The Wayback Machine - https://web.archive.org/web/20170705140837/https://developers.googleblog.com/search/label/caldav
By Piotr Stanczyk, Tech Lead CalDAV , an open standard for accessing calendar data across the web, would become a partner-only API because it appeared that almost all the API usage was driven by a few large developers. Since that announcement, we received many requests for access to CalDAV, giving us a better understanding of developers’ use cases and causing us to revisit that decision. In response to those requests, we are keeping the CalDAV API public . And in the spirit of openness, today we’re also making CardDAV – an open standard for accessing contact information across the web – available to everyone for the first time.Piotr Stanczyk is the Tech Lead of the Google Calendar APIs group. His current focus is to provide next generation Calendar APIs which make developers’ lives easier. He also participates in CalConnect consortium. Posted by Scott Knaster , Editor
By Neal Gafter, Software Engineer Google Data API back in 2006, and in that proud tradition, we're excited to offer an additional way for developers to read from, and write to Google Calendar: the CalDAV protocol . (CalDAV — an extension of WebDAV — is an evolving, open standard for calendar synchronization.)Apple's iCal 3.0 as a first working example of 2-way Google Calendar sync over CalDAV.* But we're calling all current and prospective CalDAV developers to help us firm up the implementation, and make it play nice with other popular CalDAV-friendly clients. developer's guide . And of course, don't hesitate to hurl feedback in the general direction of our Google Group .known issues , we strongly suggest that you restrict Google Calendar <> iCal 3.0 synchronization to test accounts only.
