ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] Comparable considered necessary
by Joe English other posts by this author
Aug 11 2002 3:42PM messages near this date
RE: [xml-dev] Comparable considered necessary | Re: [xml-dev] Comparable considered necessary
Simon St.Laurent wrote:
> 
>  I think the largest concrete problem I have with URIs is their lack of a
>  common mechanism for saying this equals that.

Two URIs are equal if they are textually identical; that
much should be apparent.

IMO, the only sensible scheme is to strengthen this to 
"if _and only if_" they are textually identical.  Adding 
any other criteria starts down a very steep slippery
slope into unmanageable complexity.

>  I can live without
>  ordering for names, so that's not a big deal, but the lack of clarity on
>  things like:
> 
>  HTTP://MONASTICXML.COM
>  vs.
>  http://monasticxml.com
>  vs.
>  http://monasticXML.com
> 
>  is pretty much killing, even without issues of relative and absolute,
>  query strings, etc.

The only sensible thing to do is to treat all three of
these as distinct URIs.  One _could_ argue that since
the 'http' scheme uses a server-based naming authority,
and since hostnames are case-insensitive according to DNS,
that the latter two should be considered equal.

But there's that slippery slope:  according to DNS,
'monasticxml.org', 'www.monasticxml.org', and '66.45.6.211'
are _also_ equivalent (at least today).


>  The lack of clarity - heck, the outright refusal to acknowledge the
>  question - about how to get from an identifier to a resource or back
>  again - is the nails in the coffin.

I disagree; refusing to acknowledge the question is the
only sensible thing to do.  Asking "Do these two URIs identify
the same resource?" is like asking "are the chair in my living
room and the chair in my dining room both shadows of the
same Platonic Chair?"  Better to unask the question; you
can't reliably get a useful answer.

"Are X and Y the same URI?" is answerable.  "Do X and Y identify
the same resource?" is not.


--Joe English

  jenglish@[...].com

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 
Thread:
Uche Ogbuji
Simon St.Laurent
John Cowan
Simon St.Laurent
Simon St.Laurent
Danny Ayers
Joe English
Simon St.Laurent

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved