- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jan 2016 13:32:32 +0000
- To: public-annotation@w3.org
I have the impression that two different issues are mixed up here. 1. What to do with embedding of annotations in the target document. That is the original issue, I believe, and I agree postponing it. It has not been seriously discussed in the group so far, it is a typical topic for the next possible incarnation of the group. 2. The issue raised by @csarven is, I believe, different. At present the model document allows for a more detailed characterization of the body. See many of the sections in [Section 3.2](https://w3c.github.io/web-annotation/model/wd/#bodies-and-targets) of the current latest draft. Eg, set the language, creator, media type, etc. I believe the issue/question is whether the same facilities should be provided to targets as well. Considering @csarven: although I can see the point of doing this, eg, specifying that the target is a moving image, I am not sure those are annotation specific use cases. Using RDF (whether in JSON-LD or Turtle or RDFa) means that those extra properties can be added, of course, to any target, but I do not believe that it is the issue for the WA model to provide a fine characterization of the target; it is pretty reasonable to say that the focus is on the body which is, in some sense, the "active" part of an annotation. In other words, I do not see any modification on the model. I would be o.k. if the document included a note somewhere in that section making it clear to the reader that application MAY use the properties like dctypes or dcterms to further characterize the target, too, but this document concentrates on the body only. Or something like that. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/87#issuecomment-175630091 using your GitHub account
Received on Wednesday, 27 January 2016 13:32:34 UTC