- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Mar 2016 03:40:05 +0000
- To: public-annotation@w3.org
It's consistent with the embedded content pattern, rather than the values in selectors pattern. The use of text here is because we used to use Content in RDF to embed the SVG resource's representation. The same with the CSS Style. I think this is correct, rather than value ... we're embedding the content of the representation into the graph, rather than providing a stand alone value that is not a representation. If there isn't an id, then it's just a blank node. So long as the representation _is_ available from the URI in id, I don't see a problem. That said I do see the point about type-jacking. We solved that already for Semantic Tags where the resources were very likely not to be ours. On the other hand, here it seems that finding an SVG document in the wild that happened to express the right area for the selection is so improbable as to not be worth worrying about? -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/191#issuecomment-202219100 using your GitHub account
Received on Monday, 28 March 2016 03:40:06 UTC