COmanage Developers List

["RL 'Bob' Morgan" <>]

> That last sentence by the way hits an interesting issue: How to figure 
> out where that local calendaring system actually is. A WIYCF (where is 
> your calendar from) interface does not seem very nice. Perhaps use a 
> SAML attribute to point to the local calendar resource?

There have been several attempts to deal with this kind of thing, ie 
allowing a user's service points for various kinds of services to be 
discovered by various other services.  My favorite was the Liberty People 
Service (you can search on it) from 5 years ago or so, which built on the 
ID-WSF framework and provided controlled access, fancy pseudonymity etc. 
It aint happenin but it has been inspirational I think.

Then there was MS Hailstorm, which I suppose was the inspiration for 
Liberty ...

In terms of current things ... an example of the kind of thing people are 
thinking about using the latest coolest tech:

 http://robubu.com/?p=59
 WebFinger, OAuth and Freebusy lookups

So all you have to believe in here are WebFinger, XRD, hostmeta, OAuth, 
opensocial, ... and that scheme looks pretty handy.  But at least all 
those things are supposed to have independent justifications, so might 
come to be.  Maybe in a CMS setting only a few of those elements would be 
needed.  Or maybe it's all a pipe dream.

Another current idea is the Kantara UMA work, which has some 
calendar-sharing use cases:

http://kantarainitiative.org/confluence/display/uma/UMA+Scenarios+and+Use+Cases#UMAScenariosandUseCases-Scenario%3ASharingaCalendarwithVendors%28Accepted%29

UMA proposes a particular architecture for resource-linking where the user 
makes connections between disparate services explicitly.  Could be 
interesting but not relevant to CMS situations today probably.

That's all I've got, unfortunately.

 - RL "Bob"