W3C home > Mailing lists > Public > public-annotation@w3.org > April 2016

Re: [web-annotation] Model should allow multiple Selectors per SpecificResource

From: Ivan Herman via GitHub <sysbot+gh@w3.org>
Date: Fri, 29 Apr 2016 16:50:25 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-215804584-1461948623-sysbot+gh@w3.org>

> Right :) That's how I came to the (IMO) bug.
> My understanding from #93 is:
> If there are multiple States/Selectors/Styles/Renderings/... then 
you pick one (previously it was an explicit oa:Choice)
But... doesn't that leads to interoperability issues. You pick, 
randomly, one and I pick the other? What is the use case for this?

> If you need to have more than one and they all get processed in 
order, that's where refinedBy comes in. (previously it was an explicit
> If you need more than one and the order doesn't matter ... then just
 put them in some order using refinedBy. (previously an explicit 
> The docs for refinedBy say:
> A Selector may be refinedBy 1 or more other Selectors. If more than 
1 is given, then they are considered to be alternatives that will 
result in the same selection.
> And my proposal is that this should be copied to selector as well 
(with clarification that they may not all have the same fidelity)
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub

GitHub Notification of comment by iherman
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 29 April 2016 16:50:27 UTC

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