An XML message notifying the successful receipt of a Batch or File. In an FTP context this means successful ingestion. In a Web Service context in means the reply to a Web Service Call.
A company that sends or receives DDEX messages on behalf of other companies. Aggregators enable smaller companies to participate in the DDEX ecosystem.
A grouping of one or more Releases to be processed by a Release Distributor together. The concept of a batch is used in one of the FTP Profiles of this ERN Choreography Standard.
A well-defined collection of Releases.
Note that the XML tags use the spelling “catalog” instead of catalogue.
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.
A Deal is what transforms a Release into a product. A Deal states how a Release may be made available to consumers.
The proportion of the overall Musical Work that has been assigned to a Collecting Publisher or Administrator. Note that a Writer can have zero, one or many Original Publishers, and hence zero, one or many Distribution Shares.
Exclusive Rights Owner or Licensee
A company that is either the exclusive owner of all rights for a specific territory of all Resources within a Release or the sole licensee from an exclusive Rights Owner for sound recording/Resource rights for a The term “exclusive” here refers to those sound recording/Resource rights for a specific territory or set of territories.
A company that plays both roles of Release Creator (e.g. in communications to downstream Release Distributors) and Release Distributor (e.g. in communications upstream Release Creators).
A Party to whom permission to use a Creation (e.g.: MusicalWork, Sound Recording or Release) is granted in a License Agreement.
An Agent granting permission to use a Creation (here: MusicalWork, Sound Recording or Release) in a LicenseAgreement.
An XML message signifying the delivery of a Batch.
A Musical Work is a Work whose expression is a combination of sounds, with or without accompanying words.
The concept of ensuring that a party cannot repudiate, or refute, the sending or receiving of a message.
A RightsController who is assigned rights directly by the Writer. Note that a writer may have zero, one or many Original Publishers.
Original Publisher Share
The proportion of the overall Musical Work that a writer has assigned to an Original Publisher. Note that each Writer can have zero, one or many Original Publishers, and hence zero, one or many Original Publisher Shares.
The content of one Batch to be transmitted via the a Message Exchange Protocol. Payload does not include manifests or acknowledgements.
A collection of Resources, combined with a deal that is marketed or sold as a commodity.
A Release is an abstract entity representing a bundle of one or more Resources compiled by an Issuer for the purpose of electronic distribution to individual consumers, directly or through intermediaries. 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.
A percentage or fraction of a right for a Musical Work for a particular time and place in which a party claims a controlling interest. Note: controlling interest includes ownership and/or administration.
Distribution of a Product to end consumers.
A unique identifier that links several Web Service Calls/Responses together.
A modern set of web technologies that allow small pieces of information, typically in the form of XML files, to be exchanged. Augmented with FTP they can be used to communicate Releases along the music supply chain.
Web Service Call
The sending of an XML document to a port/address on a web server, using HTTP or SHTTP.
Web Service Response
The sending of an XML document in direct response to a Web Service Call, using HTTP or SHTTP.
For the avoidance of doubt: the appropriate response is always the message indicated in the appropriate Choreography. The WsAcknowledgementMessage may not be used as a Web Service Response unless expressly specified within a specific standard.