W3C home > Mailing lists > Public > public-annotation@w3.org > July 2015

Re: "Stacked" selectors?

From: Robert Sanderson <azaroth42@gmail.com>
Date: Thu, 30 Jul 2015 14:28:00 -0700
Message-ID: <CABevsUE3BbAf3sc7==yu5QynqjVn8=L4FHA9g-pQd=y3rwjJZA@mail.gmail.com>
To: Benjamin Young <bigbluehat@hypothes.is>
Cc: W3C Public Annotation List <public-annotation@w3.org>
That is exactly what the oa:List construct is intended to be used for :)

Another use case would be to extract an HTML file from a package and then
apply a further selection mechanism.

R

On Thu, Jul 30, 2015 at 2:24 PM, Benjamin Young <bigbluehat@hypothes.is>
wrote:

> Right now, [Annotator](http://annotatorjs.org/) (for one) doesn't think
> much outside of it's own world (at least not without plugins), so the
> ranges it stores are specific to how a developer has connected it to the
> document.
> It currently stores a relative XPath range to get to the DOM node, and
> then a numeric text range for the actual selection within that DOM node.
> If the parent of the XPath range (what Annotator is "attached" to) were
> known, would it be possible to express this sort of combination of
> selectors in a way that Web Annotation implementors could understand?
>
> Is this an intended use of `oa:List`?
> http://www.w3.org/TR/annotation-model/#h3_list
>

-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305
Received on Thursday, 30 July 2015 21:28:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:38 UTC