David Maus

Can this be considered a bug? The attributes in question are: - documents - icon - fpi - see - xml:lang - xml:space - _foreign attributes_

The root issue seems to be some problem with Xalan: ```xml javax.xml.transform.TransformerConfigurationException: Translet-Klasse "compile_for_svrl" konnte nicht geladen werden. at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:433) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:451) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:486) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:762) at org.basex.query.func.xslt.XsltTransform.transformer(XsltTransform.java:127) at org.basex.query.func.xslt.XsltTransform.transform(XsltTransform.java:103)...

Change the API such that schxslt-api:report can expect a variable schxslt:report with the internal report.

This does not work as expected for XSLT 1.0

Move to SchXslt 2.0

Postponed. For a casual user of eXist and BaseX it is way to fiddly.

- [ ] svrl:metadata - [ ] svrl:suppressed-rule - [x] https://github.com/Schematron/schematron-enhancement-proposals/issues/1 - [x] https://github.com/Schematron/schematron-enhancement-proposals/issues/2 - [x] https://github.com/Schematron/schematron-enhancement-proposals/issues/3 - [x] https://github.com/Schematron/schematron-enhancement-proposals/issues/4

Not directly, yet. The way it would be done is described in the paper you linked to (thanks! didn't know this one): There will be one or more stylesheets that...

Things to consider - [ ] Obtain namespace bindings from the host language - [ ] Perform includes for the host file, too - [ ] Provide an XProc step

Maybe put this in a separate repository? Pro: Versioning independent of SchXslt