Re: [web-annotation] Make Selectors available for the wide world?

The `SpecificResource` isn't really `image/jpeg` is it? It's likely, 
if we're talking about web annotation clients and servers, also 
`application/ld+json`.

I admit that, in terms of conceptual clarity and model simplicity, I'm
 currently really intrigued by this line of inquiry as well as the 
"inverse" selector pattern.

I see no reason for `subSelector` when `source` is a functional 
inverse that we already have.

I see no reason why `hasState` should be different from `hasSelector`,
 why selecting the representation at a point in time, or under a 
particular content type request, is different from selecting the 
representation at a region in space.

And `hasSelector` goes away entirely by inverting the chain and using 
`source`. Selections have sources and selector data.

Why the selector, itself, must be a resource of its own, rather than 
having its properties be part of a selection, is not clear to me. 
Arguably, maybe, for re-use. I'm not super compelled by that, though.


```json
{
  @type: "Annotation",
  hasTarget: {
    @type: "TextQuoteSelection",
    source: {
        @type: "CssSelection",
        value: "div",
        source: {
          @type: "TimeSelection",
          source: "http://example.com/",
          sourceDate: "2016-02-23T13:30:00Z",
          cached: 
"https://web.archive.org/web/20160223161828/http://www.example.com/"
        }
    },
    exact: "illustrative"
  }
}
```

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

Received on Tuesday, 23 February 2016 19:29:39 UTC