Asset Naming Schema (OSC v1.0)
The production-wide file naming convention for One Small Crawl, extending TR-VFX-IS with asset origin, agent/vendor codes, era codes, and the OMC version model. Every asset name encodes its full provenance.
Syntax
<showid>_<vfx-sequence>_<vfx-shot>_<image-type>_<origin>_<vendor-code>_<version-code>{_<era>}{_<identifying-description>}{_<spec-version>}{.<frame-number>}.<file-extension>
Example: osc_sc02_0100_anim_gen_a003_v003_nr_snail-walk.1001.exr = show osc, scene 02 shot 0100, animation, AI-generated, agent a003, version v003, era ntrl, snail-walk, frame 1001.
Key fields
- origin: arc (archive), enh (ai_enhanced), gen (ai_generated), cmp (composite), etc.
- vendor-code: AGT-xxx agent ids (a003 = Gen-Video, a019 = Enhancement…)
- era: sf/snd/kch/vhs/dig/ntrl from the era-look-guide
- version-code: integrates OMC v2.8 versioning
- omission rule: keep underscores for omitted optional fields
Why it matters
- asset_origin lets the production answer “what did we do with your footage?” for archive licensors - the legal defensibility of the hybrid pipeline.
- Era codes keep every layer’s look metadata machine-readable.
- Naming is the surface of the omc-ontology model; each shot also has an OMC sidecar JSON with the same id.
Notes
- sc02 era code snd is still placeholder - must be ratified in naming-key xlsx.
- See naming-schema raw note, omc-ontology, ai-agent-pipeline, one-small-crawl. The VES/ETC principles this schema extends are recorded in ves-good-practices.