(Imported from Google Code) Since v2.0.0, the DDMSence Util methods for validation of NCNames and NMTOKEN values have delegated the actual work to Saxon's Name10Checker class. Although this cleans up the code, it also requires the Saxon JAR (6MB) file to be in the classpath even if another XSLT engine is being used for things like Schematron validation.
Investigate the pros/cons of custom Util methods to eliminate this large dependency.
Activity
Show:
Brian Uri
August 25, 2012 at 5:08 PM
Complete in Rev 750.
Brian Uri
June 3, 2012 at 12:45 PM
Reopening. Although the fix described above will still not be made, the documentation about the classpath can and should be updated to note that Saxon is a dependency for reasons other than Schematron parsing, and that custom XSLT engines can still be used next to Saxon.
Brian Uri
April 27, 2012 at 6:17 PM
It is not trivial to separate the NCName methods from the Saxon JAR, and the solution provided is far more robust than the original custom solution was. Although requiring the 6 MB JAR is less than convenient, it results in a stronger technical solution for NCName validation.
(Imported from Google Code)
Since v2.0.0, the DDMSence Util methods for validation of NCNames and NMTOKEN values have delegated the actual work to Saxon's Name10Checker class. Although this cleans up the code, it also requires the Saxon JAR (6MB) file to be in the classpath even if another XSLT engine is being used for things like Schematron validation.
Investigate the pros/cons of custom Util methods to eliminate this large dependency.