- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2016 17:49:14 +0000
- To: public-annotation@w3.org
> On 29 Mar 2016, at 18:20, Rob Sanderson <notifications@github.com>
wrote:
>
> 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)
>
Actually (sorry, I am on my mobile) doesn't the text says somewhere
that if there are several stetes/selectors, then they are
_alternatives_? If so, what you write is definitely not the same...
Ivan
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
>
--
GitHub Notification of comment by iherman
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/195#issuecomment-203024344
using your GitHub account
Received on Tuesday, 29 March 2016 17:49:16 UTC