- From: Juan Benet via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Nov 2015 15:26:06 +0000
- To: public-annotation@w3.org
I would really advise against using HTTP for anything that is meant to work across locations, meaning if an annotation can be made in a host (perhaps disconnected) and then served by a variety of other hosts, it is best to use a URI of some sort. In IPFS, I would use either a keypair (naming the object as `/ipns/<cryptographic_hash(public_key)>`), or use an object nested under a keypair (naming the object as something like `/ipns/<cryptographic_hash(public_key)>/annotations/<uuid>`). This would be a _name_ which resolves to an immutable object representing the state at a particular time (think of it like git-style versioning). Could even point to version history chains, if desired. -- GitHub Notification of comment by jbenet Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/96#issuecomment-157066502 using your GitHub account
Received on Monday, 16 November 2015 15:26:12 UTC