Beruflich Dokumente
Kultur Dokumente
Information Architecture
Richard Mortier
richard.mortier@nottingham.ac.uk
Horizon Digital Economy Research
26/Mar/2010
The Future: Personal Datastore
• Archive
– Complete recording of me and mine
• Coordinate
– Common control point through which my data is exposed
– Push messages via Twitter, Facebook, LinkedIn, email
• Guard
– Enable fine-grained control of access to my data
• Personal container
– Logically under my control
• Distributed vs. Centralized
– Logically a single entity
– On hosts under my control or on my cloud
– Or managed by a third-party in the cloud
– Or federated among many third-parties
• User vs. Third party owned
– Just because you can doesn’t mean you’re allowed
– Ability to collect does not imply right to process
What’s in it?
• Everything?
• A wide variety of data types
– Messaging: Facebook, Twitter, Email, …
– Media: Phone calls, SMSs, Photos, …
– Activity: Credit card transactions, loyalty card data, …
– Biometrics: heart rate, EEG, breathing rate, …
• Encrypted
– Maybe, at some level
• Audit trails, intervention
– Who accessed what, when, why?
– I need to be able to correct the inevitable mistakes
What can it do?
Data lodged
in store (3)
Device Data pushed (5) Redacted
Datastore to cloud (4) events fired
cbs cbs
Mobile Device
Application Sensors Cloud
Datastore
(5) Redacted
events fired
cf cf
Cloud
Application
Device app Applications
App installs
installed (2) install
contextf,
contextf, Data
callbacks
callbacks (1)
(1) Miner
What does this enable?
• What formats?
– How to represent all this data
• What interfaces?
– How to expose this data
• What queries?
– How to permit processing of this data
• What algorithms?
– How to generate information from this data
• What incentives?
– How to make me want to let you process my data