IXF Standard · Maintained by IAISA

AI Summary

The IXF Standard (Index.Film AI Audiovisual Asset Indexing Standard) is maintained by IAISA (International AI Audiovisual Asset Indexing Standards Alliance) as the INDEX registry authority. It defines four cores: the identity model (Public Code, Root ID, Machine URN), the record model (four index states and a common data spine), machine-readable endpoints (index.json, schema.jsonld, rights.json and more), and the registrar system (Accredited Registrar program and Registrar API). The standard maintains interoperability mapping with ISAN/EIDR, IMDb, IPTC, Schema.org/JSON-LD and C2PA. HKAIIFF Index provides the registration service channel built on the IXF Standard.

Governance

IAISA maintains the standard as the INDEX registry authority; HKAIIFF Index provides the registration service channel built on the IXF Standard. Four parts with clear roles: IAISA — maintains the IXF Standard and the governance framework for AI-native audiovisual asset indexing; IXF Standard — defines Root ID rules, resolver URLs, metadata schemas, endpoints, registrar APIs and Agent Request actions; Index.Film Registry — hosts public records, AI-readable endpoints and market-ready metadata at index.film/{code}; Accredited Registrars — approved partners that register assets and integrate Index.Film data services into their own systems. The value of the standard is operational trust.

Common data spine

All asset classes share a common data spine so that public pages, endpoints, market metadata and registrar APIs use compatible fields: Identity (title, alternate_title, asset_type, public_code, root_id) | Creator (director, producer, studio, contributors, owner) | AI Usage (writing, direction, generation, editing, sound, finishing, tools, participation) | Rights (rights_holder, license_status, territories, restrictions, third_party_materials) | Version (version_number, manifest_hash, content_hash, change_note) | ASK (ai_summary, Q&A, keywords, buyer_questions, multilingual_snippets) | Market (market_intent, availability, request_actions, market_status).

AI-readable endpoints

Public pages are for people; endpoints are for search, retrieval pipelines, buyers, registrars and external agents. Core endpoints: index.json — asset master record (identity, type, title, summary, status and core fields); schema.jsonld — web semantic layer using Schema.org/JSON-LD for search and AI retrieval pipelines; rights.json — rights declaration and license intent (owner, available rights, restrictions, third-party materials); credential.json — index credential (Root ID, issuer, status, review, signature and revocation); manifest.json — version and hash (version, manifest_hash, content_hash, change note). Smart and market endpoints: ask.json (published Q&A layer), keywords.json (keyword clusters), faq.schema.json, actions.json (Agent Request actions), market-signals.json (market signals), matching-profile.json (matching profile), agent.json (agent operating profile for external systems).

Accredited Registrar program

Platforms, institutions, tool companies, model companies, associations and market organizations can apply as accredited registrars in five types: Program Registrar — batch-create Free/Basic/Pro records for selected, submitted or participating works; Platform Registrar — embed Index.Film registration, pages and data endpoints into platform workflows; Technology Registrar — map tools, models and workflow data into the Index.Film metadata schema; Market Registrar — connect indexed assets to Market Verified, Pitch Page and Buyer Room; Institutional Registrar — provide batch registration and API management for schools, associations, funds and city nodes. Registrar APIs support: creating and updating asset records, submitting for review or activation, opening Basic/Pro index levels, reading public index records and semantic endpoints, and routing market meeting requests.

Standards mapping & interoperability

Index.Film adds AI-native layers to existing audiovisual identifiers: ISAN/EIDR — external work, version, title, edit and supply-chain identifier mapping; IMDb — human-facing reference and sameAs link; IPTC — reference for title, creator, rights, keywords and usage-terms metadata; Schema.org/JSON-LD — Movie, VideoObject, CreativeWork, FAQPage and Action; C2PA — file-level provenance, manifest and validation status; rights.json — rights holder, license status, restrictions, third-party materials and requestable actions; actions.json — request_deck, request_license, request_meeting and owner approval.

Audit, versioning & short-code rules

Every material update records version, hash, actor, timestamp and publication status. Short code set: 23456789ABCDEFGHJKLMNPQRSTUVWXYZ; excluded characters: 0, O, 1, I, L and other confusing characters; recommended 10 characters; generate, check uniqueness and regenerate on collision.

Roadmap (five phases)

Phase 1 · Registry Core — IXF Root ID, resolver, four asset classes, service tiers and AI-readable endpoints; Phase 2 · Registrar Network — accredited registrar program, API keys, dashboard, batch submission and status query; Phase 3 · AI-native Taxonomy v1.0 — AIF taxonomy, Workflow/IP/World schemas, ASK schema and market-ready fields; Phase 4 · Market Intelligence — buyer AI search, shortlist, Agent Request, permissioned data and Buyer Room; Phase 5 · Standards Collaboration — field mapping with metadata, identifiers, provenance, market and technical standards.

Official glossary

IAISA — International AI Audiovisual Asset Indexing Standards Alliance; IXF Standard — Index.Film AI Audiovisual Asset Indexing Standard; Public Code — short code used in index.film/{code}; Root ID — IXF-{ASSET_TYPE}-{YEAR}-{PUBLIC_CODE}, the technical credential number; Index Page — public page showing asset data, status, AI-readable data and market-ready information; INDEX ASK — published Q&A layer generated in backend and confirmed by the holder; Agent Request — buyer or agent action for deck, license, meeting or controlled material request; Accredited Registrar — API-connected partner that can register and publish index pages.

Facts

Full name: Index.Film AI Audiovisual Asset Indexing Standard | Maintained by = IAISA (INDEX registry authority) | Root ID rule = IXF-{ASSET_TYPE}-{YEAR}-{PUBLIC_CODE} | Core endpoints = 5 | Smart & market endpoints = 7 | Registrar types = 5 | Interoperability mapping = ISAN/EIDR · IMDb · IPTC · Schema.org · C2PA | Roadmap = 5 phases

FAQ

What is the relationship between IAISA and HKAIIFF?

IAISA maintains the standard as the INDEX registry authority; HKAIIFF Index provides the registration service channel built on the IXF Standard.

What does the IXF Standard define?

The identity model (Public Code, Root ID, Machine URN), the record model (four index states and a common data spine), AI-readable endpoints and the registrar system (Registrar program and API).

How to become an Accredited Registrar?

Platforms, institutions, tool companies, model companies, associations and market organizations can all apply, connecting via the Registrar API in five types; click Activate to apply at hkaiiff.io.

Does Index.Film conflict with ISAN or IMDb?

No conflict. Index.Film does not replace existing identifiers; it maps fields and adds an AI-native layer on top.

Can anyone read endpoint data?

Public endpoints are readable; market and sensitive data are accessed by permission layer, and every request requires owner approval.

Will the standard evolve?

Yes — it advances along the five-phase roadmap, with every material update managed through versioning and audit records.

Activate Read the full whitepaper →

IXF Standard is maintained by IAISA · index.film is the public resolver