Default Namespace should be clearly documented ...

John Cowan cowan at
Thu Dec 3 18:02:56 GMT 1998

Bryan Cooper scripsit:

> Thanx for the tip.  But then how do we tell the parser that we want it to
> switch into
> a default namespace at the start and another at the end of the ENTITY?
> If that is another way to set the default, GREAT, but
> I just would like to see that in the spec 'cause it is obtuse enough as it is.
> I suspect however that there is no way to have a PI at the beginning of the
> ENTITY....everything else encapsulated by the ENTITY....and another PI only
> at the end of the ENTITY.    And what is the proper PI to xml to change
> default namespace?

I'm not sure whether you are asking about the actual Namespaces
Proposed Recommendation, or some alternative PI-based namespace
mechanism.  Namespaces haven't been PI-based for many months now.
The current mechanism, while somewhat lacking vis-a-vis DTDs,
provides for scope control very neatly, because namespace defaulting
is always within the scope of an element with an "xmlns" attribute.

The current version is at .

John Cowan		cowan at
	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:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list