W3C home > Mailing lists > Public > public-rdf-comments@w3.org > August 2015

Re: RDF's relative IRI resolution is ambiguous

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Fri, 28 Aug 2015 00:58:34 +0200
Cc: Richard Cyganiak <richard@cyganiak.de>, RDF Comments <public-rdf-comments@w3.org>
Message-Id: <D7A7898E-A80F-48DF-A895-0C2F7101FC22@ugent.be>
To: Gregg Kellogg <gregg@greggkellogg.net>
>> Normalization of the base URI, as described in Sections 6.2.2 and 6.2.3, is optional.
> So, it would seem that we need to be explicit about expected behavior.


> Special casing <> in Turtle would be unfortunate

Indeed. Furthermore, it's not just <>, but also <#> and <?>.

If the base URI should be normalized, then given a base of <http://example.org/xxx/yyy/zzz/../../../>
    <> becomes <http://example.org/>
    <#abc> becomes <http://example.org/#abc>
    <?abc> becomes <http://example.org/?abc>

If the base URI should not be normalized, then
    <> becomes <http://example.org/xxx/yyy/zzz/../../../>
    <#abc> becomes <http://example.org/xxx/yyy/zzz/../../../#abc>
    <?abc> becomes <http://example.org/xxx/yyy/zzz/../../../?abc>

Given the Turtle spec's wording, I think the latter was intended.


Received on Thursday, 27 August 2015 22:59:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:59:49 UTC