Skip to end of metadata
Go to start of metadata

What is the aim of Basic Audio Profile for The Mechanical Licensing Collective?

The message defined in this Part provides a mechanism for Licensees (typically Digital Service Providers) to report to The Mechanical Licensing Collective sales/usage information from the exploitation of Products based on electronic Releases containing Sound Recordings which embody Musical Works and/or other Resources.

The Profile was specifically created to satisfy the communication requirements of the Mechanical Licensing Collective as established, under US law, by the Music Modernization Act.

 

How is a report built?

The profile is provided in two variants. The default variant is the Multi-Record Block Variant (MRBV) where usage and/or revenues are reported using the following way:

  • A header that contains general information such as information about the sender and receiver. The header is common to all MRBV DSR formats.
  • A summary for each sales/usage context.
    This new and powerful concept enables a licensee to report as many contexts he needs in a single report. For instance, a licensee that would like to report five commercial offers in Europe (31 territories) would need to report 5*31 contexts – leading to 155 summary records. In the main body of the sales/usage report in the report, each sales record will only need to point to a summary line instead of repeating the context information.
    The type of the summary record (SU01) or (SU02) to be used depends on the use type.
  • Blocks of detailed sales/usage information.
    These blocks are the body of the report. Each block contains all information to process it:  Information about the Release, Resource and Work that has been used as well as the relevant sales usage aspects.
    This new concept avoids for the receiver to store first all documentation and then process sales lines as it was the case with the previous XML version. Moreover, DDEX developed a notion of "sub-release" to avoid the repetition of the same documentation again and again when just part of a release is sold (e.g.: a single resource in a release …).
    Each sales lines points to a summary line, providing sales information for a release or sub-release in a single context (e.g.: the sales for this commercial offer in this territory).
    The block can be reported at release level or resource level, depending on the business model.
  • A footer that contains information about the sales/usage report such as the number of records that are included. The header is common to all MRBV DSR formats.

 

  • No labels