- From: Sarven Capadisli via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Sep 2015 08:47:44 +0000
- To: public-annotation@w3.org
csarven has just created a new issue for https://github.com/w3c/web-annotation: == Simplifying hasBody == My impression of `hasBody` and language handling as a user/publisher: As it is expected to work right now, `hasBody` is overloaded: 1. there is a split for completely different textual bodies; embedded and simple. 2. both cases have too many do's and don'ts. I'm afraid that `hasBody` (arguably) will be misused. A simpler approach here is to acknowledge that both types of textual bodies are significantly different (if so in their functionality) such that they deserve dedicated properties. An obvious strawman proposal to consider: keep `hasBody` for embedded textual body, and have (for the sake of the argument) `hasBodyText` for simple textual body. I realize that having two properties is not pretty at this point, but I think the trade off is that, it will be less complications for both publication and consumption. I think this will also significantly simplify language handling, i.e., dedicated dc:language and language tags. [Another consideration is to see whether simple textual body can be a proper subset of embedded textual body.] Thoughts? See https://github.com/w3c/web-annotation/issues/79
Received on Tuesday, 15 September 2015 08:47:46 UTC