MorganaXProc-III uses XMLResolver (developed by Norm Tovey-Walsh) as catalog system to resolve resources used in your pipeline. Use -catalogs=uri-or-path to set an initial XML catalogs as a semicolon-separated list of URIs or paths. If a path or a URI is relative it is resolved against the current working directory.

MorganaXProc-III implements a flexible way letting you choose which XSLT processor is used in p:xslt. For each supported XSLT processor MorganaXProc-III provides a connector which needs to be registered to be used. Only one connector can be registered for a specific pipeline run. To register a connector use -xslt-connector=java-classname-or-shortcut. Currently the following XSLT processors are supported:

Currently Saxon 10 is used as default setting, so if you do not set an XSLTConnector, this version will be used. Please mind that you have to put the requested XSLT processor on the Java classpath too. The easiest way is to just drop the JAR-file into folder “MorganaXProc-IIIse_lib” or “MorganaXProc-IIIee_lib” respectively. As the classes in the different version of an XSLT processor typically overlap, it is in general a risky strategy to have different versions of the same processor on the classpath. MorganaXProc-III will use the first Saxon version found on the classpath.

Another problem in setting the configuration for XSLTConnector is that MorganaXProc-III will always use the same instance of a Saxon processor if it is used for p:xslt and p:xquery. Therefor it is not possible to use Saxon 9.9 for XSLT processing and Saxon 10 for XQuery processing or the other way around.

With -xquery-connector=java-classname-or-shortcut you can select the XQuery processor to be used in p:xquery in the same ways, an XSLTConnector is used for p:xslt. Currently the following connectors are supported:

Currently version Saxon 10 is used as default. Please see the hints on Saxon as XSLTConnector for further configuration details.

Some XSLT- and XQuery processors accept configuration files to control their settings. With -xslt-config=uri-or-path and -xquery-config=uri-or-path you can provide such files. MorganaXProc-III does not do anything with these files but just pass them through to the XSLT- or XQuery processors when they are instantiated. The files nature and the semantics of its content is therefor completely determined by the receiving product. Please see its documentation.

As stated above, MorganaXProc-III will use the only one processor instance if you choose to do p:xslt and p:xquery with Saxon. If you do so, please make sure to give the same configuration file for -xslt-config and -xquery-config. As only one Saxon instance is created, only one of them will be used, but as it is not predictable, whether this will be done by a p:xslt or a p:xquery.

Using -schematron-connector=java-classname-or-shortcut you can select the Schematron processor used in p:validate-with-schematron. Currently the following Schematron processors are supported:

Currently the SchXSLT connector is default. Please note that MorganaXProc-III only provides connectors to the two implementations, but not the implementation itself. If you want to use p:validate-with-schematron in your pipeline, you have to download an implementation yourself and make their paths known to MorganaXProc-III. For details please see instructions.

MorganaXProc-III comes with out of the box support for XML Schema 1.0 validation using the Xerces implementation supplied with Java.However this validator does not know anything about XML Schema 1.1, so if attribute version on p:validate-with-xml-schema is set to 1.1 you will get an error message, saying the connector is not capable of this type of validation.

MorganaXProc-III offers support for validation with XML Schema 1.1 using either Xerces (xerces-2_12_1-xml-schema-1.1) or Saxon-EE. If you have already installed Saxon-EE for XSLT transformation or p:xquery, MorganaXProc-III will automatically select it as soon as validation with XML Schema 1.1 is invoked. If you want to use Xerces, download the package from their website and make it available on MorganaXProc-III's classpath. The JAR-files needed are xercesImpl.jar, org.eclipse.wst.xml.xpath2.processor_1.2.0.jar, and cupv10k-runtime.jar.

Caveat:

• If you use Xerces and Saxon-EE with MorganaXProc-III, the first implementation to appear on the classpath will be used. To explicitly control which validation processor is used, you can supply a command line switch or a configuration file element “schemafactory-impl”. The supplied value must be the fully qualified factory class name of a class which provides implementation of javax.xml.validation.SchemaFactory. For Xerces this is org.apache.xerces.jaxp.validation.XMLSchemaFactory (for Schema 1.0) or org.apache.xerces.jaxp.validation.XMLSchema11Factory (for Schema 1.1), for SaxonEE the class is named com.saxonica.ee.jaxp.SchemaFactoryImpl. Alternately you can supply “Xerces” or “Saxon” as short cuts. Of course you can supply the fully qualified class name of any other class implementing the named interface. Please make sure that the relevent Jar files can be found on the classpath.

• Due to the internal mechanism of Saxon-EE, the validator will try to resolve additional schemas even if you set p:validate-with-xml-schema's options use-location-hints and/or try-namespaces to false.

SaxonEE has some features to control aspects of Schema validation. For instance you can use http://saxon.sf.net/feature/strip-whitespace to control whitespace stripping of the document to be validated. MorganaXProc-III supports these features via p:validate-with-xml-schema's option parameter. The key has to be in Saxon's feature namespace and the local name is the feature's name, e.g. Q{http://saxon.sf.net/feature}strip-whitespace. Those key-value-pairs are ignored if Schema validation is performed by another validator.

Starting with release 1.3 MorganaXProc-III supports Invisible XML processing with XProc's p:ixml. The step is implemented as specified using either the NineML tools developed by Norm Tovey-Walsh or Markup Blitz developed by Gunther Rademacher. There is no default selection so you have to explicitly set your preferred processor for iXML.

• To use NineML as your IXML processor use -ixml-connector=com.xml_project.morganaxproc3.ninemlConnector.NineMLConnector on commandline or the respective <ixml-connector> in your configuration file. Additionally you need CoffeeGrinder and CoffeeFilter on classpath. The connector for NineML supports Java 8 and later.

• If you use Java 11 or later, you can use Markup Blitz by setting -ixml-connector=com.xml_project.morganaxproc3.markupblitzConnector.MarkupBlitzConnector. Additionally make sure that markup-blitz-xxx.jar is on your classpath.

Using the common attribute [p:]message pipeline author can define messages to be printed on some output channel. The same is true for xsl:message within XSLT stylesheet. Using -messages on CLI (or a message element in configuration document) users can choose whether and where these message are printed. If the value of messages is off, no messages will be printed. The values std:out or std:err tell MorganaXProc-III to print the messages to the standard output stream or the standard error stream. Any other value will be interpreted as a filepath or a URI of a ressource to where the messages should be written. If the path/URI is relative it will be resolved against the current working directory (for the CLI option) or the base URI of the configuration document. Any existing resource with the given name is overwritten without warning.