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 proposed Web 
Annotations WG.

]]

The timeline is for a FPWD in Q2-2015, with a Rec in Q4-2016; this needs 
some development, though I hope we can make good progress.


The group liaison could be:

[[
Web Annotations Working Group
This proposed group is interested in several of WebApps' specifications, 
as well as having a joint deliverable (Robust Anchoring API).

]]

We have resources to work on this deliverable, including an editor. This 
deliverable is being added for consideration by the AC during review; if 
not accepted by the AC, then the Web Annotations WG will work on it 
alone, but I'd rather it were developed under the eyes of the WebApps WG.


Any other details you need?

Regards-
-Doug

On 5/14/14 8:54 AM, Arthur Barstow wrote:

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 point, I think it would be helpful if you would please
provide a diff or a PR against
https://github.com/AFBarstow/WebApps/blob/master/charter.html
(http://afbarstow.github.io/WebApps/charter.html) so we can evaluate
your specific proposal.


Doug - are you going to provide a diff? Without a relatively firm
commitment from WebApps, my inclination is to not add this to the charter.

Philippe - what is the next step to get WebApps re-chartered (current
charter expires May 31)?

-Thanks, AB






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 point, I think it would be helpful if you would please 
provide a diff or a PR against 
https://github.com/AFBarstow/WebApps/blob/master/charter.html 
(http://afbarstow.github.io/WebApps/charter.html) so we can evaluate 
your specific proposal.


Doug - are you going to provide a diff? Without a relatively firm 
commitment from WebApps, my inclination is to not add this to the charter.


Philippe - what is the next step to get WebApps re-chartered (current 
charter expires May 31)?


-Thanks, AB




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 would please 
provide a diff or a PR against 
https://github.com/AFBarstow/WebApps/blob/master/charter.html 
(http://afbarstow.github.io/WebApps/charter.html) so we can evaluate 
your specific proposal.


-Thanks, Art








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 this functionality (that could help
people get a bit deeper understanding of the proposal)?

All - if you have any feedback - both positive/+1 or negative - please
do speak up by April 25 at the latest.

-Thanks, AB

On 4/18/14 3:45 PM, Doug Schepers wrote:

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 element boundaries
* someone linking into the document usually doesn't have write access
to the document such that they can insert permanent markers into the text
* documents might change: the passage may have moved, been slightly
altered, or even been completely removed
* many other considerations (including single-page vs. multi-page
versions of the same document, near-duplicates of the document at
different URLs, etc.)

I bring this to the WebApps WG for a couple reasons:
* there are related deliverables and discussions already underway,
including the new Selections API work from Niwa, the Clipboard API
work, and the discussions around a Find API
* if this is ever going to happen, this is the right community of
developers and browser vendors to discuss the different challenges and
possibilities

This work might take a while before we consider it ready for serious
consideration for implementation and deployment in browsers, but I'd
like to start the conversation now so we can keep this in mind while
developing related features, and build toward some tangible outcome in
the not-too-distant future.

Because finding a solution to this would be a major goal of the
proposed Web Annotations WG, it would be nice if this could be a joint
deliverable of both groups. While we propose to have the conversation
on public-webapps (for the widest and most critical review), the Web
Annotations WG will provide an Editor and a Test Lead, and we would
prefer to have a co-Editor from WebApps.

Regards-
-Doug











[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 element boundaries
* someone linking into the document usually doesn't have write access to 
the document such that they can insert permanent markers into the text
* documents might change: the passage may have moved, been slightly 
altered, or even been completely removed
* many other considerations (including single-page vs. multi-page 
versions of the same document, near-duplicates of the document at 
different URLs, etc.)


I bring this to the WebApps WG for a couple reasons:
* there are related deliverables and discussions already underway, 
including the new Selections API work from Niwa, the Clipboard API work, 
and the discussions around a Find API
* if this is ever going to happen, this is the right community of 
developers and browser vendors to discuss the different challenges and 
possibilities


This work might take a while before we consider it ready for serious 
consideration for implementation and deployment in browsers, but I'd 
like to start the conversation now so we can keep this in mind while 
developing related features, and build toward some tangible outcome in 
the not-too-distant future.


Because finding a solution to this would be a major goal of the proposed 
Web Annotations WG, it would be nice if this could be a joint 
deliverable of both groups. While we propose to have the conversation on 
public-webapps (for the widest and most critical review), the Web 
Annotations WG will provide an Editor and a Test Lead, and we would 
prefer to have a co-Editor from WebApps.


Regards-
-Doug