Re: Feedback on i28n in Rangefinder API

Hi, Addison–

On 5/12/15 3:04 PM, Phillips, Addison wrote:
>
> Thanks for this. This is an interesting problem you're working on. It
> certainly dovetails with our work on Charmod-Norm.

Yes, I was pleased when I stumbled on Charmod-Norm. Good timing, it 
seems. I appreciate that you're taking that work on, since referring to 
the Unicode docs is not as clear, from an implementation perspective.


> We could certainly meet. Note that I18N meets on Thursdays at 10am
> ET, which is after your meeting this week. In addition, we haven't
> had time to review your materials. Would it be possible for
> representatives from I18N to participate in your call next week (20
> May)? Or would you prefer to have someone(s) dial into our meeting
> this week (14 May)?

I leave it up to the chairs of the Web Annotation WG to determine the 
best date for you to join us.

I'd be happy to join you on your call this week to help provide context 
for your review. Or if you prefer, given the late timing, I could also 
join a future telcon, as well.

Regards–
–Doug

>> -----Original Message----- From: Doug Schepers
>> [mailto:schepers@w3.org] Sent: Tuesday, May 12, 2015 11:47 AM To:
>> i18n WG; Richard Ishida; Phillips, Addison; W3C Public Annotation
>> List Subject: Feedback on i28n in Rangefinder API
>>
>> Hi, Addison, Richard, I18n–
>>
>> Oops, hit send too soon, sorry... resending.
>>
>> (BCCing the Web Annotation WG mailing list, to keep them in the
>> loop)
>>
>> I'd like to schedule a liaison telcon between the
>> Internationalization WG and the Web Annotation WG, to discuss
>> issues around a client-side API for searching for strings in a web
>> document.
>>
>> The Web Annotation WG is chartered to deliver a spec for "fuzzy
>> anchoring", which basically means a way to link to a specific
>> passage in a document, even if there is no ID and even if the
>> document may have changed.
>>
>> One manifestation of this is my Rangefinder API spec [1], which is
>> basically a find-in-page API with fuzzy matching (e.g. case
>> folding, Levenshtein distance tolerance, Unicode normalization [2])
>> and location scoping.
>>
>> For the Unicode normalization, we'd like to refer normatively to
>> the updated Charmod-Norm [3]. In any case, we'd like to discuss our
>> use cases and requirements around i18n with you, for your best
>> advice on how we should proceed.
>>
>> I spoke with Richard today, and he suggested the best next step
>> would be have you take a look at my rough early draft of the
>> Rangefinder API, so we have some basis for discussion. Please
>> excuse the sketchy nature of the spec, and note that the examples
>> are illustrative but out of date with the spec's development.
>>
>> If you want to meet, would you want to join us, or have some of us
>> join you? We normally meet on Wednesdays at 11am ET.
>>
>>
>> [1] http://w3c.github.io/rangefinder/ [2]
>> http://w3c.github.io/rangefinder/#widl-RangeFinder-unicodeFolding
>> [3] http://www.w3.org/TR/2014/WD-charmod-norm-20140715/
>>
>> Regards– –Doug
>>
>

Received on Tuesday, 12 May 2015 19:25:13 UTC