คู่มือ

คู่มือสำหรับเทศกาลภาพยนตร์และตลาด

วิธีที่เทศกาลภาพยนตร์และตลาดใช้ INDEX ตรวจสอบผลงานที่ส่งเข้ามา กำหนดข้อกำหนดการเปิดเผยการใช้ AI และมอบเกียรติรางวัลที่ตรวจสอบได้

ฉบับ 1.0เผยแพร่เมื่อ 21 พฤศจิกายน 2569ใช้เวลาอ่าน 6 นาทีLire en français
เอกสารนี้เผยแพร่เป็นภาษาฝรั่งเศสและภาษาอังกฤษ โดยฉบับภาษาอังกฤษเป็นฉบับอ้างอิง ข้อความด้านล่างเป็นฉบับภาษาอังกฤษ

01Why use INDEX IDs

Festivals and markets receive works from many countries, in several versions, with very different practices on AI disclosure. An INDEX ID lets a selection team identify each work by a permanent reference, check that the screener received is a file bound to the record, read a structured AI disclosure and see what accredited parties have verified.

Verification is free for anyone, needs no account and works through the Verify page or the public API. INDEX records registration facts and verification scope, supporting the recognition of rights worldwide; it does not decide who owns a work, and your eligibility decisions remain your own.

02Requiring INDEX IDs in submissions

  1. Add an INDEX ID field to the submission form. Accept spaces, hyphens, dots and lower case, then normalise the input to ten upper-case characters.
  2. Check the format. The alphabet is 23456789ABCDEFGHJKMNPQRSTUVWXYZ; 0, 1, I, L and O are never used. IDs assigned by the Registry end with a check character: giving each character its position in the alphabet (2 = 0 … Z = 30), the sum of position in the ID (1 to 10) × value is divisible by 31. Identifiers issued before the Registry opened have no check character, so if the check fails, verify the ID online before rejecting it.
  3. Never correct characters silently. Treat a character outside the alphabet as a possible typing error and ask the entrant to confirm the intended ID.
  4. If you require BOUND or higher, ask for the certificate number (IC-{ID}-{nn}) as well.
  5. Ask entrants to have their registrar add your submission number to the record as an external identifier, which links the record and your submission in both directions.
  6. State in your rules the level required and the date at which it is assessed.

03Verifying a submission

Enter the INDEX ID, certificate number or SHA-256 fingerprint on the Verify page (index.film/verify), or scan the QR code of a printed certificate. Results come from the live register.

ResultMeaningSuggested action
Valid certificateThe certificate is the current versionProceed
Updated by a newer versionA newer certificate exists, for example after a level changeAsk for the current certificate and note the level
Being issuedThe certificate is being preparedCheck again shortly
No certificate yetThe work is registered but not yet BOUNDApply your rules for REGISTERED works
Under reviewThe record is disputed: a complaint is being examinedSee the last clause of this guide
WithdrawnThe record has been revokedDo not rely on the record

Matching the screener

Compute the SHA-256 of the screener you received and enter it on the Verify page. An exact match shows that the file is identical, bit for bit, to a file bound to the record, with its role and cut version. A mismatch is not in itself a sign of bad faith: any re-encoding, including by a submission platform, changes the fingerprint. Ask the entrant for the bound file, or for the registrar to bind the screener actually supplied. Where an ISCC code is bound, the API lookup can also report similar content with a similarity score.

04Reading levels and AI disclosure

Open the record at index.film/{ID} and note who stands behind each statement.

  • Declared fields come from the registrant, which is answerable for them, but have not been checked.
  • Verified fields name the issuer, basis, date and scope.
  • The level summarises the highest assurance reached; the attestations listed show each verification, clearance and honour with its status (valid, suspended or revoked).
  • The version history shows when each field last changed.

Every record carries an AI disclosure: a summary, generated imagery, synthetic performers, synthetic voice, real-person likeness (none, consented or unspecified) and the tools used. It is declared unless an AI disclosure review appears among the verified scopes. Pay particular attention to likeness marked “unspecified”. Where present, the AI-use policy states the rights holder’s position on training, fine-tuning, style or character reference and voice or likeness.

05Setting eligibility rules

INDEX sets no eligibility rules for festivals or markets. The following model provisions show how its elements can be used; adapt them to your sections and calendar.

  • “Every work submitted to [section] must have an INDEX ID at level BOUND or higher on the submission deadline.”
  • “The screener supplied must match a SHA-256 fingerprint bound to the record, unless the entrant explains the difference.”
  • “The AI disclosure must be complete and consistent with any disclosure card in the work’s titles.”
  • “Entrants whose record shows real-person likeness as ‘unspecified’ must provide a written statement before selection.”
  • “Works presented in market screenings must be VERIFIED.”
  • “A work whose record is disputed may be held pending the outcome; a work whose record is revoked is withdrawn.”

Publish the rules with your call for entries and apply them consistently. In your communications, do not present an INDEX level as a ruling on ownership.

06Becoming a partner and issuing Certificates of Honour

Festivals and markets can join the INDEX network as partners. Accredited partners act as issuers and record their honours — selections, awards and other distinctions — as signed credentials linked to the work’s record.

  1. Apply for partnership on the Apply page (index.film/apply). Issuer applications are reviewed by the Accreditation and Compliance Committee, which recommends accreditation to the Governing Council.
  2. On accreditation, the festival receives a did:web issuer identity, a member code and member marks, and the right to issue honours through the Registry API.
  3. For each honour, record the edition, programme or section, distinction, recipient, an optional citation, the award date and your own decision reference.
  4. The Registry links the honour to the record and, on request, generates a Certificate of Honour numbered HN-{ID}-{nn}: an A4 landscape document carrying the INDEX verification strip, in any of the eleven certificate languages.
  5. The honour appears on the record with the festival as issuer. If an honour is withdrawn, the festival suspends or revokes it.

The honour is the festival’s own statement; the Registry does not review the decision. Complaints about an issuer’s attestation, including an honour, fall within the scope of the IDRP.

07Integrating through the API

The Registry API is documented at index.film/developers and described by the OpenAPI contract at index.film/openapi.yaml. Public endpoints need no key; rate limits apply.

TaskEndpoint (api.index.film/v1)
Read a public record (JSON-LD)GET /public/records/{ID}
Read an earlier versionGET /public/records/{ID}/versions/{n}
Check a certificate versionGET /public/verify/{ID}?v={n}
Look up a fileGET /public/lookup?sha256={hash}
Retrieve a signed credentialGET /public/credentials/{credentialId}
List accredited registrarsGET /public/registrars
  • On submission, validate the ID, fetch the record and store its version number, so that you know which version your selectors saw.
  • Re-check status and level before selection announcements, catalogue printing and award ceremonies.
  • Aliases redirect to the canonical INDEX ID, and a merged record points to the surviving record. Store the canonical ID.
  • Test integrations, including honour issuance, in the sandbox at api-sandbox.index.film before going live. Errors follow RFC 9457.

08Handling a disputed or revoked record

A record is flagged as disputed when a complaint under the INDEX Dispute Resolution Policy (IDRP) appears well-founded on its face. The flag is an interim measure, not a decision. The Verify page shows “Under review”, and related credentials are suspended while the matter is examined.

  1. Note the status and the date you checked it, and inform the entrant.
  2. Apply your published rules: keep the work under consideration, hold your decision, or select it provisionally subject to the outcome.
  3. Follow the record. IDRP decisions are reasoned, written and published with personal data anonymised. They are implemented ten business days after notification unless a party shows it has started court proceedings, in which case the record stays flagged until the court decides.
  4. If the record is revoked, it verifies as “Withdrawn”. Treat its information as no longer reliable and review any honour you recorded for it.

If your team holds evidence that a record is materially false or misleading — for example an inaccurate AI disclosure — you may file a complaint with that evidence at legal@index.film. If an honour you issued is challenged, you are notified as the issuer and may respond.

09Further reading

The Verify page (index.film/verify) and the developer documentation (index.film/developers) cover verification and integration. The INDEX Standard (index.film/standard) and the Glossary (index.film/knowledge/glossary) define the record, levels and documents. Partnership applications are made on the Apply page (index.film/apply). See also the INDEX Dispute Resolution Policy (index.film/policies/disputes), the brand and mark usage guidelines (index.film/policies/brand) on showing seals in catalogues, and the authenticity and anti-counterfeiting notice (index.film/policies/authenticity).

This guide is for general information only and does not constitute legal advice.

การสมัคร

ร่วมเป็นส่วนหนึ่งของเครือข่ายศูนย์ทะเบียนระดับโลก

คู่มือสำหรับเทศกาลภาพยนตร์และตลาด · INDEX.FILM