[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Default namespaces are *evil*! (RE: Global/Local

• To: <ktl@k...>,<xml-dev@l...>
• Subject: RE: Default namespaces are *evil*! (RE: Global/Local attributes)
• From: "Aaron Skonnard" <aarons@d...>
• Date: Fri, 2 Aug 2002 13:27:17 -0600
• Importance: Normal
• In-reply-to: <3D4AD72B.C5C5B045@k...>

> Kian-Tat Lim wrote:

> The problems are:
> 
> 1) Without surrounding context, it is not possible to determine
> whether an unprefixed name belongs to no namespace or to the
> default namespace.
> 
> 2) There are two kinds of names: names belonging to no namespace
> and names belonging to a namespace.
> 
> Killing default namespaces only takes care of problem #1.
> 
> Killing "no namespace" names in namespaced documents takes care
> of both problems simultaneously.
> 
> Default namespaces are not evil; they are just a syntactic
> shorthand or minimization.  No-namespace names are the true evil.


I don't see the problem with #2; it's up to the application to deal
with. The fundamental problem with default namespaces is that it
complicates expanding QNames, a fact that has polluted layered specs as
illustrated.

-aaron
http://staff.develop.com/aarons

• Follow-Ups:
  • Re: Default namespaces are *evil*! (RE: Global/Local attributes)
    • From: Kian-Tat Lim <ktl@k...>

• References:
  • Re: Default namespaces are *evil*! (RE: Global/Local attributes)
    • From: Kian-Tat Lim <ktl@k...>

• Prev by Date: Re: Default namespaces are *evil*! (RE: Global/Local attributes)
• Next by Date: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Previous by thread: Re: Default namespaces are *evil*! (RE: Global/Local
• Next by thread: Re: Default namespaces are *evil*! (RE: Global/Local attributes)
• Index(es):
  • Date
  • Thread