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

Re: xslt phases for FAQ, was Reading the XML declarat

Subject: Re: xslt phases for FAQ, was Reading the XML declaration using XSL
From: Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx>
Date: 20 Jan 2005 11:10:49 +0000
Re:   xslt phases for FAQ
>>>>> "Dave" == Pawson, David <David.Pawson@xxxxxxxxxxx> writes:

    Dave> Phase 0, XML parse: Resolve entities; Determine source doc
    Dave> encoding Validate (if using a validating parser with
    Dave> validation switched on)
    Dave> Catalog resolution (if appropriate)

This is either just a special case of entity resolution (in which case
it needs no further mention in this phase), or else it is a special
case of URI resolution (in which case it takes place both when
building the stylesheet, and when executing the doc() and document()
functions).

    Dave> Build the internal model of the source document Build the
    Dave> internal model of the stylesheet

Other way round - the stylesheet must be compiled first, in order to
determine the whitespace-stripping rules to be applied when stripping
the source document.
I suppose that an implementation might build the source document in
two stages, but this seems illogical.
Also, in XSLT 2.0 - a source document need not be present, so building
it is an optional step.


-- 
Colin Paul Adams
Preston Lancashire

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.