[web-annotation] Remove TextPositionSelector in favor of RangeSelector?

azaroth42 has just created a new issue for 
https://github.com/w3c/web-annotation:

== Remove TextPositionSelector in favor of RangeSelector? ==

Assuming #153 is acceptable, do we want to instead have a text 
position selector that selects a character offset, and use two of them
 with a RangeSelector to duplicate the effects? The same would apply 
to DataPositionSelector.  (Both of which are really 
(Text/Data)RangeSelectors, not single positions anyway)

Thus, the current way:
```
{
  "type": "TextPositionSelector",
  "start": 10,
  "end": "15
}
```
Would become:
```
{
  "type": "RangeSelector",
  "startSelector": {
    "type": "TextPositionSelector",
    "position": 10
  },
  "endSelector": {
    "type": "TextPositionSelector",
    "position": 15
  }
}
```

I'm not really in favor as it makes more work for no real gain, but 
having one way to do things is better than having two and making 
implementers choose, so I'm throwing it out there.


Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/177 using your GitHub 
account

Received on Wednesday, 24 February 2016 21:27:11 UTC