What is next for OpenSocial
I’m at the Google IO conference, currently in the “What’s next for OpenSocial” presentation. I’m going to try and live blog this:
Speaker: How to balance dictatorship and anarchy…
OpenSocial 0.8 has been release, see http://opensocial.org
Enhancements to JS and XML definitions, RESTful APIs, Templating language
JS/XML:
Main thing: Cleanup and convenience (Gadgets XML, gedgets.* opensocial.*)
InlinedMessage bundles (languages, i18ln)
Server rendering Gadgets can preload data (ServerSide), improves perceived performance since Gadget doesn’t need to make async XHR to query data
OAuth supported
John Panzer on stage for talk on RESTful APis
Access to new environments (Mobile, etc)
Discovery via XRDS-Simple (Same as OpenID)
Authentication + Authorization: OAuth (Authorizing third party code to act on behalf of user)
Data: People, Activites, AppData, Groups
Fomats: JSON, Atom XML
RESTful API provides facilities for: Messaging, Concurrency, Batching
Templating Language and tags:
Goals: Easy to develop, Secure (XSS Security preventions), Fast (Pre-Process server side), OpenSocial-Style, Can build an entire application
Template mime type is text/os-template — defines inline template section, template is valid xml snippet , uses JSP expression language.
Containers can provide their own template tag libraries…(YouTube could provide its own tags for exmaple.
Filed under: Semantic Web




