Page last modified 10:55, 17 Aug 2016 by Antero

Validation pipe

    Table of contents
    No headers

    Version as of 16:41, 7 Dec 2021

    to this version.

    Return to Version archive.

    View current version

    Validation pipe is a term often used by XMLdation to describe an item containing structural validation (.xsd) as well as business rules validation. XML-file may be inserted into validation pipe to find out whether the file is valid according the the rules present in validation pipe. 

    Validation pipe consists of

    Schema (.xsd)

    Schema defines the basic structure for validation pipe (and for the XML-file). Usually the schemas used in XMLdation service are defined by ISO 20022. It is of course possible to use whatever valid schema for a validation pipe. 

    Business Rule validation

    Business rule validation is the core of the validation service.

    Validation rules are written by XMLdation experts or by myXML users. The amount of rules depends on the pipe, but in total it is usually somewhere between 50 - 200.

    Following is an example of two business rules, defined by ISO 20022 for Credit Transfers: 

    When element PmtInf/PmtTpInf is present, 
    then PmtInf/CdtTrfTxInf/PmtTpInf is not allowed.
    Group Header ControlSum has to match with the arithmetic sum of 
    all InstdAmt and EqvtAmt/Amt elements.

    These business rules are not possible to be validated by ISO 20022 schema, as they are not (and in this case cannot be) defined in schema. Based on these business rules we are able to create two business rule validation rules. 

    Validation rules are created using OCL, object constraing language.


    Ruleset is a collection of business rules. We have rulesets so we are able to inform the style and origin of the rules better to the user. For example in Credit Transfer and Direct Debit pipes we often have ISO 20022 Business Rules as one ruleset. This way we are able to separate ISO rules from bank/organisation specific rules.