Google Developers Blog: caldav
COLLECTED BY
Organization:
Internet Archive
These crawls are part of an effort to archive pages as they are created and archive the pages that they refer to. That way, as the pages that are referenced are changed or taken from the web, a link to the version that was live when the page was written will be preserved.
Then the Internet Archive hopes that references to these archived pages will be put in place of a link that would be otherwise be broken, or a companion link to allow people to see what was originally intended by a page's authors.
The goal is to
fix all broken links on the web .
Crawls of supported "No More 404" sites.
A daily crawl of more than 200,000 home pages of news sites, including the pages linked from those home pages. Site list provided by
The GDELT Project
The Wayback Machine - https://web.archive.org/web/20181009155607/https://developers.googleblog.com/search/label/caldav
By Piotr Stanczyk, Tech Lead
In March we announced that 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.
Both of these APIs are getting other updates as well:
In addition, the CalDAV API now has a new endpoint:
https://apidata.googleusercontent.com/caldav/v2
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 The Calendar team was the first to launch its 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.) So far we've focused on 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. For information on how Google Calendar data maps to the CalDAV protocol, please check out our CalDAV developer's guide . And of course, don't hesitate to hurl feedback in the general direction of our Google Group . * Disclaimer: during this developer-focused release, and in light of known issues , we strongly suggest that you restrict Google Calendar <> iCal 3.0 synchronization to test accounts only.