- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Jun 2016 16:11:55 +0000
- To: public-annotation@w3.org
The first solution is essentially what was proposed and rejected previously, of requiring a SpecificResource for every body and target. It was rejected as making the simple cases overly complex for no significant gain. The second solution would preclude TextualBody, which again is the simple case. And yes, clients should believe the resource rather than the metadata in the Annotation (e.g. `Content-Type` header should be used when if conflicts with `format`). Maybe that should be explicit in the model, but that's the only change I could see as valuable at this stage. -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/247#issuecomment-223341315 using your GitHub account
Received on Thursday, 2 June 2016 16:12:04 UTC