In this repository, demo and xslt subdirectories are kept separate, and demonstrations are all self-contained, so nothing in demo calls code released in xslt.
As xslt code is developed specifically for adaptation and reuse, it is not nor should it be maintained as a demo. But a demo could use it.
A demo that displayed a catalog using the xslt display logic could be useful not only as a demo, but as an easy way to support extension/debugging of the XSLT.
We could address this with some sort of shell XSLT combined with scripting that would compile XSLT into a (single) SEF in the usual way, for SaxonJS. (Hint: package.json.)
A demo of such a demo is underway in a local branch.
Catalog display XSLT is ready for this; the architecture should be adaptable to SSP, CDEF, POAM, AP, AR etc.
In this repository,
demoandxsltsubdirectories are kept separate, and demonstrations are all self-contained, so nothing indemocalls code released inxslt.As
xsltcode is developed specifically for adaptation and reuse, it is not nor should it be maintained as a demo. But a demo could use it.A demo that displayed a catalog using the
xsltdisplay logic could be useful not only as a demo, but as an easy way to support extension/debugging of the XSLT.We could address this with some sort of shell XSLT combined with scripting that would compile XSLT into a (single) SEF in the usual way, for SaxonJS. (Hint:
package.json.)A demo of such a demo is underway in a local branch.
Catalog display XSLT is ready for this; the architecture should be adaptable to SSP, CDEF, POAM, AP, AR etc.