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: Fri, 15 Apr 2016 09:21:54 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-210378918-1460712113-sysbot+gh@w3.org>
@azaroth42 : 

> States describe the representation (or state) of the resource that 
is desired. Once the processor has that representation, the Selector 
describes the part of the representation that is being annotated. So 
there is (still) a difference between the two classes.

I am personally fine with this, hence I am fine keeping the current 
separation. One could debate whether 'state' is the best term, but 
finding anything else would be bikeshedding. No need for it now.

As for the original issue: I still believe the simple approach in [my 
comment](https://github.com/w3c/web-annotation/issues/195#issuecomment-203239919)
 would work well:

1. 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)
2. allow the refinement of a state by a selector

We achieve the same effect (first extract the resources with, eg, HTTP
 restrictions, then select part of the resource), without any further 
complication in the specification.



-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/195#issuecomment-210378918
 using your GitHub account
Received on Friday, 15 April 2016 09:21:56 UTC

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