MeatballWiki | RecentChanges | Random Page | Indices | Categories
Traditionally, safety deposit boxes have been used to store valuable items in environments that are relatively more secure. Such items were generally small objects with high values. This "Electronic Safety Deposit Box" (EsDb?) page should develop those aspects of 'safe custody' that are now pertinent to 'electronic' assets such as...
- Secure custody of private personal information that is increasingly being used in technology-enabled crimes such as IdentityTheft.
- Efficient and secure storage of "definitive data" such as...
- Credit Bureau reports that are used to assess the Risks of a Loan.
- Since lenders incorporate a "risk" premium into each loan's interest rate, it becomes important for the borrower to establish their creditworthiness.
- Effective and efficient access to electronic assets (now that "money" is little more than bits of computer data).
- ... Any other aspects that this communities participants care to explore.
Other uses of an electronic safety deposit box include:
- "Verification", "Adjudication", "Certification", and "Distribution" of the individual data 'fields' that can be used to construct a "HyperReord?".
- TrustMetric support
- If the contents of the ESDB are "certified", then they can be used to establish an appropriate level of Confidence or Trust. This can be thought of as the archaic "letter of introduction" that Bankers used to provide to assert the trustworthiness of a traveller.
- OnlyOnce? information presentation (derived from c2:'s OnceAndOnlyOnce?)
- Provision of "Sufficient" (just enough) information (and no more than is necessary, since "Data wants to be free" and "Trusted Custody appears elusive", at least at this time.)
- Programming efficiencies will result from:
- having reliable data, since data edits will not be needed in many programs that currently have no choice but to include such defensive code.