Lists Home |
Date Index |
- From: "Borden, Jonathan" <firstname.lastname@example.org>
- To: "XML Developers' List" <email@example.com>
- Date: Fri, 15 Jan 1999 09:43:53 -0500
This is the *current* state of affairs. There are people who also believe
that in the future the namespace concept is to be extended to incorporate
Schema definition. That is, when a namespace URN points to a Schema
definition, the Schema may, can or will be enforced in the same way that a
DTD is enforced by a validating parser and a <!DOCTYPE definition.
So to summarize, today a namespace is simply a naming scheme but in the
future namespaces may become part of a typing scheme.
> Roger L. Costello writes:
> > I thought I knew what a namespace was ... but now I think perhaps I
> > don't.
> It's simpler than you think.
> > That is, is the file itself (BookCatalogue.dtd) a namespace?
> No -- it's irrelevant as far as the current namespaces REC is
> > In all the examples that I see in the namespace spec they don't
> > refer to a specific file. Instead, they refer to "some place",
> > such as:
> > http://www.w3.org/TR/HTML/
> Not a place, just a unique URI. The URI doesn't actually have to work
> (a URI that throws up a 404 is just fine).
> > So, perhaps the "directory" that BookCatalogue.dtd resides in is the
> > namespace? i.e.,
> > file://localhost/xml-course/xml-part1/
> > I thought I knew the way, now I don't. Help me find my way again.
> A namespace is very similar to a package name in Java -- it's just a
> way of disambiguating names. Consider
> package com.megginson.xml;
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/
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)