Which is exceedingly reasonble to think, since XSLT actually mandates XPath expressions for all select attributes. However The major conceptual difference I ca

Which is exceedingly reasonble to think, since XSLT actually mandates XPath expressions for all select attributes. However The major conceptual difference I can see is the ability for (apparent) in-place editing/updating, the lack of which was/is a major pain point in XSLT. As XSLT is a functional language for traversing and manipulating heterogenous trees, one can expect quite a lot similarities beneath the surface syntax for most solutions targeting the same problem. At least in part because the limitations of the users (us) and the problem to be solved tends to constrain the solution space for generic (library like) solutions rather strongly.