W3C home > Mailing lists > Public > www-tag@w3.org > October 2004

Re: referendum on httpRange-14 (was RE: "information resource")

From: Walden Mathews <walden@eqwality.com>
Date: Wed, 27 Oct 2004 10:02:02 -0400
Message-ID: <021401c4bc2d$891e21a0$c21bfea9@WALDENNOTEBOOK>
To: "Bullard, Claude L \(Len\)" <len.bullard@intergraph.com>, "Patrick Stickler" <patrick.stickler@nokia.com>
Cc: <www-tag@w3.org>

Representations are also solid bits, and time
seems comparatively "solid" too.  What if a URI
is the name of a relation that maps from time
to representations?

The idea is not new.

Walden

----- Original Message ----- 
From: "Bullard, Claude L (Len)" <len.bullard@intergraph.com>
To: <Patrick.Stickler@nokia.com>
Cc: <www-tag@w3.org>
Sent: Wednesday, October 27, 2004 9:49 AM
Subject: RE: referendum on httpRange-14 (was RE: "information resource")


| 
| I'm not sure it's useful either.  It's just that when one 
| factors the definitions, URIs are the only solid bits.  
| Everything else is 'turtles all the way up'. 
| 
| That means the web isn't an information space.  
| It's a name space of opaque identities.
| 
| len
| 
| 
| From: Patrick.Stickler@nokia.com [mailto:Patrick.Stickler@nokia.com]
| 
| It's an odd thing to do, but I don't see why you can't have e.g.
| 
|    <http://example.com/blargh> owl:sameAs
| "http://example.com/foo"^^xsd:anyURI .
| 
| Thus, <http://example.com/blargh> identifies the specific
| URI "http://example.com.foo". Note that the above statement is not
| the same as
| 
|    <http://example.com/blargh> owl:sameAs <http://example.com/foo> .
| 
| I.e. in the first case, <http://example.com/blargh> is identifying the
| URI, the string conforming to the lexical constraints for URIs, and
| is not (necessarily) identifying what the URI "http://example.com/foo"
| itself identifies.
| 
| --
| 
| How having one URI identify another URI would be useful is unclear to me.
| 
| But in principle, a URI is a thing, and if a URI can identify anything,
| then one URI can certainly identify another URI.
| 
| And having an RDF description of <http://example.com/blargh> available
| allows one to clarify that it identifies a URI, which is quite clear
| from the first RDF statement above.
| 
| Patrick
| 
| 
| 
| > From: ext Bullard, Claude L (Len) [mailto:len.bullard@intergraph.com]
| > Sent: 26 October, 2004 22:49 
| > 
| > A mad thought:  if URIs identify resources (not representations), 
| > and resources are abstract, do URIs only (put verb here) 
| > other URIs?
| 
| 
| __________ NOD32 1.907 (20041027) Information __________
| 
| This message was checked by NOD32 antivirus system.
| http://www.nod32.com
| 
|
Received on Wednesday, 27 October 2004 14:02:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:43 UTC