[web-annotation] value or text on the definition of an SVG selector

iherman has just created a new issue for 
https://github.com/w3c/web-annotation:

== value or text on the definition of an SVG selector ==
(This issue is *not* aimed at the 2016-03-31 publication, it can be 
handled for future releases!)

At present, the SVGSelector has a the following structure:

Either the svg is referred to via a URI; in JSON this means that it 
uses the id:

```json
"selector" : {
   "type" : "SvgSelector",
   "id" : "http://ex.org/svg"
}
```
or the svg part in incorporated in the object, ie,

```json
"selector" : {
   "type": ["Selector","Content"],
   "text": "<svg:svg> ... </svg:svg>"
}
```

I have several problems with this

1. Modeling-wise, in terms of RDF, I believe what we have here is that
 we add an `rdf:type` to the `http://ex.org/svg`. I do not think this 
is the right thing to do, it looks a little bit like type hijacking 
(we may not "own" the `http://ex.org/svg`, adding an extra type is not
 really our thing to do)
2. This is the only place in selectors where an extra type should be 
used.
3. Everywhere else we use "value" when we specify the details of a 
Selector, the usage of 'text' is a bit odd.

What about:

```json
"selector" : {
   "type" : "SvgSelector",
   "source" : "http://ex.org/svg"
}
```
and

```json
"selector" : {
   "type" : "SvgSelector",
   "value": "<svg:svg> ... </svg:svg>"
}
```

This seems to be more consistent with the rest


Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/191 using your GitHub 
account

Received on Sunday, 27 March 2016 11:35:32 UTC