The rule that a specification names only terms the ontology defines (commons 0018-standards-firstFR-001, 0003-mizanFR-019): every prefixed name in code font whose prefix is one of the ontologies given (mz:Rung, pm:PackageManager) must be a term of that ontology, a class, a property or an individual of a code list. A prefix that is not given (schema:, skos:, a standard's own) is not read: the standard defines it, and an import that holds it makes its use compile.
A second rule goes the other way (0003-mizanFR-044): a requirement that names a term of the ontology in code font must be cited back by that term's mz:definedBy, so that the requirement and the term are two ends of one link (the requirement-to-term stage of the trace chain, 0020-ifccmFR-014).
Pure over text. Prefixed names are read only inside backticks, so that a sentence's colon, a URL or a **Status:** is not one.
The definitions of the terms of audit records, by CURIE: the IRI of each record is written with the first of prefixes (a prefix and its namespace) that begins it, and carries what its definedBy says. A term of no given namespace is left out.
The requirement-to-term stage of the trace (0003-mizanFR-044): for each requirement that names a term of a given ontology in code font (mz:Rung), the term must say, in mz:definedBy, that the requirement defines it. One finding for each requirement and term: where the term states no definedBy, and where it states others and not this requirement. A requirement that names a term the ontology does not define is mizan/spec-term-unknown's, and a prefix not given is not read. The findings are warnings a baseline holds.