Before an eForms notice can be accepted for publication, it is always validated against a set of business rules by the TED Central Validation Service (TED CVS).
|TED CVS checks the information submitted in the notice for correctness, consistency and completeness as a measure for improving the quality of the data collected and shared through public procurement notifications.|
The ultimate goal of your application is to submit a notice for publication. Submitting a valid notice is therefore essential for your notice to be accepted for publication.
An obvious choice that is available to everyone, is to rely on the Validation API for validating your notices. The API will provide you with a validation report in SVRL (Schematron Validation Report Language) which you can use to pass validation messages on to your end-users.
The report contains a list of all validation rules that were executed. Any assertions that failed will be indicated with
svrl:failed-assert elements providing you with additional information on the severity of the failure (in the
@role attribute), the
@location (XPath) of the issue, and the
@test (XPath) that was performed.
The validation message intended for display to your end-user is provided in the
svrl:text element, in the language you indicated in your request. If the message is not available yet in this language, the identifier of the label is given instead.
For certain types of rules, the value in the
@location attribute does not indicate the exact element that caused the problem. For example, for a rule that checks that a mandatory element is present,
@location will point to the XML element that is supposed to contain this mandatory element. In this case, the XPath of the missing element is given in the
svrl:diagnostic-reference element, relative to the XPath indicated in
If you want to avoid the round-trip to the TED Validation API, or you want to combine the validation rules provided in the eForms SDK with additional Schematron validation rules of your own, you may consider setting up your own validation service, local to your information system.
The validation rules provided in the
schematrons folder are meant to validate fully formed XML files. If you want to provide validation inside your application while the user is still filling in their form, then this set of rules is not suitable for the job.
To allow applications to performed so-called "live validation" (a.k.a. "client-side validation"), we have included a set of suitable validation rules as constraints attached to every field in