Google Developers Blog: atom publishing protocol
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/20181009142202/https://developers.googleblog.com/search/label/atom%20publishing%20protocol
By DeWitt Clinton, Google Developer Programs Google Contacts Data API , we're opening up this contact list to your applications as well.announcement post on the Google Data APIs blog, and join the conversation on the Contacts API Group .
Post by Joe Gregorio, Google Developer Programs IETF ) Application Area Architecture Workshop. This was a chance for people active in the IETF Applications Area to get together and work on architectural issues, topics that span many specific groups in the Applications area."...that is, things that are not security (part of the security area), nor networks (most of the other areas), but rather things that use the networks and security services to provide things of benefit to the end-user." This was of particular interest to me since that includes specifications like the Atom Syndication Format and the Atom Publishing Protocol , which we use extensively at Google . From the call for participation :"These should be a few pages of text on some topic related to Applications area architectural issues. Since the group of attendees is expected to span HTTP and AtomPub, email, IM, calendaring, directories and more, issues should be of interest to more than one of these groups. Some existing Applications architecture "modules" that already are reused include SASL, URLs, MIME types, XML and XML schemas and namespaces, HTTP as a substrate, TLS, ABNF, BEEP." We had around 20 attendees and the breakout sessions ranged over all the topics listed above and many more. There were two days of great conversation and everyone had a good time."Thank you for the high quality hosting and convenience of location and food!"-Lisa Dusseault (Apps Area Director)
Posted by DeWitt Clinton, Google Developer Programs interoperability meetup earlier this week in Mountain View, CA.Atom Publishing Protocol is a specification that helps define the interactions between clients and servers that wish to read and write collections of documents via the web. Building upon the popular Atom Syndication Format , the Atom Publishing Protocol formalizes many of the mechanisms required for the exchange of rich and meaningful content via a process known as Representational State Transfer, known familiarly as REST . Nearing completion as an Internet Engineering Task Force (IETF ) standard, the protocol is already seeing wide adoption, and the working group felt it was time to bring people together to see how the various existing implementations interacted with each other.20 representatives from organizations and companies far and wide (some hailing from all the way across the Pacific) made the trip to Mountain View for two days of interoperability testing. The meetup was open to anyone who has built client or server software that uses the protocol, and it was extensively blogged about and "simulcast" over the Atom IRC channel for those who could not attend in person. Striking was the diversity of both the organizations in attendance (AOL, IBM, Google, Microsoft, Oracle, O'Reilly, Six Apart, to name just a few) and the wide variety in types of applications being built. And a special thanks to Tim Bray , co-chair of the Atom Publishing Protocol working group , for his tireless devotion to the standards process and for leading the group in making the most of our time together.many implementations of the protocol do at interoperability? Well, authentication was a hurdle for most clients (the specification itself considers authentication to be an orthogonal concern), but beyond that our servers are relatively compliant and some of our client code is well along the way to full support for the protocol. Perhaps more importantly, Google is committed to continued support of the working group, and we intend to keep pace with the draft specifications as they are finalized.
