Skip to content

Latest commit

 

History

History
31 lines (16 loc) · 1.45 KB

File metadata and controls

31 lines (16 loc) · 1.45 KB

FAQ

AIM stands for Attribution & Ingestion Manifest for Music.

Is AIM an audio codec?

No. AIM is a package format and specification layer around media assets, metadata, references, editing lineage, provenance pointers, and conformance rules.

Is AIM only for karaoke?

No. Karaoke is one important subset, but AIM also covers AI-editable audio, WEB multi-track playback, and disclosure-ready downstream workflows.

Is AIM a disclosure schema?

No. AIM is a container and workflow layer that can carry or generate downstream disclosures such as Apple XML, DDEX-oriented credits, C2PA pointers, and machine-readable no-AI or AI-involvement statements.

What does aim.disclosure_ready.v1 mean?

It means the package has the structural basis required for disclosure-oriented downstream handling. It does not imply that every possible downstream export has already been materialized by every tool.

Does aim.signed.v1 mean authenticity has already been verified?

No. It indicates that the package has the structural fields needed for a signed-attached shape. Signature trust and authenticity verification remain external to the AIM specification.

Why release the spec before all tools are finished?

Because the format can be reviewed, implemented, and tested independently of any single converter, player, or editor.

Are the examples production media assets?

No. They are small structural examples intended to make the spec easier to understand and test.