2 more (dubious ones):
- when validating using XML Schema the source tree gets annotated with
type information.
- namespace prefixes get expanded (namespaces aren't mentioned so far...
need to squeeze them in somewhere)
Amended by comments so far:
Phase 0, XML parse of stylesheet and input document:
Expand character references and parsed entities;
Determine source doc encoding.
Normalize newlines.
Normalize whitespace.
Replace CDATA sections with characters.
Validate (if using a validating parser with validation switched on)
Populate defaulted values if using DTD/XML Schema.
Identify any nodes with ID values.
URI resolution (E.g. Catalog management)
Build the internal model of the stylesheet
(including URI resolution if needed) by parsing the stylesheet
including any included or imported stylesheets.
Build the internal model of the source document (if present)
Action document properties such as xml:space, xml:base etc
Phase 1, XSLT transformation.
Apply the stylesheet to the input document (if present) (Colin)
URI and entity resolution for any doc() and document() calls
from the stylesheet. (Colin)
Parse additional entities such as the result of
document() calls,
Build the output tree.
Phase 2, Output | Serialisation
From the output tree, produce the output document
Apply applicable document properties such as xml:space
Apply appropriate character encodings
Apply any character maps (XSLT 2.0)
This could be
DOM Document or
SAX stream or
Serialised to a Disk file (Jarno)
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--