CardSpace Identity Versioning
As i posted my last comment to this board, a leaflet was dropped on my desk called "A New Identity". Now, i am finishing up some consultancy for a large UK Bank and with this timely leaflet i started to think about how versioning of identity information would work.
So say in the past you did something with this bank. If you wanted to look back at a record, and with it simply had some guid or card identifier associated with this bank, then the data that would retrieved if a live card was used may be different from that at the time of the transaction.
This may not sound like a big deal, but in the cases of millions of dependent customers, it may be. If parts of your identity changes (e.g. registered address), it likely impact someone. I know you could store the data along with the transaction, but then you get into data duplication and data privacy and so on.
So, I realize this is a hugely complex area and there is no single/simple solution, but i'm interested in thoughts on what kind of best practice could used in this case. In the case of a large organization, they may be happy to keep older versions of cards alive so people can link through to data as it was at the time (there is also the complex question of data that is at an IP). In the case of a home user, he may not wish to maintain versioned identity cards.
steven
http://stevenR2.com
