• Anomaly Reporting - Part 2: Reporting of consumer engagement anomalies
Hide navigation
  • Anomaly Reporting - Part 2: Reporting of consumer engagement anomalies
    • 1 Introduction
    • 2 Organisation of the document
    • 3 Normative references
    • 4 Terms and abbreviations
      • 4.1 Terms and definitions
      • 4.2 Abbreviations
    • 5 Scenarios for use of messages
    • 6 Message Definition
      • 6.1 Namespace
      • 6.2 Structure of the messages
      • 6.3 Allowed-value sets
      • 6.4 Schema validation
      • 6.5 Indicating unknown values
      • 6.6 Contractually mandatory
      • 6.7 MessageId and AnomalyId
Show navigation

6.6 Contractually mandatory

Any message is deemed conformant only if and when it contains all the contractually mandatory tags or composites as determined by the bilateral agreement between the message sender and the message recipient even if those tags are optional in the JSON Schema Definition.

Search

    Powered by Instant Websites for Confluence