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 section of the DDEX Knowledge Base contains Version 1.4 of the "ERN Choreography Standard"

  1 Introduction

DDEX has standardised a series of Message Suite Standards that define the syntax and semantics of business metadata exchanged by members of the digital media delivery chain. DDEX has also standardised a two automated message exchange protocols that enable the reliable communication of DDEX messages and associated documents such as resource files, using FTP or Web Services.

This standard utilises these two aspects – message format and message exchange – for providing a uniform mechanism for Release Creators to provide Release Distributors with Releases (metadata and Resource files) as well as Deals for making such Releases available.

This standard also defines an interactive choreography that helps Release Creators to be kept informed about the Releases that have been made available through a specific Release Distributor, and Release Distributors to be kept informed about the Releases that will be made available by a specific Release Creator.

Any organisation wishing to implement this (or any other DDEX Standard) is required to apply for an Implementation Licence. The terms of the licence and an application form can be found at http://www.ddex.net/implementation/form.html

2 Scope

 2.1 Introduction
This standard provides a standardised means for Release Creators to make Releases available via Release Distributors. It defines four Profiles, one using FTP/SFTP and three using Web Services as its underlying message exchange mechanism.

In addition to the simple transfer of Release information, Release deals, and Resource files, this standard defines a series of messages that can be exchanged to increase the visibility of the queue of Releases that have been (or are about to be) released. As such this standard defines:

  • A choreography for communicating new Releases and new Deals from a Release Creator to a Release Distributor via an FTP server;
  • A choreography for communicating new Releases and new Deals from a Release Creator to a Release Distributor via an Web Service architecture where a Web Service is hosted by the Release Creator; 
  • A choreography for communicating new Releases and new Deals from a Release Creator to a Release Distributor via an Web Service architecture where a web service is hosted by both, the Release Creator and the Release Distributor.

The Web Service architectures are based on the REST-like architecture[Note] and make use of an FTP/SFTP server for the communication of resource files. This approach was taken to combine the simplicity of REST architectures with the flexibility of sending XML documents as part of Web Service calls.

This specification allows for the secure transmission of information and caters for non-repudiation requirements to be met.

While the location and owner of the FTP/SFTP server is not defined herein (this is left to be agreed by Release Creator and Release Distributor), the structure of the FTP/SFTP severs and names for files are defined by this standard.

At this stage, this standard does not address issues arising from data mismatches detected during the information exchange.


Note: For further information of Representational State Transfer architectures of Web Services, please refer to “Building Web Services the REST Way” by Roger L. Costello (available from, <http://www.xfront.com/REST-Web-Services.html>) or the Wikipedia article at <http://en.wikipedia.org/wiki/Representational_State_Transfer>.

 2.2 Organisation of the Document
This DDEX Standard has eleven clauses and five annexes. Clauses 1 and 2 provide a general introduction and the scope of this Standard. Clauses 3, 4 and 5 give a set of normative references as well as terms, definitions and abbreviations that are used in this Standard. Clause 6 then explains the general approach taken by DDEX to message standardisation.

Clause 7 introduces several Profiles defined in this standard: exchanging Releases using FTP, asymmetric Web Services and symmetric Web Services. These Profiles are then defined in Clauses 8, 9 and 10. Finally, Clauses 11 and 12 provides a way to handle hard disk deliveries and defines the messages required for this standard.

Annex A provides a list of all allowed-value sets, including their allowed values and respective definitions as used in this Standard. Annex B provides an informative mapping between OrderTypes and MessageActionTypes as used in different profiles of this standard. The last annex to be part of this document, Annex C, provides release notes, indicating the features new to this version of the ERN Message Suite Standard.

3 Normative References

 3 Normative References
The following normative documents contain provisions, which through reference in this text constitute provisions of this Standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest version applies.
  • DDEX Data Dictionary Standard. Latest Version
  • DDEX Party Identifier (DPID) Standard. Latest Version
  • DDEX Digital Signature Standard. Latest Version
  • DDEX Automated Message Exchange Protocol
  • DDEX Electronic Release Notification Message Suet Standard; Main Profile. Latest Version.
  • W3C: XML Schema Part 1: Structures. Second Edition. 2004
  • W3C: XML Schema Part 2: Data types. Second Edition. 2004

4 Terms and Definitions

 4 Terms and Definitions

Batch

A grouping of one or more DDEX Messages to be processed by the recipient together.

Contractually Mandatory

An entity in a DDEX Message that has the technical cardinality of 0-1 or 0-n but that is mandatory when a DDEX message is sent in a specific commercial context.

Contractually Mandatory fields may, however, be mandatory when a DDEX message is sent in a specific commercial context. In such circumstances, a message is deemed conformant only if and when it contains all the “contractually mandatory” fields as agreed by Message Sender and Message Recipient.

Message Choreography

A series of message calls and their responses which together communicate a more comprehensive level of meaning between the two business partners.

Non-repudiation

The concept of ensuring that a party cannot repudiate, or refute, the sending or receiving of a message.

Release

A Release is an abstract entity representing a bundle of one or more Resources compiled by an Issuer. The Resources in Releases are normally primarily sound recordings or music audio-visual recordings, but this is not invariably the case. The Release is not itself the item of trade (or “Product”). Products have more extensive attributes than Releases; one Release may be disseminated in many different Products.

REST

REST is an architecture style of networked systems. REST is an acronym for Representational State Transfer.

Release Creator

Release Creator is an organisation which is the owner of copyrights in sound and/or music audiovisual recordings and/or exclusive licensees of copyrights in sound and/or music audiovisual recordings.

Release Family

A set of Releases that are closely related. A typical example of a Release Family is an album communicated as a Main Release plus all the Track Releases whose Resources together form the Album.

Release Distributor

Release Distributor is an organisation, which is duly authorised by a Release Creator to offer Releases manifested in the form of Products to consumers. Release Distributors include Digital Service Providers (DSPs) and Mobile Service Providers (MSPs) as well as other organisations.

Resource

A digital fixation of an expression of an abstract Work (such as a sound recording, a video, an image, software or a passage of text). Resources are individual assets that make up a Release. Typical Resources are sound recordings, video clips and cover art images.

Ticket ID

A unique identifier that links several Web Service Calls/Responses together.

Web Service Call

The sending of an XML document to a port/address on a web server, using HTTP or HTTPS.

Web Service Response

The sending of an XML document in direct response to a Web Service Call, using HTTP or HTTPS.

For the avoidance of doubt: the appropriate response is always the message indicated in the appropriate Choreography.

 

5 Abbreviations

 5 Abbreviations
AMEPAutomated Message Exchange Protocol
ACAAppointed Certification Agency
AVSAllowed Value Set
BPBusiness Profile
CISAC

Confédération internationale des sociétés d'auteurs et compositeurs, the International Confederation of Societies of Authors and Composers (see cisac.org)

CACertification Agency
CTConformance Tester
DAWDigital Audio Workstation
DDEX

Digital Data Exchange

DSIGDigital Signature
DSPDigital Service Provider (incudes Mobile Service Providers)
DSRDigital Sales Reporting
ERNElectronic Release Notification
FTPFile Transfer Protocol (FTP specifically includes SFTP)
GRidGlobal Release Identifier
HTTPHypertext Transport Protocol  (HTTP specifically includes HTTPS)
HTTPSSecure Hypertext Transport Protocol
IECInternational Electrotechnical Commission (see iec.ch)
ISOInternational Organisation for Standardisation (see iso.org)
MIMEMultipurpose Internet Mail Extensions
MLCMusic Licensing Company
MWLMusical Works Licensing
MWNMusical Works Notification
MRBV

Multi-Record-Block Variant

PCAPrivate Certification Agency
PDFPortable Document Format
RESTREpresentational State Transfer
RINRecording Information Notification
SFTPSecure FTP
SRBV

Single-Record-Block Variant

TISTerritory Information System (a CISAC Standard)
TLSTransport Layer Security
UGCUser-generated content
URLUniform Resource Locator
XMLeXtensible Markup Language
XSDXML Schema Definition
W3CWorld Wide Web Consortium (see w3c.org)
WSWeb Service

6 Message Design Approach (informative)

 6 Message Design Approach (informative)
All messages developed within DDEX are based upon a common set of elements and their definitions. These are contained in the DDEX Data Dictionary. The full namespace for the XML Schema document for this Standard is
http://ddex.net/xml/echo/14

All messages defined in this standard make intensive use of allowed-value sets. These allowed value sets are shared between all DDEX standards and DDEX provides a XML Schema Definition file for all of these allowed values. These values are also contained in the DDEX Data Dictionary available from http://ddex.net .


The full namespace for the XML Schema document for the allowed-value sets is

http://ddex.net/xml/avs/avs

DDEX may regularly extend this list of allowed-value sets. Any such extensions to this list are issued on a date later than the date on which this Standard is issued form part of this Standard. Thus the list of allowed-value sets provided Annex A contains the list of allowed-value sets valid on the data of issuance of this Standard.

W3C’s XML Schema Standard has been used to define the structure of the messages and some of the business rules. However, XML Schema alone cannot easily provide a means for complex and conditional validation but XML tools such as eXtensible Stylesheet Language Transformation (XSLT) and XPath could provide a means of developing standard validation modules for each message set.

7 Profiles of the ERN Choreography Standard

 7 Profiles of the ERN Choreography (informative)
This standard defines several different Profiles for exchanging new Release information, Deals regarding Releases and “visibility” information as follows:
  • An entry-level approach in which all information, organised in Batches, is exchanged via a structured FTP server. In one Profile of this approach, a ManifestMessage is used to announce the availability of a Batch for download and an FtpAcknowledgementMessage is used by the recipient to announce the completion of the download/access. In the second entry-level profile, Releases are delivered not in Batches but one by one using FTP.
  • An “advanced” approach in which the XML messages are exchanged via a series of Web Service calls while binaries, if needed, are exchanged via a FTP server, albeit without a ManifestMessage and FtpAcknowledgementMessage. Their roles are fulfilled by appropriate Web Service Call and Web Service Response messages.

    The advanced approach is provided into two Profiles: One in which both parties, Release Creator and Release Distributor are offering Web Services to each other (Symmetric Web Service Profile) and one in which only the Release Creator is offering a Web Service to the Release Distributor  (Asymmetric Web Service Profile). These profiles are then provided in two levels that offer different degrees of supply chain visibility. DDEX may, in the future add a third web service profile in which only the Release Distributor is offering a Web Service to the Release Creator.

The different Profiles are defined in Clauses 8, 9 and 10 respectively.

8 FTP and SFTP Profiles

8.1 Introduction

 8.1 Introduction
This clause defines the method how a Release Creator can provide metadata and Resource files to a Release Distributor via (i) an FTP/SFTP server that is hosted by the Release Creator, (ii) an FTP/SFTP server that is hosted by the Release Distributor, (iii) an FTP/SFTP server that is hosted by a third party or (iv) a hard disk that is populated by/on behalf of the Release Creator and then shipped to the Release Distributor.

This specification does not define on whose hardware the files are being stored; this is for Release Creator and Release Distributor to agree.

Metadata delivery via FTP/SFTP can occur in two Profiles: Release-by-Release and in Batches. These two modes are  defined below.

Security and non-repudiation issues are addressed as specified by the  Automated Message Exchange Protocol Standard.

8.2 FTP and SFTP Release-by-Release Profile

 8.2.1 Choreography
The choreography of the FTP/SFTP Release-by-Release Profile is as depicted in Figure 1.

 

The NewReleaseMessage is defined in the latest version of the Electronic Release Notification Message Suite Standard. The structure of the NewReleaseMessage shall follow the Release and Business Profiles agreed as appropriate for the communicated Release(s).

The FtpAcknowledgementMessage is defined in this standard:

The structure and file naming conventions for the FTP Release-by-Release Profile are defined in Clauses 8.2.2 and 8.2.3 of this standard.

This standard does not define when the Release Creator shall start or finish to upload the next NewReleaseMessage (incl. all Resource files). Equally, this standard does not define when the Release Distributor shall start or finish its download.

In addition to the exchanged shown in the diagram above, the recipient of the NewReleaseMessage may use the same message for subsequent status updates (e.g. when, after reporting FileOK after ingestion, closer inspection shows deficiencies not detected previously.

The recipient of the FtpAcknowledgementMessage may remove a FtpAcknowledgementMessage from the FTP server after an appropriate and mutually agreed period of time. The default period is one month.

 8.2.2 FTP and SFTP Server Organisation
Each Release shall be placed into a separate folder of its own. The folder shall be named with the ReleaseId of the Release communicated followed by an underscore character and the date/time of creation in the form YYYYMMDDhhmmssnnn to indicate a sequence with YYYY indicating the year in which the Release is placed on the ftp server while MM and DD indicate the month and day, hhmmss indicate the hour (in 24 hours), minutes and seconds. Finally nnn indicate the millisecond in which the Release is placed on the ftp server.

The NewReleaseMessage shall be placed into the same folder. Resource files shall be placed into a subfolder called “resources/”.

If possible, the ReleaseId used should be a GRid as defined in the GRid standard. However, if that is not possible, the Release Creator and Release Distributor shall mutually agree a different unique identifier.

The FtpAcknowledgementMessage shall be placed into a folder called acknowledgements/.

 8.2.3 File Naming Conventions
The NewReleaseMessage shall be named as follows
ReleaseId.Ext

Each Resource file shall be named as follows:

ReleaseId_TechnicalResourceId_ResourceType_Hierarchy.Ext

The FtpAcknowledgement shall be named as follows

ACK_YYYYMMDDhhmmssnnn_ReleaseId.Ext

With:

  • ReleaseId being the identifier used in the NewReleaseMessage to uniquely identify the Release.
  • TechnicalResourceId being an optional string, starting with the letter “T”, that is used in the NewReleaseMesage’s relevant XML tag of the same name to uniquely identify the Resource.
  • ResourceType being an optional element to indicate the type of resource (typically where this is not clear from the Ext element).
  • Hierarchy being an optional element to indicate where, in the hierarchy of the Release the Resource fits. This element should comprise of a sequence of three-digit, zero padded numbers separated by underscores (e.g. 008_015 for the 15th Resource in the 8th Resource Group). This Hierarchy element should correspond to the ResourceGroup composite in the NewReleaseMessage.
  • YYYYMMDDhhmmssnnn being the date and time that the Release is placed on the ftp server.
  • Ext being the typical file extension for the Resource type (or .xml for the NewReleaseMessage or FtpAcknowledgement Message).

Note: The Resource file name in accordance with this clause is only guaranteed to be unique and useful for the duration of the Release delivery (i.e until an acknowledgement has been sent).

This naming convention is not necessary for machine-to-machine communication but adherence to this convention will aid human intervention for cases where such intervention is necessary.

 8.2.4 Example of FTP and SFTP Server Organisation and File Naming Convention (Informative)
The example below shows two delivered Releases (both with two Resource files). The first Release has already been acknowledged by the Release Distributor, the second has not. The example does not use the Resource Type component of the file name.

A10301A0001887532A_20100517154800000/

 A10301A0001887532A.xml

 

resources/

  

A10301A0001887532A_T1.mp3

 

 

A10301A0001887532A_T2.jpg

A10301A00017EG98F_20100517155422000/

 A10301A00017EG98F.xml

 

resources/

  A10301A00017EG98F_T1_001.mp4

 

 

A10301A00017EG98F_T2_2.jpg

acknowledgements/

 ACK_20100517154800000_A10301A0001887532A.xml

8.3 FTP and SFTP Batch Profile

 8.3.1 Choreography
The choreography of the FTP Batch Profile is as depicted below:

The trigger to indicate that a Batch is complete is a ManifestMessage as defined in Clause 12.3 of this standard. In exceptional circumstances, such as for support human intervention, it is permissible to use a zero-byte semaphore file to indicate the upload is complete. This semaphore has to be used instead of an XML manifest formatted in accordance with Clause 12.3. The use of such a semaphore file may trigger a flag on the recipient’s side, indicating the manual nature of the override. The message is also depicted below.

The structure of the NewReleaseMessages communicated in this profile shall follow the Release and Business Profiles agreed as appropriate for the communicated Release(s).

The FtpAcknowledgementMessage is defined in this standard; is also depicted in Clause 8.2.1.

The structure and file naming conventions for the FTP Release-by-Release Profile are defined in Clauses 8.3.3 and 8.3.4 of this standard.

This standard does not define when the Release Creator shall start or finish to upload the next NewReleaseMessage (incl. all Resource files). Equally, this standard does not define when the Release Distributor shall start or finish its download.

In addition to the exchanged shown in the diagram above, the recipient of the NewReleaseMessage may use the same message for subsequent status updates (e.g. when, after reporting FileOK after ingestion, closer inspection shows deficiencies not detected previously.

The recipient of the FtpAcknowledgementMessage may remove a FtpAcknowledgementMessage from the FTP server after an appropriate and mutually agreed period of time. The default period is one month.

 8.3.2 Batch Constraints
The maximum size of a Batch is not defined in this standard but shall be agreed by Release Creator and Release Distributor before using this Profile. It is not permitted to include the same Release more than once in a single Batch.

If the Release Creator wants to have several Batches “open” at the same time, it needs to ensure that no Release is contained in more than one Batch.

The maximum time a Batch may be kept “open” is a matter for Release Creator and Release Distributor to define in their commercial agreement.

To ensure sequential processing, a Batch is identified by the date and time of its creation in the form YYYYMMDDhhmmssnnn with

  • YYYY being the year of Batch creation;
  • †MM being the month of Batch creation;
  • †DD being the day of Batch creation;
  • †hh being the hour of Batch creation;
  • †mm being the minute of Batch creation;
  • †ss being the second of Batch creation; and
  • †nnn being the millisecond of Batch creation.

The Release Creator shall make sure that for each of its Release Distributors the BatchId is unique.

 8.3.3 FTP and SFTP Server Organisation
Each Batch shall be placed into a separate folder of its own. The folder shall be named with the BatchId. Each Release within that Batch shall be placed into a separate folder using the ReleaseId of the Release as its name. A NewReleaseMessage for each Release shall be placed into that folder; Resource files shall be placed into a subfolder called “resources/”.

The ManifestMessage, shall be placed into the root folder of the Batch.

If possible, the ReleaseId used should be a GRid as defined in the GRid standard. However, if that is not possible, the Release Creator and Release Distributor shall mutually agree a different unique identifier.

The FtpAcknowledgementMessages shall be placed into a folder called acknowledgements/.

 8.3.4 File Naming Convention
The file name of the ManifestMessage for each Batch shall be the string BatchComplete_ followed by the BatchId (as defined above) and the .xml file extension. The same file name applied to the zero-byte semaphore discussed in Clause 8.3.1.

The file name of the FtpAcknowledgementMessage for each Batch shall be the string ACK_  the date and time that the Batch is placed on the ftp server, followed by an underscore and the BatchId. The file shall have an .xml file extension.

The NewReleaseMessages shall be named using the same ReleaseId as used for the enclosing folder with an .xml file extension.

To aid human intervention, each Resource file should be named as described in Clause 8.2.2.

 8.3.5 Example of FTP and SFTP Server Organisation and File Naming Convention (informative)
The example below shows one delivered Batch with two Releases (both with two Resource files). The Batch is not yet acknowledged.

 

20100310130322000/

 A10301A0001887532A/
  A10301A0001887532A.xml

 

 

resources/

   A10301A0001887532A_T1_001.mp3

 

 

 

A10301A0001887532A_T2_001.jpg

 

A10301A00017EG98F/


 

  A10301A00017EG98F.xml

 

 

resources/

   

A10301A00017EG98F_T1_001.mp4

 

 

 

A10301A00017EG98F_T2_002.mp3

 

BatchComplete_20100310130322000.xml

acknowledgements/
 <empty>

 8.3.6 Order of Processing
The Release Distributor is expected to process Batches in sequence as indicated by the date of the batch name.

9 Asymmetric Web Services Profile

 9.1 Introduction
This standard provides three Web Service Profiles. Two, defined in this clause, where only one of the two parties offer a Web Service. The third Profile defines, in Clause 10, the case where both parties offer a Web Service.

While the symmetric Profile is more efficient as it requires less traffic, the asymmetric Profiles offer the benefit that only one Party needs to publish and maintain a Web Service. Offering a Web Service requires a non-significant amount of resources and experience that may not be available to all users of this standard.

All Web Service calls in the asymmetric Web Service Profiles use a REST-like architecture as required in DDEX-AMEP. Each Message Choreography within this standard is defined in this Clause in three forms: a graphical representation of the choreography, a textual description of the triggers and messages that are exchanged and, for each Web Service Call and Response, the respective message content. For each Web Service Call, the URL from which the Web Service shall be made available by a user of this standard is also defined.

The two asymmetric Web Service are defined as follows:

  • Clause 9.2 defines the Profile where only the Release Creator offers a Web Service; and
  • Clause 9.4 defines the Profile where only the Release Distributor offers a Web Service.

Note: Clause 9.4 will be provided in a subsequent version of this standard.

Security and non-repudiation issues are addressed as specified by the DDEX Automated Message Exchange Protocol Standard.

 

 

 9.2 Error Handling
For each Web Service Call, this standard defines a specific reply. However, the recipient of the Web Service Call may reply with a WsAcknowledgementMessage (as defined in DDEX-AMEP) in case the Web Service Call was erroneous or misplaced.

 9.3 Release Creator Offering Web Service

9.3.1 Introduction (informative)

In this Profile only the Release Creator offers a Web Service. All communication between Release Creator and Release Distributor is initiated by the Release Distributor calling the Web Service of the Release Creator who answers the Web Service Call with a Response message.

Note: in this Profile, it is impossible for the Release Creator to proactively deliver content to the Release Distributor.

The overall sequence of communications within this Profile are depicted in Figure 4. It is not mandatory for two parties to implement all of the individual communications, each wrapped into a dashed box, that form part of the Asymmetric Web Service Profile of the ERN Choreography Standard. The number within each dashed box links to the sub clause in this standard that defines that particular communication.

 

Figure 4: Asymmetric Web Service Profile – Release Creator (Overview)

Note that a Release Distributor can ask for either “the next Release” – and leave the choice to the Release Creator as to which Release to send; or the Release Distributor can ask for a specific Release.

9.3.2 Insert/Update a Set of Releases into the Supply Chain

Once a Release Distributor is ready to receive the next Release for ingestion, the Release Distributor calls the Release Creator’s Web Service who will respond with a ReleaseAvailabilityResponseMessage as follows:

  • If no new Release is available, that fact is communicated;
  • †If new Releases are available (i.e. a new Release, or an update of metadata or Resource files to an already notified Release), the NewReleaseMessage element of the ReleaseAvailabilityResponseMessage shall be communicated. That element shall only contain Releases from one Release Family.        

No such message shall be sent unless all Resources have been made available on an FTP site accessible to the Release Creator.

Upon receiving that message the Release Distributor ingests the contained Releases accordingly and provides, at suitable points in time – typically agreed beforehand between Release Creator and Release Distributor – SupplyChainStatusMessages for each Release communicated.

 

Figure 5: Asymmetric Choreography: Insert/Update

Table 1: ReleaseAvailabilityRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (ReleaseAvailabilityRequestMessage in accordance with Clause 12.14)

Return Body

XML (ReleaseAvailabilityResponseMessage in accordance with Clause 12.15)

 

Table 2: SupplyChainStatusCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (SupplyChainStatusMessage in accordance with Clause 12.23)

Return Body

XML (WsAcknowledgementMessage in accordance with DDEX-AMEP)

 

The messages used in the three defined web service calls are defined in Clause 12 or in the case of the WsAcknowledgementMessage, in DDEX-AMEP. All messages are also depicted below.

The structure of the NewReleaseMessage shall follow the Release and Business Profiles agreed as appropriate for the communicated Release(s).

Figure 6: ReleaseAvailabilityRequestMessage

Figure 7: ReleaseAvailabilityResponseMessage

Figure 8: SupplyChainStatusMessage

Figure 9: WsAcknowledgementMessage


9.3.3 Requested Re-delivery of a Release

If a Release Distributor requires a re-delivery of a single Release already delivered, the ReleaseCreator can request, by giving the ReleaseId and a reason code, which Release it needs re-delivered and whether a partial redelivery would suffice.

The Release Creator provides a status code back and, if a redelivery is to occur, the process is continued as defined in Clause 9.3.2.

Figure 10: Asymmetric Choreography: Redelivery

Table 3: RedeliveryRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (RedeliveryRequestMessage in accordance with Clause 12.11)

Return Body

XML (RedeliveryResponseMessage in accordance with Clause 12.12)

The messages used in the defined web service call are defined in Clause 11. They are also depicted below.

Figure 11: RedeliveryRequestMessage


Figure 12: RedeliveryResponseMessage

9.3.4 Takedown of a Release

The process of delivering a takedown notice is the same as the delivery/update of a new Release as defined in Clause 9.3.2.

Each NewReleaseMessage may provide a takedown notice for one Release only.

9.3.5 Control of the Frequency of Delivery

In order to control the flow of new Releases and updates a Release Distributor can send a DeliveryFrequencyChangeRequestMessage. This is acknowledged by the Release Creator and the new delivery frequency is in effect until the end of the requested AffectedPeriod (if given and unless either a new DeliveryFrequencyChangeRequestMessage is sent or the parties agree new delivery frequency out of bands).

Figure 13: Asymmetric Choreography: Control

Table 4: DeliveryFrequencyChangeRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (DeliveryFrequencyChangeRequestMessage in accordance with Clause 12.5)

Return Body

XML (DeliveryFrequencyChangeResponseMessage in accordance with Clause 12.6)

 

The messages used in the defined web service call are defined in Clause 12. They are also depicted below.

Figure 14: DeliveryFrequencyRequestMessage

Figure 15: DeliveryFrequencyResponseMessage

9.3.5 Request for Information About Releases Currently available

If a Release Distributor wants to see a selected list of the Releases that the Release Creator is planning to or considering to send to the Release Distributor, the Release Distributor can request a list of such Releases.

The search criteria include:

  • Release ID;
  • Release artist;
  • †Releasing Label Name;
  • †Territory of availability; and
  • †RightsAgreementId (for Releases that are available under a special Deal between Release Creator and Release Distributor).

The response will contain a TicketId alongside an estimate of the time when such a list, formatted in accordance with Clause 12.25, would be ready.

To receive the list, the Release Distributor can send a ReportRequestMessage with the TicketId which is either answered by the list requested earlier or by a code that states that the list is not yet ready.


 

Table 5: OrderedReleaseInQueueRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (OrderedReleaseInQueueRequestMessage in accordance with Clause 12.9)

Return Body

XML (OrderedReleaseInQueueResponseMessage in accordance with Clause 12.10)

Table 6: ReportRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (ReportRequestMessage in accordance with Clause 12.20)

Return Body

XML (ReportResponseMessage in accordance with Clause 12.21)

The messages used in the defined web service call are defined in Clause 12. They are also depicted below.

Figure 17: OrderedReleaseInQueueRequestMessage

 

Figure 18: OrderedReleaseInQueueResponseMessage

 

 9.4 Release Distributor offering Web Service
The definition of this Profile will be added in a later version of this standard.

10 Symmetric Web Services Profile

 10.1 Introduction
As described above, this standard provides three Web Service Profiles. Two, defined in Clause 9, where only one of the two parties communicating information about making Releases available to consumers offers a Web Service. The third Profile defines, in this clause, the case where both parties offer a Web Service.


Figure 19: Symmetric Web Service Profile (Overview)

All Web Service calls in the Symmetric Web Service Profiles use a REST-like architecture as specified in DDEX-AMEP. Each choreography within this standard is defined in this Clause in three forms: a graphical representation of the choreography, a textual description of the triggers and messages that are exchanged and, for each Web Service call and response, the respective message content is defined. For each Web Service call the URL from which the Web Service shall be made available by a user of this standard is also defined.

Security and non-repudiation issues are addressed as specified by DDEX-AMEP.

The overall sequence of communication within this Profile is depicted in Figure 19. It is not mandatory for two parties to implement all of the individual communications, each wrapped into a dashed box, that form part of the Symmetric Web Service Profile of the ERN Choreography Standard. The number within each dashed box links to the sub clause in this standard that defines this communication.

All Web Service calls in this Profile use a REST-like architecture as specified in DDEX-AMEP.

 10.2 Error Handling
For each Web Service Call, this standard defines a specific reply. However, the recipient of the Web Service Call may reply with a WsAcknowledgementMessage (as defined in DDEX-AMEP) in case the Web Service Call was erroneous or misplaced.

 10.3 Insert, Update a Set of Releases into the Supply Chain
Once a Release Creator is ready to send the next Release to the Release Distributor, it calls the Release Distributor’s ReleaseAvailabilityMessage Web Service who will respond with an WsAcknowlegementMessage.

The NewReleaseMessage element of the ReleaseAvailabilityMessage shall only contain Releases from one Release Family and no such message shall be sent unless all Resources have been made available on an FTP/SFTP site accessible by the Release Creator.

Upon receiving the ReleaseAvailabilityMessage, the Release Distributor ingests the sent Releases accordingly and provides, at suitable points in time – typically agreed beforehand between Release Creator and Distributor – SupplyChainStatusMessages for each Release communicated.

Figure 20: Symmetric Choreography: Insert/Update

 

Table 7: ReleaseAvailabilityCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (ReleaseAvailabilityMessage in accordance with Clause 12.13)

Return Body

XML (WsAcknowledgementMessage in accordance with DDEX-AMEP)

The provision of the SupplyChainStatusMessage is defined in Table 2. The two messages are depicted below and in Figure 9.

The structure of the NewReleaseMessage shall follow the Release and Business Profiles agreed as appropriate for the communicated Release(s).

Figure 21: ReleaseAvailabilityMessage

 

 10.4 Requested Re-Delivery of a Release
If a Release Distributor requires a re-delivery of a single Release already delivered, the ReleaseCreator can request, by giving the ReleaseId and a reason code, which Release it needs re-delivered and whether a partial redelivery would suffice.

This choreography is the same as defined in Clause 9.3.3.

 10.5 Take-down of a Release
The process of delivering a take-down notice is the same as the delivery/update of a new Release as defined in Clause 10.2.

Each NewReleaseMessage may provide a take-down for one Release only.

 10.6 Control the Frequency of Delivery
This process of adjusting the frequency of deliveries is the same as defined in Clause 9.3.5.

 10.7 Request for Information about Available Releases
If a Release Distributor wants to see the Releases that the Release Creator is planning to or considering to send to the Release Distributor, the Release Distributor can request a list of such Releases. Request criteria include:
  • † Release ID;
  • † Release artist;
  • † Releasing Label Name;
  • † Territory of availability; and
  • † RightsAgreementId (for Releases that are available under a special Deal between Release Creator and Release Distributor).

The response will contain a TicketId alongside an estimate of the time when such a list would be ready.

Once the report, formatted in accordance with Clause 12.25, is ready, the Release Creator shall send the message in a ReportDeliveryMessage which is acknowledged by the Release Distributor.

 

Figure 22: Symmetric Choreography: Query Available Releases

Table 8: ReportDeliveryCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (ReportDeliveryMessage in accordance with Clause 12.20)

Return Body

XML (WsAcknowledgementMessage in accordance with DDEX-AMEP)

The two messages are depicted below and in Figure 9. The OrderedReleaseInQueueRequestCall is defined in Table 5.

Figure 23: ReportDeliveryMessage

 

 

Figure 24: ReleasesInQueueReportMessage (Part 1)


Figure 25: ReleasesInQueueReportMessage (Part 2)


 10.8 Request for Information About Release Distributor Status
If the Release Creator requires information about the general status of the Release Distributor’s supply chain, the Release Creator sends a ReleaseSupplyChainStatusRequestMessage which is answered by a status code in the ReleaseSupplyChainStatusResponseMessage.

Figure 26: Symmetric Choreography: Release Distributor Status (Request)

Table 9: ReleaseSupplyChainRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (ReleaseSupplyChainStatusRequestMessage in accordance with Clause 12.18)

Return Body

XML (ReleaseSupplyChainStatusResponseMessage in accordance with Clause 12.19)

The two messages are depicted below.


Figure 27: ReleaseSupplyChainRequestMessage


Figure 28: ReleaseSupplyChainResponseMessage

 10.9 Information About Release Distributor Status
A Release Distributor may which to proactively inform the Release Creator about the status of one of the Releases it is working on. The choreography is shown below and is the same as the second half of the choreography defined in Clause 9.3.2.

Figure 29: Symmetric Choreography: Release Distributor Status (Proactive)

 10.10 Request for Information About A Release Distributor’s Data about a Release
Unable to render {include} The included page could not be found.

 10.11 Request for Information about Releases delivered and currently available (Release Distributor to Release Creator)
In some circumstances a Release Creator may which to receive a list of all the Releases that a Release Distributor is currently offering to consumers. This list is to be formatted in accordance with Clause 12.25.

The choreography is shown below.


Figure 33: Symmetric Choreography: Releases Currently Available

Table 12: InformationAboutDeliveredAndAvailableReleasesRequestCall

URL

http://baseurl.com/ddex/echo/12/

Method

POST

Request Body

XML (InformationAboutDeliveredAndAvailableReleasesRequestMessage in accordance with Clause 12.7)

Return Body

XML (InformationAboutDeliveredAndAvailableReleasesResponseMessage in accordance with Clause 12.8)

The four messages are depicted below and in Figure 9. The ReportDeliveryCall is defined in Table 8. The report delivered is formatted in accordance with Clause 12.26.


Figure 34: InformationAboutDeliveredAndAvailableReleasesRequestMessage


Figure 35: InformationAboutDeliveredAndAvailableReleasesResponseMessage


Figure 36: InformationAboutDeliveredAndAvailableReleasesReportMessage (Part 1)


Figure 37: InformationAboutDeliveredAndAvailableReleasesReportMessage (Part 2)

 10.12 Request for Information about Releases delivered and currently available (Release Creator to Release Distributor)
The above choreography may also be used by a Release Creator to query a Release Distributor about the Releases it currently offers to its customers.

11 Hard Disk Delivery

 11.1 Introduction
In order to support the delivery of large numbers of Releases, Release Creators sometimes deliver entire catalogues stored on a hard disk via courier.

The precise way in which such a hard disk delivery is integrated into the technical infrastructure between sender and recipient depends on the agreed profile for the on-going communication between the two parties.

 11.2 Hard disk deliveries as part of a Release-by-Release FTP or SFTP Profile
The hard disk shall be organised as defined in Clause 8.2 with the exception that no acknowledgements can be communicated via the hard disk.

Acknowledgements are to be communicated via the FTP/SFTP sever agreed between sender and recipient. The sender of the acknowledgement needs to create the same hierarchy for the acknowledged Release in the FTP/SFTP server as was found on the hard disk.

 11.3 Hard disk deliveries as part of a Batched FTP or SFTP Profile
The hard disk shall be organised as defined in Clause 8.3 with the exception that no acknowledgements can be communicated via the hard disk.

Acknowledgements are to be communicated via the FTP/SFTP sever agreed between sender and recipient. The sender of the acknowledgement needs to create the same hierarchy for the acknowledged Batch in the FTP/SFTP server as was found on the hard disk.

 11.4 Hard disk deliveries as part of a Web Service Profiles
Note, this sub-clause applies to symmetric and asymmetric web service profiles.

The hard disk shall be organised as defined in Clause 8.2 with the exception that no acknowledgements can be communicated via the hard disk.

Acknowledgements are to be communicated via the appropriate web service call without a WsMessageThreadId being communicated.

 11.5 Ingestions of Updates
If the sender of the Releases provide an update to a Release already ingested from the hard disk, the normal process for updated applies.

If the sender of the Releases provide an update to a Release not yet ingested from the hard disk, the recipient shall ingest, pet normal protocol, the update; should that update not provide any resource files, the recipient should look for these on the hard disk.

The sender shall not ingest the Release from the hard disk after having received an update via the normal on-going communication channel.

12 Message Definition

 12.1 Introduction
The hierarchical structure of the messages is provided through indentation in the tables below. In addition to the tabular description of the message, which should always be read in conjunction with Annex A, additional conformance rules, which go beyond XML Schema validation, are provided where necessary. The general conformance rules for all messages within this Standard are provided in Clause 11.2.

Specific business processes between sender and recipient may require even further conformance rules. These are, however, not part of the Standard and will need to be agreed by the business partners. Rules relating to the authority of business partners to unilaterally change the Message

 12.2 General Conformance Rules

12.2.1 Schema Validation

A message is conformant to this specification only when it validates against the set of XML Schema files provided in Annex B.

12.2.2 Allowed Value Lists

The allowed values are listed, defined and provided through the DDEX Data Dictionary Standard in accordance with the latest version of DDEX-DICT. Other values are not possible unless by using the mechanism described below:

This Standard does not explicitly list allowed values. The XML Schema files – as provided in Annex B – contain the allowed values at the time of writing of this Standard. Some of the allowed value sets contain a provision to either use a User Defined Value instead of a DDEX-defined value (in that case the MessageSender has to select the value “UserDefined” from the AVS and provide its own value in the XML attribute “UserDefinedValue”) or to augment a DDEX-defined value (in that case the MessageSender may not select the value “UserDefined” from the AVS but shall provide its additional information in the XML attribute “UserDefinedValue”). In either case the Namespace attribute shall be used to indicate where the UserDefinedValue is defined and maintained.

12.2.3 Contractually Mandatory

The messages defined in this standard contain fields with cardinality “0-1” or “0-n”. Therefore these fields are from the standard’s point of view, optional. Such fields may, however, be mandatory when a DDEX message is sent in a specific commercial context.

In such circumstances, a message is deemed conformant only if and when it contains all the “contractually mandatory” fields as agreed by MessageSender and Message Recipient.

12.2.4 Schema Version Id

For messages defined directly herein the only valid value for this field is

2011/ECHO/12

 

For messages defined in DDEX-AMEP, the relevant value of that standard shall be used.

 12.3 Manifest Message (for the FTP Profiles)

echo:ManifestMessage

A Message in the ECH DdexMessageSuite that is sent to document the FTP transfer of a batch of ERN Messages, potentially accompanied by Resoure or Release files.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:FtpMessageHeader

1

The MessageHeader for the ManifestMessage.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

IsTestFlag

Boolean

1

The Flag indicating whether the Message is a TestMessage (=True) or a LiveMessage (=False).

RootDirectory

String

1

An Identifier of the root directory of all Messages in the batch communicated through the ManifestMessage.

NumberOfMessages

Integer

1

The number of Messages in the batch communicated through the ManifestMessage.

MessageInBatch

ddexC:ErnMessageInBatch

1-n

A Composite containing details of an ERN Message in the batch.

 

MessageType

ErnMessageType

1

The Type of Message.

 

MessageId

String

1

An Identifier of the Message.

 

URL

String

1

A URL of the Message.

 

IncludedReleaseId

ddexC:ReleaseId

1-n

A Composite containing details of ReleaseIds. If available, a GRid should always be used.

 

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

 

ISRC

String

0-1

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.

 

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 

DeliveryType

ddexC:MessageActionType

1

A Composite containing details of the Type of action that the MessageSender applies to the Message.

 

 

Namespace

String

0-1

The Namespace of the MessageActionType. This is represented in an XML schema as an XML Attribute.

 

 

UserDefinedValue

String

0-1

A UserDefined value of the MessageActionType. This is represented in an XML schema as an XML Attribute.

 

ProductType

ddexC:ProductType

1

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.

 

 

Namespace

String

0-1

The Namespace of the ProductType. This is represented in an XML schema as an XML Attribute.

 

 

UserDefinedValue

String

0-1

A UserDefined value of the ProductType. This is represented in an XML schema as an XML Attribute.

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum of the File and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 12.4 FtpAcknowledgementMessage (for the FTP Profiles)
FtpAcknowledgementMessage
A default response Message in the Release Delivery Choreography Standard that is sent to acknowledge the receipt of a manifest File via FTP.
Message ElementData TypeCardElement Description
MessageVersionId String1The Version of the Message.
MessageHeader ern-c:FtpMessageHeader1The MessageHeader for the Message.
 MessageSenderddexC:MessagingParty1A Composite containing details of the MessageSender.
  LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
  PartyId ddexC:PartyId1-nA 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.
   NamespaceString0-1The Namespace of the PartyId if it belongs to a proprietary Party xsID 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.
   IsDPIDBoolean0-1The Flag indicating whether the PartyId is a DPID (=True) or not (=False). This is represented in an XML schema as an XML Attribute.
   IsISNIBoolean0-1The Flag indicating whether the PartyId is an ISNI (=True) or not (=False). This is represented in an XML schema as an XML Attribute.
  PartyNameddexC:PartyName0-1A Composite containing details of the PartyNames for the Party handling the Message.
   LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   FullNameddexC:Name1A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   FullNameAsciiTranscribedString0-1The FullName transcribed using 7-bit ASCII code.
   FullNameIndexedddexC:Name0-1A 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, A Composite containing the).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   NamesBeforeKeyNameddexC:Name0-1A 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).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   KeyNameddexC:Name0-1A 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.
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   NamesAfterKeyNameddexC:Name0-1A 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.
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   AbbreviatedNameddexC:Name0-1A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
  TradingNameddexC:Name0-1A Composite containing a TradingName for the Party handling the Message.
   LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
 MessageRecipientddexC:MessagingParty1A Composite containing details of the MessageRecipient.
  LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
  PartyId ddexC:PartyId1-nA 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.
   NamespaceString0-1The Namespace of the PartyId if it belongs to a proprietary Party xsID 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.
   IsDPIDBoolean0-1The Flag indicating whether the PartyId is a DPID (=True) or not (=False). This is represented in an XML schema as an XML Attribute.
   IsISNIBoolean0-1The Flag indicating whether the PartyId is an ISNI (=True) or not (=False). This is represented in an XML schema as an XML Attribute.
  PartyNameddexC:PartyName0-1A Composite containing details of the PartyNames for the Party handling the Message.
   LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   FullNameddexC:Name1A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   FullNameAsciiTranscribedString0-1The FullName transcribed using 7-bit ASCII code.
   FullNameIndexedddexC:Name0-1A 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, A Composite containing the).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   NamesBeforeKeyNameddexC:Name0-1A 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).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   KeyNameddexC:Name0-1A 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.
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   NamesAfterKeyNameddexC:Name0-1A 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.
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
   AbbreviatedNameddexC:Name0-1A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).
    LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
  TradingNameddexC:Name0-1A Composite containing a TradingName for the Party handling the Message.
   LanguageAndScriptCodeString0-1The 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[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.
 MessageCreatedDateTimeDateTime1The DateTime on which the Message was created (the only allowed format is ISO 86012004: YYYY-MM-DDThhmmssTZD).
AcknowledgedFile ern-c:AcknowledgedFile1A Composite containing details of the Message Files whose receipt is acknowledged.
 ReleaseId String0-1The Identifier of the main Release of the XML file containing the acknowledged NewReleaseMessage. This is the same string that is part of the path for the NewReleaseMessage's XML file.
 Date  String0-1The Date on which the batch or XML file containing the acknowledged NewReleaseMessage was set up. This is the same string that is part of the path for the NewReleaseMessage's XML file.
FileStatus  ern-c:FileStatus1A Composite containing details of the FileStatus.
 Namespace String0-1The Namespace of the FileStatus. This is represented in an XML schema as an XML Attribute.
 UserDefinedValueString0-1A UserDefined value of the FileStatus. This is represented in an XML schema as an XML Attribute.
ErrorText  String0-1A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.
ProposedActionTypeern-c:ProposedActionType0-1A Composite containing details of the Type of action that is proposed.
 Namespace String0-1The Namespace of the ProposedActionType. This is represented in an XML schema as an XML Attribute.
 UserDefinedValueString0-1A UserDefined value of the ProposedActionType. This is represented in an XML schema as an XML Attribute.
ManualCheckRequiredBoolean0-1A 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).
AffectedResource ddexC:ResourceId0-nA Composite containing details of ResourceIds for hte Resources that are affected.
 IsReplaced Boolean0-1The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.
 ISRC  String0-1The 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.
 ISMN  String0-1The 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.
 ISAN  String0-1The 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.
 VISAN  String0-1The 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.
 ISBN  String0-1The 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.
 ISSN  String0-1The 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.
 SICI   String0-1The 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.
 CatalogNumberddexC:CatalogNumber0-1A Composite containing details of the CatalogNumber of the Resource.
  NamespaceString1The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.
 ProprietaryId ddexC:ProprietaryId0-nA Composite containing details of a ProprietaryIdentifier of the Resource.
  NamespaceString1The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 12.5 Delivery Frequency Change Request Message

echo:DeliveryFrequencyChangeRequestMessage

A request Message in the DeliveryFrequencyRequestCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

DeliveryActionType

DeliveryActionType

1

The Type of action requested of the MessageRecipient with respect to the delivery of further NewReleaseMessages.

OrderType

ddexC:OrderType

0-1

A Composite containing details of the Type of an order. A specific OrderType typically infers a priority which, in turn, is defined in the contractual relationship between MessageSender and MessageRecipient. If this Element is not entered on the request, then the other parameters apply to the cumulative MaximumDeliveriesPerDay over all order types (= absolute maximum).

 

Namespace

String

0-1

The Namespace of the OrderType. This is represented in an XML schema as an XML Attribute.

 

UserDefinedValue

String

0-1

A UserDefined value of the OrderType. This is represented in an XML schema as an XML Attribute.

MaximumDeliveriesPerDay

echo:MaximumDeliveriesPerDay

0-1

A Composite containing details of the maximum number of deliveries made per day. This Element applies to the OrderType (if given). One of the subelements has to be given. The MessageRecipient should stop sending web services once this limit is reached. If this Element is not entered on the request, then the recipient of the request can determine the MaximumDeliveriesPerDay.

 

NumberOfMessages

Integer

0-1

The number of NewReleaseMessages.

 

NumberOfBytes

Integer

0-1

The number of Bytes.

AffectedPeriod

ddexC:Period

0-1

A Composite containing details about a Period of Time in which the deliveries happen.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

StartDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The StartDate must be earlier than the EndDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

A

EndDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The EndDate must be later than the StartDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

StartDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The StartDateTime must be earlier than the EndDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

EndDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The EndDateTime must be later than the StartDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

Comment

String

0-1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.6 Delivery Frequency Change Response Message

DeliveryFrequencyChangeResponseMessage

 

 

A response Message in a DeliveryFrequencyRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

IsSuccessful

Boolean

1

A Flag indicating whether a delivery frequency change was successful (=True) or not (=False).

 

 

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.7 Information About Available Release Request Message

echo:InformationAboutDeliveredAndAvailableReleasesRequestMessage

A request Message in a InformationAboutDeliveredAndAvailableReleasesCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

Period

ddexC:Period

0-1

A Composite containing details about a Period of Time in which the Release was originally delivered.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

StartDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The StartDate must be earlier than the EndDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

A

EndDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The EndDate must be later than the StartDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

StartDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The StartDateTime must be earlier than the EndDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

EndDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The EndDateTime must be later than the StartDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 12.8 Information About Available Release Response Message

InformationAboutDeliveredAndAvailableReleasesResponseMessage

 

A response Message in a InformationAboutDeliveredAndAvailableReleasesCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

TicketId

String

1

The Identifier of a ticket to link different web service calls to one another.

 

A

EstimatedDateTimeOfDelivery

ddexC:EventDate

1

A Composite containing details of the Date and Place of the Event in which the delivery is scheduled to happen.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.9 Ordered Release In Queue Request Message

echo:OrderedReleaseInQueueRequestMessage

A request Message in a OrderedReleasesInQueueRequestCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

OrderType

ddexC:OrderType

0-1

A Composite containing details of the Type of an order. A specific OrderType typically infers a priority which, in turn, is defined in the contractual relationship between MessageSender and MessageRecipient.

 

Namespace

String

0-1

The Namespace of the OrderType. This is represented in an XML schema as an XML Attribute.

 

UserDefinedValue

String

0-1

A UserDefined value of the OrderType. This is represented in an XML schema as an XML Attribute.

Release

echo:ReleaseSummary

0-n

A Composite containing details of a requested Release.

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the ReleaseSummary as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

ReleaseId

ddexC:ReleaseId

0-n

A Composite containing details of ReleaseIds. If available, a GRid shall 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. More than one of these identifiers may be provided.

 

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

 

ISRC

String

0-1

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.

 

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 

ReferenceTitle

ddexC:ReferenceTitle

0-1

A Composite containing details of the ReferenceTitle of the Release.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the ReferenceTitle as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TitleText

ddexC:TitleText

1

A Composite containing the text of the ReferenceTitle.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the TitleText as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

SubTitle

ddexC:SubTitle

0-1

A Composite containing details of a SubTitle of the ReferenceTitle, including Titles of Versions used to differentiate different versions of the same Title, as required by the GRId and ISRC ReferenceDescriptiveMetadataSets (where the SubTitle is called Version Title).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the SubTitle as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

ReleaseSummaryDetailsByTerritory

ddexC:ReleaseSummaryDetailsByTerritory

0-n

A Composite containing summary details of Descriptors and other attributes of the Release which may vary according to Territory of Release. Territory of Release may be the world.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the ReleaseSummaryDetailsByTerritory as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

TerritoryCode

ddexC:TerritoryCode

1-n

A Territory to which the ReleaseSummaryDetailsByTerritory apply (represented by an ISO 3166-1 TerritoryCode). Either this Element or ExcludedTerritory shall be present, but not both.

 

 

 

ExcludedTerritoryCode

ddexC:TerritoryCode

1-n

A Territory to which the ReleaseSummaryDetailsByTerritory do not apply (represented by an ISO 3166-1 TerritoryCode). Either this Element or Territory shall be present, but not both.

 

 

DisplayArtistName

ddexC:Name

0-n

A Composite containing the Name to be used by a DSP when presenting Artist details of the Release to a Consumer.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

LabelName

ddexC:LabelName

0-n

A Composite containing the Name of the Label for the Release.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the LabelName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

LabelNameType

String

0-1

A Type of LabelName. This is represented in an XML schema as an XML Attribute.

 

 

RightsAgreementId

ddexC:RightsAgreementId

0-1

A Composite containing details of Identifiers of a License, Claim, RightShare or contract for the MusicalWork(s) used in the Release.

 

 

 

MWLI

String

0-n

A MusicalWork License Identifier identifying a License. If the Composite is meant to describe a Claim, RightShare or contract, then the License relates to that Claim, RightShare or contract. A MWLI comprises four parts: one of the strings "M1" or "M2" or "M3" or "M4", followed by five alphanumeric characters, ten alphanumeric characters and one alphanumeric check character.

 

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the License, Claim, RightShare or contract.

 

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 

RightsAgreementId

ddexC:RightsAgreementId

0-1

A Composite containing details of Identifiers of a License, Claim, RightShare or contract for the MusicalWork(s) used in the Release.

 

 

MWLI

String

0-n

A MusicalWork License Identifier identifying a License. If the Composite is meant to describe a Claim, RightShare or contract, then the License relates to that Claim, RightShare or contract. A MWLI comprises four parts: one of the strings "M1" or "M2" or "M3" or "M4", followed by five alphanumeric characters, ten alphanumeric characters and one alphanumeric check character.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the License, Claim, RightShare or contract.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

TerritoryCode

ddexC:TerritoryCode

1-n

A Territory to which the request applies (represented by an ISO 3166-1 TerritoryCode). Either this Element or ExcludedTerritory shall be present, but not both.

 

ExcludedTerritoryCode

ddexC:TerritoryCode

1-n

A Territory to which the request applies (represented by an ISO 3166-1 TerritoryCode). Either this Element or Territory shall be present, but not both.

Period

ddexC:Period

0-1

A Composite containing details about a Period of Time in which the Releases were ordered.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

StartDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The StartDate must be earlier than the EndDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

EndDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-MM-DD). The EndDate must be later than the StartDate if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

StartDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the beginning of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The StartDateTime must be earlier than the EndDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

EndDateTime

ddexC:EventDateTime

0-1

A Composite containing details of the DateTime and Place of an Event that marks the end of the Period (in ISO 8601:2004 format: YYYY-DD-MMThh:mm:ss). The EndDateTime must be later than the StartDateTime if both are provided.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported DateTime is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported DateTime (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 12.10 Ordered Release In Queue Response Message

OrderedReleaseInQueueResponseMessage

 

 

A response Message in a OrderedReleasesInQueueRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

TicketId

String

1

The Identifier of a ticket to link different web service calls to one another.

 

A

EstimatedDateTimeOfDelivery

ddexC:EventDate

1

A Composite containing details of the Date and Place of the Event in which the delivery is scheduled to happen.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.11 Redelivery Request Message

echo:RedeliveryRequestMessage

A request Message in a RedeliveryRequestCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

OrderType

ddexC:OrderType

0-1

A Composite containing details of the Type of an order. A specific OrderType typically infers a priority which, in turn, is defined in the contractual relationship between MessageSender and MessageRecipient.

 

Namespace

String

0-1

The Namespace of the OrderType. This is represented in an XML schema as an XML Attribute.

 

UserDefinedValue

String

0-1

A UserDefined value of the OrderType. This is represented in an XML schema as an XML Attribute.

ReleaseId

ddexC:ReleaseId

1

A Composite containing details of ReleaseIds. If available, a GRid should always be used. When a ReleaseId with no ResourceId is provided in a grouping, the request is for the entire Release; when a ReleaseId and a ResourceId are provided in a grouping, the request is for the specified Resource.

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

ISRC

String

0-1

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.

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

ResourceId

ddexC:ResourceId

0-n

A Composite containing details of ResourceIds. When a ReleaseId with no ResourceId is provided in a grouping, the request is for the entire Release; when a ReleaseId and a ResourceId are provided in a grouping, the request is for the specified Resource.

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

String

0-1

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.

 

ISMN

String

0-1

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".

 

ISAN

String

0-1

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.

 

VISAN

String

0-1

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.

 

ISBN

String

0-1

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.

 

ISSN

String

0-1

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.

 

SICI

String

0-1

The SICI (Serial Item and Contribution Identifier defined in ANSI/NISO Z39.56-199) for the Resource.

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Resource.

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Resource.

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

RedeliveryReasonType

ddexC:RedeliveryReasonType

0-1

A Composite containing details of a reason for the redelivery. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 

Namespace

String

0-1

The Namespace of the RedeliveryReasonType. This is represented in an XML schema as an XML Attribute.

 

UserDefinedValue

String

0-1

A UserDefined value of the RedeliveryReasonType. This is represented in an XML schema as an XML Attribute.

Comment

String

0-1

A Comment that provides additional information to the RedeliveryReasonType and must be understood by the MessageRecipient.

 12.12 Redelivery Response Message

RedeliveryResponseMessage

 

 

A response Message in a RedeliveryRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

IsSuccessful

Boolean

1

A Flag indicating whether a redelivery was successful (=True) or not (=False).

 

 

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.13 Release Availability Message

echo:ReleaseAvailabilityMessage

A Message that is sent to inform about an available Release.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

ReleaseId

ddexC:ReleaseId

1-n

A Composite containing details of ReleaseIds. If available, a GRid should always be used.

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

ISRC

String

0-1

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.

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

NewReleaseMessage

In  accordance with DDEX-ERNM

1

A Message in the ERN MessageSuite, Main Profile, containing details of a new Release.

 12.14 Release Availability Request Message

ReleaseAvailabilityRequestMessage

 

 

A request Message in a ReleaseAvailabilityRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

ReleaseId

ddexC:ReleaseId

0-n

A Composite containing details of ReleaseIds of the Release whose availability is requested. If available, a GRid should always be used.

 

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

 

ISRC

String

0-1

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.

 

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 12.15 Release Availability Response Message

ReleaseAvailabilityResponseMessage

 

 

A response Message in a ReleaseAvailabilityRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

ReleaseAvailabilityStatus

ddexC:ReleaseAvailabilityStatus

1

A Composite containing details of whether a Release is available to be delivered to the ReleaseDistributor.

 

 

 

Namespace

String

0-1

The Namespace of the ReleaseAvailabilityStatus. This is represented in an XML schema as an XML Attribute.

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the ReleaseAvailabilityStatus. This is represented in an XML schema as an XML Attribute.

 

A

NewReleaseMessage

in accordance with DDEX-ERNM

0-1

A Message in the ERN MessageSuite, Main Profile, containing details of a new Release.

 

B

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.16 Release Status Information Message

echo:ReleaseStatusInformationMessage

A response Message in a ReleaseStatusCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

Priority

Priority

0-1

The priority of a WsMessage.

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

ReleaseId

ddexC:ReleaseId

1

A Composite containing details of ReleaseIds. If available, a GRid should always be used.

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

ISRC

String

0-1

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.

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

NewReleaseMessageStatus

NewReleaseMessageStatus

1

The status of the NewReleaseMessage.

NewReleaseMessage

As per DDEX-ERNM

0-1

A Message in the ERN MessageSuite, Main Profile, containing details of a new Release.

 12.17 Release Status Request Message

ReleaseStatusRequestMessage

 

 

A request Message in a ReleaseStatusRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

0-1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

ReleaseId

ddexC:ReleaseId

1-n

A Composite containing details of ReleaseIds of the Release whose availability is requested. If available, a GRid should always be used.

 

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

 

ISRC

String

0-1

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.

 

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 12.18 Release Supply Chain Status Request Message

ReleaseSupplyChainStatusRequestMessage

 

 

A request Message in a ReleaseSupplyChainRequestCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

DSP

ddexC:PartyDescriptor

1

A Composite containing details of the DSP who is requesting information, or on whose behalf information is requested. This DSP may be different from the MessageSender if that is an aggregator.

 

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

A

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

B

PartyName

ddexC:PartyName

1-n

A Composite containing details of the PartyName(s).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

B

PartyId

ddexC:PartyId

0-1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

ReleaseId

ddexC:ReleaseId

1

A Composite containing details of ReleaseIds of the Release whose availability is requested. If available, a GRid should always be used.

 

 

IsReplaced

Boolean

0-1

The Flag indicating whether this Identifier is old and has been replaced by a new one (=True) or not (=False). The Flag may only be set to True when the new Identifier is also provided. If the Flag is not set, this Identifier is deemed to be the current one.

 

 

GRid

String

0-1

The GRid identifying the Release. This is the preferred Element and is mandatory if a GRid is available. A GRid comprises four parts: the string "A1", followed by five alphanumeric characters, ten alphanumeric characters and and one alphanumeric character.

 

 

ISRC

String

0-1

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.

 

 

ICPN

ddexC:ICPN

0-1

A Composite containing details of the 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).

 

 

 

IsEan

Boolean

1

The Flag indicating whether the ICPN is specifically an EAN (=True) or a UPC (=False). This is represented in an XML schema as an XML Attribute.

 

 

CatalogNumber

ddexC:CatalogNumber

0-1

A Composite containing details of the CatalogNumber of the Release.

 

 

 

Namespace

String

1

The Namespace of the CatalogNumber. This is represented in an XML schema as an XML Attribute.

 

 

ProprietaryId

ddexC:ProprietaryId

0-n

A Composite containing details of a ProprietaryIdentifier of the Release.

 

 

 

Namespace

String

1

The Namespace of the ProprietaryId. This is represented in an XML schema as an XML Attribute.

 12.19 Release Supply Chain Status Response Message

ReleaseSupplyChainStatusResponseMessage

 

 

A response Message in a ReleaseSupplyChainStatusCall.

Message Element

Data Type

Card

Element Description

 

MessageVersionId

String

1

The Version of the Message.

 

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

WsMessageThreadId

String

0-1

A string used to uniquely identify the thread of Messages of which the current Message is a part. This element should only be used in web service choreographies involving more than one pair of Messages.

 

 

WsMessageId

String

1

The Identifier of a WsMessage.

 

 

MessageCreatedDateTime

DateTime

1

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

 

 

IsSymmetric

Boolean

1

A Flag indicating whether the WsMessage has been sent in an environment where MessageSender and MessageRecipient publish a web service for the current choreography (=True) or whether only one Party publishes such a web service (=False).

 

 

XmlChoice

 

0-1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

 

 

HashSum

ddexC:HashSum

1

A Composite containing a HashSum and information about the algorithm with which it has been generated.

 

 

 

 

HashSum

String

1

The value of the HashSum.

 

 

 

 

HashSumAlgorithmType

ddexC:HashSumAlgorithmType

1

A Composite containing details of the Type of HashSumAlgorithm governing the HashSum.

 

 

 

 

 

Namespace

String

0-1

The Namespace of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the HashSumAlgorithmType. This is represented in an XML schema as an XML Attribute.

 

 

 

Signature

ftpx/amep:Signature (ds:Signature)

1

A digital signature in accordance with DDEX-DSIG.

 

 

Priority

Priority

0-1

The priority of a WsMessage.

 

AcknowledgedWsMessageId

String

1

The Identifier of a WsMessage.

 

ReceivedWsMessageStatus

WsMessageStatus

1

The Status of a received WsMessage.

 

XmlChoice

 

1

An XmlComposite corresponding to the xs:choice element in an XML document or schema.

 

A

Status

ddexC:SupplyChainStatus

1

A Composite containing details of the status of the Release or ReleaseDeal in terms of processing in the supply chain.

 

 

 

Namespace

String

0-1

The Namespace of the SupplyChainStatus. This is represented in an XML schema as an XML Attribute.

 

 

 

UserDefinedValue

String

0-1

A UserDefined value of the SupplyChainStatus. This is represented in an XML schema as an XML Attribute.

 

A

StatusChangeDate

ddexC:EventDate

0-1

A Composite containing details of the Date and Place of the Event in which the status of the Release or ReleaseDeal was changed.

 

 

 

IsApproximate

Boolean

0-1

The Flag indicating whether the reported Date is approximate (=True) or exact (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsBefore

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime before the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

IsAfter

Boolean

0-1

The Flag indicating whether the Event being described occurred sometime after the reported Date (=True) or not (=False). This is represented in an XML schema as an XML Attribute.

 

 

 

TerritoryCode

ddexC:TerritoryCode

0-1

The Territory in which the Event occurred (represented by an ISO 3166-1 TerritoryCode). This is represented in an XML schema as an XML Attribute.

 

 

 

LocationDescription

String

0-1

A Description of the location in which the Event occurred. It offers the opportunity to describe a place more precisely than using the TerritoryCode. This is represented in an XML schema as an XML Attribute.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the LocationDescription as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

B

ErrorText

String

1

A Comment about the Message. This is solely to aid the MessageRecipient of the Message to resolve the issues complained about.

 12.20 Report Delivery Message

echo:ReportDeliveryMessage

A request Message in a ReportDeliveryCall.

Message Element

Data Type

Card

Element Description

MessageVersionId

String

1

The Version of the Message.

MessageHeader

amep:WsMessageHeader

1

The MessageHeader for the Message.

 

MessageSender

ddexC:MessagingParty

1

A Composite containing details of the MessageSender.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesBeforeKeyName

ddexC:Name

0-1

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).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

KeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

NamesAfterKeyName

ddexC:Name

0-1

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.

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

AbbreviatedName

ddexC:Name

0-1

A Composite containing a short version of the PartyName (e.g. for use on devices with a small display).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

TradingName

ddexC:Name

0-1

A Composite containing a TradingName for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

MessageRecipient

ddexC:MessagingParty

1

A Composite containing details of the MessageRecipient.

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the MessagingParty as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

PartyId

ddexC:PartyId

1

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.

 

 

 

Namespace

String

0-1

The Namespace of the PartyId if it belongs to a proprietary Party 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.

 

 

PartyName

ddexC:PartyName

0-1

A Composite containing details of the PartyNames for the Party handling the Message.

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script for the Elements of the PartyName as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullName

ddexC:Name

1

A Composite containing the complete Name of the Party, in its normal form of presentation (e.g. John H. Smith, Acme Music Inc, A Composite containing the Beatles).

 

 

 

 

LanguageAndScriptCode

String

0-1

The Language and script of the Name as defined in IETF RfC 4646. The default is the same as indicated for the containing composite. Language and Script are provided as lang[-scipt][-region][-variant]. This is represented in an XML schema as an XML Attribute.

 

 

 

FullNameAsciiTranscribed

String

0-1

The FullName transcribed using 7-bit ASCII code.

 

 

 

FullNameIndexed

ddexC:Name

0-1

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, A Composite containing the).