Re: Selectors as URIs?

It might be worth checking with the CrossRef/CNRI boffins working on a tangentially similar problem with dated and undated references to a standard (as in ISO 9001) for which there is the added complication of multiple national adoptions of the same standard. "Resolve that" has been the jokey challenge.

Not arguing for or against, just highlighting some work that might suggest options for readers here.

The context may be too different though. But the engineering community would welcome the capability to annotate the online version of a standard, share the annotations with colleagues with access to a different national adoption of the same standard, and have those colleagues respond to their annotations.

Sent from my iPhone

> On 13 Apr 2015, at 17:30, Robert Sanderson <azaroth42@gmail.com> wrote:
> 
> 
> Which, to expand slightly, doesn't work as the DOI HTTP handler redirects to another URI without that fragment, losing the semantics of the original URI. 
> 
> Rob
> 
>> On Mon, Apr 13, 2015 at 9:19 AM, Robert Bolick <robert.bolick@gmail.com> wrote:
>> You mean like attaching it to the tail end of a DOI (which many EPUBs and other  online content objects have)? 😁
>> 
>> Sent from my iPhone
>> 
>> > On 13 Apr 2015, at 17:10, Ivan Herman <ivan@w3.org> wrote:
>> >
>> > (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
>> >
>> >
>> >
>> >
> 
> 
> 
> -- 
> Rob Sanderson
> Information Standards Advocate
> Digital Library Systems and Services
> Stanford, CA 94305