Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Thu, 21 Jan 1999 13:58:59 -0500
Paul Prescod wrote:
> If the definition of the namespace (whereever it is) says that the
> namespace's X must contain a Y, then an X *must* contain a Y, just as if
> it were a DOCTYPE declaration. The only difference is that the validation
> is done at some other level, using some other mechanism.
Namespaces needn't have definitions (schemas) in this sense, although
some will. The model of namespaces as defined by the Recommendation
contains solely names, each tagged as Element, GlobalAttribute, or
ElementType<X>SpecificAttribute, where <X> is a name of type Element.
There is nothing about content models, defaults, or anything else.
> These problems go away if you use the namespace convention in ways that
> are not in contradiction with validation (i.e. #FIXED xmlns: attributes).
Using #FIXED attributes is neither necessary nor sufficient.
What is necessary and sufficient is to alpha-convert all namespace
prefixes so that each namespace has a unique prefix, and to modify the
DTD to use those same prefixes.
John Cowan http://www.ccil.org/~cowan email@example.com
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
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)