THIS VERSION IS NOT THE LATEST RELEVANT DDEX STANDARD. DDEX RECOMMENDS TO USE THE LATEST VERSION.

Skip to end of metadata
Go to start of metadata

This standard defines 17 Business Profiles. They are categorised by a series of key allowed-values that need to be communicated in the relevant fields in a conformant sales report message.

In some cases it may be necessary to specify a specific DistributionChannelType and/or UserInterfaceType (e.g. for an internet-only Ad-Supported Download Service or an Ad-Supported Conditional Download Service limited for use on mobile phones). If none of these values are provided in a sales report any DistributionChannelType and/or UserInterfaceType may have been used by the message sender’s consumers. The same applies for DrmEnforcementType with no DrmEnforcementType meaning that the consumer accessed DRM-protected and/or non-protected content.

Table 2 — Business Profiles defined in this Standard

Profile Name

CommercialModel-Type

UseType

Other aspects

1. Generic Download Service

Consumers can download content via the internet and keep the DRM-protected Releases with no limitation (this profile was called “profile 1” in the Business Profile: Sales Reporting to Music Rights Societies).

PayAsYouGoModel

PermanentDownload

 

2. Ringtones and Mobile Service

Consumers can access content as Ringtones on their mobile phones. This also includes other "Mobile Products" (2).

PayAsYouGoModel

UseAsRingtone or UseAsRingbackTone

 

3. Subscription Download Service

Consumers can download content via the internet and keep the Releases (5).

SubscriptionModel

PermanentDownload

 

4. Interactive Subscription Streaming Service

Consumers subscribe to a service where they can interactively stream content from a large repository of content (6).

SubscriptionModel

OnDemandStream

 

5. Interactive Ad-Supported Subscription Streaming Service

Consumers can download content via the internet and keep the Releases as long as a subscription is kept. Payment is partly via subscription fees and party through advertisements (13).

AdSupportedModel followed by[1] SubscriptionModel

OnDemandStream

 

6. Tethered[2] Subscription Download Service

Consumers can download content via the internet and keep the Releases as long as a subscription is kept (7).

SubscriptionModel

Conditional-Download

 

7. Interactive Ad-Supported Streaming Service

Consumers subscribe to a service where they can interactively stream content from a large repository of content. Payment is received via advertisement.

AdSupportedModel

OnDemandStream

 

8. Ad-Supported Non-interactive Streaming[3]

Consumers subscribe to a service where they cannot interact with the stream content beyond start/pause/stop/skip from a large repository of content. Payment is received via advertisement. Also: Consumers can listens to pre-programmed (often algorithmically generated) stream of music with no interactivity. Payment is received via advertisement. (9)

AdSupportedModel

NonInteractive-Stream

 

9. Ad-Supported Time-limited-Interactive Streaming Service

Consumers can stream music with only temporal interactivity. Payment is received via advertisement (10).

AdSupportedModel

TimeInfluenced-Stream

 

10. Ad-Supported Download Service

Consumers can download content via the internet and keep the DRM-protected Releases with no limitation. Payments are funded through advertisements (11).

AdSupportedModel

PermanentDownload

 

11. Ad-Supported Teathered Download Service

Consumers can download content via the internet and keep the Releases as long as a subscription is kept. Payments are funded through advertisements (12).

AdSupportedModel

ConditionalDownload

 

12. Non-Protected Download Service

Consumers can download content via the internet and keep the non-protected Releases with no limitation.

PayAsYouGoModel

PermanentDownload

DrmEnforce-mentType of NotDrmEnforced

13. DRM-Protected Download Service

Consumers can download content via the internet and keep the DRM-protected Releases with no limitation.

PayAsYouGoModel

PermanentDownload

DrmEnforce-mentType of DrmEnforced

14. Kiosk Service

Consumers can access a physical Kiosk and download content from there. They can then keep the Releases.

PayAsYouGoModel

PermanentDownload

UserInterface-Type of Kiosk

15. Non-Interactive Subscription Streaming Service[4]

Consumers subscribe to a service where they cannot interact with the stream content beyond start/pause/stop/skip from a large repository of content. Also: Consumers can listens to pre-programmed (often algorithmically generated) stream of music with no interactivity. Payment is received via subscription fee.

SubscriptionModel

NonInteractive-Stream

 

16. Non-Interactive Ad-Supported Streaming Service

Consumers subscribe to a service where they cannot interact with the stream content beyond start/pause/stop/skip from a large repository of content. Payments are funded through advertisements

AdSupportedModel

NonInteractive-Stream

 

17. Purchase As Physical Product

Normally not used

PurchaseAsPhysicalProduct

 

The following constraints on the sales report message shall be adhered to:
  1. The MessageSchemaVersionId attribute to the root element shall be included and set in accordance with the relevant Sales Reporting Message Suite Standard.
  2. The BusinessProfileVersionId and ReleaseProfileVersionId attributes to the root element shall be set in accordance with Sub-clause 2.4 of this standard.
  3. A MessageHeader shall be provided as follows:
    1. A MessageThreadId and MessageID shall be provided.
    2. A MessageSender and MessageRecipient shall be provided through a DPID and a FullName.
    3. A SentOnBehalfOf shall be provided only if message is created by a company not liable for reporting. In that case the same structure as below shall be used as for MessageSender and MessageRecipient.
    4. A MessageCreatedDate shall be provided.
    5. No AuditTrail shall be provided.
  4. A MessageNotificationPeriod shall be provided.
  5. No RemittanceAdvice, MessageContentRevenueType or RightsCoverage shall be provided.
  6. A SalesReportToRecordCompanies shall contain ContainedReleaseSummary information for all Releases for which usages/sales are reports in the sales report message as follows:
    1. At least one ReleaseId, without the IsReplaced flag being set shall be communicated.
    2. A ReleaseType shall be communicated.
    3. A ReleaseReference shall be included.
    4. The TitleText of a ReferenceTitle shall be communicated.
    5. No RightsAgreementId or RelatedRelease shall be provided.
    6. At least one ReleaseSummaryDetailsByTerritory shall be communicated, typically with the TerritoryCode set to WorldWide with the following subelements:
      1. At least one DisplayArtistName and LabelName shall be provided.
      2. No RightsAgreementId shall be provided.
  7. A SalesReportToSocietyMessage
    1. Shall not contain any ContainedReleaseSummary but shall contain Release and Resource information in defined in Sub-clause 2.2 of this standard for all Releases for which usages/sales are reports in the sales report message.
    2. May contain a MusicalWork composite. If that is provided, at least one "creative" MusicalWorkContributor should, if possible, be provided. "Creative" parties are parties with one of the following MusicalWorkContributorRoleCodes: Adapter, Arranger,AssociatedPerformer, Author, Composer, ComposerLyricist, Contributor, Librettist, Lyricist, NonLyricAuthor. SubArranger, Translator.
  8. One SalesReport composite shall be provided as follows:
    1. A DSP composite needs to be provided with the FullName of the DSP’s PartyName and a Party ID.
    2. A Licensor shall be provided in a SalesReportToSocietyMessage with the FullName of the Licensor’s PartyName and a Party ID.
    3. At least one SalesByCommercialModel shall be provided as follows:
      1. One or more CommercialModelTypes need to be provided in accordance with Table 2.
      2. One CurrencyOfAccounting is to be provided.
      3. At least one SalesByTerritory shall be provided as follows:
        1. Exactly one TerritoryCode shall be provided. This may not be “WorldWide”.
        2. No TaxRate and no Deal shall be provided.
        3. At least one ReleaseTransaction shall be provided as follows:
          1. A TransactionReleaseReference shall be provided for each Release.
          2. At least one SalesTransaction shall be provided as follows:
            1. UseType(s), UserInterfaceType(s) and DistributionChannelType(s) shall be provided in accordance with Table 2 (note, that UserInterfaceType and DistributionChannelType may be optional).
            2. A Deal/DetailedDeal shall be provided only in a SalesReportToRecordCompanies with any combination of the following optional fields: PriceInformation (with either PrieceRangeType, WholesalePricePerUnit or ECPM), PromotionalCode, CampaignName, DeductionRate, EffectiveUnitRoyaltyRateNet (wich is mandatory), IsReplacementPurchase and TechninalInstantiation plus a mandatory PriceConsumerPaidExcSalesTax. Any other element shall not be provided. (Note: this is the only place where a Deal composite is permissible)
            3. SalesData shall be provided as follows:
              1. SalesDataGrouping, including sub-elements, may be provided, typically for Marketing Reports in accordance with the commercial relationship between message sender and recipient.
              2. NumberOfConsumerSalesGross and NumberOfFreeUnitsToConsumers shall be provided.
              3. NumberOfUnitAdjustments and NumberOfUnitAdjustmentsToFreeUnits may be provided if adjustments are to be made.
            4. No isUpgrade flag shall be set.
            5. The DataToBeForwarded flag shall be provided appropriately.
          3. Comments and DurationsUsed are not to be included in the message.
        4. RecordCompanyMarketShareData shall only be provided in a SalesReportToRecordCompaniesMessage, if required by the commercial relationship between sender and recipient. This composite shall include UnitsSoldTotal and may include UseType(s), UserInterfaceType(s) and DistributionChannelType(s) in accordance with Table 2.
        5. NumberOfSubscribers and DspNetRevenues shall be provided even if no subscribers are reported with relevant UseType(s), UserInterfaceType(s) and DistributionChannelType(s) in accordance with Table 2.
        6. DspGrossRevenue shall be provided for subscription services with UseType(s), UserInterfaceType(s) and DistributionChannelType(s) in accordance with Table 2.
        7. DspDeductionsAmounts or PercentageNetRevenueShare may be communicated if required by the commercial relationship between sender and recipient.
        8. No,MinimumAmountPerCustomer, WholesaleAmountTotal, WholesaleAmountTotalInCurrencyOfAccounting and CurrencyExchangeRate need to be reported.
        9. TotalAmountPayableInCurrencyOfAccounting shall be reported.
  9. TotalSalesByReleaseType needs to be reported in the SalesReportToRecordCompanyMessage only.
  10. RoyaltyAmount and NumberOfSalesTransactionRecords need to be provided.
  11. Systems are required to be able to operate on financial elements that are of a basic XML data type xs:decimal with six decimal digits unless specifically agreed differently by the involved parties.

All other data elements provided may be ignored by the message recipient.



[1] The sales report shall have one SalesReportByCommercialModel composites, with two CommercialModel-Type elements as defined in the table.

[2] This is also called conditional subscription download.

[3] Also known as Ad-Supported Web Radio.

[4] Also known as Subscriber Web Radio


  • No labels