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

Re: RE: Namespaces Best Practice

• From: David Carlisle <davidc@n...>
• To: jborden@m...
• Date: Fri, 21 Sep 2001 09:35:25 +0100

> On the other hand software such as XSLT processors -usually- read process
> then write, and in such cases namespace normalization is straighforward.

XSLT processors normally need to process entire input documents but XSLT
is designed so the result can be streamed. This accounts for restrictions
in XSLT, most notably that you can't add attribute nodes after you've
added any element.

It's not possible, using XSLT, to arrange that namespace declarations
are at any place at all as that's entirely up to the processor, but they
are most likely to appear as far down the tree as possible.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

• Follow-Ups:
  • Re: RE: Namespaces Best Practice
    • From: PaulT <pault12@p...>

• References:
  • RE: RE: Namespaces Best Practice
    • From: "Fuchs, Matthew" <matthew.fuchs@c...>
  • Re: RE: Namespaces Best Practice
    • From: Jonathan Borden <jborden@m...>

• Prev by Date: Re: Urgently need a reality check on the job market forXMLdevelopment
• Next by Date: Re: RE: Namespaces Best Practice
• Previous by thread: Re: RE: Namespaces Best Practice
• Next by thread: Re: RE: Namespaces Best Practice
• Index(es):
  • Date
  • Thread