- From: Sarven Capadisli via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Nov 2015 20:45:23 +0000
- To: public-annotation@w3.org
csarven has just created a new issue for https://github.com/w3c/web-annotation: == Embedded Targets == Would it make sense to broaden embedded bodies, more specifically textual bodies to also cover targets? While hasTarget has extensive ways of capturing the target information, it doesn't appear to have a simple way to refer to some text/markup. For example, hasBody can have oa:text, meanwhile hasTarget has to go through hasSelector - this is unless of course it is not prohibited to use oa:text on hasTarget. I have something along the lines of: `<mark about="[this:#foo]" typeof="http://purl.org/dcmitype/Text">foo</mark>`, which was marked by the UI. That subject (#foo) will be the target of an annotation. What I'd like to do is extend that by simply saying that the target has a value/label/description/HTMLtext instead of having to go through hasSelector. If oa:text is okay on hasTarget, I suggest some editorial on http://www.w3.org/TR/annotation-model/#textual-body and broaden the description to cover both body and target. See https://github.com/w3c/web-annotation/issues/105
Received on Friday, 6 November 2015 20:45:26 UTC