Re: TextQuoteSelector and RangeSelector question

I don't think it's a bad thing. :) I just like to work with existing tooling/specs for as far as they can take us before introducing anything new.

However this plays out, the end goal should be a Web Annotation compatible way of expressing ScrollToTextFragment selectors (and vice versa) such that these selections can be made across the various communities--i.e. we can all be pointing at the same stuff effectively. :)

Anyone up for taking a crack at designing this new selector?

I'm assuming we could add this into a new draft/iteration of the Web Annotation Data Model under this CG...but Ivan or Rob could probably tell us more on that process.

Cheers,
Benjamin


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Leonard Rosenthol <lrosenth@adobe.com>
Sent: Wednesday, August 14, 2019 9:45 AM
To: Benjamin Young <byoung@bigbluehat.com>; public-openannotation@w3.org <public-openannotation@w3.org>
Subject: Re: TextQuoteSelector and RangeSelector question


Benjamin – why do you think that adding a new selector is a bad thing?  I have always believed that “custom” selectors are a perfectly acceptable way to extend the WebAnnots model for new types of content and/or use cases.



This, to me, seems like a perfect example of the need for a new selector – I am thinking the “TextStartEndSelector” to make it clear how it differs from TextQuote.



Leonard



From: Benjamin Young <byoung@bigbluehat.com>
Date: Tuesday, August 13, 2019 at 11:22 AM
To: "public-openannotation@w3.org" <public-openannotation@w3.org>
Subject: TextQuoteSelector and RangeSelector question
Resent-From: <public-openannotation@w3.org>
Resent-Date: Tuesday, August 13, 2019 at 11:21 AM



Hi all,



I'm attempting to contribute to the ScrollToTextFragment work going on at https://github.com/WICG/ScrollToTextFragment<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWICG%2FScrollToTextFragment&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696270787&sdata=VoxjaRSCATb3rDMPBPM7oMIOzBySPM6Sp5ctjBzrCwE%3D&reserved=0>



That work is being crafted with a hope of compatibility with Web Annotation Data Model, but there's already been some early possible divergence.



Cribbing some lines from this section of the README...

https://github.com/WICG/ScrollToTextFragment#processing-model<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWICG%2FScrollToTextFragment%23processing-model&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696270787&sdata=8vNT8i2ZOs1IzzJ1%2F52zb2CX7kP1Ux2ahOQa1b4ekdM%3D&reserved=0>

"We'd like to reuse as much of the processing model...in the Web Annotation’s TextQuoteSelector as possible, potentially adding enhancements to that specification. Notably, we’d need to add the ability to specify text using a starting and ending snippet to TextQuoteSelector."



Here's what the ScrollToTextFragment "model" currently looks like:

```

targetText=[prefix-,]textStart[,textEnd][,-suffix]



            context  |-------match-----|  context

```



We don't quite have anything like that...sadly.



`TextQuoteSelector` currently requires `exact` and `prefix`/`suffix` are optional and `exact` must be the exact (surprise! ;-P) content selected (not the combination of a `textStart` and a `textEnd`).



We could almost use `RangeSelector`, but it trips itself up a bit by making the `endSelector` be exclusive rather than inclusive like the `startSelector` (or like `textEnd` above).



So, essentially, this ScrollToTextFragment selector looks like a new thing...



Perhaps we could add two new terms to `TextQuoteSelector` (perhaps `textStart` and `textEnd` as here) or (if we must) adding a new kind of Selector that supported this style.



We did have discussions within the Web Annotation WG around the risks of `exact` because it could potentially be too massive (certainly for URL use) and may also expose too much (copyrighted) content. Having a `textStart`/`textEnd` style selector would avoid that, so I think there's community benefit here beyond the ScrollToTextFragment compatibility alone.



Does that sound like a fair analysis? Or does anyone know of a different/better way to handle this style selector with the current kit?



Thanks, all!

Benjamin



[1] https://www.w3.org/TR/annotation-model/#text-quote-selector<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fannotation-model%2F%23text-quote-selector&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696270787&sdata=U8i3h%2FUw25hFLV1rezliEpY0Frc2IGiDoqdAiF3yXY0%3D&reserved=0>

[2] https://www.w3.org/TR/annotation-model/#range-selector<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fannotation-model%2F%23range-selector&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696280779&sdata=W4ojsfjWLKqrH4Tfm32bXytJhdD6hchi%2BrVKW0U0K4o%3D&reserved=0>



--

http://bigbluehat.com/<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbigbluehat.com%2F&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696280779&sdata=zoeI9apXByaqLQQPrfQjxyDKVVqoYnMnWewz4LwkzQI%3D&reserved=0>

http://linkedin.com/in/benjaminyoung<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flinkedin.com%2Fin%2Fbenjaminyoung&data=02%7C01%7Clrosenth%40adobe.com%7C2340dc61f2a5420e8f2d08d7200218e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013065696290773&sdata=tIbtNCaXhwneMB2d8OVwdeV4BQpOC8yUpmy0cIvr%2Blw%3D&reserved=0>