• Entity Cluster Message Suite - Part 1: Communication Protocol
Hide navigation
  • Entity Cluster Message Suite - Part 1: Communication Protocol
    • 1 Introduction
    • 2 Organisation of the document
    • 3 Normative references
    • 4 Terms and abbreviations
      • 4.1 Terms and definitions
      • 4.2 Abbreviations
    • 5 Message-by-message profile
      • 5.1 Choreography
      • 5.2 Server organisation
      • 5.3 File naming conventions
      • 5.4 Example of server organisation and file naming convention (informative)
    • 6 Batched profile
      • 6.1 Choreography
      • 6.2 Batch constraints
      • 6.3 Server organisation
      • 6.4 File naming conventions
      • 6.5 Example of server organisation and file naming convention (informative)
    • 7 Supporting messages
      • 7.1 Message definition
      • 7.2 Structure of the Manifest
      • 7.3 Structure of the Acknowledgement
      • 7.4 Schema validation
      • 7.5 Contractually mandatory
      • 7.6 Allowed-value sets
Show navigation

5.4 Example of server organisation and file naming convention (informative)

The example below shows three delivered messages. The second message has already been acknowledged by the message recipient, the others have not.

MusicalWorkClusterNotification_20260310130322000.json
MusicalWorkClusterNotification_20260310130323000.json
MusicalWorkClusterNotification_20260310130324000.json
acknowledgements/
    ACK_MusicalWorkClusterNotification_20260310130323000.json

Search

    Powered by Instant Websites for Confluence