- From: BigBlueHat via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Nov 2015 22:04:29 +0000
- To: public-annotation@w3.org
Tagging is not an extension mechanism...it's tagging. :smiley: Plus, the magic string "ext:typoReplacing" in a body with the role "tagging" doesn't really prep for interop anything...especially not copy-editing. Additionally, we already have [Appendix D](http://w3c.github.io/web-annotation/model/wd/#extending-motivations) for extending motivations--which is the only proper value of `oa:hasRole`--so that piece is already done regardless of having one or more than one `role` expressed. Perhaps putting some code (of various kinds) on the two scenarios (`role` as string vs. `role` as string or array of strings) could shed some light on the actual cost of this proposal to JSON developers. Graph consuming folks won't be effected by this, afaik...at least not negatively. :smile: -- GitHub Notification of comment by BigBlueHat Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/104#issuecomment-158538584 using your GitHub account
Received on Friday, 20 November 2015 22:04:30 UTC