returns the content of the data at that key, with content-type specified at upload time. Only if authorized, of course.
= TEXT BELOW THIS POINT IS OLDER AND MAY BE OUT OF DATE =
== User Data Model ==
The UDS implements a per-user key-value store abstraction. The user model is multi-identifier.
User has one or more Identifiers
Identifier has a type and a value
User has zero or more Data
Data has a key and a value
XXX are identifiers unique?
XXX collections? ordering?
The UDS will index the user database by the known identifiers (after, internally, hashing and salting them for safety).
On a per-key basis, a data element may be encrypted.
XXX encryption discussion:
* we don't have the keys
* we have a per-user key, wrapped in a symmetric key that we have in an HSM - hard to do aggregate analysis!
* the data is not per-user encrypted (on-disk encryption only)
Do we explicitly model/support the conversion of a data element from one of these encryption styles to another? (how about a collection?)
