The framework depends on one other document for its vocabulary: ISO/IEC 22989, the AI concepts and terminology standard.
What the base framework establishes
The clause makes ISO/IEC 22989 the source of the terms used in this document. The reference is undated, so the current edition of 22989, including its amendments, applies. That detail matters more than it looks: 22989 has its own Amendment 1 on generative AI in the same approval pipeline, so a change there reaches this framework's vocabulary without any change to 23053 itself. The clause also tells the reader where the official term databases live, which is the route to check a definition rather than rely on a summary.
Why it matters to an AI management system
A vocabulary dependency is easy to ignore until two documents define the same word differently. By naming 22989, the framework keeps one dictionary for AI concepts. A governance team that tracks 23053 without tracking 22989 is watching one half of a pair.
The public draft summary names no change to 2 Normative references. The final text could still touch it.
Evidence a reviewer samples
| Category | Artefact |
|---|---|
| Reference register | The list of standards cited in the AI system description, with edition and amendment status. |
| Watch record | The dated check of ISO/IEC 22989 and its Amendment 1 against the register. |
| Glossary | The internal glossary that maps each term to its standard source. |
One question to prepare for. Which edition of the terminology standard is your glossary actually built on?
Common gaps
- The register cites 23053 but not 22989, so the terminology line is invisible.
- A dated reference is used where the standard leaves it undated, freezing an old definition.
- The glossary paraphrases terms without saying which edition it read.
Prepare before publication
Add both documents to the reference register and mark the 22989 amendment as a watched item. Give the glossary a column for the source edition.
Dates that matter
No separate date attaches to 2; the record dates are the stage date, the planning estimate and the CEN expectation stated above.
Cross-references
3.1 Model development and use · 3.2 Tools · 3.3 Data · 5 Overview
Source
Source for 2: ISO/IEC 23053:2022, clause 2. The statement is read from the public base sample at 2 and is written in our words. The two official records are linked on this page so any line can be checked.
Not legal advice; does not certify. A reading of the framework and the evidence a reviewer commonly samples, not a substitute for the standard or your auditor's rules.