SlideShare a Scribd company logo
OpenSocial
   China - October 2008


Arne Roomann-Kurrik
Developer Relations

Jacky Wang
Software Engineer




                          1
OpenSocial’s goal:
Make the web more social




                           2
What does “social” mean?




            “Eliette, what do you do with your friends?”


                                                           3
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             4
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             5
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             6
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             7
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             8
What does “social” mean?




    This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License
                                                                                                             9
What does “social” mean?




           “Internet, what do you do with your friends?”

                                                           10
“We look at each other”




                          11
“Talking”




            12
“Laughing”




             13
“We help each other”




                       14
“We read together”




                     15
“We do projects together”

                            16
The social internet
A social website..
  • Provides a feature that becomes more engaging as the number of users
    grows.
  • Uses relationships between people to present users interesting
    information.




                                                                    17
The social internet
Some social websites...




                          18
The social internet
A social website..
  • Has overhead to manage users and relationships.
  • Grows slowly because users must sign up to use the site.

What if we remove
the overhead?
  • Developers can focus
    on providing
    features, not
    managing users.




                                                               19
The social internet
A social network..
  • Manages large numbers of users and relationships.
  • Is slow to add new features.




                                                        20
The social internet
Many social networks...




                          21
The social internet
How do we add new features to social networks?
 • Make the social network a platform.
 • Give creative developers the tools to add the features themselves.




                                                                        22
The social internet
A social application...
  • Lets the social network manage users and relationships.
  • Adds new features to the social network.
  • Lets users “install” the application without signing up for new accounts.
  • Grows quickly because users are already communicating with each
    other.




                                                                          23
The social internet
Lots of social apps...




                         24
Need for a social API
How do we put apps in social networks?




                                         25
A day in the life of a social app developer




                                              26
A day in the life of a social app developer




                                              27
A day in the life of a social app developer




                                              28
A day in the life of a social app developer




                                              29
A day in the life of a social app developer




                                              30
A day in the life of a social app developer




                                              31
Introduction to OpenSocial
Numbers:
 • 19+ implemented Containers
 • 40+ committed Containers
 • 3000+ applications
 • 400,000,000+ of users

In China:




                                32
The OpenSocial APIs
Versions:
  • 0.6 - Client-side APIs introduced
  • 0.7 - Server-side APIs introduced
  • 0.81 (current) - Server-side APIs finalized

Client-side:
  • Gadgets XML
  • Gadgets JavaScript
  • OpenSocial JavaScript

Server-side:
 • RESTful protocol
 • RPC protocol



                                                  33
Gadgets
Not widgets, not sprockets, not gidgets, not wadgets




                                                       34
Gadgets
A gadget spec:
  • Is an XML file.
  • Defines metadata about an OpenSocial app.
  • Is highly cacheable and does not need a high performance server.

Gadgets use existing web standards
 • XML to define metadata.
 • HTML for markup.
 • JavaScript for interactivity.
 • CSS for presentation.




                                                                       35
Gadgets
A gadget server:
  • Takes the gadget spec as input.
  • Performs optimizations on the gadget spec.
  • Outputs HTML, JavaScript, and CSS as one document.




                                                         36
Gadgets

A container:
  • Displays the social network’s user interface.
  • Opens an IFrame to the rendered gadget.




Containers and gadget
servers are both run by
the social network, but
do not need to be on
the same machine, or
even domain.


                                                    37
Gadgets
Example gadget XML spec:
 • Uses HTML to print “Hello World”.
 • Colors the text red with CSS.
 • Dynamically adjusts the height of the gadget with JavaScript.
     <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?>
     <Module>
       <ModulePrefs title=quot;Hello World!quot;>
         <Require feature=quot;dynamic-heightquot; />
       </ModulePrefs>
       <Content type=quot;htmlquot;>
         <![CDATA[
           <h1>Hello World</h1>
           <style type=quot;text/cssquot;>
             h1 { color: #dd0000; }
           </style>
           <script type=quot;text/javascriptquot;>
             gadgets.window.adjustHeight();
           </script>
         ]]>
       </Content>
     </Module>
                                                                   38
Gadgets
Requesting the gadget XML spec:
 1. The client requests an app to be rendered.




                                                 39
Gadgets
Requesting the gadget XML spec:
 1. The client requests an app to be rendered.
 2. The container fetches the gadget XML spec from its host.




                                                               40
Gadgets
Requesting the gadget XML spec:
 1. The client requests an app to be rendered.
 2. The container fetches the gadget XML spec from its host.
 3. The container renders the gadget into HTML, which is displayed
   to the client.




                                                                     41
Gadgets
Requesting the gadget XML spec:
 • Because the gadget spec is simple, it can be cached easily.
 • Caching reduces the load on your server, great when you have millions
   of users.




                                                                     42
Gadgets
Requesting a cached gadget XML spec:
 1.The client requests an app to be rendered. The container already
   has a copy of the spec stored in its cache.




                                                                      43
Gadgets
Requesting a cached gadget XML spec:
 1.The client requests an app to be rendered. The container already
   has a copy of the spec stored in its cache.
 2.The container renders the gadget into HTML, which is displayed
   to the client.




                                                                      44
Gadgets
What kind of rewriting is done by the gadget server?
 • Rewrite links to use content proxies.
 • Rewrite relative links to full paths (some containers).
 • Return only content for the current view.




                                                             45
Gadgets
What are views?
 • Gadgets can render in different locations on a container.
 • Rendering area changes from small to large.
 • Certain pages might be public, some are private.
 • Containers may have different policies depending on the page,
   especially when the gadget displays ads.
 • Views provide a way for gadgets to provide different functionality
   depending on where it is rendered.




                                                                        46
Gadgets




iGoogle quot;homequot; view:
  • On iGoogle, the quot;homequot; view is a small,
    private page that does not allow ads.

                                              47
Gadgets




          iGoogle quot;canvasquot; view:
            • Large private view, allows ads.


                                                48
Gadgets
Working with views in the gadget XML:
 • <Content> sections are repeated for each view.
 • Add a view=quot;view namequot; attribute to each section.
 • Content sections may support multiple views, for example
   view=quot;home,canvasquot;
    <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?>
    <Module>
      <ModulePrefs title=quot;Hello World!quot;>
        <Require feature=quot;dynamic-heightquot; />
      </ModulePrefs>
      <Content type=quot;htmlquot; view=quot;homequot;>
        <![CDATA[
          ...
        ]]>
      </Content>
      <Content type=quot;htmlquot; view=quot;canvasquot;>
        <![CDATA[
          ...
        ]]>
      </Content>
    </Module>
                                                              49
Gadgets
JavaScript utility functions for gadgets:
  • gadgets.io.makeRequest()
    Make cross-domain AJAX calls to remote servers.
  • gadgets.json.parse() and gadgets.json.stringify()
    Native JSON support.
  • gadgets.util.escapeString()
    Make text safe for display via innerHTML.
  • gadgets.util.registerOnLoadHandler()
    Execute code when the page is finished loading.




                                                        50
Gadgets

gadgets.io.makeRequest():
  • Make cross-domain AJAX calls to remote servers.


Remote content:
 • Most interesting gadgets will need to
   work with content stored on different
   servers.
 • AJAX cannot cross domains, so you
   cannot request content from your own
   server.
 • JSONP is only really good for one-way
   data transfer.
 • Gadgets with millions of users can
   overwhelm a remote site.

                                                      51
Gadgets
Requesting remote content:
 1.The rendered app calls gadgets.io.makeRequest() to fetch
   remote content. This call is sent to the container.




                                                              52
Gadgets
Requesting remote content:
 1.The rendered app calls gadgets.io.makeRequest() to fetch
   remote content. This call is sent to the container.
 2.The container requests content from the specified URL.




                                                              53
Gadgets
Requesting remote content:
 1.The rendered app calls gadgets.io.makeRequest() to fetch
   remote content. This call is sent to the container.
 2.The container requests content from the specified URL.
 3.The container returns the response to the application, which renders
   the data.




                                                                      54
Gadgets

Add extra features to your gadget:
 • dynamic-height - Change the size of your gadget in the container.
 • views - Navigate between different surfaces of the container.
 • skins - Make your gadget change its styles to match the container.
 • Containers may offer custom features...
           <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?>
           <Module>
             <ModulePrefs title=quot;Hello World!quot;>
               <Require feature=quot;dynamic-heightquot; />
             </ModulePrefs>
             <Content type=quot;htmlquot;>
               <![CDATA[
                 ...
               ]]>
             </Content>
           </Module>




                                                                        55
Gadgets



          <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?>
          <Module>
            <ModulePrefs title=quot;Hello Social!quot;>
              <Require feature=quot;opensocial-0.8quot; />
            </ModulePrefs>
            <Content type=quot;htmlquot;>
              <![CDATA[
                ...
              ]]>
            </Content>
          </Module>




    The OpenSocial JavaScript API is a gadget feature, too!




                                                              56
The OpenSocial JavaScript API
“It's people!”




                                57
The OpenSocial JavaScript API
Representing users:
 • Client-side, users must work with the VIEWER and the OWNER.




                                                                 58
The OpenSocial JavaScript API
Multiple personalities:
 • When you visit your own profile, you are both the VIEWER and the
   OWNER.




                                                                      59
The OpenSocial JavaScript API
 OpenSocial requests:
  • An OpenSocial DataRequest is created.
  • Requests are added to the DataRequest.
  • The DataRequest is sent to the server asynchronously.
  • When the request finishes, the supplied callback will be called.
function request() {
   var req = opensocial.newDataRequest();
   req.add(req.newFetchPersonRequest(quot;OWNERquot;), quot;get_ownerquot;);
   req.add(req.newFetchPersonRequest(quot;VIEWERquot;), quot;get_viewerquot;);
   req.add(req.newFetchActivitiesRequest(quot;VIEWERquot;), quot;vactivitiesquot;);
   req.add(req.newFetchPersonAppDataRequest(quot;OWNERquot;, quot;*quot;), quot;odataquot;);
   ...
   req.send(response);
};

function response(data) { ... };

gadgets.util.registerOnLoadHandler(request);



                                                                       60
The OpenSocial JavaScript API
OpenSocial responses:
 • Responses are bundled according to the keys specified in the request.
 • Check for an error at the global response level.
 • Check for an error at the specific response level.
 • Use getData() to retrieve the actual information in a request.

         function response(data) {
           if (data.hadError()) {
             if (data.get(quot;get_ownerquot;).hadError()) {
               ...
             }
             if (data.get(quot;get_viewerquot;).hadError()) {
               ...
             }
             ...
           }
           var owner = data.get(quot;get_ownerquot;).getData();
           var viewer = data.get(quot;get_viewerquot;).getData();
         };


                                                                      61
The OpenSocial JavaScript API
Working with people:
 • opensocial.Person - JavaScript representation of a user.




                                                              62
The OpenSocial JavaScript API
Request one person:
   req.add(req.newFetchPersonRequest(idspec, opt_params), quot;keyquot;);

 • idspec can be either “VIEWER”, “OWNER” or an ID number.
 • opt_params contains extra request parameters, such as which profile
   fields to fetch.

newFetchPersonRequest responses:
   var owner = data.get(quot;keyquot;).getData();
   alert(owner.getDisplayName());

 • Data contains a single opensocial.Person
   object.
 • Person objects can contain lots of information,
   such as addresses, companies, phone numbers,
   favorite movies, and thumbnail urls.


                                                                     63
The OpenSocial JavaScript API
Methods available on an OpenSocial Person:

• getDisplayName()
  Gets a text display name for this person; guaranteed to return a useful
  string.
• getField(key, opt_params)
  Gets data for this person that is associated with the specified key.
• getId()
  Gets an ID that can be permanently associated with this person.
• isOwner()
  Returns true if this person object represents the owner
  of the current page.
• isViewer()
  Returns true if this person object represents the
  currently logged in user.




                                                                            64
The OpenSocial JavaScript API
 An OpenSocial Person's fields:
• ABOUT_ME         • JOB_INTERESTS         •   SEXUAL_ORIENTATION
• ACTIVITIES       • JOBS                  •   SMOKER
• ADDRESSES        • LANGUAGES_SPOKEN      •   SPORTS
• AGE              • LIVING_ARRANGEMENT    •   STATUS
• BODY_TYPE        • LOOKING_FOR           •   TAGS
• BOOKS            • MOVIES                •   THUMBNAIL_URL
• CARS             • MUSIC                 •   TIME_ZONE
• CHILDREN         • NAME                  •   TURN_OFFS
• CURRENT_LOCATION • NETWORK_PRESENCE      •   TURN_ONS
• DATE_OF_BIRTH    • NICKNAME              •   TV_SHOWS
• DRINKER          • PETS                  •   URLS
• EMAILS           • PHONE_NUMBERS
• ETHNICITY        • POLITICAL_VIEWS
• FASHION          • PROFILE_SONG
• FOOD             • PROFILE_URL
• GENDER           • PROFILE_VIDEO
• HAPPIEST_WHEN    • QUOTES
• HAS_APP          • RELATIONSHIP_STATUS
• HEROES           • RELIGION
• HUMOR            • ROMANCE
• ID               • SCARED_OF
• INTERESTS        • SCHOOLS
                                                                    65
The OpenSocial JavaScript API
Working with people:
 • A Collection represents many opensocial.Person objects.




                                                             66
The OpenSocial JavaScript API
Request many people:
   var idspec = opensocial.newIdSpec({
     “userId” : “OWNER”,
     “groupId” : “FRIENDS”
   });
   req.add(req.newFetchPeopleRequest(idspec, opt_params), quot;keyquot;);

 • idspec is an object that can represent groups of people.    “userId” can be
   “VIEWER” or “OWNER” or an ID, and “groupId” can be “SELF”,
   “FRIENDS”, or the name of a group.
 • opt_params contains extra request parameters, such as which profile
   fields to fetch, and how to order or filter the returned people.
newFetchPersonRequest responses:
   var owner_friends = data.get(quot;keyquot;).getData();
   owner_friends.each(function (person) {
     alert(person.getDisplayName());
   });
 • Data contains a Collection of opensocial.Person
  objects. Iterate over these by using the each() method.
                                                                          67
The OpenSocial JavaScript API
Working with data:
 • Persistent data gives apps key, value storage directly on the container.
 • String only, but conversion to JSON allows for storage of complex
   objects.
 • Storage per app per user - scales well with growth.
 • Ideal for settings, customizations.




                                                                        68
The OpenSocial JavaScript API
Set persistent data:
   req.add(req.newUpdatePersonAppDataRequest(idspec, key, value));

 • idspec can only be “VIEWER”.
 • key is the name under which this data will be stored.
 • value is a string representing the data to store.




                                                                69
The OpenSocial JavaScript API
Fetch persistent data:
   var idspec = opensocial.newIdSpec({
     quot;userIdquot; : quot;OWNERquot;,
     quot;groupIdquot; : quot;SELFquot;
   });
   req.add(req.newFetchPersonAppDataRequest(idspec, keys),
       quot;keyquot;);
   req.add(req.newFetchPersonRequest(quot;OWNERquot;), quot;ownerkeyquot;);

 • idspec is an object that can represent groups of people, the same as
   newFetchPeopleRequest.
 • keys is a list of persistent data keys to retrieve the data for.
 • The owner is requested because the data returned is indexed by user ID
   and we want the owner’s data.

newFetchPersonAppDataRequest responses:
   var app_data = data.get(quot;keyquot;).getData();
   var value = app_data[owner.getId()][key];

                                                                      70
The OpenSocial JavaScript API
Fetch persistent data:

 • Data is returned as an object indexed by ID number, then as an object
   indexed by key name, even if there is only data returned for one user!
   { quot;1234567890quot; : { quot;key1quot; : quot;value1quot; } }


 • One person, multiple keys:
   {
       quot;1234567890quot; : {
                          quot;key1quot; : quot;value1quot;,
                          quot;key2quot; : quot;value2quot;
                      }
   }


 • Multiple people:
   {
       quot;1234567890quot; : { quot;key1quot; : quot;value1quot; },
       quot;2345678901quot; : { quot;key1quot; : quot;value2quot; }
   }
                                                                       71
The OpenSocial JavaScript API
Working with activities:
 • API to post information about what users are doing with your app.
 • Many containers have support for images and some HTML.
 • Channel to grow your application.




 orkut                     MySpace                   hi5




                                                                       72
The OpenSocial JavaScript API
Post an activity:
   function postActivity(text) {
      var params = {};
      params[opensocial.Activity.Field.TITLE] = text;
      var activity = opensocial.newActivity(params);
      opensocial.requestCreateActivity(activity,
        opensocial.CreateActivityPriority.HIGH, callback);
   };

  • Assign the activity text to the TITLE field.
  • Call opensocial.newActivity() to create a new Activity instance.
  • Call opensocial.requestCreateActivity() to post the activity to the
   container.




                                                                          73
RESTful and RPC protocols
Servers talking to servers




                             74
RESTful and RPC protocols
Opens new development models
 • Background processing.
 • Easier Flash integration.
 • Mobile applications.




                               75
RESTful and RPC protocols
Communication methods:
 • RESTful (Representational State Transfer)
 • RPC (Remote Procedure Call)
Formats:
 • XML
 • JSON
 • AtomPub




                                               76
RESTful and RPC protocols
REST:
 • Resources are URLs.
Example - People:
 • All people connected to the given user:
       /people/{guid}/@all

  • All friends of the given user:
       /people/{guid}/@friends

  • Profile of the given user:
       /people/{guid}/@self

  • Profile of the authenticated user:
       /people/@me/@self

  • Supported Person fields:
       /people/@supportedFields


                                             77
RESTful and RPC protocols
Querystring parameters customize requests:
 • Response format (JSON, XML, AtomPub)
   format={format}


 • Request extra fields
   fields={-join|,|field}.


 • Filtering:
   filterBy={fieldname}
   filterOp={operation}
   filterValue={value}
   updatedSince={xsdDateTime}
   networkDistance={networkDistance}

 • Paging:
   count={count}
   sortBy={fieldname}
   sortOrder={order}
   startIndex={startIndex}
                                             78
RESTful and RPC protocols
REST responses (Person):
 • JSON:
 {
     quot;idquot; : quot;example.org:34KJDCSKJN2HHF0DW20394quot;,
     quot;displayNamequot; : quot;Janeyquot;,
     quot;namequot; : {quot;unstructuredquot; : quot;Jane Doequot;},
     quot;genderquot; : quot;femalequot;
 }

 • XML:
 <person xmlns=quot;http://ns.opensocial.org/2008/opensocialquot;>
   <id></id>
   <displayName></displayName>
   <name>
     <unstructured>Jane Doe</unstructured>
   </name>
   <gender>female</gender>
 </person>




                                                             79
RESTful and RPC protocols
REST responses (Person):
 • AtomPub:
 <entry xmlns=quot;http://www.w3.org/2005/Atomquot;>
   <content type=quot;application/xmlquot;>
     <person xmlns=quot;http://ns.opensocial.org/2008/opensocialquot;>
       <name>
          <unstructured>Jane Doe</unstructured>
       </name>
       <gender>female</gender>
     </person>
   </content>
   <title/>
   <updated>2003-12-13T18:30:02Z</updated>
   <author/>
   <id>urn:guid:example.org:34KJDCSKJN2HHF0DW20394</id>
 </entry>




                                                                 80
RESTful and RPC protocols
REST:
 • Perform operations using different HTTP methods on each URL.

               CRUD:            HTTP:
                • Create         • POST
                • Retrieve       • GET
                • Update         • PUT
                • Delete         • DELETE




                                                                  81
RESTful and RPC protocols
REST has some disadvantages:
 • Batch support requires multiple HTTP requests, or a contrived URL
   scheme.
 • Specifying multiple users via querystring is difficult. Is
   ?uid=1234,5678 the same resource as ?uid=5678,1234 ?




                                                                       82
RESTful and RPC protocols
RPC:
 • One endpoint - parameters specify methods to call.
 • Batch support.
 • Specify collections of users through passed arguments, not URLs.

Example - Fetch current user:
  • Request                        • Response
POST /rpc HTTP/1.1               HTTP/1.x 207 Multi-Status
Host: api.example.org            Content-Type: application/json
Authorization: <Auth token>      {
Content-Type: application/json       quot;idquot; : quot;myselfquot;
{                                    quot;resultquot; : {
  quot;methodquot; : quot;people.getquot;,             quot;idquot; : quot;example.org:34KJDCSKJN2HHF0DW20394quot;,
  quot;idquot; : quot;myselfquot;                      quot;namequot; : { quot;unstructuredquot; : quot;Jane Doequot;},
                                       quot;genderquot; : quot;femalequot;
  quot;paramsquot; : {
                                   }
    quot;useridquot; : quot;@mequot;,
                                 }
    quot;groupidquot; : quot;@selfquot;
  }
}



                                                                                 83
RESTful and RPC protocols
Authentication:
 • Both protocols use OAuth to identify users and apps.
 • Depending on what the application needs to do, it can use two-legged
   or three-legged OAuth.
Two-legged OAuth:
 • The application authenticates directly with the container.
 • Perform non-user specific operations:
    • Update persistent data for app users.
    • Can request information for users who have shared their profile
      information with the app.

Three-legged OAuth:
 • The user tells the container to give profile access to the application.
 • Perform user specific operations:
    • Post activities.
    • Fetch friends of the current user.

                                                                        84
RESTful and RPC protocols
Client libraries are being created for PHP, Java, and Python.
  • Help you connect to OpenSocial containers, and work with social
    data on your server.


Sample: log into a container:




                                                                      85
RESTful and RPC protocols
RESTful and RPC use OAuth for authentication
 • OAuth is an open standard.
 • Client libraries will help make this process easier for developers.

Sample: use OAuth to get an access token for a user:




                                                                         86
RESTful and RPC protocols
 • Once OAuth is used, you can store a user token for later access.

Sample: use an existing token:




                                                                      87
RESTful and RPC protocols
 • Once authentication has happened, requests are easy:
Sample: Fetch the current user:




                                                          88
RESTful and RPC protocols
Sample: Fetch the current user’s friends:




                                            89
OpenSocial Tools
What sets us apart from the animals




                                      90
Shindig
Writing a gadget server is difficult:
 • Fast changing API - hard to keep up.
 • Standardization is hard to get right.
 • Costs ¥ / !




                                           91
Shindig
Apache Shindig to the rescue!
 • Open Source project.
 • Available in Java and PHP.
 • Run by itself and connect to an
   existing social site to add
   OpenSocial support.
 • Goal: Launch a
   new (simple)
   container in under
   an hour’s worth
   of work




http://incubator.apache.org/shindig/
                                       92
OpenSocial Dev App
Development tool to test out JS code in different containers




http://osda.appspot.com
                                                               93
Upcoming Features
Caja and Templates




                     94
Caja
When JavaScript goes bad
 • Gadgets can be a new vector for phishing, spam, malware.
 • Social spread of gadgets can spread bad gadgets too.
 • Caja reduces threats with a JavaScript
   sanitizer as an additional quot;sandboxquot;
   on top of iFrame protection.




                                                              95
Caja
Caja is:
 • A capability-based Javascript sanitizer.
 • An Open Source project from Google.
 • Optional but recommended for
   OpenSocial containers.
 • Will eventually be secure enough
   to run gadgets
   inline instead of in iframes.




http://code.google.com/p/google-caja/
                                              96
Templates
Need for a templating language:
 • Developers need a simple way to convert OpenSocial data to HTML.
 • DOM manipulation is slow and ugly.
 • innerHTML is unsafe.




                                                                  97
Templates
<script type=quot;text/javascriptquot;
  src=quot;http://ostemplates-demo.appspot.com/ostemplates.jsquot;></script>

<script type=quot;text/os-templatequot;>
  <b>${owner.displayName}'s friends</b>
  <ul>
    <li repeat=quot;friendsquot;>${displayName}</li>
  </ul>
</script>

<script type=quot;text/javascriptquot;>
   function loadData() {
     var req = opensocial.newDataRequest();
     req.add(req.newFetchPersonRequest('OWNER'), 'owner');
     var idSpecFriends = opensocial.newIdSpec(
       {'userId':'OWNER', 'groupId':'FRIENDS'});
     req.add(req.newFetchPeopleRequest(idSpecFriends), 'friends');
     req.send(function(data) {
       os.Container.processDocument(data);
     });
   }
   gadgets.util.registerOnLoadHandler(loadData);
</script>
                                     http://ostemplates-demo.appspot.com/
                                                                     98
Templates
Templates developer application available:




http://ostemplates-devapp.appspot.com/
                                             99
The OpenSocial specification process
“We can fix it, we have the technology”




                                          100
The OpenSocial specification process




                                       101
The OpenSocial specification process




                                       102
The OpenSocial specification process




                                       103
The OpenSocial specification process




                                       104
The OpenSocial specification process




                                       105
Challenges
Nobody said this was going to be easy




                                        106
Challenges
Cross container development is still tricky:
 • Containers may not follow the standard.
 • Containers may follow the standard but have different policies.
 • Follow best practices:
   http://tinyurl.com/4nuzll




                                                                     107
Challenges
No central directory
 • Hard for apps to spread to many containers.
 • Apps need to work with different install processes.
 • Directory approval requirements vary from container to container.




                                                                       108
Challenges
Scaling is hard:
 • Easy to start and get some users.




                                       109
Challenges
Scaling is hard:
 • Being popular on one social network
   can push your server to the limit...




                                          110
Challenges
Scaling is hard:
 • ...being popular on many networks
   will push you right over.




                                       111
Resources




            112
Resources

•   OpenSocial Tutorial: http://rurl.org/ss3

•   OpenSocial Spec, Foundation, Reference: http://opensocial.org

•   Caja: http://code.google.com/p/google-caja/

•   Shindig: http://incubator.apache.org/shindig/

•   OpenSocial Across Containers video: http://tinyurl.com/4nuzll

•   OpenSocial Templates: http://ostemplates-demo.appspot.com/

•   OpenSocial Dev App: http://osda.appspot.com

•   Partuza: http://partuza.nl

•   OpenSocial Specification Proposals:
    http://groups.google.com/group/opensocial-and-gadgets-spec/topics


                                                                        113

More Related Content

Similar to Open Social Tech Talk Beijing

RIAction Social Applications in the Cloud 20090226
RIAction Social Applications in the Cloud 20090226RIAction Social Applications in the Cloud 20090226
RIAction Social Applications in the Cloud 20090226
Vinoaj Vijeyakumaar
 
Open Social Summit Korea Overview
Open Social Summit Korea OverviewOpen Social Summit Korea Overview
Open Social Summit Korea Overview
Chris Schalk
 
Futuropolis 2058 Singapore - OpenSocial, a standard for the social web
Futuropolis 2058 Singapore - OpenSocial, a standard for the social webFuturopolis 2058 Singapore - OpenSocial, a standard for the social web
Futuropolis 2058 Singapore - OpenSocial, a standard for the social web
Patrick Chanezon
 
State Of Opensocial
State Of OpensocialState Of Opensocial
State Of Opensocial
Patrick Chanezon
 
Creating Value In Social Networking
Creating Value In Social NetworkingCreating Value In Social Networking
Creating Value In Social Networking
Lars Trieloff
 
Barcamphanoi Opensocial Application Development
Barcamphanoi Opensocial Application DevelopmentBarcamphanoi Opensocial Application Development
Barcamphanoi Opensocial Application Development
Hoat Le
 
Hey open source, don’t forget the user! - by Chad Kieffer
Hey open source,  don’t forget the user! - by Chad KiefferHey open source,  don’t forget the user! - by Chad Kieffer
Hey open source, don’t forget the user! - by Chad Kieffer
dmthompson
 
Goodle Developer Days Madrid 2008 - Open Social Update
Goodle Developer Days Madrid 2008 - Open Social UpdateGoodle Developer Days Madrid 2008 - Open Social Update
Goodle Developer Days Madrid 2008 - Open Social Update
Patrick Chanezon
 
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
Chris Schalk
 
Introduction to Enterprise 2.0
Introduction to Enterprise 2.0Introduction to Enterprise 2.0
Introduction to Enterprise 2.0
David Saitta
 
Integrating OpenSocial & SalesForce.com
Integrating OpenSocial & SalesForce.comIntegrating OpenSocial & SalesForce.com
Integrating OpenSocial & SalesForce.com
Chris Schalk
 
Cohere: Towards Web 2.0 Argumentation
Cohere: Towards Web 2.0 ArgumentationCohere: Towards Web 2.0 Argumentation
Cohere: Towards Web 2.0 Argumentation
Simon Buckingham Shum
 
Open Social Shindig Preso for FB and OpenSocial Meetup
Open Social Shindig Preso for FB and OpenSocial MeetupOpen Social Shindig Preso for FB and OpenSocial Meetup
Open Social Shindig Preso for FB and OpenSocial Meetup
Chris Schalk
 
Devfest09 OpenSocial Enterprise
Devfest09 OpenSocial EnterpriseDevfest09 OpenSocial Enterprise
Devfest09 OpenSocial Enterprise
Chris Schalk
 
Mobile (App) Development with Sitecore
Mobile (App) Development with SitecoreMobile (App) Development with Sitecore
Mobile (App) Development with Sitecore
Pieter Brinkman
 
Pieter Brinkman - My first mobile experience From mobile no no, to mobile go ...
Pieter Brinkman - My first mobile experienceFrom mobile no no, to mobile go ...Pieter Brinkman - My first mobile experienceFrom mobile no no, to mobile go ...
Pieter Brinkman - My first mobile experience From mobile no no, to mobile go ...
SUGCON
 
Goodle Developer Days London 2008 - Open Social Update
Goodle Developer Days London 2008 - Open Social UpdateGoodle Developer Days London 2008 - Open Social Update
Goodle Developer Days London 2008 - Open Social Update
Patrick Chanezon
 
What is Web 2.0?
What is Web 2.0?What is Web 2.0?
What is Web 2.0?
Hillary Hartley
 
Building Social Applications using Zembly
Building Social Applications using ZemblyBuilding Social Applications using Zembly
Building Social Applications using Zembly
Craig Dickson
 
Goodle Developer Days Munich 2008 - Open Social Update
Goodle Developer Days Munich 2008 - Open Social UpdateGoodle Developer Days Munich 2008 - Open Social Update
Goodle Developer Days Munich 2008 - Open Social Update
Patrick Chanezon
 

Similar to Open Social Tech Talk Beijing (20)

RIAction Social Applications in the Cloud 20090226
RIAction Social Applications in the Cloud 20090226RIAction Social Applications in the Cloud 20090226
RIAction Social Applications in the Cloud 20090226
 
Open Social Summit Korea Overview
Open Social Summit Korea OverviewOpen Social Summit Korea Overview
Open Social Summit Korea Overview
 
Futuropolis 2058 Singapore - OpenSocial, a standard for the social web
Futuropolis 2058 Singapore - OpenSocial, a standard for the social webFuturopolis 2058 Singapore - OpenSocial, a standard for the social web
Futuropolis 2058 Singapore - OpenSocial, a standard for the social web
 
State Of Opensocial
State Of OpensocialState Of Opensocial
State Of Opensocial
 
Creating Value In Social Networking
Creating Value In Social NetworkingCreating Value In Social Networking
Creating Value In Social Networking
 
Barcamphanoi Opensocial Application Development
Barcamphanoi Opensocial Application DevelopmentBarcamphanoi Opensocial Application Development
Barcamphanoi Opensocial Application Development
 
Hey open source, don’t forget the user! - by Chad Kieffer
Hey open source,  don’t forget the user! - by Chad KiefferHey open source,  don’t forget the user! - by Chad Kieffer
Hey open source, don’t forget the user! - by Chad Kieffer
 
Goodle Developer Days Madrid 2008 - Open Social Update
Goodle Developer Days Madrid 2008 - Open Social UpdateGoodle Developer Days Madrid 2008 - Open Social Update
Goodle Developer Days Madrid 2008 - Open Social Update
 
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
Open Social Technical Update for Java developers - Presented at sv-gtug.org m...
 
Introduction to Enterprise 2.0
Introduction to Enterprise 2.0Introduction to Enterprise 2.0
Introduction to Enterprise 2.0
 
Integrating OpenSocial & SalesForce.com
Integrating OpenSocial & SalesForce.comIntegrating OpenSocial & SalesForce.com
Integrating OpenSocial & SalesForce.com
 
Cohere: Towards Web 2.0 Argumentation
Cohere: Towards Web 2.0 ArgumentationCohere: Towards Web 2.0 Argumentation
Cohere: Towards Web 2.0 Argumentation
 
Open Social Shindig Preso for FB and OpenSocial Meetup
Open Social Shindig Preso for FB and OpenSocial MeetupOpen Social Shindig Preso for FB and OpenSocial Meetup
Open Social Shindig Preso for FB and OpenSocial Meetup
 
Devfest09 OpenSocial Enterprise
Devfest09 OpenSocial EnterpriseDevfest09 OpenSocial Enterprise
Devfest09 OpenSocial Enterprise
 
Mobile (App) Development with Sitecore
Mobile (App) Development with SitecoreMobile (App) Development with Sitecore
Mobile (App) Development with Sitecore
 
Pieter Brinkman - My first mobile experience From mobile no no, to mobile go ...
Pieter Brinkman - My first mobile experienceFrom mobile no no, to mobile go ...Pieter Brinkman - My first mobile experienceFrom mobile no no, to mobile go ...
Pieter Brinkman - My first mobile experience From mobile no no, to mobile go ...
 
Goodle Developer Days London 2008 - Open Social Update
Goodle Developer Days London 2008 - Open Social UpdateGoodle Developer Days London 2008 - Open Social Update
Goodle Developer Days London 2008 - Open Social Update
 
What is Web 2.0?
What is Web 2.0?What is Web 2.0?
What is Web 2.0?
 
Building Social Applications using Zembly
Building Social Applications using ZemblyBuilding Social Applications using Zembly
Building Social Applications using Zembly
 
Goodle Developer Days Munich 2008 - Open Social Update
Goodle Developer Days Munich 2008 - Open Social UpdateGoodle Developer Days Munich 2008 - Open Social Update
Goodle Developer Days Munich 2008 - Open Social Update
 

Recently uploaded

Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS  at Code Europe 2024Introduction of Cybersecurity with OSS  at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Hiroshi SHIBATA
 
Fueling AI with Great Data with Airbyte Webinar
Fueling AI with Great Data with Airbyte WebinarFueling AI with Great Data with Airbyte Webinar
Fueling AI with Great Data with Airbyte Webinar
Zilliz
 
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation TechniquesWeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Postman
 
Mariano G Tinti - Decoding SpaceX
Mariano G Tinti - Decoding SpaceXMariano G Tinti - Decoding SpaceX
Mariano G Tinti - Decoding SpaceX
Mariano Tinti
 
Project Management Semester Long Project - Acuity
Project Management Semester Long Project - AcuityProject Management Semester Long Project - Acuity
Project Management Semester Long Project - Acuity
jpupo2018
 
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with SlackLet's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
shyamraj55
 
UI5 Controls simplified - UI5con2024 presentation
UI5 Controls simplified - UI5con2024 presentationUI5 Controls simplified - UI5con2024 presentation
UI5 Controls simplified - UI5con2024 presentation
Wouter Lemaire
 
How to use Firebase Data Connect For Flutter
How to use Firebase Data Connect For FlutterHow to use Firebase Data Connect For Flutter
How to use Firebase Data Connect For Flutter
Daiki Mogmet Ito
 
Artificial Intelligence for XMLDevelopment
Artificial Intelligence for XMLDevelopmentArtificial Intelligence for XMLDevelopment
Artificial Intelligence for XMLDevelopment
Octavian Nadolu
 
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Edge AI and Vision Alliance
 
5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides
DanBrown980551
 
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024
Jason Packer
 
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 202420240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Matthew Sinclair
 
GenAI Pilot Implementation in the organizations
GenAI Pilot Implementation in the organizationsGenAI Pilot Implementation in the organizations
GenAI Pilot Implementation in the organizations
kumardaparthi1024
 
Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)
Jakub Marek
 
June Patch Tuesday
June Patch TuesdayJune Patch Tuesday
June Patch Tuesday
Ivanti
 
20240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 202420240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 2024
Matthew Sinclair
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
akankshawande
 
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup SlidesProgramming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Zilliz
 
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptxHow to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
danishmna97
 

Recently uploaded (20)

Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS  at Code Europe 2024Introduction of Cybersecurity with OSS  at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
 
Fueling AI with Great Data with Airbyte Webinar
Fueling AI with Great Data with Airbyte WebinarFueling AI with Great Data with Airbyte Webinar
Fueling AI with Great Data with Airbyte Webinar
 
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation TechniquesWeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
 
Mariano G Tinti - Decoding SpaceX
Mariano G Tinti - Decoding SpaceXMariano G Tinti - Decoding SpaceX
Mariano G Tinti - Decoding SpaceX
 
Project Management Semester Long Project - Acuity
Project Management Semester Long Project - AcuityProject Management Semester Long Project - Acuity
Project Management Semester Long Project - Acuity
 
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with SlackLet's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
 
UI5 Controls simplified - UI5con2024 presentation
UI5 Controls simplified - UI5con2024 presentationUI5 Controls simplified - UI5con2024 presentation
UI5 Controls simplified - UI5con2024 presentation
 
How to use Firebase Data Connect For Flutter
How to use Firebase Data Connect For FlutterHow to use Firebase Data Connect For Flutter
How to use Firebase Data Connect For Flutter
 
Artificial Intelligence for XMLDevelopment
Artificial Intelligence for XMLDevelopmentArtificial Intelligence for XMLDevelopment
Artificial Intelligence for XMLDevelopment
 
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
 
5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides
 
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024
 
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 202420240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
 
GenAI Pilot Implementation in the organizations
GenAI Pilot Implementation in the organizationsGenAI Pilot Implementation in the organizations
GenAI Pilot Implementation in the organizations
 
Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)
 
June Patch Tuesday
June Patch TuesdayJune Patch Tuesday
June Patch Tuesday
 
20240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 202420240607 QFM018 Elixir Reading List May 2024
20240607 QFM018 Elixir Reading List May 2024
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
 
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup SlidesProgramming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
 
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptxHow to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
 

Open Social Tech Talk Beijing

  • 1. OpenSocial China - October 2008 Arne Roomann-Kurrik Developer Relations Jacky Wang Software Engineer 1
  • 2. OpenSocial’s goal: Make the web more social 2
  • 3. What does “social” mean? “Eliette, what do you do with your friends?” 3
  • 4. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 4
  • 5. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 5
  • 6. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 6
  • 7. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 7
  • 8. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 8
  • 9. What does “social” mean? This work by Eliette Chanezon is licensed under a Creative Commons Attribution-Share Alike 3.0 License 9
  • 10. What does “social” mean? “Internet, what do you do with your friends?” 10
  • 11. “We look at each other” 11
  • 14. “We help each other” 14
  • 16. “We do projects together” 16
  • 17. The social internet A social website.. • Provides a feature that becomes more engaging as the number of users grows. • Uses relationships between people to present users interesting information. 17
  • 18. The social internet Some social websites... 18
  • 19. The social internet A social website.. • Has overhead to manage users and relationships. • Grows slowly because users must sign up to use the site. What if we remove the overhead? • Developers can focus on providing features, not managing users. 19
  • 20. The social internet A social network.. • Manages large numbers of users and relationships. • Is slow to add new features. 20
  • 21. The social internet Many social networks... 21
  • 22. The social internet How do we add new features to social networks? • Make the social network a platform. • Give creative developers the tools to add the features themselves. 22
  • 23. The social internet A social application... • Lets the social network manage users and relationships. • Adds new features to the social network. • Lets users “install” the application without signing up for new accounts. • Grows quickly because users are already communicating with each other. 23
  • 24. The social internet Lots of social apps... 24
  • 25. Need for a social API How do we put apps in social networks? 25
  • 26. A day in the life of a social app developer 26
  • 27. A day in the life of a social app developer 27
  • 28. A day in the life of a social app developer 28
  • 29. A day in the life of a social app developer 29
  • 30. A day in the life of a social app developer 30
  • 31. A day in the life of a social app developer 31
  • 32. Introduction to OpenSocial Numbers: • 19+ implemented Containers • 40+ committed Containers • 3000+ applications • 400,000,000+ of users In China: 32
  • 33. The OpenSocial APIs Versions: • 0.6 - Client-side APIs introduced • 0.7 - Server-side APIs introduced • 0.81 (current) - Server-side APIs finalized Client-side: • Gadgets XML • Gadgets JavaScript • OpenSocial JavaScript Server-side: • RESTful protocol • RPC protocol 33
  • 34. Gadgets Not widgets, not sprockets, not gidgets, not wadgets 34
  • 35. Gadgets A gadget spec: • Is an XML file. • Defines metadata about an OpenSocial app. • Is highly cacheable and does not need a high performance server. Gadgets use existing web standards • XML to define metadata. • HTML for markup. • JavaScript for interactivity. • CSS for presentation. 35
  • 36. Gadgets A gadget server: • Takes the gadget spec as input. • Performs optimizations on the gadget spec. • Outputs HTML, JavaScript, and CSS as one document. 36
  • 37. Gadgets A container: • Displays the social network’s user interface. • Opens an IFrame to the rendered gadget. Containers and gadget servers are both run by the social network, but do not need to be on the same machine, or even domain. 37
  • 38. Gadgets Example gadget XML spec: • Uses HTML to print “Hello World”. • Colors the text red with CSS. • Dynamically adjusts the height of the gadget with JavaScript. <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?> <Module> <ModulePrefs title=quot;Hello World!quot;> <Require feature=quot;dynamic-heightquot; /> </ModulePrefs> <Content type=quot;htmlquot;> <![CDATA[ <h1>Hello World</h1> <style type=quot;text/cssquot;> h1 { color: #dd0000; } </style> <script type=quot;text/javascriptquot;> gadgets.window.adjustHeight(); </script> ]]> </Content> </Module> 38
  • 39. Gadgets Requesting the gadget XML spec: 1. The client requests an app to be rendered. 39
  • 40. Gadgets Requesting the gadget XML spec: 1. The client requests an app to be rendered. 2. The container fetches the gadget XML spec from its host. 40
  • 41. Gadgets Requesting the gadget XML spec: 1. The client requests an app to be rendered. 2. The container fetches the gadget XML spec from its host. 3. The container renders the gadget into HTML, which is displayed to the client. 41
  • 42. Gadgets Requesting the gadget XML spec: • Because the gadget spec is simple, it can be cached easily. • Caching reduces the load on your server, great when you have millions of users. 42
  • 43. Gadgets Requesting a cached gadget XML spec: 1.The client requests an app to be rendered. The container already has a copy of the spec stored in its cache. 43
  • 44. Gadgets Requesting a cached gadget XML spec: 1.The client requests an app to be rendered. The container already has a copy of the spec stored in its cache. 2.The container renders the gadget into HTML, which is displayed to the client. 44
  • 45. Gadgets What kind of rewriting is done by the gadget server? • Rewrite links to use content proxies. • Rewrite relative links to full paths (some containers). • Return only content for the current view. 45
  • 46. Gadgets What are views? • Gadgets can render in different locations on a container. • Rendering area changes from small to large. • Certain pages might be public, some are private. • Containers may have different policies depending on the page, especially when the gadget displays ads. • Views provide a way for gadgets to provide different functionality depending on where it is rendered. 46
  • 47. Gadgets iGoogle quot;homequot; view: • On iGoogle, the quot;homequot; view is a small, private page that does not allow ads. 47
  • 48. Gadgets iGoogle quot;canvasquot; view: • Large private view, allows ads. 48
  • 49. Gadgets Working with views in the gadget XML: • <Content> sections are repeated for each view. • Add a view=quot;view namequot; attribute to each section. • Content sections may support multiple views, for example view=quot;home,canvasquot; <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?> <Module> <ModulePrefs title=quot;Hello World!quot;> <Require feature=quot;dynamic-heightquot; /> </ModulePrefs> <Content type=quot;htmlquot; view=quot;homequot;> <![CDATA[ ... ]]> </Content> <Content type=quot;htmlquot; view=quot;canvasquot;> <![CDATA[ ... ]]> </Content> </Module> 49
  • 50. Gadgets JavaScript utility functions for gadgets: • gadgets.io.makeRequest() Make cross-domain AJAX calls to remote servers. • gadgets.json.parse() and gadgets.json.stringify() Native JSON support. • gadgets.util.escapeString() Make text safe for display via innerHTML. • gadgets.util.registerOnLoadHandler() Execute code when the page is finished loading. 50
  • 51. Gadgets gadgets.io.makeRequest(): • Make cross-domain AJAX calls to remote servers. Remote content: • Most interesting gadgets will need to work with content stored on different servers. • AJAX cannot cross domains, so you cannot request content from your own server. • JSONP is only really good for one-way data transfer. • Gadgets with millions of users can overwhelm a remote site. 51
  • 52. Gadgets Requesting remote content: 1.The rendered app calls gadgets.io.makeRequest() to fetch remote content. This call is sent to the container. 52
  • 53. Gadgets Requesting remote content: 1.The rendered app calls gadgets.io.makeRequest() to fetch remote content. This call is sent to the container. 2.The container requests content from the specified URL. 53
  • 54. Gadgets Requesting remote content: 1.The rendered app calls gadgets.io.makeRequest() to fetch remote content. This call is sent to the container. 2.The container requests content from the specified URL. 3.The container returns the response to the application, which renders the data. 54
  • 55. Gadgets Add extra features to your gadget: • dynamic-height - Change the size of your gadget in the container. • views - Navigate between different surfaces of the container. • skins - Make your gadget change its styles to match the container. • Containers may offer custom features... <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?> <Module> <ModulePrefs title=quot;Hello World!quot;> <Require feature=quot;dynamic-heightquot; /> </ModulePrefs> <Content type=quot;htmlquot;> <![CDATA[ ... ]]> </Content> </Module> 55
  • 56. Gadgets <?xml version=quot;1.0quot; encoding=quot;UTF-8quot; ?> <Module> <ModulePrefs title=quot;Hello Social!quot;> <Require feature=quot;opensocial-0.8quot; /> </ModulePrefs> <Content type=quot;htmlquot;> <![CDATA[ ... ]]> </Content> </Module> The OpenSocial JavaScript API is a gadget feature, too! 56
  • 57. The OpenSocial JavaScript API “It's people!” 57
  • 58. The OpenSocial JavaScript API Representing users: • Client-side, users must work with the VIEWER and the OWNER. 58
  • 59. The OpenSocial JavaScript API Multiple personalities: • When you visit your own profile, you are both the VIEWER and the OWNER. 59
  • 60. The OpenSocial JavaScript API OpenSocial requests: • An OpenSocial DataRequest is created. • Requests are added to the DataRequest. • The DataRequest is sent to the server asynchronously. • When the request finishes, the supplied callback will be called. function request() { var req = opensocial.newDataRequest(); req.add(req.newFetchPersonRequest(quot;OWNERquot;), quot;get_ownerquot;); req.add(req.newFetchPersonRequest(quot;VIEWERquot;), quot;get_viewerquot;); req.add(req.newFetchActivitiesRequest(quot;VIEWERquot;), quot;vactivitiesquot;); req.add(req.newFetchPersonAppDataRequest(quot;OWNERquot;, quot;*quot;), quot;odataquot;); ... req.send(response); }; function response(data) { ... }; gadgets.util.registerOnLoadHandler(request); 60
  • 61. The OpenSocial JavaScript API OpenSocial responses: • Responses are bundled according to the keys specified in the request. • Check for an error at the global response level. • Check for an error at the specific response level. • Use getData() to retrieve the actual information in a request. function response(data) { if (data.hadError()) { if (data.get(quot;get_ownerquot;).hadError()) { ... } if (data.get(quot;get_viewerquot;).hadError()) { ... } ... } var owner = data.get(quot;get_ownerquot;).getData(); var viewer = data.get(quot;get_viewerquot;).getData(); }; 61
  • 62. The OpenSocial JavaScript API Working with people: • opensocial.Person - JavaScript representation of a user. 62
  • 63. The OpenSocial JavaScript API Request one person: req.add(req.newFetchPersonRequest(idspec, opt_params), quot;keyquot;); • idspec can be either “VIEWER”, “OWNER” or an ID number. • opt_params contains extra request parameters, such as which profile fields to fetch. newFetchPersonRequest responses: var owner = data.get(quot;keyquot;).getData(); alert(owner.getDisplayName()); • Data contains a single opensocial.Person object. • Person objects can contain lots of information, such as addresses, companies, phone numbers, favorite movies, and thumbnail urls. 63
  • 64. The OpenSocial JavaScript API Methods available on an OpenSocial Person: • getDisplayName() Gets a text display name for this person; guaranteed to return a useful string. • getField(key, opt_params) Gets data for this person that is associated with the specified key. • getId() Gets an ID that can be permanently associated with this person. • isOwner() Returns true if this person object represents the owner of the current page. • isViewer() Returns true if this person object represents the currently logged in user. 64
  • 65. The OpenSocial JavaScript API An OpenSocial Person's fields: • ABOUT_ME • JOB_INTERESTS • SEXUAL_ORIENTATION • ACTIVITIES • JOBS • SMOKER • ADDRESSES • LANGUAGES_SPOKEN • SPORTS • AGE • LIVING_ARRANGEMENT • STATUS • BODY_TYPE • LOOKING_FOR • TAGS • BOOKS • MOVIES • THUMBNAIL_URL • CARS • MUSIC • TIME_ZONE • CHILDREN • NAME • TURN_OFFS • CURRENT_LOCATION • NETWORK_PRESENCE • TURN_ONS • DATE_OF_BIRTH • NICKNAME • TV_SHOWS • DRINKER • PETS • URLS • EMAILS • PHONE_NUMBERS • ETHNICITY • POLITICAL_VIEWS • FASHION • PROFILE_SONG • FOOD • PROFILE_URL • GENDER • PROFILE_VIDEO • HAPPIEST_WHEN • QUOTES • HAS_APP • RELATIONSHIP_STATUS • HEROES • RELIGION • HUMOR • ROMANCE • ID • SCARED_OF • INTERESTS • SCHOOLS 65
  • 66. The OpenSocial JavaScript API Working with people: • A Collection represents many opensocial.Person objects. 66
  • 67. The OpenSocial JavaScript API Request many people: var idspec = opensocial.newIdSpec({ “userId” : “OWNER”, “groupId” : “FRIENDS” }); req.add(req.newFetchPeopleRequest(idspec, opt_params), quot;keyquot;); • idspec is an object that can represent groups of people. “userId” can be “VIEWER” or “OWNER” or an ID, and “groupId” can be “SELF”, “FRIENDS”, or the name of a group. • opt_params contains extra request parameters, such as which profile fields to fetch, and how to order or filter the returned people. newFetchPersonRequest responses: var owner_friends = data.get(quot;keyquot;).getData(); owner_friends.each(function (person) { alert(person.getDisplayName()); }); • Data contains a Collection of opensocial.Person objects. Iterate over these by using the each() method. 67
  • 68. The OpenSocial JavaScript API Working with data: • Persistent data gives apps key, value storage directly on the container. • String only, but conversion to JSON allows for storage of complex objects. • Storage per app per user - scales well with growth. • Ideal for settings, customizations. 68
  • 69. The OpenSocial JavaScript API Set persistent data: req.add(req.newUpdatePersonAppDataRequest(idspec, key, value)); • idspec can only be “VIEWER”. • key is the name under which this data will be stored. • value is a string representing the data to store. 69
  • 70. The OpenSocial JavaScript API Fetch persistent data: var idspec = opensocial.newIdSpec({ quot;userIdquot; : quot;OWNERquot;, quot;groupIdquot; : quot;SELFquot; }); req.add(req.newFetchPersonAppDataRequest(idspec, keys), quot;keyquot;); req.add(req.newFetchPersonRequest(quot;OWNERquot;), quot;ownerkeyquot;); • idspec is an object that can represent groups of people, the same as newFetchPeopleRequest. • keys is a list of persistent data keys to retrieve the data for. • The owner is requested because the data returned is indexed by user ID and we want the owner’s data. newFetchPersonAppDataRequest responses: var app_data = data.get(quot;keyquot;).getData(); var value = app_data[owner.getId()][key]; 70
  • 71. The OpenSocial JavaScript API Fetch persistent data: • Data is returned as an object indexed by ID number, then as an object indexed by key name, even if there is only data returned for one user! { quot;1234567890quot; : { quot;key1quot; : quot;value1quot; } } • One person, multiple keys: { quot;1234567890quot; : { quot;key1quot; : quot;value1quot;, quot;key2quot; : quot;value2quot; } } • Multiple people: { quot;1234567890quot; : { quot;key1quot; : quot;value1quot; }, quot;2345678901quot; : { quot;key1quot; : quot;value2quot; } } 71
  • 72. The OpenSocial JavaScript API Working with activities: • API to post information about what users are doing with your app. • Many containers have support for images and some HTML. • Channel to grow your application. orkut MySpace hi5 72
  • 73. The OpenSocial JavaScript API Post an activity: function postActivity(text) { var params = {}; params[opensocial.Activity.Field.TITLE] = text; var activity = opensocial.newActivity(params); opensocial.requestCreateActivity(activity, opensocial.CreateActivityPriority.HIGH, callback); }; • Assign the activity text to the TITLE field. • Call opensocial.newActivity() to create a new Activity instance. • Call opensocial.requestCreateActivity() to post the activity to the container. 73
  • 74. RESTful and RPC protocols Servers talking to servers 74
  • 75. RESTful and RPC protocols Opens new development models • Background processing. • Easier Flash integration. • Mobile applications. 75
  • 76. RESTful and RPC protocols Communication methods: • RESTful (Representational State Transfer) • RPC (Remote Procedure Call) Formats: • XML • JSON • AtomPub 76
  • 77. RESTful and RPC protocols REST: • Resources are URLs. Example - People: • All people connected to the given user: /people/{guid}/@all • All friends of the given user: /people/{guid}/@friends • Profile of the given user: /people/{guid}/@self • Profile of the authenticated user: /people/@me/@self • Supported Person fields: /people/@supportedFields 77
  • 78. RESTful and RPC protocols Querystring parameters customize requests: • Response format (JSON, XML, AtomPub) format={format} • Request extra fields fields={-join|,|field}. • Filtering: filterBy={fieldname} filterOp={operation} filterValue={value} updatedSince={xsdDateTime} networkDistance={networkDistance} • Paging: count={count} sortBy={fieldname} sortOrder={order} startIndex={startIndex} 78
  • 79. RESTful and RPC protocols REST responses (Person): • JSON: { quot;idquot; : quot;example.org:34KJDCSKJN2HHF0DW20394quot;, quot;displayNamequot; : quot;Janeyquot;, quot;namequot; : {quot;unstructuredquot; : quot;Jane Doequot;}, quot;genderquot; : quot;femalequot; } • XML: <person xmlns=quot;http://ns.opensocial.org/2008/opensocialquot;> <id></id> <displayName></displayName> <name> <unstructured>Jane Doe</unstructured> </name> <gender>female</gender> </person> 79
  • 80. RESTful and RPC protocols REST responses (Person): • AtomPub: <entry xmlns=quot;http://www.w3.org/2005/Atomquot;> <content type=quot;application/xmlquot;> <person xmlns=quot;http://ns.opensocial.org/2008/opensocialquot;> <name> <unstructured>Jane Doe</unstructured> </name> <gender>female</gender> </person> </content> <title/> <updated>2003-12-13T18:30:02Z</updated> <author/> <id>urn:guid:example.org:34KJDCSKJN2HHF0DW20394</id> </entry> 80
  • 81. RESTful and RPC protocols REST: • Perform operations using different HTTP methods on each URL. CRUD: HTTP: • Create • POST • Retrieve • GET • Update • PUT • Delete • DELETE 81
  • 82. RESTful and RPC protocols REST has some disadvantages: • Batch support requires multiple HTTP requests, or a contrived URL scheme. • Specifying multiple users via querystring is difficult. Is ?uid=1234,5678 the same resource as ?uid=5678,1234 ? 82
  • 83. RESTful and RPC protocols RPC: • One endpoint - parameters specify methods to call. • Batch support. • Specify collections of users through passed arguments, not URLs. Example - Fetch current user: • Request • Response POST /rpc HTTP/1.1 HTTP/1.x 207 Multi-Status Host: api.example.org Content-Type: application/json Authorization: <Auth token> { Content-Type: application/json quot;idquot; : quot;myselfquot; { quot;resultquot; : { quot;methodquot; : quot;people.getquot;, quot;idquot; : quot;example.org:34KJDCSKJN2HHF0DW20394quot;, quot;idquot; : quot;myselfquot; quot;namequot; : { quot;unstructuredquot; : quot;Jane Doequot;}, quot;genderquot; : quot;femalequot; quot;paramsquot; : { } quot;useridquot; : quot;@mequot;, } quot;groupidquot; : quot;@selfquot; } } 83
  • 84. RESTful and RPC protocols Authentication: • Both protocols use OAuth to identify users and apps. • Depending on what the application needs to do, it can use two-legged or three-legged OAuth. Two-legged OAuth: • The application authenticates directly with the container. • Perform non-user specific operations: • Update persistent data for app users. • Can request information for users who have shared their profile information with the app. Three-legged OAuth: • The user tells the container to give profile access to the application. • Perform user specific operations: • Post activities. • Fetch friends of the current user. 84
  • 85. RESTful and RPC protocols Client libraries are being created for PHP, Java, and Python. • Help you connect to OpenSocial containers, and work with social data on your server. Sample: log into a container: 85
  • 86. RESTful and RPC protocols RESTful and RPC use OAuth for authentication • OAuth is an open standard. • Client libraries will help make this process easier for developers. Sample: use OAuth to get an access token for a user: 86
  • 87. RESTful and RPC protocols • Once OAuth is used, you can store a user token for later access. Sample: use an existing token: 87
  • 88. RESTful and RPC protocols • Once authentication has happened, requests are easy: Sample: Fetch the current user: 88
  • 89. RESTful and RPC protocols Sample: Fetch the current user’s friends: 89
  • 90. OpenSocial Tools What sets us apart from the animals 90
  • 91. Shindig Writing a gadget server is difficult: • Fast changing API - hard to keep up. • Standardization is hard to get right. • Costs ¥ / ! 91
  • 92. Shindig Apache Shindig to the rescue! • Open Source project. • Available in Java and PHP. • Run by itself and connect to an existing social site to add OpenSocial support. • Goal: Launch a new (simple) container in under an hour’s worth of work http://incubator.apache.org/shindig/ 92
  • 93. OpenSocial Dev App Development tool to test out JS code in different containers http://osda.appspot.com 93
  • 95. Caja When JavaScript goes bad • Gadgets can be a new vector for phishing, spam, malware. • Social spread of gadgets can spread bad gadgets too. • Caja reduces threats with a JavaScript sanitizer as an additional quot;sandboxquot; on top of iFrame protection. 95
  • 96. Caja Caja is: • A capability-based Javascript sanitizer. • An Open Source project from Google. • Optional but recommended for OpenSocial containers. • Will eventually be secure enough to run gadgets inline instead of in iframes. http://code.google.com/p/google-caja/ 96
  • 97. Templates Need for a templating language: • Developers need a simple way to convert OpenSocial data to HTML. • DOM manipulation is slow and ugly. • innerHTML is unsafe. 97
  • 98. Templates <script type=quot;text/javascriptquot; src=quot;http://ostemplates-demo.appspot.com/ostemplates.jsquot;></script> <script type=quot;text/os-templatequot;> <b>${owner.displayName}'s friends</b> <ul> <li repeat=quot;friendsquot;>${displayName}</li> </ul> </script> <script type=quot;text/javascriptquot;> function loadData() { var req = opensocial.newDataRequest(); req.add(req.newFetchPersonRequest('OWNER'), 'owner'); var idSpecFriends = opensocial.newIdSpec( {'userId':'OWNER', 'groupId':'FRIENDS'}); req.add(req.newFetchPeopleRequest(idSpecFriends), 'friends'); req.send(function(data) { os.Container.processDocument(data); }); } gadgets.util.registerOnLoadHandler(loadData); </script> http://ostemplates-demo.appspot.com/ 98
  • 99. Templates Templates developer application available: http://ostemplates-devapp.appspot.com/ 99
  • 100. The OpenSocial specification process “We can fix it, we have the technology” 100
  • 106. Challenges Nobody said this was going to be easy 106
  • 107. Challenges Cross container development is still tricky: • Containers may not follow the standard. • Containers may follow the standard but have different policies. • Follow best practices: http://tinyurl.com/4nuzll 107
  • 108. Challenges No central directory • Hard for apps to spread to many containers. • Apps need to work with different install processes. • Directory approval requirements vary from container to container. 108
  • 109. Challenges Scaling is hard: • Easy to start and get some users. 109
  • 110. Challenges Scaling is hard: • Being popular on one social network can push your server to the limit... 110
  • 111. Challenges Scaling is hard: • ...being popular on many networks will push you right over. 111
  • 112. Resources 112
  • 113. Resources • OpenSocial Tutorial: http://rurl.org/ss3 • OpenSocial Spec, Foundation, Reference: http://opensocial.org • Caja: http://code.google.com/p/google-caja/ • Shindig: http://incubator.apache.org/shindig/ • OpenSocial Across Containers video: http://tinyurl.com/4nuzll • OpenSocial Templates: http://ostemplates-demo.appspot.com/ • OpenSocial Dev App: http://osda.appspot.com • Partuza: http://partuza.nl • OpenSocial Specification Proposals: http://groups.google.com/group/opensocial-and-gadgets-spec/topics 113