- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Feb 2016 16:12:44 +0000
- To: public-annotation@w3.org
As feedback I saw that the Example 1 is marked as an issue 1 in String
Body
https://www.w3.org/TR/annotation-model/#string-body
However this representation is in contradiction with the web
annotation principles, which basically say that the annotation is: a
body that is related to a target...
https://www.w3.org/TR/annotation-model/#web-annotation-principles
I agree with the simplication that in the case that the body is "only"
a string, and no more information is available/required for the body,
you can reduce the representation of the body to a string.
Otherwise the TextualBody should be used as üresented in the Example
2.
I don't think that is a good idea to introduce the "bodyText" as
replacement for a { body : {"@type" : "TextualBody"}
Of course different implementations may extend the context and
implement this solution, but I would vote against making it normative,
given the fact that the Example 2 (TextualBody) is already normative.
--
GitHub Notification of comment by gsergiu
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/149#issuecomment-181443989
using your GitHub account
Received on Monday, 8 February 2016 16:12:46 UTC