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

Re: Well-formed Blueberry

• From: David Carlisle <davidc@n...>
• To: elharo@m...
• Date: Fri, 13 Jul 2001 16:32:14 +0100

> An XSLT processor is a tree-to-tree transformation. The XML declaration
> is not part of the tree. It is produced only as part of the final,
> optional serialization of the document. Assuming the Blueberry
> declaration is part of the XML declaration, it would not be chosen until
> the entire output tree was available for inspection so that the presence
> or absence of Bluebbery characters could be definitively ascertained.

But the XSLT result tree building is explitly designed so that it is
(theoretically) possible to linearise the result tree as you go (unlike
the input tree, which you pretty much have to have in memory). This for
instance is the reason why you can not add attribute nodes to an element
after you have added any content, to do so would require backing up the
serialisation.

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.

• References:
  • RE: Well-formed Blueberry
    • From: Julian Reschke <julian.reschke@g...>
  • RE: Well-formed Blueberry
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: RE: Just a Little Explanaton for Veering (RE: Blueberry/Unicode/ XML)
• Next by Date: Re: Well-formed Blueberry
• Previous by thread: RE: Well-formed Blueberry
• Next by thread: Re: Well-formed Blueberry
• Index(es):
  • Date
  • Thread