Schematron Validator

2.5.0

Release date: 2019-03-18

Remarks

Datasource management has changed, refers to the installation manual to correctly update your instance of the tool.

Improvement

2.4.2

Release date: 2019-01-28

Bug

  • [SCHVAL-179] The checkbox “Process Unknown check type as an error?” does not work no more

2.4.1

Release date: 2018-10-18

Bug

  • [SCHVAL-173] The namespace xmlns:cda=”urn:hl7-org:v3” is defined twice after schematron compilation

2.4.0

Release date: 2018-10-05

Remarks This version is compatible with 5.8.0 EVSClient version and more.

Bug

  • [SCHVAL-135] [LUX] Problem with the compilation with schematrons typed ART-DECOR
  • [SCHVAL-136] Bug on the generation of xsl based on art-decor styled schematrons
  • [SCHVAL-156] Un-understandable error if XSD version is wrongly defined
  • [SCHVAL-157] If no XSD is defined for validation, it fails without explanation
  • [SCHVAL-159] Schematron Validator does not implement the CAS client properly
  • [SCHVAL-161] Review GazelleObjectValidatorWS structure
  • [SCHVAL-165] Mixing up between label, keyword, name of entities…
  • [SCHVAL-171] When adding or editing a Schematron, the path is not trimed
  • [SCHVAL-172] The validation stopped when there is a namespace URI that start by a number

Story

Improvement

  • [SCHVAL-166] Improve code and business location through the code for better unit-test coverage
  • [SCHVAL-168] Restructure validation result

2.3.1

Release date: 2018-03-23

Bug

  • [SCHVAL-160] Not all paths to external files are relative

2.3.0

_Release date: 2018-02-27 _

Remarks

SchematronValidator integrates the new client module for gazelle-transformation-ws-client, this 2.3.0 version is compatible with Gazelle Transformation 2.0.0 and later. The PostgreSQL driver has been externalized and must then be deployed as a JBoss module.

Bug

  • [SCHVAL-153] Update postgresql driver to version 42.2.1.jre7

Story

  • [SCHVAL-151] Integration with new Gazelle Transformation Client

2.2.4

Release date: 2018-01-22

Bug

  • [SCHVAL-133] When we dupplicate a schematron, we do not dupplicate the daffodil description and if need dafodil transformation
  • [SCHVAL-149] When the method “getAllSchematrons” is called some values in the table schematron are set to null
  • [SCHVAL-150] For some reason, all the attiribute daffodil_transformation_needed in the table sch_validator_schematron were lost and initialized to NULL

Improvement

2.2.2

Release date: 2017-11-03

Bug

  • [SCHVAL-138] When an XSD processing failed, user or admin have no clue

2.2.0

Release date: 2017-08-23

Remarks

From version 2.2.0, Schematron Validator can be used to validate flat files by calling Daffodil Transformation tool before running the schematron validator on the resulting XML file.

Bug

  • [SCHVAL-113] When an entry only as an XSD (no schematron), the compile button shall not be available
  • [SCHVAL-128] When creating a schematron entry, the path to the xsd and the schematron file is required
  • [SCHVAL-129] [EFS] Unable to retrieve schematron in EVSClient

Story

  • [SCHVAL-126] Validation report gives wrong information

Improvement

  • [SCHVAL-131] In the edit Schematron page, shows only the daffodil oid field when daffodil transformation is checked

2.1.1

Release date: 2017-01-17

Bug

  • [SCHVAL-43] When updating the XSD schema on the server, it is not taken into account by the tool
  • [SCHVAL-123] When updating to gazelle-tools:3.0.25 or higher, fix dependencies to asm

Story

  • [SCHVAL-109] Support to the Schematrons generated by ART-DECOR

2.1.0

Release date: 2017-01-05

Remarks

As the web service of Schematron Validator has been modified in this release, these tools have also been updated :

  • gazelle-tm-tools with a new release generated : 4.0.18
  • gazelle-ws-clients with a new release generated : 2.14

Thus, before deploying this Schematron Validator tool, It’s mandatory to use the next release of EVSClient, which use the tools shown above, to avoid incompatibility issues : The version 5.0.15 or ealier.

Bug

  • [SCHVAL-23] Need additional field to characterize a schematron
  • [SCHVAL-108] When Schematron contains no schematron (only XSD), then soap request from EVSClient to get schematron fails
  • [SCHVAL-118] transformUnknowns is reseted to null after calling Schematron webservice

Story

  • [SCHVAL-69] Update of the user guide on SchematronValidator
  • [SCHVAL-106] Missing line numbers and column in XSD validation report for schematron validation
  • [SCHVAL-107] Add support to XSD 1.1
  • [SCHVAL-114] XSD Validation of SVS document does not report line numbers and column numbers of error as it is done for CDA, XDW, XDS…

Improvement

  • [SCHVAL-48] we need a button on the list of manageSchematrons that allow to compile all schematrons
  • [SCHVAL-115] Add some field in the report of the Schematron Validation
  • [SCHVAL-117] Add button to select between XSD 1.0 and XSD 1.1 for schematron validation

2.0.4

Release date: 2016-11-24

Bug

Improvement

  • [SCHVAL-111] CAS login redirects to the same page instead of the home page
  • [SCHVAL-112] Automatically recompile a schematron if source is newest

2.0.3

Release date: 2016-07-20

Story

  • [SCHVAL-105] Bug in the definition of Schematrons

2.0.2

Release date: 2016-06-06

Bug

  • [SCHVAL-100] Can’t edit an existing schematron

2.0.0

Release date: 2016-06-01

Bug

  • [SCHVAL-87] In Manage Schematrons, edition feilds are not the same like creation fields
  • [SCHVAL-90] The footer is not well populated
  • [SCHVAL-91] We can’t get the version with the rest WS
  • [SCHVAL-92] Title trouble
  • [SCHVAL-94] /Schematron Validator/System testing/Manage Object Types/SCHVAL-22:Access to the object type management list page - Ex
  • [SCHVAL-95] Create a schematron with an already existing keyword leads to an unexpected error.

Story

  • [SCHVAL-85] Deploy Schematron Validator on kujira for testday (+ configuration)
  • [SCHVAL-97] Release SchematronValidator 2.0.0
  • [SCHVAL-98] Installation of SchematronValidator 2.0.0 on ovh3
  • [SCHVAL-99] Update documentation on drupal of SchematronValidator (2.0.0 release)
  • [SCHVAL-102] Test report of SchematronValidator 2.0.0 - migration to Jboss 7

1.17.4

Release date: 2015-11-27

Bug

  • [SCHVAL-61] bug in the validation of unknown check

1.17.3

Release date: 2015-11-26

Bug

  • [SCHVAL-61] bug in the validation of unknown check

1.17.2

Release date: 2015-11-26

Bug

  • [SCHVAL-60] Add the possibility to convert unknown checks to errors

1.17.1

Release date: 2015-10-12

Remarks

  • [SCHVAL-59] Add the referencing to the CAS from the db

1.17.0

Release date: 2014-06-06

Bug

  • [SCHVAL-20] WebService aboutThisApplication returns un-initialized values
  • [SCHVAL-45] delete of schematron does not work
  • [SCHVAL-50] Need to fix the pointer to the CAS for the GE and PROD profiles

1.14

Release date: 2013-09-23

Story

  • [SCHVAL-44] Add the possibility to login by ip address

1.12

Release date: 2013-06-27

Bug

  • [SCHVAL-40] add the possibility to validate according to a schema, no schematron provided

1.11

Release date: 2013-03-11

Bug

  • [SCHVAL-35] Improvement of the process of validation

Improvement

  • [SCHVAL-27] Improvement of the schematronValidator project
  • [SCHVAL-36] Add the possibility to force the view of successful reports of validation, when the schematron is configured only to report errors

1.10

Release date: 2013-03-08

Bug

  • [SCHVAL-34] Configuration fo the schematrons of pharm to gazelle style of output

1.8

Release date: 2013-02-21

Bug

  • [SCHVAL-32] When a document is not valid, the schematron validation is not performed, but the message displayed is “PASSED”

1.7

Release date: 2013-02-21

Bug

  • [SCHVAL-29] When a document is not well formed, some errors occures

1.5

Release date: 2013-02-12

Improvement

  • [SCHVAL-18] We need a notion of AffinityDomain
  • [SCHVAL-25] Improve the schema validation
  • [SCHVAL-26] Problem on the creation of versions

1.4

Release date: 2011-09-12

Bug

  • [SCHVAL-21] In some cases that needs to be identified the result file returned by the Schematron Validator is inconsistent.
  • [SCHVAL-22] [MIF validation] conflict with other validations in the CDA validation

Story

  • [SCHVAL-17] Maven module: create a ws client for validation which will be used in other projects to validate files

1.2

Release date: 2011-07-04

Improvement

1.1-GA

Release date: 2011-01-06

Story

1.0-SR9

Release date: 2010-10-22

Bug

  • [SCHVAL-12] Validation using XDS-SD schematrons always aborts

1.0-SR7

Release date: 2010-09-15

Story

  • [SCHVAL-11] Add a button which enables the admin to update schematron versions according the version mentionned in the file

1.0-SR6

Release date: 2010-09-21

Bug

  • [SCHVAL-8] File received for validation will be Base64 encoded, decode them before validation

1.0-SR5

Release date: 2010-09-09

Story

  • [SCHVAL-2] Add schematron for XCPD validation
  • [SCHVAL-7] Aborted validation : need to inform the administrator

1.0-SR1

Release date: 2010-07-30

Bug

  • [SCHVAL-6] validation aborts when XML document is not well-formed

Improvement

  • [SCHVAL-1] We must check that the document to validate is well-formed and valid

1.0-GA

Release date: 2010-07-13

Bug

  • [SCHVAL-5] Uncomplete result details when validation aborts

Story

  • [SCHVAL-14] EVS: We need a stand alone project to validate file by schematrons using web services