© 2006-2018 Digital Data Exchange, LLC (DDEX) This XML Schema Definition file is, together with all DDEX standards, subject to two licences: If you wish to evaluate whether the standard meets your needs please have a look at the Evaluation Licence at https://kb.ddex.net/display/HBK/Evaluation+Licence+for+DDEX+Standards. If you want to implement and use this DDEX standard, please take out an Implementation Licence. For details please go to http://ddex.net/apply-ddex-implementation-licence. A Message in the Release Delivery Choreography Standard that is sent to document the FTP transfer of a batch of Release Notification Messages, potentially accompanied by Resource or Release files. The MessageHeader for the ManifestMessage. The Flag indicating whether the Message is a TestMessage (=true) or a LiveMessage (=false). An Identifier of the root directory of all Messages in the batch communicated through the ManifestMessage. The number of Messages in the batch communicated through the ManifestMessage. A Composite containing details of a Release Notification Message in the batch. The Version of the Message. A Message in the Release Delivery Choreography Standard for FTP exchange. The MessageHeader for the ErnAcknowledgementStatusMessage. A Composite containing details of the Release status. A Composite containing details of a CatalogNumber. The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute. A Composite containing a digital signature of the File in accordance with DDEX-DSIG. An Element of type SignedInfoType. An Element of type SignatureValueType. A KeyInfo Composite. An XmlAttribute of type xs:ID. A Composite containing details of a Release Notification Message in a Batch. The Type of Message. An Identifier of the Message. A URL of the Message. A Composite containing details of ReleaseIds. If available, a GRid should always be used. A Composite containing details of the Type of action that the MessageSender applies to the Message. A Composite containing details of the Type of a Product defining which kinds of Products are within the delivered batch. Each batch may only contain one type of Products. A Composite containing a HashSum of the File and information about the algorithm with which it has been generated. A digital signature in accordance with DDEX-DSIG. A Composite placed at the beginning of each Message providing information about the Message such as MessageSender, MessageRecipient and a Message creation time stamp. A Composite containing details of the MessageSender. A Composite containing details of the MessageRecipient. The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD). A Composite containing a HashSum and information about the algorithm with which it has been generated. A digital signature in accordance with DDEX-DSIG. A Composite containing details of a HashSum and its governing Algorithm. The value of the HashSum. A Composite containing details of the Type of HashSumAlgorithm governing the HashSum. The datatype of the HashSum. A Composite containing details of a HashSumAlgorithmType. The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute. A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute. A KeyInfo Composite. An X509Data Composite. An XmlAttribute of type xs:ID. A Composite containing details of a MessageActionType. The Namespace of the MessageActionType. This is represented in an XML schema as an XML Attribute. A UserDefined value of the MessageActionType. This is represented in an XML schema as an XML Attribute. A Composite containing information about Parties in between the original MessageSender and ultimate MessageRecipient. A Composite containing details of a Party handling the Message and the Time at which the handling took place. A Composite containing details of a Party handling a Message and the Time at which the handling took place. A Composite containing details of a MessagingParty. The DateTime at which the Message was handled by the MessagingParty (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD). A Composite placed at the beginning of each DdexMessage providing information about the Message, such as MessageSender, MessageRecipient and a Message creation time stamp. A xs:string used to uniquely identify the thread of Messages of which the current Message is a part. The MessageThreadId shall be, in combination with the DdexPartyId (DPID) of the MessageSender, globally unique. Thus, a MessageSender shall never re-use a MessageThreadId. One example of such a 'thread' is the chain of NewReleaseMessages being sent from ReleaseCreator to wholesale ReleaseDistributor 1 to retail DSP when communicating information about the same Release(s). A common MessageThreadId will allow all these messages to be tied together. A xs:string used to uniquely identify the current Message. The MessageId shall be, in combination with the DdexPartyId (DPID) of the MessageSender, globally unique. Thus, a MessageSender shall never re-use a MessageId. The FileName, possibly including the FilePath, of the XML File containing the current Message. A Composite containing details of the MessageSender. A Composite containing details of the Party on whose behalf the Message is sent. A Composite containing details of the MessageRecipient. Note that if multiple MessageRecipients are provided, all of them will be able to read this information. The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD). A Composite containing information about Parties in between the original MessageSender and ultimate MessageRecipient. The indicator used to distinguish a live Message from a test Message. A Composite containing details of a MessagingParty. A Composite containing details of the PartyId for the Party handling the Message. If no Namespace is given, the Identifier is a DdexPartyId (DPID). Note that DPIDs are not normally used to identify Artists, producers or other Creators. A Composite containing details of the PartyNames for the Party handling the Message. A Composite containing a TradingName for the Party handling the Message. The Language and script for the Elements of the MessagingParty as defined in IETF RfC 5646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-script][-region][-variant]. This is represented in an XML schema as an XML Attribute. A Composite containing details of a MessagingParty. An Identifier of a Party according to the DdexPartyId standard DDEX-DPID. A Composite containing details of the PartyNames for the Party handling the Message. A Composite containing a TradingName for the Party handling the Message. A Composite containing details of a Name. The Language and script of the Name as defined in IETF RfC 5646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-script][-region][-variant]. This is represented in an XML schema as an XML Attribute. A Composite containing details of a PartyId. If no Namespace is given, the Identifier is a DdexPartyId (DPID). Note that DPIDs are not normally used to identify Artists, producers or other Creators. The Namespace of the PartyId if it belongs to a proprietary Party xs:ID scheme. If the PartyId is a DPID, the Namespace Element must not be used. This is represented in an XML schema as an XML Attribute. The Flag indicating whether the PartyId is a DPID (=true) or not (=false). This is represented in an XML schema as an XML Attribute. The Flag indicating whether the PartyId is an ISNI (=true) or not (=false). This is represented in an XML schema as an XML Attribute. A Composite containing details of a PartyName. Name details for a Party typically either contain a FullName or a KeyName. A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, the Beatles). The FullName transcribed using 7-bit ASCII code. A Composite containing the complete Name of the Party in the form in which it normally appears in an alphabetic index, with the KeyName first (e.g. Smith, John H.; Beatles, The). A Composite containing the Name(s) preceding the KeyName in the FullName (and that is placed after it in a FullNameIndexed). Examples: 'George' in 'George Michael'; 'John Fitzgerald' in 'John Fitzgerald Kennedy'. Not all PartyNames have a NamesBeforeKeyName (e.g. Madonna, EMI Music Inc). A Composite containing the Part of a Name of the Party normally used to index an entry in an alphabetical list, such as 'Smith' (in John Smith) or 'Garcia Marquez' or 'Madonna' or 'Francis de Sales' (in Saint Francis de Sales). For persons, this normally corresponds to the 'family name' or names, which in Western name forms usually comes as a surname at the end of a FullName, and in Asian name forms often at the beginning of a FullName. A Composite containing the Name(s) following the KeyName. Example:'Ibrahim' (in Anwar Ibrahim). This is common, e.g., in many Asian personal name forms where a FullName begins with the KeyName, which is followed by other names. A Composite containing a short version of the PartyName (e.g. for use on devices with a small display). The Language and script for the Elements of the PartyName as defined in IETF RfC 5646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-script][-region][-variant]. This is represented in an XML schema as an XML Attribute. A Composite containing details of a PartyName. Name details for a Party typically either contain a FullName or a KeyName. The complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, the Beatles). The FullName transcribed using 7-bit ASCII code. The complete Name of the Party in the form in which it normally appears in an alphabetic index, with the KeyName first (e.g. Smith, John H.; Beatles, The). The Name(s) preceding the KeyName in the FullName (and that is placed after it in a FullNameIndexed). Examples: 'George' in 'George Michael'; 'John Fitzgerald' in 'John Fitzgerald Kennedy'. Not all PartyNames have a NamesBeforeKeyName (e.g. Madonna, EMI Music Inc). The Part of a Name of the Party normally used to index an entry in an alphabetical list, such as 'Smith' (in John Smith) or 'Garcia Marquez' or 'Madonna' or 'Francis de Sales' (in Saint Francis de Sales). For persons, this normally corresponds to the 'family name' or names, which in Western name forms usually comes as a surname at the end of a FullName, and in Asian name forms often at the beginning of a FullName. The Name(s) following the KeyName. Example:'Ibrahim' (in Anwar Ibrahim). This is common, e.g., in many Asian personal name forms where a FullName begins with the KeyName, which is followed by other names. A short version of the PartyName (e.g. for use on devices with a small display). A Composite containing details of a ProductType. The Namespace of the ProductType. This is represented in an XML schema as an XML Attribute. A UserDefined value of the ProductType. This is represented in an XML schema as an XML Attribute. A Composite containing details of a ProprietaryIdentifier. The Namespace of the ProprietaryIdentifier. This is represented in an XML schema as an XML Attribute. A Composite containing details of a ReleaseId. If available, a GRid should always to be used. If the Release contains only one SoundRecording, the ISRC of the SoundRecording may be used instead. If the Release is an abstraction of a complete PhysicalProduct (such as a CD Album), the ICPN of the PhysicalProduct may be used instead. The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the xs:string 'A1', followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character. DDEX will enforce the syntax [a-zA-Z0-9]{18} using XML Schema in the future. The ISRC (International Standard Recording Code as defined in ISO 3901) used as proxy for identification of the Release. Only applicable when the Release only contains one SoundRecording or one MusicalWorkVideo. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits. DDEX will enforce the syntax [a-zA-Z]{2}[a-zA-Z0-9]{3}[0-9]{7} using XML Schema in the future. An ICPN used as proxy for identification of the Release. Only applicable when the Release is an abstraction of a complete PhysicalProduct. An ICPN comprises 12 or 13 digits, depending whether it is an EAN (13) or a UPC (12). DDEX will enforce the syntax [0-9]{12,13} using XML Schema in the future. A Composite containing details of the CatalogNumber of the Release. A Composite containing details of a ProprietaryIdentifier of the Release. A Composite containing details of a SupplyChainStatus. The Namespace of the SupplyChainStatus. This is represented in an XML schema as an XML Attribute. A UserDefined value of the SupplyChainStatus. This is represented in an XML schema as an XML Attribute. An X509Data Composite. An Element of type X509IssuerSerialType. An Element of type xs:base64Binary. An Element of type xs:string. An Element of type xs:base64Binary. An Element of type xs:base64Binary. A Composite containing details of the PartyId for the Party. If no Namespace is given, the Identifier is a DdexPartyId (DPID). Note that DPIDs are not normally used to identify Artists, producers or other Creators. A Composite containing details of an acknowledgement. The Type of Message. An Identifier of the Batch. An Identifier of the Message. A Composite containing details of the Message Status. A Composite containing details of a Message Status. A Composite containing details of the status of the Message. A Status text for the Message. A Composite containing details of a ProposedActionType. The Namespace of the ProposedActionType. This is represented in an XML schema as an XML Attribute. A UserDefined value of the ProposedActionType. This is represented in an XML schema as an XML Attribute. A Composite containing details of a Release status. A Composite containing details of ReleaseIds. If available, a GRid has to be used. If the Release contains only one SoundRecording, the ISRC of the SoundRecording may be used instead. If the Release is an abstraction of a complete PhysicalProduct (such as a CD Album), the ICPN of the PhysicalProduct may be used instead. A Composite containing details of the status of the Release. A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about. A Composite containing details of the Type of action that is proposed by the MessageSender. A Flag indicating whether the sender just needs to resend the same material again (=false) or whether someone needs to look at the material before the re-delivery is done (=true). A Composite containing details of ResourceIds for the Resources that are affected. A Composite containing details of an acknowledgement. A Composite containing details of ResourceIds. The ISRC (International Standard Recording Code as defined in ISO 3901) for the Resource. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits. DDEX will enforce the syntax [a-zA-Z]{2}[a-zA-Z0-9]{3}[0-9]{7} using XML Schema in the future. The ISMN (International Standard Music Number defined in ISO 10957) for the Resource. An ISMN is a thirteen-digit number. Pre-2008 ISMNs, which had 10 characters and are now deprecated, are converted by replacing the initial letter ('M') with '979-0'. DDEX will enforce the syntax 979[0-9]{9}[X0-9] using XML Schema in the future. The ISAN (International Standard Audiovisual Number as defined in ISO 15706) for the Resource. An ISAN comprises four blocks of four hexadecimal charaters followed by a check character. DDEX will enforce the syntax [A-F0-9]{12} using XML Schema in the future. The V-ISAN (Version Identifier of a International Standard Audiovisual Number as defined in ISO 15706-2) for the Resource. A V-ISAN comprises four blocks of four hexadecimal charaters followed by a check character, followed by two further blocks of four hexadecimal characters, followed by a further check character. DDEX will enforce the syntax [A-F0-9]{24} using XML Schema in the future. The ISBN (International Standard Book Number defined in ISO 2108) for the Resource. An ISBN is a 13-digit number. Pre-2007, ISBNs, which had 10-digits and are now deprecated, are converted by adding the prefix '978' and re-calculating the check character. DDEX will enforce the syntax 97[8-9][0-9]{9}[X0-9] using XML Schema in the future. The ISSN (International Standard Serial Number defined in ISO 3297) for the Resource. An ISSN comprises two groups of four digits, separated by a hyphen and a control digit. DDEX will enforce the syntax [0-9]{4}-[0-9]{3}[X0-9] using XML Schema in the future. The SICI (Serial Item and Contribution Identifier defined in ANSI/NISO Z39.56-199) for the Resource. DDEX will enforce the syntax [0-9]{4}-[0-9]{3}[X0-9].+ using XML Schema in the future. A Composite containing details of the CatalogNumber of the Resource. A Composite containing details of a ProprietaryIdentifier of the Resource. A Composite containing details of a Message Status. The Namespace of the Message Status. This is represented in an XML schema as an XML Attribute. A UserDefined value of the Message Status. This is represented in an XML schema as an XML Attribute.