W3C home > Mailing lists > Public > public-sweo-ig@w3.org > January 2008

Re: HTTP URIs for real world objects

From: Leo Sauermann <leo.sauermann@dfki.de>
Date: Wed, 16 Jan 2008 10:44:45 +0100
Message-ID: <478DD20D.6070706@dfki.de>
To: Reto Bachmann-Gmür <reto@gmuer.ch>
CC: public-sweo-ig@w3.org

Hi Reto,

the document you discuss is describing the already-done-decisions of the 
TAG to a greater audience. The decisions have been made long ago and the 
document explains them. We cannot incorporate your feedback as it 
suggest changing the TAG decisions, which is against the goal of the 

Your answer suggests to replace the whole architecture of the internet, 
including DNS and HTTP.
You may want to join the W3C and start a working group on this.
Otherwise, the right mailinglist to discuss this is semantic-web@w3.org

greetings and best wishes

It was Reto Bachmann-Gmür who said at the right time 15.01.2008 22:15 
the following words:
> From http://www.w3.org/TR/2007/WD-cooluris-20071217/
>> Given only a URI, machines and people should be able to retrieve a 
>> description about the resource identified by the URI from the Web. 
>> Such a look-up mechanism is important to establish shared 
>> understanding of what a URI identifies. Machines should get RDF data 
>> and humans should get a readable representation, such as HTML. The 
>> standard Web transfer protocol, HTTP, should be used.
> I think there are reasons to deprecate use of HTTP URIs for real-world 
> object as promoting the assumption that dereferencing such a URI 
> yields to an authoritative definition is dangerous.
>    * DNS is centralistic
>          o I don't know if control has passed from the US DoC to UN
>            WSIS or to someone else. The root servers are controlled by
>            a more or or less democratic central authority and so are
>            the different top-level domains. Relaying on HTTP URIs is
>            relying on the DNS system which means trusting all
>            authorities of the different levels of the domain name. This
>            seems incompatible with the design principle of
>            decentralization [1].
>    * HTTP is insecure
>          o One cannot know if an HTTP response comes from where its
>            supposed to come from, or whether it has been modified or
>            read on the way to my computer. Even if I can still encrypt
>            all my actual communication, having to look up the
>            definitions of the used terms over an unencrypted connection
>            compromises my privacy.
>    * Uncool URIs happen
>          o In an ideal world Alice will always control the response for
>            http://www.example.com/id/alice. In the real world however:
>                + Alice's server might by cracked
>                + Alice might have forgotten to renew the domain name
>                + Alice might be unable to pay for the hosting or for
>                  the domain
>                + The revolutionary guard might have taken control over
>                  7 root servers redirecting all imperialistic domains
>                  to educational content :)
>                + ...
> Cheers,
> Reto
> 1. http://www.w3.org/2003/01/Consortium.pdf

DI Leo Sauermann       http://www.dfki.de/~sauermann 

Deutsches Forschungszentrum fuer 
Kuenstliche Intelligenz DFKI GmbH
Trippstadter Strasse 122
P.O. Box 2080           Fon:   +49 631 20575-116
D-67663 Kaiserslautern  Fax:   +49 631 20575-102
Germany                 Mail:  leo.sauermann@dfki.de

Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Received on Wednesday, 16 January 2008 09:45:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:58 UTC