Cart
[Home] [By Thread] [By Date] [Recent Entries]
For me, without question, the import tree and import precedence is a
tremendous advantage of XSLT.
I have had numerous clients who, themselves, have numerous clients. Writing core XSL-FO stylesheets and then tweaking the core with onion-skin layers overriding the core (or each other) to create different customized layouts is very powerful. The two largest projects where I leveraged this are for the US intelligence community back in 2005: http://www.pdfpower.com/XML2005Proceedings/ship/18/Holman-18.HTML ... and my active work these days for https://RealtaOnline.com servicing multiple national and regional standards bodies in the publishing of NISO-STS and JATS from a single core with onion-skins for multiple layers: https://www.realtaonline.com/customers/ https://www.ncbi.nlm.nih.gov/books/NBK591971/ ... where such is important because of the layered nature of multiple expected results of a single stylesheet execution with layered input data: https://www.ncbi.nlm.nih.gov/books/NBK610635/ The inherent structure of XML is a nested hierarchy. The import facility in XSLT implements a nested hierarchy of stylesheet behaviours. These two example projects supported dozens of distinct visual results from a core of stylesheets and multiple onion-skins. I couldn't do what I do without import precedence, and I haven't worked with any other language that has such a concept. In 2002, long before the intelligence project, I created the XSLStyle documentation methodology that exposes the (sometimes very large) XSLT import tree to help in maintenance of a set of stylesheets for a software vendor with multiple clients: https://cranesoftwrights.github.io/resources/#xslstyle https://cranesoftwrights.github.io/resources/xslstyle/index.htm http://fgeorges.blogspot.com/2009/02/xslstyle-and-oxygen.html A disadvantage of this facility? Not many XSLT developers leverage or even know of xsl:import and so have not exercised the mindset needed when creating and maintaining very (very!) large stylesheet libraries. It takes the declarative nature of XSLT to the next level in nurturing a declarative nature of XSLT stylesheet fragments interacting with each other. I hope this is enlightening. I wish more developers knew about this (and that more developers were able to support very large stylesheet libraries that exploit this facility). . . . . . . . Ken At 15/02/2025 12:28 +0000, Roger L Costello costello@xxxxxxxxx wrote: Hi Folks,
|
