• US Musical Work Licensing Choreography
Hide navigation
  • US Musical Work Licensing Choreography
    • 1 Introduction
    • 2 Scope
      • 2.1 Introduction
      • 2.2 Organisation of the Document
      • 2.3 Release Notes (informative)
    • 3 Normative References
    • 4 Terms and Abbreviations
      • 4.1 Terms and Definitions
      • 4.2 Abbreviations
    • 5 US Musical Work Licensing Choreography
      • 5.1 Overall Choreography
        • 5.1.1 Direct Communication
        • 5.1.2 Communication via a Hub
      • 5.2 SFTP Choreography
        • 5.2.1 Introduction
        • 5.2.2 Folder Naming Convention
        • 5.2.3 XML File Naming Convention
        • 5.2.4 Supporting File Naming Convention
        • 5.2.5 Manifest
        • 5.2.6 Acknowledgement
        • 5.2.7 Size of Batch
        • 5.2.8 Hybrid Batches
      • 5.3 Web Service Choreography
        • 5.3.1 Introduction
        • 5.3.2 Asymmetric Choreography with Atom Feeds
        • 5.3.3 Symmetric Choreography
        • 5.3.4 URLs
        • 5.3.5 Personalising the Feed
        • 5.3.6 Web Server Set-up and Authentication
        • 5.3.7 Identifying Web Service Callers Without Authentication
        • 5.3.8 Web Service Commands
          • 5.3.8.1 POST LicenseRequest
          • 5.3.8.2 POST License
          • 5.3.8.3 GET LicenseList
          • 5.3.8.4 GET License
    • 6 Syntax & Semantics of Messages
      • 6.1 Introduction
      • 6.2 General Conformance Rules
      • 6.3 Definition of Messages
      • 6.4 Allowed Value Sets
Show navigation

5.2.6 Acknowledgement

Once the message recipient has downloaded a file from within the Batch, the recipient shall upload an Acknowledgement file. The Acknowledgement file shall be called ACK_FFFF.xml with FFFF being the file name (without extension) of the message acknowledged.

The Acknowledgement file shall be placed into the same folder as the acknowledged file. Its syntax is defined in Clause 6 .

Search

    Powered by Instant Websites for Confluence