WAI Extension: Music Rights
Mirrored from the canonical text at commit 498e6b88 ().
Status: Draft. Registers the record
wai.media.music_rights: the identifiers the music industry names recordings, works and parties by, carried and checked where WAI names what it holds. A recording is named by its ISRC (ISO 3901:2019), a musical work by its ISWC (ISO 15707:2022) and a party by its ISNI (ISO 27729:2024); WAI reads each in its normative form and checks the check character the ISWC and the ISNI carry (§3). A work statement names a work by its title, its ISWC where it is known, and its writers and publishers (§4). A works document, signed and kept beside a package of packaging, names the package’s recordings with their ISRCs, the spans of its components they are, their artists and the works they are performances of (§5), and §6 maps what it carries onto the fields of the release message of DDEX ERN 4.3.2, a mapping release-message writes and reads. In a live room, a performer names the work it plays in a work cue, ametaevent of the room, alone or beside an intent of co-performance (§7); a matcher states the fingerprint of a recording’s audio in a signed fingerprint statement (§8); and a signed performed-works report lists each work performed in a show, its span on the room clock, its identifiers where known and its evidence class (declared by the performer, matched by a fingerprint against a stated reference under a pinned rule, or both), which a verifier recomputes from the room’s events and recording (§9) and which gives the fields public setlist forms ask for (§10). A signed rights record beside a recording states, per work and span, whether the rights its signer holds cover the live moment only, a replay in stated territories for a stated term, or are unknown; a clip or a recording whose window holds a work not cleared for replay is not publishable for a replay purpose, a condition this text adds to live-recording’s verdicts and that changes none of them (§11). Unknown stays unknown: an identifier that is not known isnull, and an end no evidence states isnull, never a value made up to fill the field or a duration of 0. No transport changes and no core text changes. The reference implementation is themusic_rightsmodule ofwai-rs(featuremusic_rights); the corpus islive-conformance/music-rights/, and its second implementation islive-conformance/music_rights_verify.py. Keywords MUST, MUST NOT, SHOULD, MAY are RFC 2119/8174.Texts read for this revision, fetched read-only on 14 November 2026: the International Standard Recording Code (ISRC) Handbook, 4th edition (2021), of the International ISRC Registration Authority, which interprets ISO 3901:2019 (its §3.3, the structure, and §5, the visual presentation), and the agency’s list of the two-character codes allocated to its agencies (October 2026); ISO 15707:2022, second edition, as far as its published preview gives it (clauses 1 to 7 and Annex A in part; its informative Annex B, the computation of the check digit, is not in the preview and was not read); the ISWC agency’s public pages on the code and its use; ISO 27729:2024, edition 2, as far as its abstract and table of contents go (its normative Annex A, the check character, was not read), and the ISNI agency’s public answers on the structure of an ISNI; ISO 7064:1983, first edition, clause 6.1 (the pure system recursive method, with its example of MOD 11-2), from its published preview (ISO/IEC 7064:2003, which replaces it, was not read); and, of DDEX, the XML Schema of the release notification message of ERN 4.3.2 and its allowed-value sets, read as documentation of the message’s fields; and, for §10, a public paper set list form for live events and two public guides to reporting a live performance’s set list online. Decision D110 states what was read of each identifier’s text, where the method of a check character comes from where its text was not read, and how DDEX’s licences bear on §6; D112 states the readings behind §7 to §10, and D113 those behind §11.
1. Scope
In scope: the forms of an ISRC, an ISWC and an ISNI and the checks of the ISWC’s and the ISNI’s
check characters (§3); the work statement (§4); a package’s works document and its verification
(§5); the mapping of a works document onto DDEX ERN 4.3.2’s fields (§6); the work cue (§7); the
fingerprint statement (§8); the performed-works report, its computation and its verification
(§9); the fields of a setlist form a report gives (§10); and the rights record, clearing a window
for a live or a replay use, and the condition it adds to a clip’s and a recording’s publishable
(§11).
Out of scope: assigning an identifier, which is its agency’s and its registrants’; whether an identifier is registered, or names what a document says it names, which only its agency’s database states; a party’s identifiers other than the ISNI (a collecting society’s own numbers among them); the rest of an ERN message, which release-message writes and reads (§6.1); computing a fingerprint from audio samples, which iscc §1 leaves out too; submitting a report or a form to anyone; and every legal effect of a statement this extension carries. WAI texts set no rules of rights or consent: this extension states what a party can carry and how it is checked, not what a law requires.
Relationship to the core spec: wai.media.music_rights is a record (SPEC §5):
signed records a WAI tool emits and verifies. It names no payload format and is not
dispatchable.
2. Terms
- Document, canonical form, digest, token, key and signature: as route-record §2.
- Recording: a sound or music video recording, as the ISRC names one.
- Work: a musical work, as the ISWC names one: the abstract creation that recordings and performances are of.
- Party: a person, a group or an organisation, under the public name an ISNI names.
- Writer: a party credited with making a work, in one or more roles:
composer(the music),lyricist(the words),arrangerandtranslator. - Publisher: a party that publishes a work.
- Package: a package of packaging §11, named by its pack digest, the SHA-256 of its
LISTING(packaging §11, the package), and holding the components its receipt names (packaging §9). - Text: a string of 1 to 256 bytes of UTF-8 holding no code point below U+0020 and not U+007F.
- A span of a component is
from_mstoto_msof its presentation, in milliseconds,from_msincluded andto_msexcluded. - Room, room clock, principal and event: as live-events §2. An instant on the room clock is in microseconds.
- Take and chunk: as capture-binding §2.
- Show: the span of a room’s clock a report covers.
- Intent: a statement of co-performance §5.1,
WPI1.
3. Identifiers
3.1 ISRC
An ISRC is the twelve characters of its normative form (ISRC Handbook §3.3.1, §5): a prefix
of two letters A–Z and three characters each a letter A–Z or a digit 0–9; a year
of reference of two digits; and a designation code of five digits. It carries no check
character. A string that is not of this form is isrc_malformed: among them the form a person
reads (ISRC AA-6Q7-20-00047, with its code identifier and hyphens, which do not form part of
the ISRC) and a string holding a lower-case letter. The handbook recommends that a system map a
lower-case letter to its capital before it validates a code: a writer of a WAI document does so
before it writes, and a reader takes the form as written, so that one recording is one string
in every document that names it.
WAI checks the form, not the allocation: whether a prefix is allocated, and to whom, is the
agency’s list, which changes, and a prefix says nothing reliable of a current rights owner
(ISRC Handbook §3.3.1). The display form of an ISRC is ISRC , its first two characters,
-, the next three, -, the year of reference, - and the designation code (§5 there).
3.2 ISWC
An ISWC is the eleven characters T, nine digits (the work identifier, from 000000001 to
999999999) and one check digit (ISO 15707:2022 clause 4). The standard lets its registration
authority designate another prefix in place of T; none is designated in what was read, and a
string with another prefix is iswc_malformed, as is one with a work identifier of nine zeros,
one with separators (the form a person reads, ISWC T-034.524.680-1, whose hyphens and dots are
for reading only) and any other string not of the form.
The check digit is computed on a weighted modulus 10 (clause 4.4): with d₁ … d₉ the work identifier’s digits from the left,
S = 1 + 1·d₁ + 2·d₂ + 3·d₃ + 4·d₄ + 5·d₅ + 6·d₆ + 7·d₇ + 8·d₈ + 9·d₉
check digit = (10 − (S mod 10)) mod 10
where the 1 is the prefix’s. An ISWC of the form whose last digit is not its check digit is
iswc_check_digit. The standard’s own example, T0345246801, is one (D110 states where the
weights come from). The display form of an ISWC is ISWC T-, the work identifier’s digits in
three groups of three joined by ., - and the check digit (ISWC T-034.524.680-1).
3.3 ISNI
An ISNI is sixteen characters: fifteen digits and a check character, a digit or the capital X
(the agency’s answer on its structure). A string not of this form is isni_malformed: among them
one written in groups with spaces, and one ending in a lower-case x.
The check character is ISO 7064’s MOD 11-2 (ISO 7064 clause 6.1, the pure system recursive
method with modulus 11 and radix 2): with p = 0, for each of the fifteen digits a in order,
p = ((p + a) × 2) mod 11; the check value is (12 − p) mod 11, written as its digit, or
as X for 10. An ISNI whose last character is not its check character is isni_check_character.
3.4 Where they are carried
| identifier | carried in | member |
|---|---|---|
| ISRC | a works document’s recording (§5.1) | isrc |
| ISWC | a work statement (§4) | iswc |
| ISNI | a work statement’s writer or publisher (§4), a works document’s artist (§5.1) | isni |
Each member is the identifier’s normative form or null, and null states that it is not
known. A document never states an identifier it was not given: a writer that does not know a
recording’s ISRC writes null, not a code of its own making, and a verifier that recomputes a
document from its inputs (as §5.3 does) refuses one that states an identifier none of them
states.
4. The work statement
A work statement names one work. It is an object of exactly these members:
| member | form |
|---|---|
title | a text: the work’s title |
iswc | an ISWC (§3.2) or null |
writers | an array of 0 to 32 writers, each an object of exactly name (a text), isni (an ISNI or null) and roles (an array of 1 to 4 of the strings composer, lyricist, arranger, translator, each at most once, in that order) |
publishers | an array of 0 to 32 publishers, each an object of exactly name (a text) and isni (an ISNI or null) |
Two writers of one statement are not equal, nor are two publishers. An empty writers states
that no writer is known, not that the work has none.
Two work statements name the same work when both carry an ISWC and the two are equal, or when neither does and their canonical forms are equal. A statement with an ISWC and one without never name the same work: which work a statement without one names is not known.
5. A package’s works
5.1 The works document
A works document names the recordings and works of one package. It is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-music-works" |
version | 1 |
signer | a key: whoever states what the package holds |
package | 64 lowercase hexadecimal digits: the package’s pack digest |
works | an array of 0 to 1 024 work statements (§4) |
recordings | an array of 1 to 1 024 recordings |
sig | a signature (§5.2) |
Each recording is an object of exactly these members:
| member | form |
|---|---|
title | a text: the recording’s title |
isrc | an ISRC (§3.1) or null |
component | a token: the id of the package’s component the recording is in |
from_ms, to_ms | integers: the span of the component the recording is, from_ms below to_ms |
artists | an array of 0 to 32 objects of exactly name (a text) and isni (an ISNI or null): the artists principally associated with the recording, in the order they are credited |
works | an array of 0 to 32 integers, each the index in works of a work the recording is a performance of, ascending, each at most once |
Two artists of one recording are not equal.
5.2 Digest and signature
The digest of a works document is SHA-256 over the canonical form of the document without
sig, written as 64 lowercase hexadecimal digits. The signature is Ed25519 by signer over
wai:music-works (ASCII) and 0x01, followed by that same canonical form, verified strictly as
SPEC §7 Signatures verifies every signature. Every signed document of this
extension is digested and signed the same way, each under its own domain.
5.3 Verification
A verifier is given a works document’s text and the package it names: its pack digest and the ids of the components its receipt names. It refuses, at the first that applies:
works_malformed: the text holds more than 1 048 576 bytes, is not a document, or its members are not exactly §5.1’s, each of its form, but for the identifiers, which steps 2 and 3 read; or two writers, publishers or artists of one object are equal; or a recording’sworksnames an index that is not one ofworks.- Each identifier, in document order (the works, each its
iswcand then its writers’ and its publishers’isni; then the recordings, each itsisrcand then its artists’isni):isrc_malformed,iswc_malformed,iswc_check_digit,isni_malformedorisni_check_character(§3). isrc_repeated: two recordings carry one ISRC, which names one recording only (ISRC Handbook §4.1);iswc_repeated: two work statements carry one ISWC.works_signature_invalid: the signature does not verify.works_package_mismatch:packageis not the package’s pack digest.works_component_unknown: a recording’scomponentis not a component of the package.
A document that passes is accepted, and the verifier states its digest and signer; the
number of works, recordings and distinct parties (§6.2); and the number of identifiers stated
null: of ISRCs, of ISWCs and of ISNIs. It does not check that a span lies within its component,
which the component’s stage index states (packaging §6), nor anything an identifier’s agency
alone knows.
6. DDEX ERN 4.3.2
6.1 What this section is
A release that is delivered to a service as a release notification of DDEX ERN 4.3.2 names its
recordings, works and parties in that message’s fields. This section maps what a works document
carries onto those fields, so that whoever writes the message takes the values from a signed
document. release-message §6 writes a message from a works document by this
mapping, and its §7 reads one back into WAI’s types, holding it to the message’s XML Schema within
a profile (D117 and D118, which supersede in part D110’s reading that WAI writes and reads no ERN
message). The paths below are of the NewReleaseMessage element; a path ending @ an
attribute’s name is that attribute. The fields of ERN 4.3.2 that disclose the use of generative
models (ContainsAI, a contributor’s AiContribution and a SpecialContributor of
GenerativeAI) and its training permissions are marking-layers §3.5’s (The
release message), which holds them to a synthesis origin claim; this section maps none of them.
6.2 Parties
Each distinct pair of name and isni among a document’s writers, publishers and artists, in
order of first appearance (works first, then recordings), is one party, numbered from 1.
| works document | ERN 4.3.2 |
|---|---|
| party n | PartyList/Party, whose PartyReference is P and n in decimal |
its name | PartyList/Party/PartyName/FullName |
its isni, where not null | PartyList/Party/PartyId/ISNI, the sixteen characters as §3.3 has them, the form the schema’s documentation gives ([0-9]{15}[X0-9]) |
6.3 Recordings and works
| works document | ERN 4.3.2 |
|---|---|
| a recording | ResourceList/SoundRecording, its ResourceReference A and its position in recordings from 1 |
its isrc, where not null | SoundRecording/SoundRecordingEdition/ResourceId/ISRC, the twelve characters (the schema’s documentation gives [a-zA-Z]{2}[a-zA-Z0-9]{3}[0-9]{7}, which every ISRC of §3.1 matches) |
its title | SoundRecording/DisplayTitleText and SoundRecording/DisplayTitle/TitleText |
to_ms − from_ms | SoundRecording/Duration, an xs:duration of the form PThHmMsS (seconds with up to three digits after the point; an hour or minute part of 0 left out) |
| each artist, in order | SoundRecording/DisplayArtist/ArtistPartyReference (its party’s reference) with @SequenceNumber its position from 1 and DisplayArtist/DisplayArtistRole MainArtist, and SoundRecording/DisplayArtistName the artists’ names joined by , |
| each work it names | SoundRecording/WorkId/ISWC of the work, where the work’s iswc is not null |
| each writer of those works | SoundRecording/Contributor/ContributorPartyReference (its party’s reference), with one Contributor/Role/Value for each of its roles: Composer, Lyricist, Arranger, Translator (the schema’s Role holds the value in a Value element) |
| each publisher of those works | SoundRecording/Contributor/ContributorPartyReference, with Contributor/Role/Value MusicPublisher |
A work’s ISWC is not in a message whose work has none: ERN’s WorkId is optional, and an empty
ISWC is no ISWC. The ERN schema’s documentation states the identifier forms DDEX “will enforce
in the future”; a document of this extension already holds its identifiers to §3, which is no
looser than any of them.
6.4 What ERN needs that a works document does not carry
A message needs more than this document states: its header, its parties’ roles in the deal, a
recording’s SoundRecordingType, its P line, its release, deals and territories, and every
field this section does not name. They come from the message’s writer. A works document states
only what it carries, and a field the writer fills from elsewhere is not vouched for by its
signer.
7. Work cues
7.1 The cue
A performer names the work it is playing in the room’s events. A work cue is the payload of
a meta event (live-events §4.2): the four bytes WMW1 followed by the
canonical form of a document of exactly these members:
| member | form |
|---|---|
kind | "wai-music-cue" |
version | 1 |
action | "start" or "end" |
work | for a start, a work statement (§4): the work the author plays from the event’s instant; for an end, null |
intent | null, or, for a start, 64 lowercase hexadecimal digits: the digest of an intent of co-performance §5 by the cue’s own author, whose material is a performance of the work |
The event’s signature, by its principal, signs the cue; the cue carries no signature of its own.
Its author is the event’s principal and its instant the event’s t. A cue is bounded by its
author’s policy (live-events §5, max_payload), as every payload is.
7.2 Reading a cue
A reader is given a room id and an event’s record. It refuses, at the first that applies:
cue_event_malformed: the record does not read (live-events §3.3).cue_wrong_room: the record’sroomis not the room id.cue_signature_invalid: its signature does not verify (live-events §3.2).cue_not_meta: its kind is notmeta.cue_no_magic: its payload does not begin withWMW1.cue_malformed: the rest of the payload is not a document of exactly §7.1’s members, each of its form, or is not its canonical form byte for byte; or the action isendwith aworkor anintentthat is notnull, orstartwith aworkthat isnull.- The work’s identifiers, in document order (§5.3 step 2): their reasons.
A cue that passes is read: its author, its instant, its action, its work and its intent.
8. Fingerprint statements
8.1 The statement
A matcher that fingerprints a recording’s audio states what it fingerprinted. A fingerprint statement is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-music-fingerprint" |
version | 1 |
matcher | a key: whoever computed the fingerprint |
room | 64 lowercase hexadecimal digits: the room id |
take | 64 lowercase hexadecimal digits: the take id (capture-binding §3) whose chunks it fingerprinted |
first | an integer: the index of the first chunk |
chunks | an array of 1 to 1 024 digests: the SHA-256 of each chunk’s bytes, as the chunk’s descriptor states it (capture-binding §4), from first on, in index order |
from, to | integers: the room-clock span the chunks cover, from included and to excluded |
fingerprint | an array of 1 to 65 536 integers from 0 to 4 294 967 295: the Chromaprint fingerprint of those chunks’ audio, each value’s 32 bits as an unsigned integer |
sig | a signature (§5.2), under wai:music-fingerprint |
Computing a fingerprint from samples is out of scope (iscc §1): the statement is the matcher’s, signed. What a verifier holds it to is the chunks it names and the span they cover; the fingerprint itself it takes as stated.
8.2 The Audio-Code
The Audio-Code of a statement is the Audio-Code of its fingerprint at 256 bits (iscc
§4.4), each value read as the signed 32-bit integer of its bits. Its canonical form is iscc §3.2’s.
8.3 Verification
A verifier is given a statement’s text, the room id and the takes of the room’s recording: for each its take id and, for each of its chunks, the chunk’s index, its digest and its capture span mapped onto the room clock (capture-binding §9.3, the start and the end). A verifier given a recording takes them from each take’s manifest and its offset, once the recording verifier has accepted the recording (live-recording §4). It refuses, at the first that applies:
fingerprint_malformed: the text holds more than 1 048 576 bytes, is not a document, or its members are not exactly §8.1’s, each of its form, orfromis not belowto.fingerprint_signature_invalid: the signature does not verify.fingerprint_wrong_room:roomis not the room id.fingerprint_chunks_mismatch: no take given has the idtake, or a chunk fromfirsttofirstplus the number ofchunks, less one, is not among the take’s chunks or has another digest than the statement’s.fingerprint_span_mismatch:fromis not the first chunk’s mapped start, ortois not the last chunk’s mapped end.
A statement that passes is accepted, and the verifier states its digest, its matcher, its span and its Audio-Code.
9. The performed-works report
9.1 The report
A performed-works report states what works were performed in a show and when, and on what evidence. It is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-performed-works" |
version | 1 |
signer | a key: whoever states the report |
room | 64 lowercase hexadecimal digits: the room id |
from, to | integers: the show’s span on the room clock, from below to, both included |
threshold | an integer from 0 to 100: the threshold T of a match (iscc §5) |
references | an array of 0 to 256 references, each an object of exactly work (a work statement, §4) and audio_code (the canonical form of an Audio-Code of 256 bits: an ISCC of MainType CONTENT, SubType AUDIO, Version 0 and Length 7, iscc §3.2): the reference recordings a fingerprint is matched against |
fingerprints | an array of 0 to 1 024 digests, ascending, each once: the fingerprint statements the report reads |
lines | an array of 0 to 1 024 lines (§9.2) |
sig | a signature (§5.2), under wai:performed-works |
9.2 Lines
Each line is an object of exactly these members:
| member | form |
|---|---|
work | a work statement (§4): the work performed |
from | an integer: the room-clock instant the performance began |
to | an integer above from, or null: the instant it ended, null when no evidence states an end |
duration_us | an integer or null: to − from in microseconds, and null when to is null (§9.4 step 6 holds a line to this) |
evidence | "declared", "matched" or "both": its evidence class |
declared | an array of digests: the work cues that declare it, in their order (§9.3); empty for matched |
matched | an array of objects of exactly fingerprint (a digest), reference (an index in references) and similarity (an integer from 0 to 100), in the order of fingerprints; empty for declared |
A line is declared when its evidence is the performer’s: work cues, each its own or naming
an intent of its own. It is matched when its evidence is a fingerprint matched against a
stated reference under the report’s threshold. It is both when a declared performance and a
match of the same work overlap. An end, an identifier and a duration a line states are the
evidence’s: a line whose evidence states no end has to and duration_us null, never 0.
9.3 Computing the lines
The lines of a report follow from the room’s work cues, the fingerprint statements it names and its references, by these rules; a verifier computes them and compares (§9.4).
- The cues. The cues read (§7.2) from the events given whose instant is from the report’s
fromto itsto, both included, in cue order: ascending instant, then ascending author (by its 32 bytes), then ascendingseq. - Declared spans. Each cue whose
intentis notnulldeclares its work over the intent’s span, from itsattoatplusspan(co-performance §5.1). The other cues, in cue order, keep one open span for the room: a start of the open span’s work (§4) joins it; any other start ends the open span at its own instant and opens one of its work from that instant; an end ends the open span at its instant, and declares nothing when none is open. A span still open after the last cue has no end. A span that ends at the instant it began declares nothing. - One work, one line. Two declared spans of the same work that overlap (each begins before
the other ends, a span with no end ending after every instant) are one span, from the earlier
start to the later end (no end, where either has none), with the cues of both; this repeats
until no two overlap. Each span is a line whose
declaredlists its cues’ digests in cue order, and whose work is the work statement of its first cue in cue order. - Matches. For each fingerprint the report names, in its order: the statement’s Audio-Code
(§8.2) is compared with each reference’s (iscc §5): with d the bits in which they differ of
n = 256, a reference is a candidate when 100 (n − d) ≥ T n, and its similarity
is ⌊100 (n − d) / n⌋. The fingerprint matches the work of the candidate with the
fewest differing bits, the first such in
referencesorder, unless another candidate as near is of another work (§4): then it is ambiguous and matches nothing. A fingerprint with no candidate is unmatched. - Both. A match whose span overlaps a declared line of its work makes that line
bothand adds its entry to the line’smatched; of several such lines, the first in line order (step 7). A line’s span stays its declared span. - Matched lines. Matches of one work that overlap no declared line of it are one line for
each run whose spans overlap or meet (one ends where the next begins), from the earliest start
to the latest end, with their entries in the order of
fingerprints; its work is the work statement of the reference of its first entry. - Order. The lines are in ascending
from, then ascending canonical form of their works.duration_usisto−from, ornullwithto.
9.4 Verification
A verifier is given a report’s text, the room id, the room’s event records, its takes (§8.3) and fingerprint statements’ texts. It refuses, at the first that applies:
report_malformed: the text holds more than 4 194 304 bytes, is not a document, or its members, its references’ or its lines’ are not exactly §9.1’s and §9.2’s, each of its form; then each work’s identifiers, in document order (the references’ works, then the lines’), their reasons (§5.3 step 2).report_signature_invalid: the signature does not verify.report_wrong_room:roomis not the room id.report_event_invalid: an event record given does not read, is not of the room, or does not verify (live-events §3); then eachmetaevent whose payload beginsWMW1reads as a cue (§7.2 steps 6 and 7, their reasons), and a cue whoseintentis notnullnames the digest of an event given, by its author, of kindmeta, whose payload beginsWPI1and holds theatandspanof co-performance §5.1: otherwisecue_intent_unknown.- Each fingerprint the report names, in its order: a statement given has that digest, otherwise
report_fingerprint_missing; it verifies (§8.3, its reasons); and its span lies within the show, fromfromtoto: otherwisereport_fingerprint_outside. - The lines computed (§9.3) and the report’s:
report_line_missingwhen the report has fewer,report_line_extrawhen it has more; then, line by line in order, the first that differs:- its work:
report_identifier_inventedwhen the report’s work, with each identifier the computed work statesnullset tonulltoo, is the computed work: the report states an identifier no input states; otherwisereport_work_mismatch; - its
fromorto:report_span_mismatch; - its
duration_us:report_duration_unknown_as_zerowhen the computed one isnulland the report’s is 0; otherwisereport_duration_mismatch; - its
evidence,declaredormatched:report_evidence_mismatch.
- its work:
A report that passes is recomputed, and the verifier states its digest and signer; its number of lines, of each evidence class, of lines with no end and of lines whose work has no ISWC; and the number of fingerprints unmatched and ambiguous.
10. Setlist forms
A show’s report gives what the public forms on which performances are reported ask of each work performed: the title, the writers, the publisher, the duration and an identifier. Each line is one row, in line order:
| a form’s field | from the line |
|---|---|
| title of the work | the work’s title |
| composer, author, arranger | each writer’s name, a space and its roles in parentheses joined by , (composer, author for lyricist, arranger, translator), the writers joined by ; ; empty where writers is empty |
| publisher | the publishers’ names joined by ; ; empty where there are none |
| duration | ⌊duration_us / 60 000 000⌋, : and ⌊duration_us / 1 000 000⌋ mod 60 in two digits; empty where duration_us is null, never 0:00 |
| identifier | the ISWC’s display form (§3.2); empty where it is null |
| performances | the number of the report’s lines whose work is the same work (§4) as this line’s: what a form that lists a work once with a count of performances asks |
A field a form asks for that the report does not hold (the venue, the act’s name, the date) is the writer of the form’s. An empty field is a field the evidence does not fill: a form’s writer leaves it empty or fills it from what it knows, and the report vouches for no value it did not state.
11. Live to replay
11.1 The rights record
The rights a party holds in the works of a show can cover the moment it is performed live and not a replay of its recording, or a replay too, in some territories and for a term, or neither as far as it knows. A rights record states, per work and span, which; it is kept beside a recording (live-recording §4), naming its manifest by digest. It is a document of exactly these members:
| member | form |
|---|---|
kind | "wai-music-rights" |
version | 1 |
signer | a key: whoever states what the rights cover |
room | 64 lowercase hexadecimal digits: the room id |
recording | 64 lowercase hexadecimal digits: the digest of the recording manifest (live-recording §4.1) it is beside |
report | 64 lowercase hexadecimal digits, the digest of the performed-works report (§9) whose works it covers, or null |
entries | an array of 1 to 1 024 entries |
sig | a signature (§5.2), under wai:music-rights |
Each entry is an object of exactly these members:
| member | form |
|---|---|
work | a work statement (§4) |
from, to | integers: the span of the room clock the entry covers, from below to |
scope | "live": the moment it is performed live only; "replay": the live moment and a replay, in the territories and during the term below; "unknown": the signer does not know |
territories | for replay, an array of 1 to 250 codes of two capitals A–Z (ISO 3166-1 alpha-2 as the signer means them), ascending, each once, or the one string "world"; otherwise null |
term_from, term_to | for replay, integers, seconds since 1970-01-01T00:00:00Z, term_from below term_to: the term a replay may be presented in; otherwise null |
A scope is the signer’s statement of what it holds, in the terms of this table, and nothing more: this extension sets no rule of what a law grants or requires.
11.2 Verification
A verifier is given a rights record’s text, the room id, the digest of the recording manifest, and, where the record names a report, a report’s text. It refuses, at the first that applies:
rights_malformed: the text holds more than 1 048 576 bytes, is not a document, or its members or its entries’ are not exactly §11.1’s, each of its form; then each work’s identifiers, in document order, their reasons (§5.3 step 2).rights_signature_invalid: the signature does not verify.rights_wrong_room:roomis not the room id.rights_recording_mismatch:recordingis not the manifest’s digest.rights_report_mismatch:reportis notnulland no report is given, the report given does not read as §9.1’s form, or its digest is notreport.
A record that passes is read. A verifier takes the report’s lines as they are written: that they are the show’s is §9.4’s, which a party checks first.
11.3 Clearing a window
A use is live, presenting the show as it is performed, or replay, presenting its recording
later in a territory (a code of two capitals) at an instant (seconds since 1970-01-01T00:00:00Z).
A window [w₀, w₁) of the room clock is cleared for a use under a read record when, the
first reason below that applies otherwise:
- Each entry whose span overlaps the window (each begins before the other ends), in the
record’s order:
rights_unknownwhen its scope isunknown; and for a replay,rights_live_onlywhen its scope islive,rights_territorywhen its territories are not["world"]and do not hold the territory, andrights_termwhen the instant is beforeterm_fromor not beforeterm_to. - Where the record names a report, each of the report’s lines whose span overlaps the window (a
line with no end ending after every instant), in line order: every instant of the line within
the window lies in the span of an entry of the same work (§4), otherwise
rights_unknown. A work the report says was performed and the record says nothing of is a work whose rights are not known.
A window that holds no entry and no line is cleared: no work is stated in it.
11.4 Clips and recordings
A clip’s window is its record’s window_in to window_out (live-recording §5.1), and a
recording’s is its session span, from to to + 1. Where a rights record is given beside a
recording, a clip or the recording is publishable for the purpose live (capture-binding
§2) only when its window is cleared for the live use, and for the purpose distribute, which
presents a recording after the live moment, only when its window is cleared for a replay in the
territory and at the instant its presenter gives; and the reason a window is not cleared is the
reason of the verdict. The purposes record and train are unchanged. A verifier given no rights
record gives the verdicts of live-recording §4.5 and §5.4 as they are: this section adds a
condition and changes none.
12. Reasons
| reason | raised at |
|---|---|
isrc_malformed | §3.1, §5.3 step 2 |
iswc_malformed | §3.2, §5.3 step 2 |
iswc_check_digit | §3.2, §5.3 step 2 |
isni_malformed | §3.3, §5.3 step 2 |
isni_check_character | §3.3, §5.3 step 2 |
works_malformed | §5.3 step 1 |
isrc_repeated | §5.3 step 3 |
iswc_repeated | §5.3 step 3 |
works_signature_invalid | §5.3 step 4 |
works_package_mismatch | §5.3 step 5 |
works_component_unknown | §5.3 step 6 |
cue_event_malformed | §7.2 step 1 |
cue_wrong_room | §7.2 step 2 |
cue_signature_invalid | §7.2 step 3 |
cue_not_meta | §7.2 step 4 |
cue_no_magic | §7.2 step 5 |
cue_malformed | §7.2 step 6, §9.4 step 4 |
cue_intent_unknown | §9.4 step 4 |
fingerprint_malformed | §8.3 step 1 |
fingerprint_signature_invalid | §8.3 step 2 |
fingerprint_wrong_room | §8.3 step 3 |
fingerprint_chunks_mismatch | §8.3 step 4 |
fingerprint_span_mismatch | §8.3 step 5 |
report_malformed | §9.4 step 1 |
report_signature_invalid | §9.4 step 2 |
report_wrong_room | §9.4 step 3 |
report_event_invalid | §9.4 step 4 |
report_fingerprint_missing | §9.4 step 5 |
report_fingerprint_outside | §9.4 step 5 |
report_line_missing | §9.4 step 6 |
report_line_extra | §9.4 step 6 |
report_identifier_invented | §9.4 step 6 |
report_work_mismatch | §9.4 step 6 |
report_span_mismatch | §9.4 step 6 |
report_duration_unknown_as_zero | §9.4 step 6 |
report_duration_mismatch | §9.4 step 6 |
report_evidence_mismatch | §9.4 step 6 |
rights_malformed | §11.2 step 1 |
rights_signature_invalid | §11.2 step 2 |
rights_wrong_room | §11.2 step 3 |
rights_recording_mismatch | §11.2 step 4 |
rights_report_mismatch | §11.2 step 5 |
rights_unknown | §11.3 steps 1 and 2 |
rights_live_only | §11.3 step 1 |
rights_territory | §11.3 step 1 |
rights_term | §11.3 step 1 |
13. Conformance
live-conformance/music-rights/ holds the corpus, in one
file, vectors.json, written from fixed seeds by wai_music_rights_vectors gen. It has:
- identifiers (§3): strings read as an ISRC, an ISWC or an ISNI, each read, with its display form where §3 defines one, or refused with its reason;
- works (§5): a works document’s text and the package it names, accepted with its digest, its counts and its unknown identifiers, or refused with its reason;
- cues (§7): an event’s record read as a work cue, or refused with its reason;
- fingerprints (§8): a fingerprint statement’s text, verified against the room and its takes
(the corpus’s
takes, unless the case gives its own), accepted with its Audio-Code, or refused; - reports (§9): a show’s events, the fingerprint statements given and a report’s text, recomputed with its counts, or refused with its reason;
- forms (§10): a report’s text and the rows it gives a setlist form;
- rights (§11.2): a rights record’s text, the recording manifest’s digest and the report it names, read or refused with its reason;
- clearances (§11.3): a rights record and its inputs, a window and a use, cleared or not, with the reason.
Every reason of §12 has a case refused with it, and the accepted cases include documents whose identifiers are all known and documents that state some unknown, and reports with a performance whose end no evidence states, a fingerprint no reference reaches and one two works reach alike. Among the refused cases, each a control of one defect: an ISWC whose check digit is wrong; an ISNI whose check character is wrong; an ISRC in lower case; one ISRC named by two recordings; a recording in a component the package does not hold; a report that states an ISWC no cue states; a report that writes an unknown duration as 0; a report that drops a line, and one that calls a matched line declared; a replay of a work cleared for the live moment only; and a window over a performance whose end no evidence states, past the last entry’s end.
A conforming implementation gives every case the outcome the corpus states.
wai_music_rights_vectors verify and the test tests/music_rights.rs check that the file
regenerates byte for byte and that wai-rs gives every case its outcome.
live-conformance/music_rights_verify.py is the second implementation, written from this text
and sharing no code with wai-rs; it also mutates copies of the corpus and drops each of its own
checks in turn, and requires each to be caught.
14. Security and privacy considerations
- An identifier is a claim of its writer. A works document’s signature says who states that a recording is the one an ISRC names, not that the ISRC’s agency agrees. A verifier checks form and check characters; whether a code was assigned, and to what, is answered only by the agency’s database, and a well-formed code can still be wrong or stolen.
- A check character catches slips, not forgery. The ISNI’s check character catches every mistyped digit and every swap of two adjacent digits. The ISWC’s check digit catches every swap of two adjacent digits, and a mistyped digit unless its weight times the change is a multiple of 10 (a digit changed by 5 at an even weight, or by an even amount at weight 5). Anyone can compute either for a code of their own making.
- Names of people. A document names writers, publishers and artists by the names they are publicly known by, and an ISNI names a public identity, which the ISNI agency describes as the minimum needed to tell two public identities apart. A document carries nothing about a party but the name and the identifier, and states no share, contract or payment.
- Unknown is not zero. An unknown identifier is
null(§3.4), and an end no evidence states isnull(§9.2): a field filled to look complete would be a statement nobody made. - A cue is its author’s statement. Any principal whose policy permits
metacan send a work cue; the room’s event policy and grants decide who can, and a report counts every cue the room carried. Each line names the cues that declare it, so a reader that counts only some authors’ declarations can see whose they are. - A fingerprint statement is its matcher’s. WAI computes no fingerprint from samples: a verifier holds a statement to the chunks it names and their span, and takes the fingerprint as the matcher states it. A match is a similarity under a threshold, not proof that a work was performed (iscc §5); a report’s references are its signer’s choice, and a report against other references gives other lines.
- A rights record is its signer’s statement. It says what the signer holds, in this text’s three scopes; it is not a licence, and WAI does not check it against one. A territory code is the signer’s, and a presenter states the territory and the instant it presents in. A window a record clears is cleared on that statement only.
- Automatic identification finds part of a show. A fingerprint unmatched or ambiguous is counted, never turned into a line; a work performed with no cue and no matching reference does not appear. A report states what its evidence shows, and is complete only where its evidence is.