Lists Home |
Date Index |
- From: Dan Brickley <Daniel.Brickley@bristol.ac.uk>
- To: XML Developers' List <email@example.com>
- Date: Mon, 8 Mar 1999 23:09:17 +0000 (GMT)
On Mon, 8 Mar 1999, David Megginson wrote:
> Tom Harding writes:
> > David Megginson wrote:
> > > As I wrote before, it doesn't much matter whether we use Java property
> > > names incorporating domain names (like
> > > 'org.xml.sax.features.validation') or URIs (like
> > > 'http://xml.org/sax/features/validation'), as long as we have the
> > > ability for people to create new names without fear of collision.
> > I would also urge against using an http: URI since it is not meant
> > that a resource actually be retrieved using the http protocol.
> I've been thinking about this issue, and I'm fairly convinced that the
> URI is the right choice.
> Think of the URI a statement of ownership. Assume that my ISP is
> host.net, and that I've been allocated 5MB of web space at
Just to head off one possible objection... that of the persistence (or
lack of) w.r.t. http URLs. The PURL folks (Persistent URLs) make a
credible case when they argue that URLs can be managed just a
responsibly as URNs, and that persistence of http naming is a social
issue not a technical one. PURL servers are available to help here -- eg
XML-DEV's own XSchema (now DDML) pages have been available from several
different http servers, but have always had the same URI:
The PURL server at that address sends an HTTP redirect messge if you try
to derefence it. So we could for eg use PURLs to name software features,
with reassurance that PURL.ORG have committed to do their best to manage
http://purl.org/* names responsibly.
> Namespaces seems to have got it right.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)