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

Each of the messages defined in this Standard conveys a set of data elements from sender to recipient. The following diagrams show these information elements for the various messages. They allow a rapid overview of the different messages for technicians as well as for business process experts of organisations that are to implement the Standard defined herein. The data element names shown in the diagrams below are not the formal names used in the messages as thediagram is intended to provide a quick overview of the data to be provided within the messages. The diagrams are not normative.

Note that one XML Attribute, LanguageAndScriptCode, is only shown on the top-level (message) composites. This attribute is, in fact, present on all composites or elements that might benefit from being coded in different languages and/0r scripts. If placed on a composite, its value applies to all sub-elements (and, potentially, overrides a different LanguageAndScriptCode “further up”. If placed on an element its value applies only to that element. The LanguageAndScriptCode is provided in accordance with IETF RfC 4646.

Also note that dashed lines represent logical relationships between entities. These relationships are represented not but one entity’s metadata physically including the other entity’s metadata but by referencing — using XML Schema’s xs:ID/xs:IDREF mechanism — the linked entity. The “anchors” for these references are not listed in the diagrams below.


Figure 4 — Information content in the RequestSoundRecordingInformationMessage

 Figure 5 — Information content in the DeclarationOfSoundRecordingRightsClaimMessage

Figure 6 — Information content in the RevokeSoundRecordingRightsClaimMessage

Figure 7 — Information content in the SalesReportMessage

Figure 8 — Information content in the DeclarationOfRevenueMessage


  • No labels
Write a comment…