Streaming Availability

Example Streaming Deal - Split CommercialModelType

<Deal>
  <DealTerms>
    <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>
    <Usage>
      <UseType>Stream</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <ValidityPeriod>
      <StartDate>2017-09-01</StartDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>
<Deal>
  <DealTerms>
    <CommercialModelType>SubscriptionModel</CommercialModelType>
    <Usage>
      <UseType>Stream</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <ValidityPeriod>
      <StartDate>2017-09-01</StartDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>

Example Streaming Deal - Grouped CommercialModelType

<Deal>
  <DealTerms>
    <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>
    <CommercialModelType>SubscriptionModel</CommercialModelType>
    <Usage>
      <UseType>Stream</UseType>
    </Usage>
    <TerritoryCode>GB</TerritoryCode>
    <TerritoryCode>DE</TerritoryCode>
    <ValidityPeriod>
      <StartDate>2017-09-01</StartDate>
    </ValidityPeriod>
  </DealTerms>
</Deal>

Deal Terms and Usage

This element encapsulates the terms under which a music release is made available to partners. Each <Deal> specifies the commercial conditions and usage rights for which we can make tracks and releases available to services.

<DealTerms>

• Description: Contains the specific terms and conditions governing the distribution and usage of the release.

• <CommercialModelType>: Defines the business model under which the release is offered. It can vary between deals and may be grouped together if the terms are identical across different models, or specified separately for distinct terms.

  Example: AdvertisementSupportedModel and SubscriptionModel show two types of commercial models that could be offered concurrently, specifying different access conditions under the same deal terms.

  Note: MassiveMusic only supports the AdvertisementSupportedModel and SubscriptionModel for streaming services.

  • Grouped Specification: When multiple territories or usage conditions share the same commercial model, they can be grouped under a single <CommercialModelType> within the deal terms to simplify the deal structure and reduce redundancy.

  • Separate Specification: Alternatively, different <CommercialModelType>s can be specified separately within distinct <Deal> elements if the terms differ significantly—such as different start dates, territories, or usage types—requiring individual detailing.

• <Usage>:

  • <UseType>: Specifies the type of usage allowed under the deal, such as streaming or downloading.

    Example: Stream - This use type indicates that the release is available for streaming.

    Note: Stream is required for the provision of content on the platform and is the only supported <UseType>. Music not delivered containing OnDemandStream will not pass our validation rule and will fail ingestion.

  • <TerritoryCode>: Indicates the territories where the deal is applicable. Multiple <TerritoryCode> elements can be used to specify more than one country.

    Example: GB, DE - Specifies that the deal applies within the United Kingdom and Germany. When WW or Worldwide is used, MassiveMusic interprets this as the release or track being available in all territories, eliminating the need for extensive lists of territories when there are no geographic restrictions on the release.

    A full list of valid TerritoryCode can be found.

• <ValidityPeriod>

  This element specifies the duration during which the deal terms are effective, including both the start and end dates.

  • <StartDate>

    Description: The date from which the deal terms become effective.

    Example: 2024-06-02 - Marks the beginning of the validity period for the deal terms.

  • <StartDateTime>

    Description: Specifies the exact date and time from which the deal terms become effective.

    Example: 2024-06-02T08:00:00 - Though specified, this will be interpreted as 2024-06-02 00:00:00 local time.

  • <EndDate>

    Description: The date on which the deal terms expire. Where no EndDate is provided, a release will stay live indefinitely. An EndDate can be provided without a StartDate to indicate that a release should no longer be commercially available and taken down from the platform.

    Example: 2024-06-02 - Indicates the end of the validity period for the deal terms.

Deal Terms and Usage

This element encapsulates the terms under which a music release is made available to partners. Each <Deal> specifies the commercial conditions and usage rights for which we can make tracks and releases available to services.

<DealTerms>

• Description: Contains the specific terms and conditions governing the distribution and usage of the release.

• <CommercialModelType>: Defines the business model under which the release is offered. It can vary between deals and may be grouped together if the terms are identical across different models, or specified separately for distinct terms.

  Example: AdvertisementSupportedModel and SubscriptionModel show two types of commercial models that could be offered concurrently, specifying different access conditions under the same deal terms.

  Note: MassiveMusic only supports the AdvertisementSupportedModel and SubscriptionModel for streaming services.

  • Grouped Specification: When multiple territories or usage conditions share the same commercial model, they can be grouped under a single <CommercialModelType> within the deal terms to simplify the deal structure and reduce redundancy.

  • Separate Specification: Alternatively, different <CommercialModelType>s can be specified separately within distinct <Deal> elements if the terms differ significantly—such as different start dates, territories, or usage types—requiring individual detailing.

• <Usage>:

  • <UseType>: Specifies the type of usage allowed under the deal, such as streaming or downloading.

    Example: Stream - This use type indicates that the release is available for streaming.

    Note: Stream is required for the provision of content on the platform and is the only supported <UseType>. Music not delivered containing OnDemandStream will not pass our validation rule and will fail ingestion.

  • <TerritoryCode>: Indicates the territories where the deal is applicable. Multiple <TerritoryCode> elements can be used to specify more than one country.

    Example: GB, DE - Specifies that the deal applies within the United Kingdom and Germany. When WW or Worldwide is used, MassiveMusic interprets this as the release or track being available in all territories, eliminating the need for extensive lists of territories when there are no geographic restrictions on the release.

    A full list of valid TerritoryCode can be found.

• <ValidityPeriod>

  This element specifies the duration during which the deal terms are effective, including both the start and end dates.

  • <StartDate>

    Description: The date from which the deal terms become effective.

    Example: 2024-06-02 - Marks the beginning of the validity period for the deal terms.

  • <StartDateTime>

    Description: Specifies the exact date and time from which the deal terms become effective.

    Example: 2024-06-02T08:00:00 - Though specified, this will be interpreted as 2024-06-02 00:00:00 local time.

  • <EndDate>

    Description: The date on which the deal terms expire. Where no EndDate is provided, a release will stay live indefinitely. An EndDate can be provided without a StartDate to indicate that a release should no longer be commercially available and taken down from the platform.

    Example: 2024-06-02 - Indicates the end of the validity period for the deal terms.