Re: [charter] Addressable Ranges?

2014-06-16 Thread Doug Schepers
Hi, Art– Following on from the discussion at the AC, here is my suggested wording: [[ Robust Anchoring API Defines APIs for finding, addressing, and linking to a document selection based on a set of selectors, even when the document has changed. This may be a joint deliverable with the

Re: [charter] Addressable Ranges?

2014-05-14 Thread Arthur Barstow
On 4/25/14 8:44 AM, Arthur Barstow wrote: On 4/22/14 9:40 AM, Doug Schepers wrote: Hi, Art– There are different approaches that could be taken, but one concrete implementation in JavaScript is from the Hypothes.is Annotator [1]. https://hypothes.is/blog/fuzzy-anchoring/ OK, so at this

Re: [charter] Addressable Ranges?

2014-04-25 Thread Arthur Barstow
On 4/22/14 9:40 AM, Doug Schepers wrote: Hi, Art– There are different approaches that could be taken, but one concrete implementation in JavaScript is from the Hypothes.is Annotator [1]. https://hypothes.is/blog/fuzzy-anchoring/ OK, so at this point, I think it would be helpful if you

Re: [charter] Addressable Ranges?

2014-04-22 Thread Doug Schepers
Hi, Art– There are different approaches that could be taken, but one concrete implementation in JavaScript is from the Hypothes.is Annotator [1]. https://hypothes.is/blog/fuzzy-anchoring/ Regards– –Doug On 4/22/14 9:04 AM, Arthur Barstow wrote: Hi Doug, Do you have some prior art/work for

[charter] Addressable Ranges?

2014-04-18 Thread Doug Schepers
Hi, folks– I'd like to ask for feedback on the notion of adding addressable ranges to the WebApps WG charter. There are a set of use cases for being able to link to a specific passage of text in a document, which has a number of what I consider hard problems: * the passage might cross