Point properly to release version 1.3.3 (=not yet released!).

README.md

@@ -68,7 +68,7 @@ We use [JSON Schema 2020-12](https://json-schema.org/specification.html) to defi
 
 For files which have a different schema - such as `vaccine-encoding-instructions` - the validator supports the definition of a custom schema. By convention these schema files are named `<valueset-file-name>.schema.json` and are stored in `./schema`. So for `vaccine-encoding-instructions.json` the schema `vaccine-encoding-instructions.schema.json` is used.
 
-The validator also checks whether the set of actual valuesets coincides with the set expected by the [EU DCC Schema standard](https://github.com/ehn-dcc-development/eu-dcc-schema/blob/release/1.3.2/DCC.ValueSets.schema.json).
+The validator also checks whether the set of actual valuesets coincides with the set expected by the [EU DCC Schema standard](https://github.com/ehn-dcc-development/eu-dcc-schema/blob/release/1.3.3/DCC.ValueSets.schema.json).
 The exact GitHub reference - being a (release) tag, or branch - is configured through the `EU_DCC_SCHEMA_REF` constant defined in [this config file](./schemas/config.js).
 This constant needs to be updated when a new release of the EU DCC Schema is released, or while being worked on.
 

schemas/config.js

@@ -1,6 +1 @@
-// module.exports.EU_DCC_SCHEMA_REF = "release/1.3.2";
-
-// to verify that the 1.3.3 version of the EU DCC Schema will work:
-module.exports.EU_DCC_SCHEMA_REF = "feature/vaccine-encoding-instructions-valueset";
-// FIXME  remove and uncomment 1st line before merging
-
+module.exports.EU_DCC_SCHEMA_REF = "release/1.3.3";