Re: [web-annotation] Annotation updated timestamp

So, one option would be to use a UUID (as @timbl suggested at TPAC), 
but use it as the `id` value--obviously this makes these `id`'s 
non-dereferencable.

However, if we require (I know, I know...) a `via` chain to be present
 such that the minimal **published** Annotation becomes:
```json
{
  "id": "...uuid...",
  "type": "Annotation",
  "via": "http://annotation-server.example/~bigbluehat/...uuid...",
  "target": "http://example.com/"
}
```

Before publication it would be just the `id`, `type`, and `target`. At
 publication, the `via` *URL* would get added-- the *expectation* 
being that others can use the IRI's stored in `via` as locators 
(though that wouldn't be a requirement, I don't think).

Here's via's definition from 
[RFC4287](http://tools.ietf.org/html/rfc4287#page-22):
>    The value "via" signifies that the IRI in the value of the href
       attribute identifies a resource that is the source of the
       information provided in the containing element.

A copy made by @jbenet in IPFS +/- some additional statements could 
then look like:
```json
{
  "id": "...uuid...",
  "type": "Annotation",
  "via": [
    "http://annotation-server.example/~bigbluehat/...uuid...",
    "https://ipfs.io/ipfs/...ipfs hash of annotation content, public 
key, etc..."
  ]
  "target": "http://example.com/"
}
```

Annotation systems (offline web browsers, ebook readers, etc) could 
make Web Annotations, and publish them later.

Obviously this is beginning to effect protocol topics...so, tagging it
 that way also.

-- 
GitHub Notification of comment by BigBlueHat
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/96#issuecomment-157075465
 using your GitHub account

Received on Monday, 16 November 2015 15:49:32 UTC