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

Re: RE: Namespaces Best Practice

• From: PaulT <pault12@p...>
• To: David Carlisle <davidc@n...>, jborden@m...
• Date: Fri, 21 Sep 2001 02:18:25 -0700

----- Original Message ----- 
From: "David Carlisle" <davidc@n...>

> XSLT processors normally need to process entire input documents but XSLT
> is designed so the result can be streamed. 

Really? Is there any W3C document that says it?
Sofar I have not seen a single XSLT engine 
not accumulating the output... What is 'normally', 
by the way?

> This accounts for restrictions
> in XSLT, most notably that you can't add attribute nodes after you've
> added any element.

You can:

<xsl:stylesheet 
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
   version="1.0">

   <xsl:template match="/">
     <A>
      <xsl:attribute name="b">bbb</xsl:attribute>
     </A>
   </xsl:template>

</xsl:stylesheet>

Rgds.Paul.

• Follow-Ups:
  • Re: RE: Namespaces Best Practice
    • From: David Carlisle <davidc@n...>
  • Re: RE: Namespaces Best Practice
    • From: Bill Lindsey <bill@b...>

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

• Prev by Date: Re: RE: Namespaces Best Practice
• 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