Re: Fragment URIs incompatible with Fragment Selectors?

The text could be clearer, but the intent is that you cannot use Specifiers
(State, Selector, Scope, Style) with fragment URIs, you need a
SpecificResource.

Rob


On Mon, Sep 14, 2015 at 2:38 AM, Vladimir Alexiev <
vladimir.alexiev@ontotext.com> wrote:

> http://www.w3.org/TR/annotation-model/#fragment-uris says
> "Fragment URIs are not compatible with other methods of describing the
> segment more specifically, described in the Specific Resources section"
>
> But I wonder why the two must be incompatible.
> - It seems to me that in
> http://www.w3.org/TR/annotation-model/#fragment-selector, using a URL with
> fragment (e.g. <target1#fragment>) instead of an unrelated URL (e.g.
> <sptarget1>) would be nicer
> - the fragment is not sent by a client to the server, is that the problem?
>    If so, please add it to the list of "consequences" at
> http://www.w3.org/TR/annotation-model/#fragment-uris.
>    I'm not sure that's a problem, eg NIF uses <#char=start,end> URLs with
> impunity
>
> (Otherwise, I agree that URLs are opaque, and providing the fragment in a
> separate field is a better practice)
>
> Cheers!
>
>
>


-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305