RE: Proposal: new top level domain '.urn' alleviates all need for urn: URIs

> -----Original Message-----
> From: ext Julian Reschke [mailto:julian.reschke@greenbytes.de]
> Sent: 09 July, 2003 23:20
> To: Stickler Patrick (NMP/Tampere); uri@w3.org
> Subject: RE: Proposal: new top level domain '.urn' alleviates all need
> for urn: URIs
> 
> 
> > From: uri-request@w3.org [mailto:uri-request@w3.org]On Behalf Of
> > Patrick.Stickler@nokia.com
> > Sent: Wednesday, July 09, 2003 11:04 AM
> > To: hardie@qualcomm.com; uri@w3.org
> > Subject: RE: Proposal: new top level domain '.urn' 
> alleviates all need
> > for urn: URIs
> >
> > ...
> >
> > > At 9:52 AM +0300 7/8/03, <Patrick.Stickler@nokia.com> wrote:
> > > >
> > > >As for https: URIs, well https: is an oddball URI scheme that
> > > >has inherent in it (IMO) an equivalence assertion. I.e. for
> > > >any two URIs
> > > >
> > > >    http://X
> > > >and
> > > >    https://X
> > > >
> > > >the following can be presumed
> > > >
> > > >    <http://X> owl:sameAs <https://X>
> > >
> > > No, it really cannot.  I know of several cases where they
> > > point to different resources, and many cases where one points
> > > to a resource and the other does not.
> >
> > Perhaps actually different representations, rather than
> > different resources.
> 
> Come on. It's perfectly legal to have port 80 and port 443 served by
> completely separate processes that do not have anything in 
> common. Is this a
> good idea? Probably not. But does it happen? Yes. So do both 
> URIs identify
> the same resource? Only sometimes.

Point taken. I can see that my assertion was perhaps a bit to
strong. It's perhaps only a generalization, and thus not valid
as the basis for an axiom of equivalence.

Patrick

Received on Thursday, 10 July 2003 09:29:35 UTC