Re: odrl-ISSUE-16: Use of @base and relative URIs in examples [ODRL 2 Ontology]

On  2013-Nov-14, at 17:44, Michael Steidl (IPTC) <mdirector@iptc.org> wrote:

> By the code you are right but conclusions from it are surprising - at first sight:
> Our case:
> Base URI = http://example.com/
> Relative path = /asset:9898
> T.authority = Base.authority --> example.com
> T.scheme = Base.scheme --> http
> T.path = /asset:9898
> This makes a final URI http://example.com/asset:9898 - ok.
>
> This example shows a possibly surprising result:
> Base URI = http://example.com/odrl/
> Relative path = /asset:9898
> T.authority = Base.authority --> example.com
> T.scheme = Base.scheme --> http
> T.path = /asset:9898
> The result is also http://example.com/asset:9898 as the code
> if (R.path starts-with "/")
> completely avoids the use of base.path.
>
> I don't want to know how many people looking at the base URI and the relative path would have quickly known that. One could argue in web server terminology that /asset:9898 apparently starts at the root directory of a host but many semantic people simply apply the rule "append a relative path to the base URI and the result is the full URI”.

Why on earth would they do that? Base URI has _never_ meant that, in any context, ever.

I am genuinely perplexed at this idea of a base URI simply being a strict string prefix, particularly given that almost everybody doing semweb has at least dabbled with the basic first principles of the Web and URLs to begin with.

I am fundamentally opposed to actively modifying something which (demonstrably) isn’t broken because some people don’t understand the basics: they will have MUCH bigger problems than this if that’s the case.

M.

--
Mo McRoberts - Analyst - BBC Archive Development,
Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
MC3 D6, Media Centre, 201 Wood Lane, London W12 7TQ,
0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

Received on Thursday, 14 November 2013 17:51:37 UTC