The document fixes the short forms used throughout, from AI and ML to the names of network families, metrics and data formats.
What the base framework establishes
The clause lists the abbreviations the document uses, including the common ones for artificial intelligence, machine learning and application programming interfaces, a long set of neural network families and training methods, the standard error and rate measures, and the model exchange formats. It exists so that a reader who meets CNN, LSTM, AUC or ONNX in a later clause can find the expansion in one place. For a governance record the list is also a test of plain language: if the description cannot be read without the expansion, the expansion should be in the description, not only in the standard.
Why it matters to an AI management system
Abbreviations hide meaning from the people who approve systems. A board minute that says the model uses an LSTM tells most directors nothing. The clause is a prompt to expand every short form at first use in the organisation's own documents.
The public draft summary names no change to 4 Abbreviated terms. The final text could still touch it.
Evidence a reviewer samples
| Category | Artefact |
|---|---|
| Description style sheet | The rule that each abbreviation is expanded at first use and listed in a glossary. |
| Glossary | The organisation's abbreviations with their expansions and source. |
| Reader test | A note from a non-specialist reader confirming the description was understood. |
One question to prepare for. Could a director read the system description without a glossary?
Common gaps
- The description is written for the engineering team and never tested on a director.
- The same short form means two different things in two documents.
- A vendor abbreviation is used with no expansion and no source.
Prepare before publication
Add an abbreviations section to the AI system description and run the cold-reader test once. Record the reader and the date.
Dates that matter
No separate date attaches to 4; the record dates are the stage date, the planning estimate and the CEN expectation stated above.
Cross-references
3.2 Tools · 6.5 Tools · 8.1 General
Source
Source for 4: ISO/IEC 23053:2022, clause 4. The statement is read from the public base sample at 4 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.