• To: xml-dev@l...
• Subject: When to design an attribute in a namespace?
• From: <kynn@p...>
• Date: Wed, 21 Apr 2004 08:51:58 -0400 (EDT)

In http://www.rpbourret.com/xml/NamespacesFAQ.htm#q5_3, it says:

  ...the purpose of XML namespaces is to uniquely identify element
  and attribute names.  Unprefixed attribute names can be uniquely
  identified based on the element type to which they belong, so
  there is no need identify them further by including them in an
  XML namespace.  In fact, the only reason for allowing attribute
  names to be prefixed is so that attributes defined in one XML
  language can be used in another XML language.

This quote suggests that, when designing a schema/DTD one can safely
let most (if not all) attributes have no namespace (i.e. be
"unprefixed"); the designer only rarely should need to specify an
attribute as belonging to a namespace (i.e. requiring a prefix).

But I am interested in learning to recognize those rare situations
in which, as a designer, one *should* put a particular attribute
in a namespace.  This is still very unclear to me.  What are the
requirements that an attribute must fulfill to be a good candidate
for being placed in a namespace by the schema/DTD designer?

Thanks!

kj

• Follow-Ups:
  • Re: When to design an attribute in a namespace?
    • From: Jonathan Borden <jonathan@o...>
  • Re: When to design an attribute in a namespace?
    • From: "Chiusano Joseph" <chiusano_joseph@b...>
  • RE: When to design an attribute in a namespace?
    • From: "Nicolas Toper" <ntoper@b...>

• Prev by Date: Re: XUL Compact Syntax Study Now Online - Is XML too hardfor Aunt Trudie?
• Next by Date: RE: When to design an attribute in a namespace?
• Previous by thread: XPath expression
• Next by thread: RE: When to design an attribute in a namespace?
• Index(es):
  • Date
  • Thread