The document discusses the evolution of identity cards from static "Information Cards" to dynamic "Relationship Cards" that give users more control over their personal data and digital identities. It introduces Higgins, an open-source identity management platform, and describes how Relationship Cards work by sending pointers to user data over front channels, while user-managed back channels allow bi-directional sharing through various protocols. Relationship Cards and personal data agents aim to put individuals in control of their online identities and preferences.

1. From Information Cards to Relationship Cards IIW IX November 3, 2009 Paul Trevithick, paul@azigo.com

6. Act I: Regular Information Cards

7. Information Cards & Claims Data Portability: profile & social networking attributes are made portable by referencing them on Information Cards Any kind of information: your preferences, favorite songs, employee id numbers, drivers licenses, affiliations, your health plan id, etc., can be on a card. Cards from multiple sites are managed in a local Card Selector application (Microsoft CardSpace™ or Azigo™ or Novell DigitalMe™)

8. Card-based Login Click Higgins is interoperable with Microsoft CardSpace™ shown here

10. Actors A U r P p Identity Provider Relying Party User R

11. Personal Card A U r P p R Personal Card has

12. Personal Card: Data Flow A U r P p R Personal Card

13. Managed Card A U r P p R points to token generator Managed Card has

14. Managed Card: Data Flow A U r P p R points to token generator Managed Card has

15. Managed Card: Alice goes to site A U r P p R

16. Managed Card: Selector retrieves policy A U r P p R Required and Optional Claims

17. Managed Card: Display cards that match policy A U r P p R

18. Managed Card: Alice selects a card A U r P p R

19. Managed Card: Auth to IdP A U r P p R

20. Managed Card: Generate token A U r P p R

21. Managed Card: Browser sends token A U r P p R Set of Claims

22. Managed Card: Validate token A U r P p R

23. Managed Card: Alice accesses resource A U r P p R

26. Act II: Relationship Cards

28. Relationship Cards: Sending a pointer claim value over the front channel A U r P p R Set of Claims & Ptr

29. Personal Relationship Cards: Sending a pointer over the front channel A U r P p R Set of Claims & Ptr Personal R-Card points to data has

30. Personal Relationship Cards: User managed data channel A U r P p R Any protocol

31. Managed Relationship Cards: Sending a pointer over the front channel A U r P p R Set of Claims & Ptr has Managed R-Card

32. Managed Relationship Cards: User managed data channel A U r P p R Managed R-Card has Kantara UMA Access Manager control control control Any protocol