2020-10-01 V2.0
  Based on draft ST96 Annex I V4.0 from 2021-09-24.

-- List of Changes --
- Updated to Ant 1.9.16 from Ant 1.9.4
- Updated to Saxon HE 10.5 from Saxon 9.3.0.5

- Added option to indicate previous Schema directory. Results of comparison are shown in the Component Name Report and Conformance Checking report (by prioritizing rule violations in new/modified components)
- Added capability to identify new/modified components if previous Schema directory is provided. 
- Added spell checking of component names, component documentation, and some enumeration values (results provided in Integrity check)
- General improvements to UI of reports

- Fixed permissions for Linux/Mac users running the bash scripts.
- Bash script does not rely on settings.xml
- Added method to automatically update st96rules.xml and AcronymsAndAbbreviations.xml based on the Annex I Word document
- Logging of the Ant build execution is possible by setting the property debug. 

Conformance check improvements:
- general improvements to regular expressions
- st3Codes is automatically maintained based on the corresponding schema file (used for SD-63)
- configure whether approved exceptions are checked in the report or in the Schematron run using the attribute in the file ApprovedExceptions.xml
- improvements to GD-13, GD-14, GD-23, GD-25, GD-26, GD-31, GD-32, SD-01, SD-02, SD-03, SD-06, SD-30, SD-31, SD-33, SD-35, SD-36, SD-38, SD-42, SD-43, SD-45, SD-49, SD-58, SD-60, SD-63, SD-64
- Added partial checking for GD-25, SD-38, SD-53, SD-60
- Added check for SD-28
- Added checks for manual review of SD-46, SD-48
- Added diagnostics to better merge results by design rule

Integrity check improvements:
- Added Spell checking (indicated above)
- Added check for duplicate enumeration values
- Added check for duplicate components when xsd:extension is used
- Added check for non-local path provided in xsd:include
- Added check for components missing explicit datatype

-- Limitations --
Flattened Schemas were not tested according to the new convention. Validator may provide irregular/unexpected results if flattened schemas are used, rather than design schemas. 