- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Feb 2016 07:58:59 +0000
- To: public-annotation@w3.org
> On 19 Feb 2016, at 19:14, Rob Sanderson <notifications@github.com>
wrote:
>
> to the functionality. Let's discuss the details
>
> To try and make this slightly more concrete, is the proposal to
allow:
>
> {
> "type": "RangeSelector",
> "startSelector": {
> "type": "FragmentSelector",
> "value": "startId"},
> "endSelector": {
> "type": "FragmentSelector",
> "value": "endId"}
> }
> With the semantics being that the selection is from the beginning of
source.html#startId until the ... beginning? ... of source.html#endId
?
>
> Thus a new class oa:RangeSelector (subClassOf oa:Selector), and two
new relationships oa:hasStartSelector, oa:hasEndSelector (both with
domain oa:RangeSelector, range of oa:Selector)
>
> Note that they can't be just start and end, as they're already in
use for TextPositionSelector
(https://www.w3.org/TR/annotation-model/#text-position-selector
<https://www.w3.org/TR/annotation-model/#text-position-selector>)
>
I am fine with this. There is only so many ways of doing this, and
this seems to be an obvious one.
--
GitHub Notification of comment by iherman
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/153#issuecomment-186540216
using your GitHub account
Received on Saturday, 20 February 2016 07:59:01 UTC