WAI Extension: Right Shares
Mirrored from the canonical text at commit 498e6b88 ().
Status: Draft. Registers the record
wai.media.right_shares: who holds what share of which right in the works a package’s works document names (music-rights §5). A share statement, signed by one or more signers and naming the works document by its digest, states per work, per share type and per right type each party’s share in integer millionths of the whole, and the part no party it lists claims as its remainder (§4). The right types and share types are the values DDEX’s allowed-value sets publish for musical-work right shares, read as the sets name them (§3). The shares of one entry and its remainder sum to exactly 1 000 000; a share that is not known isnull, never 0, and holds part of the remainder; and a statement that writes a share as 0 is refused with its own reason. Statements by different signers are combined into one view per work, share type and right (§5): where two statements give one party different shares, or the shares claimed pass the whole, the view states a conflict with every claim and the statement that makes it, and resolves nothing. A pinned rule turns a session’s contribution record into a proposed split of a work’s manuscript shares (§6): who made which samples, people and models, counted in units, with no share to a model party under the human-authorship reading the text records, never as a rule WAI imposes. A proposal is never final: it becomes a share statement only when every party it gives a share signs one that states exactly its shares. Share statements are written as aMusicalWorkClaimNotificationMessageof DDEX’s MWN 1.3.1, and such a message is read into WAI’s types within a profile, refused outside it and held to DDEX’s schema, fetched where it is used (§7). No transport changes and no core text changes. The reference implementation is theright_sharesmodule ofwai-rs(featureright_shares); the corpus islive-conformance/right-shares/, and its second implementation islive-conformance/right_shares_verify.py. Keywords MUST, MUST NOT, SHOULD, MAY are RFC 2119/8174.Texts read for this revision, fetched read-only on 14 November 2026: DDEX’s Musical Work Right Share Notification Choreography Standard, Part 1: Message definition, version 1.3.1 (published 2025-12-22), its clause 4.1 (the terms right share, rights type, manuscript share, original publisher share, collection share and writer), clause 7.3 and clause 7.9.3; its Part 2, Profiles, version 1.0, clause 7.3; DDEX’s allowed-value sets, version 11 (the version that standard names) and version 12 (the version release-message §8 pins), their sets
RightsCoverage_MWDRandRightShareType_MWDR; and the pages of DDEX’s Knowledge Base Communication of percentages, Precision of numeric values in MWN and Communicating right share percentages in MWN 1.3. Decision D127 states what was read of each, with its SHA-256, and why this is an extension of its own. For §6, read on 14 November 2026: the docket of the Supreme Court of the United States for No. 25-449, and the report contribution §1 reads, fetched again; decision D131 states what was read of each and the reading §6.3 records. For §7, read on 14 November 2026: MWN Part 1, version 1.3.1, clauses 1, 3, 4.1, 5.1, 5.2, 7.1 to 7.7, 7.9.1 to 7.9.3 and Annex A; its XML Schema (works-share-notification-choreography.xsd, its headerSCOW Version v0.9.14 251213) with the allowed-value sets of version 11 it names; MWN Part 2, version 1.0, clauses 5, 6, 7.1 to 7.3, 8.1.1 and 8.3.1; and the pages of DDEX’s Knowledge Base on MWN, its structure and its samples; each pinned in decision D134.The allowed-value sets are © 2006-2025 and © 2006-2026 Digital Data Exchange, LLC (DDEX). This text names the values of two sets as far as implementing them needs, under DDEX’s Implementation Licence (release-message §4); it reproduces no allowed-value set.
1. Scope
In scope: the right types and share types a statement names (§3); the share statement, its digest, its signatures and its verification against the works document it names (§4); combining statements by several signers into one view, with every conflict stated (§5); and the rule that turns a contribution record into a proposed split, the proposal, its verification and the share statement that countersigns it (§6); and MWN 1.3.1’s notification message, written from share statements and read within a profile (§7).
Out of scope: every other message of MWN (a claim request, a recall, a manifest) and every element of the notification message outside §7’s profile; sending a message to anyone; whether a party holds what a statement says it holds, which no WAI record states; how a share was agreed; shares by territory and for a term, and every other dimension a right share can have besides its work, share type and right type (a statement’s shares apply in every territory and at every time in this revision); computing a payment from a share; and every legal effect of a statement. WAI texts set no legal rules: this extension states what a statement carries and how it is checked, not what anyone holds under any law.
Relationship to the core spec: wai.media.right_shares is a record (SPEC §5):
signed records a WAI tool emits and verifies. It names no payload format and is not
dispatchable.
Relationship to music-rights: a statement names a works document by its digest (music-rights
§5.2) and a work by its position in the document’s works; it adds a document beside the works
document and changes none of music-rights’ records, rules, corpus or reasons.
2. Terms
- Document, canonical form, digest, key and signature: as route-record §2.
- Works document, work statement, text and package: as music-rights §5.1, §4 and
§2. A party is named by a
name(a text) and anisni(an ISNI of music-rights §3.3, ornull). - Two parties are the same party when both carry an ISNI and the two are equal, or when neither does and their names are equal. A party with an ISNI and one without are never the same party, as music-rights §4 has two works.
- Millionths: an integer from 0 to 1 000 000, a share of the whole right: 1 000 000 is all of it. A share in millionths m is the percentage m / 10 000, a decimal of at most four digits after the point.
- Signer: a key that signs a statement (§4.2).
3. Right types and share types
A right type is the kind of right a share is of. The values are those of DDEX’s allowed-value
set RightsCoverage_MWDR, which the allowed-value sets of versions 11 and 12 both hold, but its
value All: MWN 1.3.1’s schema documents that all rights are stated by naming every other value,
not All. In the order this text uses:
| right type | the set’s definition, in short |
|---|---|
InformationNetworkDisseminationRight | to disseminate a work over a digital network |
LyricsRight | to reproduce a work’s lyrics |
MechanicalRight | to record and distribute a work on a carrier |
PerformingRight | to perform a work to the public |
PrintRight | to make and distribute a visual copy of a work |
RentalRight | to rent or lend a copy of a work to the public |
SynchronizationRight | to combine a work in timed relation with works of other types |
A share type is what a share is a share of. The values are those of DDEX’s allowed-value set
RightShareType_MWDR, in this order:
| share type | what it is (the set’s and MWN Part 1 clause 4.1’s definitions, in short) |
|---|---|
MusicalWorkManuscriptShare | a writer’s share of a work, as agreed between its writers; a work’s manuscript shares sum to the whole |
OriginalPublisherShare | the part of the work a writer has assigned to a publisher that holds it directly from the writer |
MusicalWorkCollectionShare | the share as calculated for collecting money |
LicensingShare | a share that entitles its holder to license the work |
A value outside a table is not a right type or a share type of this revision. The sets are DDEX’s; a later version of the sets that adds a value is read again before this text names it.
4. The share statement
4.1 The statement
A share statement states shares in the works of one works document. It is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-right-shares" |
version | 1 |
works | 64 lowercase hexadecimal digits: the digest of the works document (music-rights §5.2) |
proposal | null, or 64 lowercase hexadecimal digits: the digest of a proposed split (§6.4) the statement countersigns; §4.3 reads it as stated, and §6.6 holds the statement to the proposal |
entries | an array of 1 to 1 024 entries, in strictly ascending order of work, then of share_type and right in §3’s orders |
signers | an array of 1 to 64 keys, in strictly ascending order of their bytes |
sigs | an array of signatures, one for each signer, in the order of signers (§4.2) |
Each entry is an object of exactly these members:
| member | form |
|---|---|
work | an integer: the position from 0 of a work statement in the works document’s works |
share_type | a share type (§3) |
right | a right type (§3) |
holders | an array of 0 to 64 holders, no two of them the same party (§2) |
remainder | millionths: the part of the right no holder’s stated share holds |
Each holder is an object of exactly these members:
| member | form |
|---|---|
name | a text: the party’s name |
isni | an ISNI (music-rights §3.3) or null |
organization | true where the party is an organisation, false where it is a person, null where the statement does not say |
key | a key, or null: the key the party signs with, where the statement names it |
share | millionths from 1 to 1 000 000, or null: the party’s share, null where it is not known |
An entry states the shares of one right type, of one share type, in one work. Its holders’ stated
shares and its remainder sum to exactly 1 000 000. A party the entry does not list holds nothing
the entry states. A share that is not known is null, and it is part of the remainder:
an entry with a holder whose share is null has a remainder above 0, which holds that share and
whatever part no listed holder claims. A share is never written as 0: a party with no share is not
listed, and a share not known is null.
4.2 Digest and signatures
The digest of a statement is SHA-256 over the canonical form of the statement without sigs,
written as 64 lowercase hexadecimal digits. Each signature is Ed25519 by its signer over
wai:right-shares (ASCII) and 0x01, followed by that same canonical form, verified strictly as
SPEC §7 Signatures verifies every signature. Every signer signs the same bytes: a
statement with several signers is one statement that each of them makes.
4.3 Verification
A verifier is given a statement’s text, a works document’s text and the package the works document names (music-rights §5.3). It refuses, at the first that applies:
shares_malformed: the text holds more than 1 048 576 bytes, is not a document, or its members, its entries’ or its holders’ are not exactly §4.1’s, each of its form, but for a holder’sisni, which here is only a string ornulland which step 2 reads, and for ashareof 0, which step 3 refuses; or the entries are not in strictly ascending order, or two holders of one entry are the same party, or the number ofsigsis not the number ofsigners.- Each holder’s
isnithat is notnull, in document order:isni_malformedorisni_check_character(music-rights §3.3). shares_unknown_as_zero: a holder’sshareis 0.- Each entry, in order, both checks of an entry before the next entry:
shares_sum_mismatchwhen its holders’ shares that are notnulland itsremainderdo not sum to 1 000 000;shares_unknown_without_remainderwhen a holder’sshareisnullandremainderis 0. shares_signature_invalid: a signature does not verify by its signer.- The works document, verified against the package by music-rights §5.3: that text’s reason.
shares_works_mismatch:worksis not the works document’s digest.shares_work_unknown: an entry’sworkis not the position of one of the works document’s works.
A statement that passes is accepted, and the verifier states its digest, its signers and its
proposal, and for each entry, in order: its work, share type and right; its number of holders;
known, the sum of its shares that are not null; its remainder; the number of its holders
whose share is null; and its status, complete when remainder is 0 and partial
otherwise.
5. Combining statements
5.1 The view
Several parties state shares in one work, each its own: a writer its manuscript share, a publisher what it holds. A combination reads statements by any signers over one works document and gives one view for each work, share type and right type that any of them states (a key), in ascending order of keys (§4.1’s order of entries). A view states what the statements agree on and every conflict between them; it never chooses one statement’s claim over another’s.
A party’s claims in a key are its shares as each statement’s entry for the key states them, in the order the statements were given, each with the statement’s position from 0 in that order.
5.2 Steps
A verifier is given statements’ texts, in order, a works document’s text and its package. It refuses a combination when it refuses a statement:
- Each statement, in order, verified by §4.3: its reason, with the statement’s position. So every
statement names the one works document given, and a statement over another is refused
shares_works_mismatch.
Otherwise, for each key, in order:
- Parties. The holders of every statement’s entry for the key, each party once (§2), in
order of first appearance: statements in their order, holders in their entry’s order. Each
party is named by its first holder’s
nameandisni. - Disagreement. A party whose claims are not all equal, a
nullclaim counting as a value of its own, is a conflictdisagree, which states the party and each of its claims. - Agreed parties. Every other party has one share, its claims’ value: a number, or
null. - Overclaim. With K the sum of the agreed parties’ shares that are not
null: when K is above 1 000 000, or is exactly 1 000 000 while an agreed party’s share isnull, a conflictoverclaim, which states K: in the second case the known shares leave nothing for the share no claim states. - The view. Its parties with their agreed shares and the statements that state each (a party
in a
disagreeconflict has none here); its conflicts,disagreeones in order of their parties and then anoverclaim; its remainder, 1 000 000 − K where the key has no conflict, andnullwhere it has one; the number of agreed parties whose share isnull; and its status:conflictwhere it has a conflict,completewhere its remainder is 0, andpartialotherwise. Anoverclaimis decided on the agreed parties alone, whether or not a party of the key disagrees.
A statement’s own remainder is what that signer does not claim; another statement’s holders can
claim it. So a writer’s statement of its manuscript share and its co-writer’s statement of theirs,
each with the rest in the remainder, combine into a view whose shares are both and whose remainder is
what neither claims.
5.3 What a conflict is not
A conflict is the statements’ state, stated: it is not a refusal, and a view with one is complete as a statement of what the statements say. Nothing in a view says which claim is right, which signer is entitled to state it, or what a reader does next: a reader that needs one share for a key with a conflict has none from the view, and asks the signers.
6. Proposed splits from contribution records
6.1 What a proposal is
A session of contribution records who made which samples of an output: its
authorship map gives every sample the parties whose act produced its value (made_by) and those
whose choices conditioned it (directed_by), people and models alike (contribution §7). A
proposed split turns that map into manuscript shares of a work by a pinned rule (§6.2). The rule
is data: the same session and map give the same proposal on every machine, and the proposal says
which rule made it. A proposal is not a share statement and states no share anyone holds: it is
never final until the parties it gives a share sign a share statement that states exactly its
shares (§6.6), and parties who agree other shares sign those instead, as §4 lets any signers do.
6.2 The rule
The rule wai-right-shares:contribution/1 is given a session record (contribution §3.1) and the
stated authorship map its contribution record names (contribution §7.3):
- Samples. Every sample of the map, N of them, its width times its height.
- Makers. The makers of a sample are the parties its
made_byholds, in ascending position, thenunknownwhere the set holds it; a set holding neither has the one makerunknown. (A stated map holds noundisclosed, contribution §7.3.) Of m makers, each takes ⌊1 000 000 / m⌋ units of the sample, and the first also takes 1 000 000 − m · ⌊1 000 000 / m⌋, so a sample is 1 000 000 units. - Units. U(x) is the units maker x takes over all the samples, for each party and for
unknown. - What a share divides. D is the units of the session’s keyed parties (contribution §3.1, a
human or an audience party) and of
unknown: every unit but those a model party takes. - Shares. Where D is 0, the rule gives no holder and a remainder of 1 000 000. Otherwise each
keyed party p has the share ⌊1 000 000 · U(p) / D⌋; the holders are the keyed
parties whose share is at least 1, in ascending position; and the remainder is 1 000 000
less their shares. The remainder holds the units of
unknownand what rounding down leaves. - Direction. For each party, the number of samples whose
directed_byholds it, as contribution §7.4 counts them: stated beside the shares, never added to one.
Products are computed in integers wide enough not to overflow: 1 000 000 · U(p) reaches 2⁶⁵.
6.3 The reading the rule records
The rule gives a model party no share: the units a model takes are left out of D, so the people’s shares divide what people made, and samples whose maker no pinned rule fixes stay in the remainder, since a person may have made them. This is the reading of human authorship that WAI’s texts record, and the rule’s content; it is not a rule WAI sets, and no WAI text decides who is an author. Contribution §1 records the conclusion of the report it reads: an output can be protected in whole or in part where a person was able to determine the expressive elements it contains, and prompts alone are unlikely to suffice. The court’s docket for No. 25-449 records that a petition for certiorari on whether a work a machine made alone can be registered was denied on 2 March 2026, and the research note behind this package records, from a summary, that the requirement of a human author stands (D131). It is one jurisdiction’s reading, as those texts state it. The rule credits making, not direction: a party whose prompt, mask, selection or arrangement conditioned samples is stated with its count (step 6), and the parties weigh it; the report treats such contributions case by case, which no pinned rule decides. Parties who read otherwise, under any law, sign a share statement of other shares, which §4 holds to the same checks and which names no proposal.
6.4 The proposal
A proposal is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-share-proposal" |
version | 1 |
proposer | a key: whoever computed the proposal |
rule | "wai-right-shares:contribution/1" |
session | 64 lowercase hexadecimal digits: the link hash of the session record (contribution §2) |
record | 64 lowercase hexadecimal digits: the link hash of the contribution record |
works | 64 lowercase hexadecimal digits: the digest of the works document (music-rights §5.2) |
work | an integer: the position from 0 of the work in the works document’s works whose manuscript shares the proposal splits |
rights | an array of 1 to 7 right types (§3), in strictly ascending order of §3’s: the rights the split is proposed for |
samples | an integer: N |
units | an array of 0 to 64 objects of exactly party (an integer: a party’s position in the session) and units (an integer above 0), one for each party whose U is above 0, in ascending party |
unknown_units | an integer: U(unknown) |
holders | an array of 0 to 64 objects of exactly party, name (a text: the name a share statement names the party by), isni (an ISNI or null) and share (millionths from 1 to 1 000 000), in ascending party |
remainder | millionths |
directed | an array of 0 to 64 objects of exactly party and samples (an integer above 0), one for each party some sample’s directed_by holds, in ascending party |
sig | a signature by proposer |
The digest of a proposal is SHA-256 over the canonical form of the proposal without sig, and
its signature is Ed25519 by proposer over wai:share-proposal (ASCII) and 0x01, followed by that
canonical form, verified strictly as SPEC §7 Signatures has it. A holder’s name and isni are
the proposer’s statement of who the party is; the party’s own signature on the share statement
vouches for them (§6.6).
6.5 Verification
A verifier is given a proposal’s text, a contribution case (contribution §10.1: the session record, its memberships, the contribution record, the disclosed steps, the stated map, the openings, the states, the model files, the origin claims and a policy), a works document’s text and its package. It refuses, at the first that applies:
proposal_malformed: the text holds more than 1 048 576 bytes, is not a document, or its members or its entries’ are not exactly §6.4’s, each of its form, but for a holder’sisni, which here is only a string ornull; or an array is not in its order, or names a party twice.- Each holder’s
isnithat is notnull, in order:isni_malformedorisni_check_character(music-rights §3.3). proposal_signature_invalid: the signature does not verify.proposal_contribution_invalid: contribution §10 refuses the case.proposal_contribution_mismatch:sessionis not the session record’s link hash, orrecordis not the contribution record’s.- The works document, verified against the package by music-rights §5.3: that text’s reason.
proposal_works_mismatch:worksis not the works document’s digest;proposal_work_unknown:workis not the position of one of its works.proposal_model_holder: a holder’spartyis a model party of the session.proposal_counts_mismatch:samples,units,unknown_unitsordirectedis not what §6.2 gives for the session and the case’s map. (Apartythat is not a position in the session reads at step 1 as an integer and fails here or at step 10, since §6.2 gives it nothing.)proposal_holders_mismatch: the holders’ parties are not the holders §6.2 gives.proposal_share_mismatch: a holder’sshare, orremainder, is not what §6.2 gives.
A proposal that passes is accepted, and the verifier states its digest, its proposer, the tier contribution §10.3 gives the case, each holder’s party and share, and the remainder.
6.6 Countersigning
A share statement countersigns a proposal when it states exactly the proposal’s shares and every party the proposal gives a share signs it. A verifier is given a share statement’s text, a proposal’s text, and the proposal’s contribution case, works document and package. It refuses, at the first that applies:
- The proposal, verified by §6.5: its reason.
- The statement, verified by §4.3 against the works document and the package: its reason.
countersign_proposal_mismatch: the statement’sproposalis not the proposal’s digest.countersign_entries_mismatch: the statement’s entries are not, for each of the proposal’srightsin order, the entry of the proposal’swork, of the share typeMusicalWorkManuscriptShareand of that right, whose holders are the proposal’s holders in order, each with itsname, itsisni,organizationfalse(a keyed party is a person, contribution §3.1),keyits key in the session andshareits share, and whoseremainderis the proposal’s.countersign_missing: a holder’s key is not among the statement’s signers: that party has not signed, and the split is not final.
A statement that passes is final: the verifier states its digest, the proposal’s digest and its signers. Other signers may sign beside the holders, the proposer among them; a proposal with no holder is countersigned by any signer, since it gives no one a share.
7. Right share notifications
7.1 What this section is
A party that notifies its shares in musical works to a service or a collective does so in a
MusicalWorkClaimNotificationMessage of DDEX’s Musical Work Right Share Notification Choreography
Standard, Part 1, version 1.3.1 (MWN 1.3.1), whose namespace is http://ddex.net/xml/mc-notif/131.
This section writes such a message from share statements (§7.5) and reads one into WAI’s types
(§7.6) within a profile (§7.2 to §7.4), the way release-message §5 to §8
write and read an ERN message: the XML is release-message §5.1’s subset, read the same way; a DPID
is read as release-message §3.1 reads it; the reader refuses what DDEX’s XML Schema refuses within
the profile, refuses what the profile does not read, and refuses an identifier the schema admits as
a string but whose syntax or check character is wrong; and DDEX’s schema files are not in the tree
but fetched where they are used (§7.7). A message names its sender and its recipients by their
DPIDs, and the exchange of messages is release-message §4’s: WAI’s code grants nothing of DDEX’s
licence. MWN Part 2, version 1.0, gives the message profiles of its own; the messages §7.5 writes
are of two of them, ShareNotification (its clause 8.1) and ConflictNotification (clause 8.3).
In §7.2 to §7.6, a path, text, ID, reference, date and time and the rules for
an element of simple or element content are release-message §2 and §5.1 to §5.8’s, with mwn_ in
place of ern_ in every reason.
7.2 The message
The root is MusicalWorkClaimNotificationMessage in the namespace
http://ddex.net/xml/mc-notif/131; another root is mwn_not_notification. Its children are
unqualified: a child in a namespace is mwn_element_unexpected. In the tables below, each type
lists the elements the profile reads, in the schema’s order, each with the schema’s least and most
occurrences (n for unbounded) and the most the profile reads; an element not listed, wherever it
stands, is mwn_unmapped. An attribute not listed on an element is mwn_unmapped, but
xsi:schemaLocation on the root, which the reader ignores.
The root carries AvsVersionId (required; a text) and LanguageAndScriptCode (required; the
pattern release-message §5.2 states, which MWN 1.3.1’s schema gives too). Its children:
| element | schema | profile | value |
|---|---|---|---|
MessageHeader | 1 | 1 | below |
ProfileId | 0–1 | 1 | ShareNotification or ConflictNotification |
PartyList | 0–1 | 1 | below |
WorkList | 1 | 1 | below |
RightShareList | 0–1 | 1 | below |
MessageHeader holds MessageThreadId (0–1; a text), MessageId (1; a text), MessageSender
(1), MessageRecipient (1–n; 64), MessageCreatedDateTime (1; a date and time) and
MessageControlType (0–1; LiveMessage or TestMessage, the whole set). MessageSender and
MessageRecipient each hold PartyId (1; a DPID) and PartyName (0–1), which holds FullName
(1; a text).
7.3 Parties and works
PartyList holds Party (1–n; 4 096). A Party holds:
| element | schema | profile | value |
|---|---|---|---|
PartyId | 1 | 1 | holds ISNI (0–1; an ISNI), DPID (0–1; a DPID) and ProprietaryId (1–n; 4; a text, with the required attribute Namespace, a text) |
PartyReference | 1 | 1 | an ID of pattern P and one or more of _, -, digits and letters |
PartyName | 1–n | 1 | holds FullName (1; a text) |
IsOrganization | 1 | 1 | a boolean (§7.4) |
WorkList holds MusicalWork (1–n; 1 024). A MusicalWork holds:
| element | schema | profile | value |
|---|---|---|---|
MusicalWorkReference | 1 | 1 | an ID of pattern W and one or more of _, -, digits and letters |
MusicalWorkId | 1 | 1 | holds ISWC (0–1; an ISWC) and ProprietaryId (1–n; 4; as a party’s) |
Title | 1–n | 1 | holds TitleText (1; a text) |
Writer | 0–n | 32 | holds WriterPartyReference (1; a reference to a party’s ID) and Role (0–n; 4; Composer, Lyricist, Arranger or Translator) |
7.4 Right shares
RightShareList holds RightShare (1–n; 4 096) and then Conflict (0–n; 1 024). A RightShare
holds:
| element | schema | profile | value |
|---|---|---|---|
RightShareReference | 1 | 1 | an ID of pattern S and one or more of _, -, digits and letters |
RightShareType | 1 | 1 | a share type (§3), the whole set |
RightShareWorkReference | 1–n | 1 | a reference to a work’s ID |
TerritoryCode | 1–n | 1 | Worldwide |
RightsType | 1–n | 7 | a right type (§3); All, which the set holds, is mwn_unmapped, and a value outside the set mwn_value_invalid |
RightsController | 1 | 1 | holds RightsControllerPartyReference (1; a reference to a party’s ID) |
RightsControllerUnknown | 1 | 1 | true |
RightShareUnknown | 1 | 1 | true |
RightSharePercentage | 1 | 1 | a percentage (below) |
The schema makes TerritoryCode one branch of a choice whose others the profile does not read, so
a right share without it is mwn_element_missing, named TerritoryCode. RightsController and
RightsControllerUnknown are a choice of one, as are RightShareUnknown and
RightSharePercentage (with RightShareNotClaimed, which the profile does not read): both of a
choice is mwn_element_unexpected and neither mwn_element_missing, named by the first. Once its
children and their values are read, a right share whose controller and whose share are both unknown
is mwn_unmapped, at the right share’s own path: no entry of §4 states it. One right type given
twice is read twice: neither the schema nor the profile refuses it. A Conflict holds ConflictRightShareReference (1–n; 64; a reference to a right share’s ID).
Values (release-message §5.8, its order of checks):
- A boolean (
xs:boolean), white space collapsed:true,false,1or0(mwn_value_invalidotherwise); the profile readstrueandfalse, and where a table saystrue,trueonly (mwn_unmappedotherwise). - A percentage (
xs:decimal), white space collapsed: a sign where given, then digits and, where given, a point and digits, with at least one digit in all, so60.and.5are of the type (mwn_value_invalidotherwise); the profile reads one with no sign above 0 and at most 100 that is a whole number of millionths of the whole (10 000 times it is an integer), and gives it in millionths (mwn_unmappedotherwise). A percentage of 0 is outside the profile, as MWN Part 2 clause 7.3 keeps 0 out of a share. - An allowed value: a share type and a right type are of sets the profile holds whole (§3), as
are
ProfileId’s four values,ConflictNotification,LinkNotification,RevocationandShareNotification, of which it maps the first and the last (another of the four ismwn_unmapped, another stringmwn_value_invalid); of the roles and the territory, sets the profile does not hold, another value ismwn_unmapped. - A DPID, an ISNI and an ISWC: release-message §5.8 and §3.2, with their reasons.
7.5 Writing
The writer is given a notification statement: a document of exactly these members:
| member | value |
|---|---|
works | a works document’s text (music-rights §5.1) |
package | exactly pack_digest and components: the package it names |
statements | an array of 1 to 16 share statements’ texts (§4), in order |
message_id, thread_id, created, control, language, avs_version, sender, recipients | as release-message §6.1’s |
It refuses at the first that applies:
- The statement is not of this form:
mwn_write_malformed; but a DPID that is not one is refused with its reason of release-message §3.1. - The statements combined by §5.2 over the works document and its package: that refusal’s reason.
mwn_write_organization_unknown: a party the message names (steps 4 and 5 below) is not stated as an organisation or as a person by every holder that is that party, in every entry of every statement, whether or not that entry’s right shares are written: the schema requiresIsOrganization, and the writer fills no value a statement does not give.mwn_write_no_party: the message names no party, since no view gives a party a share: MWN Part 2 asks a share notification for its parties.
Otherwise it writes, from the combination’s views (§5.2):
- Which works and right shares. Where no view has a conflict, the message is of the profile
ShareNotification, and its works are every work a view names. Where one has, it is of the profileConflictNotification, and its works are those a view with a conflict names (MWN Part 2 clause 8.3.1 lists only works whose shares are in conflict). Each view of a work written gives, in view order, its right shares: for a view with no conflict, one for each agreed party, with its share orRightShareUnknown, and then, where the view states no party’s share as not known and its remainder is above 0, one ofRightsControllerUnknownand the remainder; for a view with a conflict, one for each claim, the statements in their order and each statement’s holders in their order, and aConflictthat names every right share of the view. - Parties. The holders of the right shares written, each party once (§2), in order of first
appearance, each with its first holder’s name and ISNI and the organisation all its holders
state. A work’s writer that is the same party as one of them is written as the work’s
Writer, with its roles (composer,lyricist,arranger,translatorasComposer,Lyricist,Arranger,Translator); a writer that holds no share written is not, since nothing states whether it is an organisation. - Identifiers. Each party’s
PartyIdholds its ISNI where known and oneProprietaryId, and each work’sMusicalWorkIdits ISWC where known and oneProprietaryId, as MWN Part 2 clause 7.2 asks every work to have: in the namespace of the sender’s DPID, the digest (route-record §2) of the document of the party’snameandisni, or of the work statement. A proprietary identifier names what the sender states, and two writers give it the same value. - The message. The header as release-message §6.3 writes one;
ProfileId; the parties asP1on; the works asW1on, each with its title; the right shares asS1on, each of its share type, its work,TerritoryCodeWorldwide, its right type, its controller’s reference orRightsControllerUnknowntrue, andRightSharePercentageorRightShareUnknowntrue; and the conflicts. A share in millionths m is written as ⌊m / 10 000⌋ and, where m mod 10 000 is not 0, a point and its four digits with their trailing zeros left out (66.6666,50,0.0001).
The bytes are fixed as release-message §6.3 fixes an ERN message’s, with the root written
mc-notif:MusicalWorkClaimNotificationMessage and xmlns:mc-notif="http://ddex.net/xml/mc-notif/131".
A message the writer writes is in the profile, and the reader reads it back to the right shares it
was written from.
7.6 Reading
The reader refuses at the first that applies, with the reason and the path, in release-message
§7.1’s steps 1 to 6 with this section’s names; a document that is not of the root is
mwn_not_notification.
A message read gives WAI’s types: its AvsVersionId, LanguageAndScriptCode and header; its
profile; its parties (reference, name, ISNI, DPID, each or null, its proprietary identifiers with
their namespaces, whether it is an organisation); its works (reference, ISWC or null, proprietary
identifiers, title, writers with their party and roles); its right shares (reference, share type,
work, right types, controller’s party or null where unknown, share in millionths or null where
unknown); and its conflicts, each the right shares it names. It states what the message leaves
unknown: the parties with no ISNI, the works with no ISWC, the right shares whose controller is not
known and those whose share is not. A message read is what it says: the reader does not combine
its right shares (§5) or hold them to a works document.
7.7 The schema
The reader’s acceptance and the writer’s output are held to DDEX’s schema of MWN 1.3.1: every message the writer writes, and every message the reader accepts, validates; of a message with one defect, one refused with a reason of the schema’s class fails validation, and one refused with an identifier’s reason validates. The corpus states each refused message’s verdict, measured.
DDEX’s files are not in the tree, and are fetched where they are used, each held to its SHA-256
before it is used, by live-conformance/right-shares/fetch.sh:
| file | address | SHA-256 |
|---|---|---|
works-share-notification-choreography.xsd (284 368 bytes) | https://service.ddex.net/xml/mc-notif/131/works-share-notification-choreography.xsd | d53bd20ab9b255986d49dd6441173c60b068c04d2f8cae28b687d16d8dd86608 |
allowed-value-sets.xsd (3 228 596 bytes, version 11) | https://service.ddex.net/xml/allowed-value-sets/allowed-value-sets_011.xsd | 1725875b3de1da74fa483abfdefbe36bb7132e9f1d7b1124b710848ec48b125f |
xmldsig-core-schema.xsd (10 293 bytes) | https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd | 35cf8197da812c85e40d57891b35c94187569ed474a2dac813ce5090dafcd35c |
The schema imports the allowed-value sets from the address at which DDEX publishes every version,
and the standard (Part 1 clause 7.3) names version 11, the version the standard’s own archive of
its schema holds beside it; it also imports W3C’s XML Signature schema, whose components it refers
to. An XML catalog resolves both imported addresses to the files fetched (version 11 at its own
address, which does not change), so validation uses no network and no later version. libxml2’s
validator, as release-message §8 and D118 found for ERN, does not check that an ID is unique or that
a reference names an ID when either is an element’s value; the reader checks both, and the corpus
states null for those two verdicts.
8. Reasons
| reason | raised at |
|---|---|
shares_malformed | §4.3 step 1 |
shares_unknown_as_zero | §4.3 step 3 |
shares_sum_mismatch | §4.3 step 4 |
shares_unknown_without_remainder | §4.3 step 4 |
shares_signature_invalid | §4.3 step 5 |
shares_works_mismatch | §4.3 step 7 |
shares_work_unknown | §4.3 step 8 |
proposal_malformed | §6.5 step 1 |
proposal_signature_invalid | §6.5 step 3 |
proposal_contribution_invalid | §6.5 step 4 |
proposal_contribution_mismatch | §6.5 step 5 |
proposal_works_mismatch | §6.5 step 7 |
proposal_work_unknown | §6.5 step 7 |
proposal_model_holder | §6.5 step 8 |
proposal_counts_mismatch | §6.5 step 9 |
proposal_holders_mismatch | §6.5 step 10 |
proposal_share_mismatch | §6.5 step 11 |
countersign_proposal_mismatch | §6.6 step 3 |
countersign_entries_mismatch | §6.6 step 4 |
countersign_missing | §6.6 step 5 |
mwn_xml_malformed | §7.6 |
mwn_xml_unsupported | §7.6 |
mwn_not_notification | §7.2, §7.6 |
mwn_element_unexpected | §7.2, §7.4, §7.6 |
mwn_element_missing | §7.4, §7.6 |
mwn_attribute_missing | §7.6 |
mwn_value_invalid | §7.4 |
mwn_reference_duplicate | §7.6 |
mwn_reference_dangling | §7.6 |
mwn_unmapped | §7.2, §7.3, §7.4, §7.6 |
mwn_write_malformed | §7.5 step 1 |
mwn_write_organization_unknown | §7.5 step 3 |
mwn_write_no_party | §7.5 step 3 |
The verifier also gives music-rights’ reasons for a holder’s ISNI (§4.3 step 2, §6.5 step 2) and
for a works document it refuses (§4.3 step 6, §6.5 step 6), and a message’s reader its reasons for
an ISNI and an ISWC (music-rights §3.2, §3.3) and for a DPID (release-message §3.1). Of §7’s
reasons, mwn_xml_malformed, mwn_not_notification, mwn_element_unexpected,
mwn_element_missing, mwn_attribute_missing, mwn_value_invalid, mwn_reference_duplicate and
mwn_reference_dangling are of the schema’s class, mwn_xml_unsupported and mwn_unmapped of the
profile’s, and the identifiers’ reasons of an identifier’s class (§7.7).
9. Conformance
live-conformance/right-shares/ holds the corpus, in one
file, vectors.json, written from fixed seeds by wai_right_shares_vectors gen. It holds the
works document its statements name and the package that document names, and:
- statements (§4): a statement’s text, accepted with its digest, signers and entries, or refused with its reason;
- combinations (§5): statements’ texts in order, combined into their views, or refused with the reason and the position of the statement refused;
- proposals (§6.5): a proposal’s text and its contribution case, accepted with its digest, its proposer, the case’s tier, its holders and its remainder, or refused with its reason;
- countersignatures (§6.6): a share statement’s text, the proposal it names and the proposal’s case, final, or refused with its reason;
- notifications (§7.5): a notification statement’s text, written to the message it states, or refused with its reason;
- messages (§7.6): a message, read into WAI’s types with what it leaves unknown, or refused with
its reason and path, each with
schema, whether the pinned schema admits or refuses it as measured, ornullwhere the case’s rule is one the schema states and the validator does not check.
Every reason of §8 has a case refused with it. The accepted statements include a complete manuscript split signed by both its writers, a publisher’s statement of its share with the rest in the remainder, a statement with a holder whose share is not known, entries in §3’s order of share types where it is not the alphabet’s, and one name held with and without an ISNI as two parties. Among the refused statements, each a control of one defect: a share written as 0; shares and a remainder that sum to more than the whole, and to less; a holder whose share is not known with nothing left in the remainder; two holders that are the same party by their ISNI; entries out of order; a signature by a key that is not the signer’s, first and second of two; a signer listed twice; each bound passed; a statement over another works document; and a work the document does not hold. The combinations include two writers’ statements that agree, a writer’s and a publisher’s that combine to the whole, given in either order, two signers who give one party different shares, two whose claims pass the whole, a share stated by one signer and called unknown by another, and a share not known with nothing left for it beside a party that disagrees, each conflict stated with every claim. The proposals are of sessions made with contribution’s records: two people, every step checked; two people and a model; four samples of three makers upscaled, so that samples between makers are made by each of them and one by all three; a model’s picture filtered by a derivation no text pins and half of it redrawn; one sample made by two people and by no maker a pinned rule fixes; and a model’s picture alone, which gives no holder. Among the refused proposals, each a control of one defect: a model given a share; the model’s units counted in what a share divides; samples no rule attributes given to a person; a share rounded up; a share and a remainder each misstated alone; a holder left out; samples, units and direction misstated; another session and another record; a contribution case contribution §10 refuses; and a signature by a key that is not the proposer’s. The countersignatures include a split both its holders sign, with the proposer and without, a proposal with no holder, and refused, one a holder has not signed, other shares, a holder named without its key or as an organisation, a statement that names no proposal, and a proposal that gives a model a share.
The notifications include one statement’s split, a writer split beside a publisher’s share whose
remainder no one claims, a share not known, two statements in conflict, and a conflict beside an
agreed work; and, refused, a party no statement says is an organisation or a person, one stated as
each, a statement refused, nothing to notify, no recipient and a DPID whose check character is
wrong. The messages accepted are those the writer wrote, one written otherwise (a comment, the
schema’s location, single quotes, a CDATA section, CR LF line ends, white space around a reference,
a percentage and a boolean), two proprietary identifiers and no profile; each refused message is a
fixed edit of one the writer wrote, a control of one defect: of the schema’s class, a document cut
short and an undeclared entity, another namespace, a required element after a later one, an
element out of order, an element twice, a child in MWN’s namespace, text in the header, a required
element and a choice removed, both of a choice, an attribute removed, a boolean, a share type, a
percentage, a reference, a date, a language code, a control type and a DPID off their forms, an ID
twice and a dangling reference; of the profile’s, a document type declaration and another
encoding, an identifier, an attribute, an empty title, a share of 0 and of five decimals, All, a
profile, a boolean digit, a share not claimed, a territory, a share whose controller and amount
are both unknown and a role the profile does not read; and of an identifier’s, an ISNI and an ISWC
whose check characters are wrong, an ISNI in groups, an ISWC in its display form and a DPID whose
check character is wrong.
A conforming implementation gives every case the outcome the corpus states.
wai_right_shares_vectors verify and the test tests/right_shares.rs check that the file
regenerates byte for byte and that wai-rs gives every case its outcome.
live-conformance/right_shares_verify.py is the second implementation, written from this text and
sharing no code with wai-rs; it writes every notification’s message itself to the same bytes and
reads every message with the standard library’s XML parser; it also mutates copies of the corpus
and drops each of its own checks in turn, and requires each to be caught. With --schema, it
validates every message the corpus holds against the schema live-conformance/right-shares/fetch.sh
fetched, with the xmllint it builds, and holds each case’s schema to the verdict.
10. Security and privacy considerations
- A statement is its signers’. It says what its signers state each party holds, in the terms of §3 and §4, and nothing more: it is not a contract, a licence or a registration, and WAI checks it against none. A verifier checks its form, its sums and its signatures; whether a signer is entitled to state a share is not a question this extension answers.
- A signer can state another party’s share. A publisher’s statement names a writer’s share; the
writer need not sign it. A reader that accepts only shares a holder signed reads a holder’s
keyand the statement’ssigners. - Unknown is not zero. A share not known is
null, part of the remainder, and a statement that writes 0 is refused (§4.3 step 3): a field filled to look complete would be a share nobody stated. - Conflicts are stated, not resolved. Two signers that disagree are both shown (§5.2 steps 3 and 5); a combination never drops a claim, never takes one signer over another and never scales claims to fit the whole.
- A proposal is a computation, not a split. It states what a pinned rule gives for a session’s stated map, which the contribution case behind it vouches for only as far as its tier reaches (contribution §10.3): a proposal over a map whose steps were attested rests on the attestations. Nothing is final until every party it gives a share signs a statement of exactly those shares (§6.6), and any parties may sign other shares instead.
- The rule records a reading; it does not decide one. It counts making, not direction, and gives a model no share, as §6.3 says the texts it cites read one jurisdiction’s law. A share statement records what its signers agree, under whatever law they read.
- A message is not signed here. An MWN message carries no WAI signature: its writer takes every share from signed statements (§7.5), and a reader of a message holds it to the schema and the profile, and to nothing a statement signed. A message’s proprietary identifiers name what its sender states, in its sender’s namespace.
- The reader is bounded. It reads release-message §5.1’s subset of XML, so no entity expands, and the document, its depth and every repeated element are bounded (§7.2 to §7.4).
- Names of people. A holder is named by the name it is publicly known by, an ISNI where known, whether it is an organisation, and a key where the statement names one. A statement carries nothing else about a party; a proposal names a session’s people by the names its proposer gives them, and their signatures on the statement are what vouches for those names.