Selectors as URIs?

(Although this may not be immediately relevant to the Working Group right now, I think the question *may* become relevant, hence my copy to it…)

Rob, Paolo,

a question came up at the Digital Publishing IG today. The IG is looking at general fragment identifiers for the purpose of identifying portions within a digital document (typically EPUB, but also some future versions of it). The Selector structure of the OA obviously gives a great model for various types of anchors, mainly when combined with other, existing fragment id definitions.

However, at present, the selectors are defined in terms of RDF resources; to take an example from the spec, it says, for example

selector": {
      "@id": "http://example.org/selector1",
      "@type": "oa:DataPositionSelector",
      "start": 4096,
      "end": 4104
}

To be usable for a fragment identification, this structure should be turned into some sort of a, well, URI fragment. I mean, it is probably relatively easy to do this, something like

http://www.example.org/#selector(type=DataPositionSelector,start=4096,end=4104)

would do it but, of course, the ideal would be if that type of fragment format would be defined at one place.

The question is: has this ever been discussed previously on the OA model? If it hasn't been done, should it be done? If it should be done, should it be done by this WG, or some other group?

Thanks

Ivan


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704