You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2011/06/14 23:01:49 UTC
[Couchdb Wiki] Update of "SignedDocuments" by jchrisa
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.
The "SignedDocuments" page has been changed by jchrisa:
http://wiki.apache.org/couchdb/SignedDocuments?action=diff&rev1=6&rev2=7
Comment:
added link to jsond.js
Note: The OLPC spec allows arbitrary byte sequences in strings, for easy storage of binary data. But this contradicts the [[http://www.ietf.org/rfc/rfc4627.txt|JSON specification]], which clearly states that "a string is a sequence of zero or more Unicode characters".
+ Here is a [[https://github.com/jchris/canonical-json|JavaScript library for creating repeatable JSON serializations.]]
+
== A Digression On Identities ==
This mechanism considers a signer to be identical to his/her/its public key. In other words, there is no additional form of identification such as a URL or Social Security Number. This is sometimes called "key-centric identity", and it seems pretty weird if you're not used to it, but actually works very well. Assigning a human-meaningful identity turns out to be intractably difficult, for reasons that are as much social as technological. (In a nutshell: there is no single form of identification that will be meaningful to all the people you might want to identify yourself to; and the more forms of identification you provide, the more privacy you lose.) I've written about this at greater length [[http://mooseyard.com/Jens/2007/12/facebook-and-decentralized-identifiers/|elsewhere]].