Re: Important Change to HTTP semantics re. hashless URIs

On Mon 2013-Mar-25, at 09:33, Adrian Gschwend <ktk@netlabs.org> wrote:

> On 25.03.13 09:42, Mo McRoberts wrote:
>
> Hi Mo,
>
>> It's good to have the clarification (the wording in the new draft is
>> nicer), but it's probably worth stressing that Content-Location isn't
>> at all new, and this *mostly* amounts to a tidying-up of wording
>> rather than a change in semantics.
>
> that's IMHO the beauty of it.
>
>> The biggest change here is actually the “However, such an assertion
>> cannot be trusted..." part!
>
> correct but I don't see that as a problem for what we try to solve.

no, absolutely — again, I think it's primarily a point of clarification.

most LOD implementations that I've come across put the document on what would be considered to be the same origin as the Request-URI, so it'd generally have little impact even if were to be validated by the harshest of current agents!

M.

--
Mo McRoberts - Analyst - BBC Archive Development,
Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
MC3 D4, 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 Monday, 25 March 2013 09:39:56 UTC