Identify the statement that is NOT true about XSLT (Extensible Stylesheet Language Transformations).

Introduction / Context:
XSLT transforms XML (or XML-like trees) into other formats such as HTML, plain text, or different XML vocabularies. Its programming model is distinct from imperative languages because it is template- and rule-driven.

Given Data / Assumptions:

• XSLT operates declaratively with pattern matching.
• It applies templates to nodes, guided by XPath expressions.
• We must spot the statement that mischaracterizes XSLT as procedural.

Concept / Approach:
In XSLT, developers declare templates that match parts of the source tree. The processor decides order of application based on patterns and priorities. There is no explicit step-by-step “procedure” that mutates state in the classic imperative sense, although XSLT 2.0/3.0 add functions and stronger typing.

Step-by-Step Solution:

Verification / Alternative check:
Review XSLT specs: templates, pattern matching, and result trees are central; no required imperative control flow.

Why Other Options Are Wrong (as choices for “not true”):
They correctly describe XSLT’s rule-based, transformation-oriented nature (even if option B’s wording is awkward).

Common Pitfalls:
Trying to write XSLT like a procedural script rather than leveraging template matching and XPath selection.

Final Answer:
XSLT uses a set of procedures that specify how a document is to be programmed.