sorted by: recent | see :
popular
Content Tagged with Atom + Google
something about gcal
I had a request for creating events in Google Calendar from some business processes. It gave me the opportunity to play with Google Data; it wasn’t too difficult, especially since it’s based on Atom and AtomPub.
I have thus started working on a new rufus library. It’s very limited for now, but I can have code that looks like that :
require 'rubygems'
require 'rufus/gcal'
calendars = Rufus::Google::Calendar.get_calendars(
:account => ENV['GUSER'],
:password => ENV['GPASS'])
#calendars.values.each { |c| p [ c.name, c.href ] }
cal = calendars['gwork']
id = cal.post_quick!(
'Tennis with John November 13 3pm-4:30pm')
cal.events(:q => 'tennis').each do |e|
puts
puts e.to_s
end
Behind the scenes, it relies heavily on the fine atom-tools gem by Brendan Taylor.
The only authentication mechanism used is the ClientLogin. For the other mechanisms, one can look at gdata-ruby.
My next step will be to polish the Event class and to allow for manipulation of Calendar resources. Then I will take a look at other Google Data APIs.
source : http://github.com/jmettraux/rufus-google
mailing-list : http://groups.google.com/group/rufus-ruby
Common Elements: "Kinds" - Google Data APIs - Google Code
's often useful for services that use the Google data APIs to be able to provide a consistent set of information about a particular kind of item.
For example, various Google data API (or "GData") services might provide contact information for a person or an organization; it makes sense for all such services to use the same set of contact-information elements.
The collection of elements that together describe a contact is called the Contact "kind." Some of the elements in the Contact kind are ordinary Atom or RSS elements; others are defined by Google in a namespace called the "Google data namespace." By convention, the Google data namespace is usually referred to in XML code using the gd: alias; for example, the element that contains a telephone or fax number is <gd:phoneNumber>. The schema URL for the Google data namespace is http://schemas.google.com/g/2005.
Google Data APIs - Google Code
Überblick über APIS
GData Scala Client
Allows client software to connect to Google Services through the Google Data API protocol. It makes it easy to retrieve and modify data exposed by services like Calendar or YouTube, without worrying about the underlying XML representation or how queries are made.
The Atom Syndication Format 0.3 (PRE-DRAFT)
Google uses 0.3 Atom for many of its feeds.f
RESTful API Specification - OpenSocial - Google Code
RESTful API Specification
Google Data APIs - Google Code
<sep/>Standard protocol for reading and writing data on the web. These APIs use either of two standard XML-based syndication formats: Atom or RSS. The following data APIs allow your client applications to<sep/>
Introducing the Google Contacts Data API
A common contact list has helped power applications like Gmail, Google Reader, and Google Calendar. And now, with the launch of the Google Contacts Data API, we're opening up this contact list to your applications as well.
Based on AtomPub, the Contacts API can be used to safely read, create, edit, and delete contact information stored with Google, all while keeping users' passwords private via delegated authentication and authorization. Learn the details from Sebastian Kanthak in his announcement post on the Google Data APIs blog, and join the conversation on the Contacts API Group.
IETF Applications Area Architecture Workshop
On February 11 and 12 Google hosted the Internet Engineering Task Force (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.
The Applications Area is the part of the IETF that deals with applications
"...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)
The future of XML
"Even when the XML vocabulary is as poorly documented and incoherent as OpenOffice XML, it's still about a thousand times easier to work with than previous opaque binary formats." "Now no one will care who manufactures their operating system as long as it
google-feedserver - Google Code
Google FeedServer is an open-source Atom Publishing provider based on the Abdera Framework. Google FeedServer has chosen to implement simple backend data adapters that allow the developer to quickly deploy a feed for an existing data source such as a db
Page 1 | Next >>
