- From: Randall Leeds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Apr 2016 06:45:32 +0000
- To: public-annotation@w3.org
Rob, thank you. I accept that the handling of state and selector happens in different phases in the course of common annotation interactions. You've described this well and your description helpfully reveals the assumptions we have that seem to justify the separation, that a state is used to fetch a representation and then a selector specifies a segment of that representation. I can, however, imagine uses where arbitrary refinement simplifies processing. In archival situations, where many versions of a single URL might already be available, the selector vocabulary could be leveraged for search. Perhaps I want to reference the set of archived versions of some document that contain some particular text. I could represent this query in a structured way using this vocabulary. Separating the terms perhaps simplifies processing and renders the intent clearer for our common use cases. Structurally, it flattens the graph a bit by lifting selector out from a refinement of the state (if any). If questioning this is unappealing to everyone, I am not too bothered, but I find it interesting to consider. There is an elegance to the unification to my brain. -- GitHub Notification of comment by tilgovi Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/195#issuecomment-211758796 using your GitHub account
Received on Tuesday, 19 April 2016 06:45:34 UTC