- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Thu, 3 Sep 2015 10:52:34 +0200
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: Gregory Williams <greg@evilfunhouse.com>, RDF Comments <public-rdf-comments@w3.org>
Hi Gregg,
> As @base may have a relative IRI, it seems reasonable to always attempt to make it absolute by resolving it to the document location, yet this is at odds with your interpretation
Upon further inspection, I found this:
while RFC3986 indeed would resolve this way,
the Turtle spec says that:
Relative IRIs are resolved with base IRIs as per Uniform Resource Identifier (URI): Generic Syntax [RFC3986]
So apparently, only relative IRIs may follow the algorithm in RFC3986.
> Here the scheme is missing from @base, so it clearly needs to be resolved, but will yield different results from <http://a/bb/ccc/../d;p?q> (assuming file location/previous base used http scheme), which would be pretty odd.
So while it is certainly odd, I'm afraid it is the correct way,
because <http://a/bb/ccc/../d;p?q> is not relative and should thus not be resolved,
if we follow what the Turtle spec says.
That is, if I interpret correctly. What do you think?
Best,
Ruben
Received on Thursday, 3 September 2015 08:53:05 UTC