Namespace question: Do attributes inherit the element's namespace?

james anderson James.Anderson at
Fri Jan 7 10:15:20 GMT 2000

ie., Mr Waldin's conclusion is correct, and the REC actually requires
application recognize that a conforming parser may well distinguish between
the two encodings and the application must act as if the standard is option #2.

Ray Waldin wrote:
> Tim Bray wrote:
> > So... let's try again.  Consider these two
> >
> >    <html:a href="foo">
> >    <html:a html:href="foo">
> >
> > The namespace spec could have said one of three things:
> >
> > 1. These must always be treated as identical
> > 2. These must always be treated as different
> > 3. Applications can make up their minds
> >
> > The then-Working Group eventually went for #3. ...
> How can #3 be an option at the application level if #2 isn't enforced at
> the parser level?  Will parsers allow switching between these universes
> at parse time?

Tim Bray responded:
> At 04:48 PM 1/6/00 -0800, Ray Waldin wrote:
> >  <html:a href="foo" html:href="bar"/>
> >
> >This element must be considered well-formed from the standpoint of XML
> >1.0 + Namespaces in order to allow #3 at the application level, no?  And
> >furthermore, applications wanting to live in #1 have to do extra work
> >for each and every attribute to ensure that documents in #3 are in the
> >subset that is universe #1.  Yikes!
> That's correct.  Apps can't rely on a generic XML or namespace processor
> to raise an error on this.  If they want to do so, they have to do the
> work themselves.  But the alternative - never allowing this to happen -
> seemed even more unattractive. -Tim

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe 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