- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2016 16:20:37 +0000
- To: public-annotation@w3.org
I would represent that as:
```
{
"type": "SpecificResource",
"state": {
"type": "TimeState",
"sourceDate": "2016-01-01",
"refinedBy": {
"type": "HttpRequestState",
"value": "Accept: application/pdf"
}
},
"selector": {
"type": "FragmentSelector",
"value": "page=2"
},
"source": "http://example.com/negotiable/dynamic"
}
```
Where the specific resource has the selector on it, rather than the
state. But I agree that the pattern Ivan suggests is more accurate, as
if you have not retrieved the PDF, then selecting the second page of
it is meaningless and potentially dangerous (if page=2 matches an
anchor of the HTML, for example)
--
GitHub Notification of comment by azaroth42
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/195#issuecomment-202983143
using your GitHub account
Received on Tuesday, 29 March 2016 16:20:40 UTC