Translucent Databases

Jon Udell blogs about some of his investigation into translucent databases. In talking about databases, “translucent” metaphorically describes the ability of the database to obscure relationships between data. This is a key design approach for privacy, and as Udell finds, the theories are all there — it’s just that most companies are unwilling to put in the little more work required to ensure privacy when they can get away without it.

Still, Amazon obviously has to store your name somewhere, plus your credit card number and street address, in order to do the e-commerce dance, right? Well, actually, no, it does not need to store those data, it needs your permission to use them — and a means to access them. This was, of course, the Hailstorm vision. Microsoft floated that trial balloon a couple of years ago, and it got shot down. It’s clear now that Microsoft won’t own the identity business, and that identity systems will federate. But we ought not forget that at the core of Hailstorm is an idea that is correct, necessary, and inevitable. Services don’t need to store your data, they need to use it with your permission. Hailstorm, as originally conceived, was a translucent database — and a darned good idea.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>