Martynas, I think you have to go way back in time to fully appreciate the anchor reference and its "interference" with URI local names. :)
Fundamentally URIs as identifiers are not meant to be retrieved as such Laura. So a web browser is not designed to follow the implicit "physical" link of an identifier. To "browse" URIs as identifiers only you need a RDF browser or plugin that may dereference documents from objects for display as URLs. Marco On Fri, Nov 24, 2023 at 1:55 PM Martynas Jusevičius <marty...@atomgraph.com> wrote: > On Fri, Nov 24, 2023 at 12:50 PM Laura Morales <laure...@mail.com> wrote: > > > > > If you want a page for every book, don't use fragment URIs. Use > > > http://example.org/book/1 or http://example.org/book/1#this instead of > > > http://example.org/book#1. > > > > yes yes I agree with this. I only tried to present an example of yet > another "quirk" between raw data and browsers (where this kind of data is > supposed to be used). > > Still don't understand the problem :) http://example.org/book#1 > uniquely identifies a resource, but you'll need to get the whole > http://example.org/book document to retrieve it. That's just how HTTP > works. > -- --- Marco Neumann
