• From: Elliotte Rusty Harold <elharo@i...>
• To: Paul Spencer <xml-dev-list@b...>
• Date: Sat, 2 Jan 2010 17:48:49 -0500

On Sat, Jan 2, 2010 at 5:27 PM, Paul Spencer
<xml-dev-list@b...> wrote:
> I deal with many document types that have an envelope within which is both
> addressing information (and perhaps other things such as a digital
> signature) and a single payload element containing data. In other words, the
> payload data would be a well-formed XML document on its own with its own
> root element, but this is embedded in something else. In this case, it is
> common to declare a default namespace in the embedded element that is
> different from the namespace(s) of the envelope. SOAP-based web services
> also come to mind.

A default namespace that changes is not nearly as big a problem as a
prefix that changes. I am 95% certain that the pain caused by allowing
prefix declarations only on the root element would be far less than
the pain caused by allowing redeclarations of prefixes.

-- 
Elliotte Rusty Harold
elharo@i...

• Follow-Ups:
  • Re: Lesson Learned: Use namespaces for both markup anddata
    • From: Richard Salz <rsalz@u...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Michael Kay" <mike@s...>

• References:
  • Re: Lesson Learned: Use namespaces for both markup anddata
    • From: Dave Pawson <davep@d...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Michael Sokolov" <sokolov@i...>
  • RE: Lesson Learned: Use namespaces for both markup anddata
    • From: "Paul Spencer" <xml-dev-list@b...>