OpenSAM Overview

1.0 Overview

Authors: Tom Snyder & Eric Hoffert. Created 9/15/06. Updated 2/27/07.

The Internet is a very connected environment in which to work. Huge arrays of information and tools are one click away. Until now, however, online Web 2.0 applications were not connected with each other. You had to log in several times, organize your work separately in each, and copy/paste - upload/download documents amongst them.

OpenSAM solves this.

Within OpenSAM, Web 2.0 applications launch each other. They share task and contextual information automatically. They store your documents and images in one, easily browsable and searchable place. In an OpenSAM mashup, the typical user does not even realize they are using two or three applications from different vendors. The applications work together so intuitively that the user views them as one.

OpenSAM is not an API or platform. Your work adding OpenSAM to your application will also work with other platforms such as Microsoft SharePoint and Salesforce.com. Several OpenSAM applications can be wired together into a solution by performing meta customization via a GUI interface. No programming required.

Two Types of Web 2.0 Applications

It is constructive to split Web 2.0 applications into two types:

	Home Application
	Stores, organizes, and orchestrates user's documents and work-flow. Users log in here first to begin work. Examples: ShareMethods.com, Zimbra messaging and collaboration, Microsoft SharePoint.

	Productivity Application
	A focused solution to one area or document type. Examples: iNetWord word processor, EditGrid online spreadsheet, calendaring services, photo gallery services.

The Home Application serves the role the operating system does on a desktop system. Of course the Web 2.0 versions of these applications are more connected and collaborative than their desktop counterparts.

Many Web 2.0 systems have both Home Application and Productivity Application characteristics. We recommend you initially classify your application(s) as one or the other and first focus on implementing SAM for that role.

Incremental Development

Adding OpenSAM to a Web 2.0 application is an incremental process. Start with Single Sign On before adding the richer features. Test your OpenSAM Single Sign On with the current OpenSAM applications and show it to associates. The more you observe novice users using your application within OpenSAM, the better your design for subsequent phases will be.

Three phases of development might be:

Single Sign On

In a Home Application		your application can launch any other OpenSAM application.
Productivity Application		your application can be launched by any other OpenSAM application

This, alone, can improve the connectedness of your application.

Simple Document Read/Write

In a Home Application		your application can store and organize any OpenSAM application's documents.
Productivity Application		your application can store your documents in any OpenSAM application.

This will show the connectedness and compatibility of your application.

Full OpenSAM Implementation

In a Home Application		launch applications with contextual information, manage and utilize document meta data, search and manage any application's documents within your workflow capabilities, etc.
Productivity Application		be launched with and preserve and transmit contextual information for the user. Browse, create, open, save documents, images, resources + meta data to any OpenSAM document repository. Give rich and accurate diagnostics to any error or mis-configuration.