August 19th, 2011 | by Google Docs | published in Google Docs
Hello from the Google Docs team! It’s been a hot summer in many parts of the United States, so our New York based team escaped to Governor’s Island for a refreshing afternoon of team bonding.
Wishing all of you a happy (and collaborative!) month of A…
August 19th, 2011 | by Jeremy Milo, Google Apps Marketing Manager | published in Google Apps, Google Enterprise, Uncategorized
Posted by Muzammil Esmail, Product Manager, Google AppsIn our continuous drive to make it easier for Google Apps administrators to create, manage and secure their users and data, we’ve introduced a number of features over time in the Google Apps for …
August 19th, 2011 | by Google Apps Team | published in Google Apps, Uncategorized
Page-level permissions is now available in Google sites, allowing you to control who can view and edit the site on a page by page basis. For instance you can make some pages available for your domain while making some pages private for certain users.On…
August 19th, 2011 | by miriam | published in Google Enterprise
Posted by Wayne Kimball, Jr., Google HR Associate, NC A&T Class of 2011
Today’s Official Google Blog post highlights the vital role that Historically Black Colleges and Universities (HBCUs) continue to play in the development of the African-Amer…
August 19th, 2011 | by A Googler | published in Google Blog
Across the United States, Historically Black Colleges and Universities (HBCUs) provide educational homes for hundreds of thousands of African-American students. Small and community-focused, usually with fewer than 5,000 students, privately or publicly …
August 19th, 2011 | by Aaron Lichtig | published in Google CPG, Uncategorized
WHAT’S HOT 1. Patrick Pichette (Google CFO) in McKinsey Quarterly: Check out McKinsey’s wonderful interview with our laid-back Canadian CFO.
2. Google to acquire Motorola Mobility: Since its launch in November 2007, Android has no…
August 18th, 2011 | by Jonathan LeBlanc | published in Google OpenSocial
Following the 11:59 PDT voting cutoff last night, version 2.0 of the OpenSocial specification has officially passed with 22 positive and 0 negative votes.
Version 2 of the OpenSocial specification opens up integration with other well known open source social specifications, ties in both a simplified gadget format as well as new powerful tools, plus announces some deprecated features.
Some of the major revisions to the specification include:
-
Activity Streams support: Activity Stream provides a mechanism for defining rich and detailed social activities, defined in a simple actor / object / target format. The adoption of this open specification allows OpenSocial to not only provide richer data sources but also to be interoperable with more open streams.
-
-
Deprecated support for ATOM: It was determined that the ATOM serialization format for OpenSocial information was not being utilized in practice. Since there were a number of adjacent specification utilizing JSON for the preferred data format, the community has decided to deprecate support for ATOM.
-
-
Simplified gadget format: Providing a mechanism for embedding template libraries into a gadget specification file, the ability to integrate data pipelining and templating features within a gadget has been greatly simplified.
-
-
Embedded Experiences: The community saw a need to provide a mechanism for providing embedded experiences directly within the gadget. By integrating these features, the content host is able to tell a service how to render its content instead of having the service figure it out themselves. This will provide a higher degree of control over data in a gadget.
-
-
New Incubating API
-
OAuth 2 support: The OpenSocial 2.0 specification now includes support for OAuth 2. Since the OAuth 2.0 specification has not been finalized by the time of this release, OAuth 2 support is currently in an incubating mode. Currently revision 20 of the OAuth 2 specification is being integrated. Support for OAuth 1.0a is still included in the OpenSocial 2.0 specification and has not been deprecated.
-
-
Common Container: In OpenSocial 2.0, a new optional specification has been added for a common container API. The goal is to simplify the container and gadget integration model. It provides a set of common services that Container developers can leverage for features like in-browser Gadget lifecycle event callbacks, embedded experiences, and selection and action handlers.
Here are a few links that will help you get up to speed on the recent changes and additions:
- Release notes.
- OpenSocial specifications.
- Full list of the published features in version 2.
In addition to this announcement, Andrew Davis has another piece of great news on the Shindig side:
Along with releasing the OpenSocial 2.0 spec today, the OpenSocial Foundation is working together with our members companies, and implementor friends at Shindig are proud to announce the availability of the first OpenSocial 2.0 Container, running the latest Shindig 3.0 build, the Open Social Sandbox, at http://sandbox.opensocial2.org:8080/. The site is a live demo of the latest features of the OpenSocial 2.0 spec including Embedded Experiences, Declarative Actions, OpenSearch and powerful new open gadgets APIs to enable gadgets to jump out of the box. The site provides tutorials, demo videos and is geared towards enabling gadget developers immediately to build new gadgets, and test them out on the site through the “Customize” button.
Lastly, I wanted to say thank you to the entire community and dedicated participants who have made this major release possible.
Jonathan LeBlanc (@jcleblanc)
Jonathan LeBlanc is a principal developer evangelist with X.commerce. Jonathan has been a member of the OpenSocial community for over three years and is the author of O’Reilly’s “Programming Social Applications“.
August 18th, 2011 | by Scott Knaster | published in Google Code
By Kenneth Leftin, Software EngineerWith the recent addition of OAuth 2.0 support for the Latitude API, it is now easier than ever to start writing applications that utilize users’ location history or current location if they have opted in to sharing…
August 18th, 2011 | by James Whittaker | published in Google Testing
We’ve completed the agenda for GTAC 2011 and are in the process of notifying accepted speakers and attendees. Once we have firm accepts we’ll be publicizing the agenda.
August 18th, 2011 | by Google Students | published in Google Student Blog
Today, we launched page-level permissions for Sites, giving you greater control over who can edit or view specific pages on your Google Site.This is welcome news for me. As a student at UCLA, I participated in the university’s Undergraduate Student I…
August 18th, 2011 | by Google Docs | published in Google Docs, Uncategorized
Today we’re introducing page-level permissions, a new feature that will allow you to control who can view and edit your Google Site on a page by page basis.
Using page-level permissions, you can make some pages private for certain users while keepin…
August 18th, 2011 | by Lauren Kolodny | published in Google Apps, Google Docs, Google Enterprise, Uncategorized
Posted by Eric Zhang, Software Engineer
(Cross-posted from the Google Docs Blog.)
Today we’re introducing page-level permissions, a new feature that will allow you to control who can view and edit your Google Site on a page by page basis.
Using pa…
August 18th, 2011 | by Erica Sievert | published in Google Affiliate Network
The Google Affiliate Network team is excited to join our fellow affiliate marketers at Affiliate Summit East from August 21-23, 2011 at Hilton New York.At the conference, you’ll have the opportunity to hear from our product management team. Many member…
August 18th, 2011 | by Aaron Lichtig | published in Google CPG, Uncategorized
Do you ever feel like you don’t know how to most effectively leverage your mobile marketing campaigns? While mobile is an incredible new way to distribute content and reach customers, it also presents a unique challenge when it comes to measuring th…
August 18th, 2011 | by Scott Knaster | published in Google Code
By Christian Stefansen, Native Client TeamWouldn’t it be great if you could create web apps using your existing C and C++ code? Native Client lets you do just that, and it is now enabled for Chrome Web Store apps in Google Chrome’s beta channel.Nat…