W3C home > Mailing lists > Public > www-rdf-interest@w3.org > October 2003

RE: Announcement: The "info" URI Scheme

From: Paskin, Norman (DOI-ELS) <n.paskin@doi.org>
Date: Wed, 1 Oct 2003 16:18:01 +0100
Message-ID: <2EA918FE7CC6FB4BA0510D671ADB2AB406FAE29F@elsoxfvexch01.elsevier.co.uk>
To: "'thabing@uiuc.edu'" <thabing@uiuc.edu>, Jeremy Carroll <jjc@hplb.hpl.hp.com>
Cc: "Hammond, Tony (ELSLON)" <T.Hammond@elsevier.com>, 'Patrick Stickler' <patrick.stickler@nokia.com>, www-rdf-interest@w3.org, uri@w3.org

Yes, such a mapping to a URL is needed; and yes, it exists; we have this and
it's called the DOI: www.doi.org

Norman Paskin
International DOI Foundation
web site: http://www.doi.org
Tel: (+44) 1865 314033
Fax: (+44) 1865 314475

-----Original Message-----
From: Thomas G. Habing [mailto:thabing@uiuc.edu]
Sent: 01 October 2003 16:01
To: Jeremy Carroll
Cc: Hammond, Tony (ELSLON); 'Patrick Stickler'; www-rdf-interest@w3.org;
Subject: Re: Announcement: The "info" URI Scheme

Hi all,

I'm usually just an interested observer in this list.  However, in reading 
about the 'info' scheme and the car/document problem, an idea has struck 
which I will float past the group.  Perhaps its already been thought of in 
other contexts and shot down or not, but I'm too lazy to do the research, so

here it is :-)

The specification of the 'info' scheme could define a standard mapping 
between the 'info' and 'http' schemes.  Whenever the 'info' URI is used it 
is understood to represent the concept.  However, after applying the 
standard mapping the resulting 'http' URI is understood to represent the 
document describing the concept (which may or may not actually be 
resolvable). For example:


maps to:


The "info.niso.org" domain is chosen as an example, but there would need to 
be some domain which is controlled by the same organization who is 
responsible for maintaining the 'info' namespaces.  This group is also 
responsible for managing any subdomains and resolvable documents in those 
subdomains which correspond to the various info namespaces.

Presumable the mapping could go both ways if one recognizes that 
info.niso.org (or whatever) is the domain which manages the info namespace.

I'm sure there are lots of ugly details that would need to be worked out, 
but it seems like something like this could work, and potentially solve the 
car/document problem in a fairly simple manner.

Kind regards,

Thomas Habing
Research Programmer, Digital Library Projects
University of Illinois at Urbana-Champaign
155 Grainger Engineering Library Information Center, MC-274
thabing@uiuc.edu, (217) 244-4425

Jeremy Carroll wrote:

> While having some sympathy with Patrick here, I note that a new scheme 
> that is URIs not URLs neatly sidesteps the car/document problems.
> An info URI identifies a concept not a document about that concept.
> A similar http URL would be taken as identifying either or both 
> depending on who you talk to.
> Jeremy
> Hammond, Tony (ELSLON) wrote:
>>> Why define and manage the URI space outside the scope of the core Web
>>> and SW machinery?
>> Hi Patrick:
>> I have to query the question you put above. IMO the "info" URI scheme 
>> fits
>> full square within the core Web and SW machinery as articulated in the
>> latest Web Architecture Draft:
>>     Architecture of the World Wide Web
>>     W3C Working Draft 27 June 2003
>>     http://www.w3.org/TR/webarch/
>> The domain of URI is more extensive than HTTP alone. I would assert 
>> that the
>> actual domain of URI is the Web.
Received on Wednesday, 1 October 2003 11:20:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:44 UTC