- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Nov 2015 19:31:30 +0000
- To: public-annotation@w3.org
I agree that we don't want to preclude an HTML serialization, and I don't see that using a JSON-LD key of "role", that maps to a predicate of "oa:hasRole" precludes it in any way. We have a 'target' key, and that's an attribute on the a tag, and also in no way precludes an HTML mapping. I'm fine with having a different name for it, just neither of the proposed. It could be the "function" that the resource plays, but function is also overloaded, and implies a specific outcome (re #113). "purpose"? "use"? That said, we discussed this in great detail and at great length while coming to the current _accepted_ proposal. And communities who don't like our JSON-LD keys can trivially create a new context. -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/112#issuecomment-158502955 using your GitHub account
Received on Friday, 20 November 2015 19:31:36 UTC