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

Re: [web-annotation] Can I refine a state via a selector?

From: Ivan Herman via GitHub <sysbot+gh@w3.org>
Date: Thu, 21 Apr 2016 17:02:47 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-213017601-1461258166-sysbot+gh@w3.org>
I actually realized I was misunderstandable, my mistake. What I meant 
was not to have two states or two selectors in one place. At the 
moment it is not defined what this means. We also have to define 
formally what it means to have state *and* selector in one place, by 
the way.

Ivan

---
Ivan Herman
Tel:+31 641044153
http://www.ivan-herman.net

(Written on mobile, sorry for brevity and misspellings...)



> On 21 Apr 2016, at 18:41, Rob Sanderson <notifications@github.com> 
wrote:
> 
> As for the original issue: I still believe the simple approach in my
 comment would work well:
> 
> disallow state and selector appearing in the same object in parallel
 (otherwise we will have to give some formal definition on priority of
 these, something that is not in the document)
> allow the refinement of a state by a selector
> I'm not keen, as it means that you couldn't reuse a State in 
different Annotations, they would always be tied together with the 
Selectors. It would also be inconsistent with the way styles and the 
other aspects of SpecificResources work. To disallow both hasState and
 hasSelector on the same specific resource seems like a big change, 
compared to just allowing Selectors to be refined by other Selectors, 
and States to be refined by other States.
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> 


-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/195#issuecomment-213017601
 using your GitHub account
Received on Thursday, 21 April 2016 17:02:49 UTC

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