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
On Fri, Nov 24, 2023 at 12:50 PM Laura Morales 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
> 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
On Fri, Nov 24, 2023 at 11:46 AM Laura Morales wrote:
>
> > > in the case that I want to use these URLs with a web browser.
> >
> > I don't understand what the trouble with the above example is?
>
> The problem with # is that browsers treat them as the start of a local
> reference. When you open
> > in the case that I want to use these URLs with a web browser.
>
> I don't understand what the trouble with the above example is?
The problem with # is that browsers treat them as the start of a local
reference. When you open http://example.org/book#1 the server only receives
The URI syntax is defined by the Internet Engineering Task Force (IETF) in
RFC 3986.
W3C RDF is just a rule-taker here ;)
https://datatracker.ietf.org/doc/html/rfc3986
Marco
On Fri, Nov 24, 2023 at 10:36 AM Laura Morales wrote:
> > What do you mean by human-readable here? For large technical
> What do you mean by human-readable here? For large technical systems it's
> simply not feasible to encode meaning into the URI and I might even
> consider it an anti-pattern.
This is my problem. I do NOT want to encode any meaning into URLs, but I do
want them to be human readable simply
(side note) preferably the local name of a URI should not start with a
number but a letter or underscore.
What do you mean by human-readable here? For large technical systems it's
simply not feasible to encode meaning into the URI and I might even
consider it an anti-pattern.
There are some
On Fri, Nov 24, 2023 at 10:31 AM Laura Morales wrote:
>
> Thank you a lot. FILTER(STR(?id) = "...") works, as suggested by Andy. I do
> recognize though that it is a hack, and that URLs should probably not have a
> [.
>
> But now I have trouble understanding UTF8 addresses. I would use random
Thank you a lot. FILTER(STR(?id) = "...") works, as suggested by Andy. I do
recognize though that it is a hack, and that URLs should probably not have a [.
But now I have trouble understanding UTF8 addresses. I would use random
alphanumeric URLs everywhere if I could, or I would %-encode
Laura, see jena issue #2102
https://github.com/apache/jena/issues/2102
Marco
On Fri, Nov 24, 2023 at 7:12 AM Laura Morales wrote:
> I have a few URLs containing square brackets like
> http://example.org/foo[1]bar
> I can create a TDB2 dataset without much problems, with warnings but no
>
11 matches
Mail list logo
