Cart
[Home] [By Thread] [By Date] [Recent Entries]
On 28/02/2018 19:33, Dimitre Novatchev wrote: What you’d regard as beautiful XPath, Dimitre, might be far too concise for other people to comprehend ;)Extending a little: What is a "beautiful XPath expression"? Occurrence of xsl:next-match, possibly also with one or more tunneled parameters, often serves as an indicator of an elegant XSLT transformation (and it tells me that the author knows how to virtuously employ XSLT core concepts such as template matching, priority, import precedence, tunneling etc.).What is a beautiful XSLT transformation? Other “advanced XSLT” indicators merely document good practice. Examples include the “as” attribute for type checking, xsl:for-each-group instead of collecting following nodes and then then desperately trying to suppress duplicating them, or using xsl:sequence instead of xsl:value-of when they want to return an atomic value rather than a text node. But this isn’t beautiful in itself, this is just good practice. Gerrit
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
