W3C home > Mailing lists > Public > semantic-web@w3.org > April 2005

Re: SemWeb Non-Starter -- Distributed URI Discovery

From: Patrick Stickler <patrick.stickler@nokia.com>
Date: Tue, 5 Apr 2005 08:57:56 +0300
Message-Id: <6906ee9ed664c988051b85a7936970a3@nokia.com>
Cc: Ora Lassila <ora.lassila@nokia.com>, "<semantic-web@w3.org>" <semantic-web@w3.org>
To: "ext Richard Newman" <r.newman@reading.ac.uk>

On Apr 5, 2005, at 00:13, ext Richard Newman wrote:

> Patrick,
>   It's funny you should say that, because I think I just added some 
> weight to your argument -- I just implemented a URIQA server using 
> Ora's Wilbur[1] toolkit and the Araneida Web server[2].


(I really need to put together an online listing of all the
  various URIQA implementations, sever and client side; there
  are quite a few, and more all the time -- which is great)

> It only took me a few hours of work, and I think everything's in there 
> barring the facets format (the PDF for which seems to have 
> disappeared).

I believe you are referring to 
though note that this is not part of URIQA, but a technique we use in 
with our generalized search and navigation solution (which covers both
metadata and textual content).

>   Extending my other software clients to use it is trivial, and 
> (seeing as they also use Wilbur) making a knowledge-sharing web of 
> apps using URIQA is a simple matter.


>   Granted, this has not been well-tested, and I haven't compared it 
> thoroughly to the reference implementation (there's a shortage of 
> Windows machines in my office!), but it seems to work on my machine :) 
> I thought you might be interested regardless.


>   Full scoop at [3].



> -R
> [1] <http://wilbur-rdf.sourceforge.net>
> [2] <http://cliki.net/Araneida>
> [3] <http://www.holygoat.co.uk/blog/entry/2005-04-04-2>
> On Apr 4, 2005, at 07:17, Patrick Stickler wrote:
>> Actually, because URIQA is based at the lowest architectural layer of 
>> the web, the
>> HTTP protocol itself, adoption of URIQA is orders of magnitude easier 
>> and less
>> costly than other "best practice" solutions (e.g. special headers, 
>> embedded metadata,
>> content negotiation, etc.) because implementation and deployment of 
>> the fundamental
>> URIQA functionality can be constrained to the web server platform 
>> itself, either
>> natively or by plug in, and each web site owner does not have to 
>> introduce, police,
>> and manage the practices of each user, but rather, each user is free 
>> to exploit
>> the standardized functionality made available for describing 
>> resources.
Received on Tuesday, 5 April 2005 06:40:05 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:52 UTC