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

Re: [web-annotation] Multiple Selectors

From: Ivan Herman via GitHub <sysbot+gh@w3.org>
Date: Tue, 26 Jan 2016 07:41:00 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-174875839-1453794059-sysbot+gh@w3.org>
I just realized that this issue has a strong connection to issue #110 
('Make Selectors available for the wide world?'). I do not want to 
repeat the arguments there; the short version is that I believe we 
should leave the door open to (1) make the selectors useful for usage 
patterns that are not necessarily related to annotations and (2) it 
may be useful/important to define new fragment identifiers expressing 
selectors. We agreed that this cannot be done, as recommendations, in 
the WG, but we should not make such an evolution unnecessarily 
difficult if we can avoid.

Looking at the "direct" vs. the "inverse" approach it is fairly clear 
to me that, mainly in view of (2) above, this shifts the balance 
strongly towards the "direct" approach. Indeed, one of the 'cons' for 
the "inverse" is that it mixes, in some sense, the original source's 
URL with the selection mechanism, whereas the "direct" approach 
doesn't. This means that translating the "direct" approach into a 
fragment identifier is doable (with the non-fragment part of the URL 
referring to the source) whereas the "inverse" approach becomes much 
less obvious.

As far as I am concerned, this tips the balance for me. My vote goes 
firmly towards the "direct" approach.



-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/93#issuecomment-174875839
 using your GitHub account
Received on Tuesday, 26 January 2016 07:41:02 UTC

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