Re: RDF's relative IRI resolution is ambiguous

On Sep 3, 2015, at 12:52 PM, Ruben Verborgh <ruben.verborgh@ugent.be> wrote:

>> This implies that we should accept Greg’s reasoning on the tests, but perhaps add <http://a/bb/ccc/../> and <http://a/bb/ccc/./> cases to be sure. Right now, there should be no difference between <http://a/bb/ccc/> <http://a/bb/ccc/.>, <http://a/bb/ccc/..>, or <http://a/bb/ccc/d>
>
> Agree on adding those, but the behavior for <http://a/bb/ccc/../> should be different from <http://a/bb/ccc/..>, right?
> Since "the right-most '/' in the base URI" would then be the last one, I would expect
> that resolving <g> against <http://a/bb/ccc/../> yields <http://a/bb/g>,
> whereas resolving <g> against <http://a/bb/ccc/..> yields <http://a/bb/ccc/g>.
>
> Can I add the cases like that (and correct the existing ones)?

Yes, the point would be to check the effect of the dot segments in
base with trailing slash.

>> We need to tread lightly, and get broader input across other implementations of different related specs.
>
>
> I knew I didn't start this thread lightly ;-)

I'll check my other implementations, but we'd need to check against
different implementations of these specs, and be prepared to update
those test suites as well before I'd be comfortable releasing such a
change.

Gregg

> Best,
>
> Ruben

Received on Thursday, 3 September 2015 20:19:24 UTC