W3C home > Mailing lists > Public > public-annotation@w3.org > November 2015

Re: [web-annotation] Annotation updated timestamp

From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 Nov 2015 16:18:43 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-157085623-1447690723-sysbot+gh@w3.org>
Some design considerations I'd like to propose, based on the above 
discussions:
  * We should avoid mandating a versioning model. Some systems will do
 immutable resources with replacements, some will simply modify in 
place. There's advantages and disadvantages for each, and we're not 
going to solve that. Picking one is splitting the community 
unnecessarily.
  * We should (continue to) make use of the Linked Data best 
practices, and notably that the URI for a resource should be 
dereferencable and provide useful information.
  * We should not invent relationships when they already exist, and we
 should prefer well used and web-focused ontologies. So in this case, 
I think that DC and the IANA rels would be preferable to PROV-O.
  * We should not prevent the use of non HTTP/S URIs, but this is the 
__Web__ Annotation WG and recommending their use seems entirely 
consistent with our mission and charter.

Thus, along with #21, we can fulfill these with iana:via and 
dcterms:modified.  We might consider using `updated` as the key for 
modified, per #102.  We can allow UUIDs or any other URI as the object
 of iana:via, but id should be HTTP/S and provide useful standards 
based RDF compatible data.

-- 
GitHub Notification of comment by azaroth42
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/96#issuecomment-157085623
 using your GitHub account
Received on Monday, 16 November 2015 16:18:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:42 UTC