On 25/11/2023 13:47, Marco Neumann wrote:
I was looking for an IRI validator and this one didn't come up in the
search engines. This service might need a bit more visibility and some
incoming links.
It gets lost in all the code library "validators"
Marco
On Sat, Nov 25, 2023 at 1:34 PM
I was looking for an IRI validator and this one didn't come up in the
search engines. This service might need a bit more visibility and some
incoming links.
Marco
On Sat, Nov 25, 2023 at 1:34 PM Andy Seaborne wrote:
>
>
> On 24/11/2023 10:05, Marco Neumann wrote:
> > (side note) preferably the
On 24/11/2023 10:05, Marco Neumann wrote:
(side note) preferably the local name of a URI should not start with a
number but a letter or underscore.
It's a hangover from XML QNames.
Turtle doesn't care.
Style-wise, yes, avoid an initial number.
What do you mean by human-readable here?
On 24/11/2023 08:55, Marco Neumann wrote:
Laura, see jena issue #2102
https://github.com/apache/jena/issues/2102
It's specific to [].
Because data formats accept these bad URIs (with a warning), the fact
SPARQL generates errors is a bug to be fixed.
Andy
Marco
On Fri, Nov 24,
On 24/11/2023 10:40, Marco Neumann wrote:
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
We've drafted a non-normative section:
Another option is the HTTP query string - think of it as asking a
question of resource "http://example.org/book;
Andy
On 24/11/2023 11:03, Martynas Jusevičius wrote:
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
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
ey are much easier to read/edit manually), what is the list of
> characters that MUST be %-encoded?
>
>
> > Sent: Friday, November 24, 2023 at 9:55 AM
> > From: "Marco Neumann"
> > To: users@jena.apache.org
> > Subject: Re: Querying URL with square brackets
> >
> > Laura, see jena issue #2102
> > https://github.com/apache/jena/issues/2102
> >
> > Marco
>
--
---
Marco Neumann
anually), what is the list of characters that
> MUST be %-encoded?
>
>
> > Sent: Friday, November 24, 2023 at 9:55 AM
> > From: "Marco Neumann"
> > To: users@jena.apache.org
> > Subject: Re: Querying URL with square brackets
> >
> > Laura, see jena issue #2102
> > https://github.com/apache/jena/issues/2102
> >
> > Marco
because I want them to be human-readbale (also because they are
much easier to read/edit manually), what is the list of characters that MUST be
%-encoded?
> Sent: Friday, November 24, 2023 at 9:55 AM
> From: "Marco Neumann"
> To: users@jena.apache.org
> Subject: Re: Q
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
>
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 errors.
I can also query these nodes "indirectly", that is if I query them by some
property and not by URI. My problem is that I cannot query
18 matches
Mail list logo
