- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Dec 2015 08:28:03 +0000
- To: public-annotation@w3.org
> @iherman <https://github.com/iherman> When we add a feature, we need to know what the requirements are, so we can make sure it has the right characteristics. My expectation is that this will be pretty simple, and I'd like Hypothes.is and others who have implemented a "groups" feature to let us know what is needed. > Well, I do not know what this feature is, in fact (apart from what can already be modeled with the Audience, as I said in my previous reply). I still do not know what we are *really* discussing. > While I agree that we shouldn't define the details of authorization and access control, if we want interoperability, we may wish to add a normative requirement that a UA SHOULD honor a stated restriction, whether that is group or some other well-defined "audience" (I can imagine that students might not have access to instructor annotations on a textbook, for example). > > I think this falls under the resolution we decided for issue #19 -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/119#issuecomment-161549365 using your GitHub account
Received on Thursday, 3 December 2015 08:28:08 UTC