It’s be cool though if they put out embed-a-ble feeds. I looked at the microformat local stuff this week — their integration of Yellow Pages, Local & Reviews from across the web. Being able to grab that stuff back to a site in a feed would rock — putting your ad in their page is not the same.

Hm. It’s like reverse advertising. Take our formatted content and pay for it - and keep the ad dollars on your own site. Syndicatizing.

In any case, it’ll be interesting to see how it plays out.
-j

It seems that GData communications are only used to interact with a pre-existing feed, which is provided by the underlying service (ex, Google Calendar will provide you with the URL of the feed of your calendar items, which you send gdata requests to).

The scraping you describe would require an easy way to get a large list of readable feeds. Looking at the calendar API, there doesn’t seem to be a way to do this for Google Calendar feeds.

This makes sense I think– calendar data is inherently more private than items placed in Base, which is meant to allow public viewing and searching. Perhaps when they add a GData interface to Google Base, the Base service would extend GData to let you get a list of feeds. (Atompub, one of the emerging standards that GData is based on, lets you do this already via it’s introspection features).

Maurice

Scraping is what search engines do to create their indexes.

Jarvis is asking if Google will make this data available to Yahoo and the like, not to its owners. (Its owners don’t need access - they can keep a copy of what they upload.)

Whether or not Google decide to follow this path in their other products is another matter, but it looks to me like as far as GData is concerned, the garden has no wall.