Hitching Federation to the collaboration train
By dr156914 on Jan 02, 2008
Check out the blog below from Eric Norlin of Digital ID World.
I couldn't agree with him more. If we only talk about security when it comes to federation we forget one of the most compelling aspects of the opportunity -- collaboration. Today, collaboration stacks limit flexibility because of dependencies on vendors software infrastructure. For example, you can't deploy IBM's Lotus Connections without the use of IBM Websphere or Microsoft Sharepoint without the use of Microsoft Windows Server System. These types of collaboration stacks place unnecessary infrastructure requirements on the customer.
Federation has the ability to free us of the burden of stack requirements and allow users to pick and choose those collaboration services that best fit their needs. In short, I should be able to easily leverage federation to create a "custom collaboration suite" comprised of those SaaS services that best meet my needs. I should also be able to enable these service regardless of what containers and OS platforms I have deployed.
Why use Lotus connections calendar service when I can use Google Calendar? Why use use IBMs blogging service, when I can use Wordpress? Let the end user choose the collabortion tools that best fit their needs and let's avoid creating a monolithic collaboration stack that is weighted down with infrastructure dependencies.