01Scope
This Standard specifies the identifier, record, assurance levels, documents and verifiable credentials used by INDEX.FILM, the International AI Audiovisual Asset Registry, to give digital works — films, series, episodes, characters, workflows and worlds — a permanent and independently verifiable identity.
INDEX records registration facts and verification scope, supporting the recognition of rights worldwide. Every statement in an INDEX record names the party that made it, the basis on which it was made and the time at which it was recorded.
The key words MUST, SHOULD and MAY in this document are to be interpreted as described in IETF BCP 14.
02Terms and parties
| Party | Description |
|---|---|
| Registry | INDEX.FILM. Maintains this Standard, assigns INDEX IDs, keeps the authoritative register, signs registration facts and operates public verification. |
| Registrar | An accredited organisation that registers works for registrants, binds content fingerprints and issues verification credentials under its own identity. |
| Issuer | Any party that signs a credential about a work: the Registry, accredited registrars, accredited law firms and festivals. |
| Registrant | The party that declares a work through a registrar and is answerable for the declaration. |
| Verifier | Anyone who checks an INDEX ID, record, certificate or credential. |
03The INDEX ID
| Property | Rule |
|---|---|
| Length | 10 characters |
| Alphabet | 23456789ABCDEFGHJKMNPQRSTUVWXYZ — 31 symbols, excluding 0, 1, I, L and O |
| Case | Case-insensitive; stored and displayed in upper case |
| Display | Grouped 4-4-2 in a monospaced face: 7K3P 9Q2M 4X |
| Links and QR codes | Written continuously: index.film/7K3P9Q2M4X |
| Canonical IRI | https://index.film/{ID} |
| Assignment | Random. An INDEX ID carries no year, category or registrar information and is never reused. |
Check character
INDEX IDs assigned by the Registry end with a check character. With symbol values v₁…v₁₀ taken from their positions in the alphabet, the sum of i × vᵢ for i = 1…10 MUST be divisible by 31. Because 31 is prime, every single-character error and every transposition of adjacent characters is detected.
Identifiers issued before the Registry opened remain valid exactly as issued. Verifiers MUST NOT reject such an identifier for lacking a check character.
Input tolerance
Implementations SHOULD remove spaces, hyphens and dots and convert input to upper case before parsing. Characters outside the alphabet SHOULD be treated as possible typing errors and answered with candidate identifiers; they MUST NOT be silently replaced.
Earlier identifiers
Earlier long-form identifiers, such as IXF-AIF-2026-{ID}, resolve permanently to the same record.
04Permanent addresses
The following addresses are printed on certificates, posters and end cards. Once published they remain valid permanently.
| Address | Content |
|---|---|
| https://index.film/{ID} | Work record (HTML with JSON-LD) |
| https://index.film/{ID}.json | Public record (JSON-LD) |
| https://index.film/{ID}/v/{n} | Record version n |
| https://index.film/verify/{ID}?v={n} | Verification of certificate version n — the target of every certificate QR code |
| https://index.film/d/{number} | Public summary of a certificate or schedule |
| https://index.film/.well-known/did.json | Registry DID document |
| https://index.film/ns/v1 | INDEX JSON-LD vocabulary |
| https://index.film/status/{list} | Credential status lists |
| https://api.index.film/v1/… | Registry API, described by the OpenAPI contract |
05The record
An INDEX record describes one work. Each public field states its source: declared by the registrant, or verified by a named issuer. A verified field that is later changed returns to declared.
| Field | Required from | Notes |
|---|---|---|
| id, aliases | Creation | Canonical INDEX ID and earlier identifiers |
| workType, formType | Creation / BOUND | film, series, episode, character, workflow, world; feature, short, series, episode and others |
| title.original, title.originalLanguage, title.translations | Creation / BOUND | Original spelling preserved; languages tagged with BCP 47 |
| logline, productionYear, durationSeconds | — / BOUND | Logline up to 500 characters |
| originalLanguages, countries, genres, credits | BOUND / — | Countries as ISO 3166-1; up to 30 credits |
| rightsHolder.name | Creation | Shown as the registrant-declared rights holder |
| rightsHolder.legalName, jurisdiction, registrationNumber / LEI / ISNI | VERIFIED | At least one organisational identifier |
| aiDisclosure | Creation / BOUND | Summary, generated imagery, synthetic performers, synthetic voice, real-person likeness, tools |
| aiUsePolicy | — | Training, fine-tuning, style or character reference, voice or likeness: permitted, reserved or by agreement |
| assets[] | BOUND | Role, SHA-256, ISCC, size, media type and cut |
| externalIds, relations | — | EIDR, ISAN, IMDb, festival submission numbers; series, adaptation and derivative relations |
| level, status, version, versionHash, timestamp | System | See clauses 6 and 9 |
| registrar, attestations, currentDocument | System | Issuing parties and current certificate |
06Assurance levels
Assurance levels only increase. Each level is represented by a seal from the INDEX.FILM visual identity.
| Level | Colour | Requirement | Granted by | Document |
|---|---|---|---|---|
| Registered | — | INDEX ID and core fields | Registrar submission | Record page |
| BOUND | #B13D36 | At least one master or screener SHA-256 bound and BOUND fields complete | Registrar submission | Certificate of Registration |
| VERIFIED | #D7AA12 | A verification credential covering at least the rights holder's identity and the registrant's authority | Accredited registrar | Certificate of Registration (re-issued) |
| CLEARED | #216947 | A rights clearance conclusion with territory, media, term and conditions | Accredited law firm | Certificate of Registration and Rights Clearance Schedule |
Seal statements
- BOUND — Submitted files are bound to the record. The registrant's declarations are published with it.
- VERIFIED — The verifier, basis, date and items checked are listed in the record.
- CLEARED — Legal opinion, territory, media, term and conditions are documented in a rights clearance schedule.
07Documents
| Document | Format | Number | Issuer |
|---|---|---|---|
| Certificate of Registration | A4 portrait | IC-{ID}-{nn} | Registry, with the submitting registrar |
| Rights Clearance Schedule | A4 portrait | RS-{ID}-A{nn} | Accredited law firm |
| Certificate of Honour | A4 landscape | Assigned by the festival | Festival, carrying the INDEX verification strip |
- A Certificate of Registration is issued from level BOUND, once content fingerprints are bound.
- Each work has one current Certificate of Registration. A change of level issues a new version; earlier versions keep their signatures and verify as updated by a newer version.
- Every certificate carries a QR code to index.film/verify/{ID}?v={n} (error correction level Q, printed at 22 mm or larger) and embeds its signed credential.
- Every certificate is issued in English, the reference edition, together with an edition in the official language of the jurisdiction concerned: the rights holder's jurisdiction, failing that the first country of production, failing that the sponsoring registrar's country. Where that language is English, the certificate is issued in English only.
- Editions are available in eleven languages: English, French, German, Spanish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese, Korean, Thai and Arabic. A registrar may request further editions at any time. All editions of a certificate share one certificate number, one QR code and one signed credential; where editions differ, the English edition prevails.
- Arabic text runs right to left; identifiers, domains and hashes run left to right. Titles keep their original spelling and script in every edition.
- Certificates are titled “Certificate of Registration” and carry the statement: “This certificate attests the registration facts and verification scope listed, supporting the recognition of rights worldwide. The live record at index.film is authoritative.”
08Verifiable credentials
| Credential | Issuer | Principal claims |
|---|---|---|
| RegistrationCredential | did:web:index.film | INDEX ID, title, declared rights holder, content fingerprints, registrar, registration time, record version hash |
| VerificationCredential | Registrar DID | Verification scope, basis, verifier reference, date, evidence hash references |
| ClearanceCredential | Law firm DID | Conclusion, scope of review, territory, media, term, exclusions, counsel and opinion reference |
| HonourCredential | Festival DID | Edition, section, honour, recipient, citation and decision reference |
- Credentials conform to the W3C Verifiable Credentials Data Model 2.0.
- Proofs are DataIntegrityProof with the eddsa-jcs-2022 cryptosuite (Ed25519, RFC 8032; JSON canonicalised with RFC 8785).
- Each credential carries credentialStatus entries of type BitstringStatusListEntry for revocation and suspension.
- The credential subject is https://index.film/{ID}. Issuers are identified by did:web.
09Versions and evidence
Every change to a record creates a new version. The version content is canonicalised with RFC 8785 and hashed with SHA-256 (FIPS 180-4) to produce versionHash, which includes the hash of the previous version and so forms a hash chain.
Each versionHash is time-stamped by a trusted time-stamping authority under RFC 3161. The time-stamp token is published with the version and can be verified with standard tools.
versionHash = SHA-256( JCS( { indexId, iri, registrar, version, level, status,
record, registrantRefHash, assets, previousVersionHash, recordedAt } ) )10Content fingerprints
- A SHA-256 digest is required for every bound file. An ISCC code (ISO 24138) MAY be added to support discovery of copies across formats.
- File roles: master, screener, trailer, poster, still, subtitle, audio, project_file, other.
- The Registry receives fingerprints only. Files remain with the registrant or registrar.
- A master fingerprint belongs to one work.
- Fingerprints may be retired; retired fingerprints remain in the record history.
11Verification
Anyone can verify an INDEX ID, a certificate number or a content fingerprint at index.film/verify or through the public API. A verification response states one of the following results:
| Result | Meaning |
|---|---|
| Valid certificate | The certificate is the current version for the work. |
| Updated by a newer version | A newer certificate has been issued; its number is given. |
| Being issued | The certificate is being prepared. |
| Under review | The registry is reviewing a rights matter and publishes the outcome on the record. |
| Withdrawn | The record has been withdrawn following registry review. |
Signatures, status lists and time-stamps can also be checked offline with any implementation of the referenced specifications.
12Privacy
- The Registry stores an opaque registrant reference supplied by the registrar, not the registrant's personal contact details.
- Verification materials, contracts and consents enter the Registry as hash references; originals remain with the issuing party.
- Public pages show only the fields marked public in clause 5. For individual rights holders, only the name is published.
13Normative references
- W3C — Verifiable Credentials Data Model v2.0
- W3C — Decentralized Identifiers (DIDs) v1.0; did:web method
- W3C — Data Integrity EdDSA Cryptosuites v1.0 (eddsa-jcs-2022)
- W3C — Bitstring Status List v1.0
- W3C — JSON-LD 1.1
- IETF — RFC 3161 Time-Stamp Protocol
- IETF — RFC 8785 JSON Canonicalization Scheme
- IETF — RFC 8032 Edwards-Curve Digital Signature Algorithm
- IETF — RFC 9457 Problem Details for HTTP APIs
- IETF — BCP 14 Key words; BCP 47 Tags for Identifying Languages
- NIST — FIPS 180-4 Secure Hash Standard
- ISO — ISO 24138 International Standard Content Code; ISO 3166-1 Country codes
- OpenAPI Initiative — OpenAPI Specification 3.1