...

Embedded experiences allows application developers to embed content from their applications inside OpenSocial 2.0 containers.  An embedded experience can be built as an OpenSocial gadget, or it can be a simple web page, but because both are based on standard web technologies like HTML, CSS, and Javascript, and any web developer should be able to create an embedded experience.  Embedded experiences are backed by a simple data model.  Containers and gadgets which support embedded experiences will recognize this data model and can choose to render the embedded experience.  Embedded experiences can be used anywhere inside a container but the two most common use cases are inside an email, or inside an activity stream entry.

What Type Of Embedded Experience Should I Choose?

As mentioned above, there are two types of embedded experiences, OpenSocial gadgets and web pages.  Embedded experiences which point to web pages are the simplest to create, especially if the web page you want to use already exists, in which case there is little development to do.  URL embedded experiences .  Embedded experiences which point to web pages can also be embedded in any container, even if they don't support OpenSocial.  You may choose a URL embedded experience if you just want to show static content, which is publically available is publicly available on the internet.  Good examples of this would be an embedded experience which tracks a package, or an embedded experience which asks a user to fill our out a survey.  These types of applications are usually public content which does not require authentication to access.  However you will also be limited on the type experience you can provide with a URL embedded experienceweb page.  You will not for example be able take adavantage of take advantage of any of the OpenSocial features APIs when you are using an URL embedded experience.

Embedded experiences based on gadgets have the ability to be more powerful and take advantage of all the OpenSocial APIs.  Probably the number one reason you would choose a gadget over a URL web page is because the user needs to authenticate to view the content in the embedded experience, or to take an action on the content in the embedded experience.  OAuth is part of the OpenSocial specification and it can allow your embedded experience gadget to access secure content once the user has delegated access to the gadget to do so.  Embedded experience gadgets can also use any of the OpenSocial APIs within the gadget.  Your gadget can access to the users friends, send messages to other users, or contribute actions to the surrounding container.

What Is This "Data Model"?

The embedded experiences data model represents is way to represent an embedded experience in JSON or XML.  It tells the container everything is needs to know so it can render the embedded experience.  The data model can be represented in either JSON or XML, with the preferred method being JSON, especially if it is being places inside an activity in an activity stream.  The data model has only a couple of properties.

• gadget - The URL to the gadget you would like to use as an embedded experience.
• url - The URL to a text/html page you would like to use as an embedded experience.
• context - The context can compliment a gadget embedded experience.  This can be any information you may want to be passed to your embedded experienceis information you would like to use in your gadget.  Note the context is not used with embedded experiences that are web pages.
• previewImage - This is a URL to an image which can be used as a preview before rendering an of the embedded experience.  This information is not necessary, but is a convenience to the container if it doesn't want to render the embedded experience immediately but still wants would instead want to show a preview of the content that could be rendered.

All embedded experiences must include either EITHER a gadget or OR URL in order to be valid embedded experience.  The data model MAY choose to include both if the service application wants to provide both types of embedded experiences.  Services may include any combination of the other properties based on their use cases.  Here are some example data models.

...

{
  "url": "http://example.com/ee.html",
  "gadget": "http://example.com/EE_Gadget.xml",
  "context": {
    "title": "Foo",
    "id": "1234"
  }
  "previewImage": "http://example.com/EE_Preview.png"
}

How Do I Get Started

...

Developing My Own Embedded Experience?

Now that you know what an embedded experience is, and we know what makes up an embedded experience, we are ready to get started building an embedded experienceone.  In this tutorial we will build a gadget based embedded experience since that is the more complex and interesting type of embedded experience.  If your interested in building a URL embedded experience its a simple as building a web page and placing the URL to that page in the data model you want to use.  See below on how to embed the data model in different types of mediumsemails or activity streams.

For this tutorial we will build an embedded experience gadget which will embed a YouTube video in both emails and activity streams.  The first thing we need to do is decide on the what our data model is going to look like.  For this tutorial we will keep it fairly simple.  Lets , our embedded experience gadget will just embed a YouTube video.  Lets say we want to embed the URL a video to this an OpenSocial tutorial video,  http://www.youtube.com/watch?v=9gW2YVBrNVA.  As most people know , you can already embed YouTube videos into any HTML page using this HTML.



<object width=480" height="285">
  <param name="movie" value="http://www.youtube.com/v/9gW2YVBrNVA"></param>
  <param name="allowFullScreen" value="true"></param>
  <param name="allowscriptaccess" value="always"></param>
  <embed src="http://www.youtube.com/v/9gW2YVBrNVA" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="285">
  </embed>
</object>

We could just place this HTML in the gadget use that gadget as out embedded experience.  Lets take a look at what an embedded experience gadget and data model would look like using this HTML.

...

Data Model

...

{
  "gadget": "http://example.com/YouTube_EE.xml"
}

...

<?xml version="1.0" encoding="UTF-8"?>
<Module>
<ModulePrefs title="YouTube Player" description="YouTube Player Using Embedded Experiences" height="400" width="700"/>
<Content type="html">
  <![CDATA[
    <object width=480" height="285">
  <param name="movie" value="http://www.youtube.com/v/9gW2YVBrNVA"></param>
  <param name="allowFullScreen" value="true"></param>
  <param name="allowscriptaccess" value="always"></param>
  <embed src="http://www.youtube.com/v/9gW2YVBrNVA" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="285">
  </embed>
</object>
  ]]>
</Content>
</Module>

However the The problem with this embedded experience is that it is very static.  What if we wanted to create an embedded experience for a different YouTube video. ?  With our current embedded experience we would have to build a new gadget.  The embedded experiences data model can solve this problem Fortunately there is a way to solve this problem.

Using The Embedded Experiences Context

The context property in the embedded experiences data model can be used to make a more abstract embedded experiences gadget.  Really  If we wanted to show a different video using the gadget above the only thing we would need to change in the gadget above is the video id in the URLs in the param and embed tags.  We can also build that HTML dynamically in the gadget itself once we know  Based on that, the only data that needs to be abstracted from the gadget above is the YouTube video id.  To do this we can change our data model so the context property includes the video id, that way its not hard coded into the gadget.  Here is what our new data model will look like.

...

The first difference you will notice in our new gadget XML is that we have included two features in the ModulePrefs section of the gadget XML.  The dynamic-height feature is used to adjust the height of the gadget once the video has been placed in the gadget.  The more important feature is the embedded-experiences feature.  This is the feature which will get the context information and make it available to the gadget.  The context information from the data model is placed in the data context object, under the key org.opensocial.ee.context.  You can access information from the data context object by using the data context APIs to get the data set for the embedded experiences key.

Notice in the content section of the gadget we have also removed all the HTML from our previous embedded experience gadget and now just have a script tag and a div tag.  If we take a look at the contents of the script tag you will see two functions and a call to register an on load handler to kick everything off.  The on load handler we register, initData, will be called once the gadget has been loaded.  When initData is called we register a listener for the key org.opensocial.ee.context on the data context object.  When the data set attached to the key org.opensocial.ee.context is has changed our listener function , will be called , and can retreive the can retrieve the data set for that key.  In the embedded experiences case the data set is the context information from the data model.  The data set, or context information, can be retrieved by calling opensocial.data.getDataContext().getDataSet('org.opensocial.ee.context').  In our example embedded experience gadget we call showPlayer with the context information, which in our data model is the YouTube video id.  The showPlayer function sets the inner HTML of the div element with the id player to the HTML to show the YouTube video.

The above embedded experience gadget can now be used to provide an embedded experience for any YouTube video.  All we have to do as the service is the application is change the context informaiton in context information in our data model.  This is much simpler than having to have a separate gadget for every YouTube video.

...

Now that we know what our data model is going to look like and we have written our gadget we are ready to start providing embedded experiences.  One of the most interesting use cases is to provide a richer experience in emailemails.  The majority of services today send static HTML emails based on a standard called MIME.  This is a step above plain text emails but, the HTML has its own limitations as well.  Embedded experiences has taken advantage of the MIME email spec to allow applications to send embedded experiences in MIME emails as well.  If the application aleady is an application already is sending MIME emails, the changes will be minimal and it will not effect users who are using mail clients which don't support embedded experiences.  

...

This is a pretty standard multipart/alternative MIME email.  It has two parts, a text/plain and a text/html part.  This is pretty similar to most MIME emails which applications send today.  Like I said above Like I said above, to make this an embedded experience email we just have to add another part.

From: notifications@example.com
To: johndoe@example.com
Subject: Check Out This YouTube Video
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="XXXXboundary text"

Check out this YouTube video.
http://www.youtube.com/watch?v=9gW2YVBrNVA

--XXXXboundary text
Content-Type: text/plain

Check out this YouTube video.
http://www.youtube.com/watch?v=9gW2YVBrNVA

--XXXXboundary text
Content-Type: text/html

Check out this <a href="http://www.youtube.com/watch?v=9gW2YVBrNVA">YouTube video</a>.

--XXXXboundary text
Content-Type: application/embed+json
{
  "gadget" : "http://example.com/YouTube_EE.xml",
  "context" : 123
}

In this example our new email you can see we have added another part with the content type of application/embed+json.  This is a MIME type the OpenSocial foundation has registered with IANA to represent embedded experiences.  In addition to the JSON MIME type the OpenSocial foundation has also registered applicaiton/embed+xml for the XML data model.  The content of the MIME part is just our embedded experiences data model.  When email clients which support embedded experiences , receive this email, they will be looking for a MIME part with the type application/embed+json or application/embed+xml, and if they find it they can choose to render the embedded experience.  If a client which does not support embedded experiences receives this email they will choose to render whatever other part they support, most likely the text/html part.

...

OpenSocial 2.0 supports the ActivityStreams 1.0 specification.  OpenSocial also has defined a namespace extension to the ActivityStreams spec which contains OpenSocial specific concepts.  The embedded experiences data model can be places placed inside this namespace the OpenSocial extension.  Say we have this activity entry.

{
  "postedTime": "2011-02-10T15:04:55Z",
  "actor": {
    "url": "http://example.com/john",
    "objectType" : "person",
    "id": "tag:example.com,2011:john",
    "image": {
      "url": "http://example.com/john/image",
      "width": 250,
      "height": 250
    },
    "displayName": "John Doe"
  }
  "verb": "post",
  "object" : {
    "url": "http://www.youtube.com/v/9gW2YVBrNVA",
    "id": "tag:youtube.com,2011:9gW2YVBrNVA"
  },
  "target" : {
    "url": "http://example.org/favorites/",
    "objectType": "favoriteslist",
    "id": "tag:youtube.com,2011:9gW2YVBrNVA",
    "displayName": "John's Favorites"
  }
}

To add our embedded experience to this activity entry we need to add the OpenSocial namespace extension and then add our embedded experience data model inside of it.

{
  "postedTime": "2011-02-10T15:04:55Z",
  "actor": {
    "url": "http://example.com/john",
    "objectType" : "person",
    "id": "tag:example.com,2011:john",
    "image": {
      "url": "http://example.com/john/image",
      "width": 250,
      "height": 250
    },
    "displayName": "John Doe"
  }
  "verb": "post",
  "object" : {
    "url": "http://www.youtube.com/v/9gW2YVBrNVA",
    "id": "tag:youtube.com,2011:9gW2YVBrNVA"
  },
  "target" : {
    "url": "http://example.org/favorites/",
    "objectType": "favoriteslist",
    "id": "tag:youtube.com,2011:9gW2YVBrNVA",
    "displayName": "John's Favorites"
  }
  "opensocial" : {
    "embed" : {
      "gadget": "http://example.com/YouTube_EE.xml",
      "context": "9gW2YVBrNVA"
    }
  }
}

We can now post this activity to any activity stream and if the container rendering the activity stream supports embedded experiences it can choose to display the embedded experience in the activity stream as well.

Resources

1. Embedded Experiences - http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#Embedded-Experiences
2. OAuth In OpenSocial - http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#OAuth
3. Data Context - http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#DataContext_Client
4. OAuth Spec - http://oauth.net/
5. Activity Streams Spec - http://activitystrea.ms/
6. MIME RFC - http://www.rfc-editor.org/rfc/rfc2046.txt