Pointer to article:
This article mentions the concept of “federation” in a non-IdM context. As I noted in a previous blog entry (“imho Federation much broader than identity”), the term “federate” refers to any governance framework within which autonomous domains honor each other’s decisions and accept each other’s assertions, subject to their respective local policies. In that prior post, I outlined federation scenarios in the presentation, business-logic, data, identity/security, and management tiers. This article generally discusses federation in the data tier, which I characterize as a involving data repositories in different domains federating domain-spanning information-integration scenarios. It all comes down to extending permission-based arms-length sharing of data among autonomous domains. For an interesting application of federation in the data tier, visit www.epok.net, one of the first vendors federating data via XRI/XDI. Yeah, they’re an EII vendor (as are the vendors mentioned in this article), but one that leverages a federated IdM environment to create a federated data-sharing environment. Epok calls it “identity rights management” (not to be confused with digital rights management).