W3C home > Mailing lists > Public > public-lod@w3.org > October 2011

Re: Explaining the benefits of http-range14 (was Re: [HTTP-range-14] Hyperthing: Semantic Web URI Validator (303, 301, 302, 307 and hash URIs) )

From: Leigh Dodds <leigh.dodds@talis.com>
Date: Wed, 19 Oct 2011 22:29:03 +0100
Message-ID: <CAJgK0KHg5nAsVy=+XsVpGYx2L==FcR4=Kzf_HNTSn_8i__ua9w@mail.gmail.com>
To: Jonathan Rees <jar@creativecommons.org>
Cc: "public-lod@w3.org" <public-lod@w3.org>
Hi Jonathan

On 19 October 2011 18:36, Jonathan Rees <jar@creativecommons.org> wrote:
> On Wed, Oct 19, 2011 at 12:59 PM, Leigh Dodds <leigh.dodds@talis.com> wrote:
>> So, can we turn things on their head a little. Instead of starting out
>> from a position that we *must* have two different resources, can we
>> instead highlight to people the *benefits* of having different
>> identifiers? That makes it more of a best practice discussion and one
>> based on trade-offs: e.g. this class of software won't be able to
>> process your data correctly, or you'll be limited in how you can
>> publish additional data or metadata in the future.
>> I don't think I've seen anyone approach things from that perspective,
>> but I can't help but think it'll be more compelling. And it also has
>> the benefits of not telling people that they're right or wrong, but
>> just illustrate what trade-offs they are making.
>> Is this not something we can do on this list? I suspect it'd be more
>> useful than attempting to categorise, yet again, the problems of hash
>> vs slash URIs. Although a canonical list of those might be useful to
>> compile once and for all.
>> Anyone want to start things off?
> Sure.  http://www.w3.org/2001/tag/2011/09/referential-use.html

Thanks for the pointer. That's an interesting document. I've read it
once but need to digest it a bit further.

The crux of the issue, and what I was getting at in this thread is
what you refer to towards the end:

"It is possible that D2 and S2 can be used side by side by different
communities for quite a while before a collision of the sort described
above becomes a serious interoperability problem. On the other hand,
when the conflict does happen, it will be very painful."

I think what I'm interested in is what problems might surface and
approaches for mitigating them. I'm particularly curious whether
heuristics might be used to disambiguate or remove conflict.

>> As a leading question: does anyone know of any deployed semantic web
>> software that will reject or incorrectly process data that flagrantly
>> ignores httprange-14?
> Tabulator.

Yes. That's the only piece of software I've heard of that has problems.

Leigh Dodds
Product Lead, Kasabi
Mobile: 07850 928381

Talis Systems Ltd
43 Temple Row
B2 5LS
Received on Wednesday, 19 October 2011 21:29:31 UTC

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