LoD samples

LoD samples are available here.

They cover different aspects of direct communication between licensee and licensor about letters of directions as well as communications via a hub. For both set-ups fill and partial letters of directions are being shown.

 Additional information on the Statutory Reversion Sample (/LoD/Direct/LoD_statutory_reversion.xml)

Catalogue transfers that are communicating statutory reversions are signalled as being such by setting the CatalogTransfer’s CatalogTransferType to UsStatutoryReversion.

Effective 10th March 2020, Publisher C owns James Fitz’ 50% in the US (i.e., Publisher C is now Original Publisher).

This is expressed using HasOriginalPublisherShare to point to the RightShare with a RightShareType of OriginalPublisherShare and Publisher C’s PartyReference in the RightsController tag. 

The percentage is expressed using a RightSharePercentage with a value of 50 (not: 0.5!) in the MusicalWorkCollectionShare (it is 0 in the OriginalPublisherShare). This is due to the definition of RightSharePercentage, which reads: 

The share of the licensed Rights owned by the RightsController. This is the share to be collected during the validity period (which for manuscript shares and original publisher shares would be =0 but for collection shares would typically be >0). RightShare information is given as a decimal value with up to 6 digits (e.g. '12.5' represents 12.5%).

So, for the original publisher shares, the value has to be 0, not 100 or 50.

The date (10th March 2020) goes into the EffectiveTransferDate element.

Publisher A administers or otherwise “controls” that 50% o/b/o Publisher C in the US and collects the royalties for that share.

As a consequence, Publisher A is found in the RightsController field(s) in this example. 

Publisher A is thus the RightsController of the RightShare with a RightShareType of MusicalWorkCollectionShare and a RightSharePercentage of 50, as mentioned above.

 Licenses in effect before termination date stay with the prior publisher. Royalties due on these licenses remain payable to prior publisher. 

The third party involved here is the relinquishing publisher, Publisher B, whose PartyReference is therefore in the RelinquishingPublisher tag. There is no further encoding or description of what happens to royalty payments and actions to be taken by the labels are not spelled out.

All samples are being provided as a valid XML message and a human readable HTML file.