Linking right shares in MWN

In the MWN standard, communicating a right share chain (e.g. a collection share based on an original publisher share based on a manuscript share) is possible by using the elements HasOriginalPublisherShare and IsFollowerInTitleOf in the RightShare composite.

When communicating such related right shares, some of the values need to agree. For instance, a right share percentage must not be larger than the right share percentage of the manuscript share that is at the beginning of the chain, and the rights types and use types of a follower in title must be the same or a subset of the rights types and use types of the base right share.

Linking an original publisher share to a manuscript share

An original publisher share is linked to a manuscript share using the IsFollowerInTitleOf element, in which both the BaseRightShare and the ManuscriptShare elements are set to the manuscript share using its reference identifier:

<RightShare>
    <RightShareReference>S003</RightShareReference>
    <RightShareType>OriginalPublisherShare</RightShareType>
    ...
    <RightsController>
        <RightsControllerPartyReference>P0001
        </RightsControllerPartyReference>
    </RightsController>
    <RightSharePercentage>60</RightSharePercentage>
    <IsFollowerInTitleOf>
        <BaseRightShare>S010</BaseRightShare>
        <RightSharePercentage>100</RightSharePercentage>
        <ManuscriptShare>
            <BaseRightShare>S010</BaseRightShare>
            <RightSharePercentage>100</RightSharePercentage>
        </ManuscriptShare>
    </IsFollowerInTitleOf>
</RightShare>

 

Linking a follower in title

A follower in title is linked to preceding right shares using the HasOriginalPublisherShare and IsFollowerInTitleOf elements. The following is an example of a right share that is based on the original publisher share defined above, which is referenced using the HasOriginalPublisherShare element and the IsFollowerInTitleOf/BaseRightShare element, while the underlying manuscript share is specified in the IsFollowerInTitleOf/ManuscriptShare element:

<RightShare>
    <RightShareReference>S0005</RightShareReference>
    <RightShareType>LicensingShare</RightShareType>
    <RightShareWorkReference>W0001</RightShareWorkReference>
    <TerritoryCode>US</TerritoryCode>
    <RightsType>MechanicalRight</RightsType>
    <RightsController>
        <RightsControllerPartyReference>P0003
        </RightsControllerPartyReference>
    </RightsController>
    <RightSharePercentage>30</RightSharePercentage>
    <HasOriginalPublisherShare>
        <OriginalPublisherShare>S0003</OriginalPublisherShare>
    </HasOriginalPublisherShare>
    <IsFollowerInTitleOf>
        <BaseRightShare>S0003</BaseRightShare>
        <RightSharePercentage>60</RightSharePercentage>
        <ManuscriptShare>
            <BaseRightShare>S010</BaseRightShare>
            <RightSharePercentage>100</RightSharePercentage>
        </ManuscriptShare>
    </IsFollowerInTitleOf>
</RightShare>

 

As the message schema only allows specifying a single preceding right share using the HasOriginalPublisherShare and IsFollowerInTitleOf/BaseRightShare elements, a RightShare composite cannot be based on multiple right shares described by separate RightShare composites. So once a right share is split in a chain of right shares, any following right shares must be described by separate RightShare composites and cannot be merged into a single RightShare composite.

For example, as illustrated in the figure below, if a publisher (P0004) obtains the rights to a share of a work in which it already had rights, the resulting control of rights must be communicated using two RightShare composites (S004 and S006). The same applies if a publisher who controls a work for one country obtains the rights to the same work for a different country: the resulting control of rights must be communicated using two RightShare composites, one for one country and one for the other.

x.jpg

Aligning right share specifications

When communicating related right shares, the values of the following elements need to agree.

Types

The elements RightShareType, WorkPart, RightsType, UseType/ExcludedUseType, DSP/ExcludedDSP, CarrierType, CommercialModelType, which describe the scope of the right shares with regards to the rights and usages must be compatible. This applies to the values for an individual right share, where e.g. a UseType must be applicable to a RightsType, but also along a chain of right shares, where the RightsType and UseType values of right share further down in the chain must be the same or a subset of the RightsType and UseType values of the preceding right share.

Territories

The territories of the right shares, which are specified using TerritoryReference or one of the alternative elements, must be consistent, i.e. the territory of a right share further down in the chain must not be larger than the territory of the preceding right shares.

Validity periods

The values communicated in the ValidityPeriod elements must be consistent, e.g. a start value of a right share further down in the chain must not start before the preceding right shares.

Percentages

The values communicated in the RightSharePercentage, IsFollowerInTitleOf/RightSharePercentage and IsFollowerInTitleOf/ManuscriptShare/RightSharePercentage elements must be compatible, i.e. the percentage of a right share further down in the chain must not be larger than the percentage of the preceding right shares. Further information on percentages can be found here.

Search