- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Nov 2015 05:04:13 +0000
- To: public-annotation@w3.org
Works for me. > On 6 Nov 2015, at 20:40, Rob Sanderson <notifications@github.com> wrote: > > TextualBody and SpecificResource say that there may be 0-1 roles, however there are use cases where multiple roles would be valuable: > > Tagging + clarification. For example tagging + describing, to distinguish from just describing where the body is full text. > Broad + specific. For example editing + ext:typoReplacing, to have a general category and a more specific, machine actionable role that would only be understood by limited implementations > Conciseness. If the same resource really plays two roles, it would be strange to have it as two bodies rather than just giving it two roles. For example, the text of the body may both describe and identify the target. > Proposal: Change 3.2.2.2 and 4.1 to both be MAY have 1 or more roles > > — > -- GitHub Notif of comment by iherman See https://github.com/w3c/web-annotation/issues/104#issuecomment-154621976
Received on Saturday, 7 November 2015 05:04:15 UTC