Skip to end of metadata
Go to start of metadata

 

During the integration phase, the content provider and DSP will need to conduct a "peer conformance procedure" where 

  1. the content owner determines if the DSP is able to receive and ingest the content according to the provided test packages and 
  2. the DSP reviews the test packages from the content owner to verify the delivered packages complies with the standards.

The content provider will send a series of sample deliveries containing test products and business scenarios. These sample deliveries are intended to test the DSP's ability to receive/ingest content using the chosen delivery choreography, as well as their ability to correctly interpret the NewReleaseMessages.

  • DDEX provides both content providers and DSPs with a consistent means of interpreting the metadata within NewReleaseMessages. During the integration phase, the content provider would typically send the DSP various XML messages to the partner, representing the following:
  • Different Release types, e.g. single release, album release, etc.; (The most common Release types are defined the Release Profile Standard for Common Release Types, which is available from URL);
  • Different Deal terms: single/multi-territories, multiple deal terms, price code/values, etc.; (The most common Deal types are defined the Business Profile Standard for Common Deal Types, which is available from URL);
  • Different Business Scenarios; insert, update, revoke, takedown

The test messages, delivered during the conformance test phase, will have the IsTestFlag set to true to indicate that the messages are test messages and their content should not be made available to real consumers.

These messages ensure that the DSP's ingestion engine interprets the NewReleaseMessages accurately. During the Metadata conformance process, the content provider will need to verify the content and message ingestion results with each DSP based on their choice of choreography.

Read on

 

  • No labels