XSLT programming model — evaluate the statement: “With XSLT, you specify a procedure for materializing document elements.” Indicate whether this characterization is correct or incorrect.

Introduction / Context:
XSLT (Extensible Stylesheet Language Transformations) is a functional, template-driven language for transforming XML trees into other trees (XML, HTML, text). This question checks whether you understand that XSLT is declarative, not procedural: you write template rules that match patterns, not step-by-step procedures.

Given Data / Assumptions:

• XSLT uses templates, pattern matching, and XPath expressions.
• Execution relies on rule selection and template application, not linear instruction sequences.
• While XSLT supports iteration and conditionals, they are expressed functionally (e.g., xsl:for-each, xsl:apply-templates).

Concept / Approach:
In XSLT you declare how to transform nodes by defining templates that match nodes and produce result fragments. The processor determines the order of application based on matches and priorities. Although you can simulate procedural flow, the core model remains declarative. Therefore, calling XSLT “specifying a procedure” is inaccurate; you specify transformation rules, not imperative procedures.

Step-by-Step Solution:

Verification / Alternative check:
Consider a stylesheet with multiple templates and priorities: the engine chooses matching templates dynamically. This behavior is inconsistent with strictly procedural programming where control flow is explicitly sequenced by the programmer.

Why Other Options Are Wrong:

• XSLT 2.0/3.0 add functions and packages but remain declarative.
• Using extension functions does not change the language paradigm.
• XPath is intrinsic to XSLT and does not make it procedural.

Common Pitfalls:
Assuming that presence of loops or conditionals makes a language procedural; overlooking template matching and rule-based execution as the defining characteristic.

Final Answer:
Incorrect