Lists Home |
Date Index |
At this point, I feel I need to intrude into the thread and ask [again, I'm
afraid] for the benefits of using URIs for namespace names?
The most oft-cited reason for using URIs (especially URLs (and especially
HTTP URLs)) is that you can guarantee uniqueness. Since nobody else uses
www.sernaferna.com, I can create a URI (again, people usually use URLs)
including that domain name, and be fairly sure nobody else is using it.
But is this benefit really worth all of the bother of trying to use the
little-understood URIs for namespace names? (And don't kid yourselves; very
few claim to understand the zen of URI, and I'd be willing to bet cold hard
cash that even those few disagree with each other.) I can really, truly,
understand using URNs for namespace names, they're a good fit, but URLs...
The costs (mass confusion, thousands upon thousands of emails to XML-DEV,
thousands of person-hours burned on discussing the issue ad infinitum) just
seem to vastly outweigh the benefits (easier uniqueness) of using certain
types of URI (HTTP URLs being the most common, and most ill-fitted, example,
So what are the other benefits of using URI for namespace names, that I'm
Do people have these kinds of problems with Java package names?
Author: A book he sometimes regrets getting involved with...
----- Forwarded message from "Clark C . Evans" <firstname.lastname@example.org>
Date: Wed, 24 Jul 2002 09:28:58 -0400
From: "Clark C . Evans" <email@example.com>
Subject: DNS based URIs that don't imply access method
Speaking of URIs, I was wondering if there is an official URI/URN
scheme which uses DNS for uniqueness but does not imply a particular
method of access (such as http, mailto, telnet, etc.)
For example, something like...
Clark C. Evans Axista, Inc.
XCOLLA Collaborative Project Management Software
-------- End of forwarded message --------