ASSETS VERSIONED IN GIT MANDATORY

Contents

Introduction

In order to facilitate interoperability for the ebMS Message Header, a set of business rules must be applied for the ebMS Header in each transaction (Evidence Request, Evidence Reponse, Error Response). The business rule IDs for the ebMS Message Header are using the prefix EDM-ebMS. For each business rule, a corresponding schematron rule is defined that references the same rule ID. The business rules are sets of rules that guarantee the correct structure of the transactions and they clarify the content of instances by stating mandatory fields, fixed values (like code lists), the dependency between fields in the same object and dependency between different objects.

Each business rule is associated with an error level (role) that expresses a validation result when an XML instance is proven against the rules through schematron validation:

• caution: A hint that an additional object is needed in some cases; It may not be wrong, but care is required.
• warning: Offering recommendations to improve the quality of the instance or regain full validity; Something wrong has happened, but it does not necessarily require action. 
• fatal: The rule point to a major issue of consistency or data correctness. Something so bad that processing or validation should or did stop. 

The rule type classifies the principle goal of a business rule. The rule ID is used to identify the rule and can be used as an error code next to the rule description. Rule descriptions containing "MUST" correspond to an error level that is flagged as fatal, leading to a termination of the process while "SHOULD" rules correspond to an error level that is flagged as a warning. The process can continue in this case. "MAY" rules point to error level caution and are indications that also do not lead to a process termination of the process.