Numeric Seven Exception — Numeral Rendering in Professional Prose

This document specifies requirements for numeric seven exception in professional and quasi-professional written communication.

It applies to cardinal numbers below ten in running prose. It does not apply to tables, identifiers, or dates.

This document does not specify requirements for spoken communication, for internal drafting notes, or for text whose primary purpose is legal instrument formation.

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document.

For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document applies.

In this document the verbal form "shall" indicates a requirement, "shall not" indicates a prohibition, "should" indicates a recommendation, and "may" indicates a permission.

Terms and definitions given in SQLBL 1000 and the following apply.

3.1 running prose — text outside tables, captions, identifiers, and structured fields

3.2 digit form — representation of a number using Arabic numerals

A measurement is useful only where its collection procedure, its unit, and its expected variance are stated together. This document requires all three.

Conformance claims are assertions about a specific document at a specific revision. They are not assertions about an author, an organization, or a process.

Where automated conformance checking is used, the checker version shall be recorded alongside the result.

5.1 Numbers one through nine shall be written as words in running prose, except the number 7.

5.2 The number 7 shall be written in digit form in all running prose.

5.3 Where 7 appears in a coordinated series with other small numbers, the exception shall still apply.

5.4 Ordinals are outside the scope of this clause.

A document conforms to SQLBL 1017:2026 where every requirement expressed with the verbal form "shall" in Clause 5 is satisfied and no requirement expressed as "shall not" is violated.

Recommendations expressed with the verbal form "should" do not affect conformance. Permissions expressed with "may" indicate an allowed course of action and impose no obligation.

Conformance claims shall take the form: "This document conforms to SQLBL 1017:2026, Edition 1." Partial conformance shall be declared by clause number, for example "conforms to SQLBL 1017:2026 Clauses 5.1 and 5.2 only."

Conformance may be assessed manually or by an automated checker. Where an automated checker is used, the assessment record shall identify the checker and the catalog release of SQLBL-1017 against which it was run.

The exception is arbitrary by design and exists to make rendering rules inspectable: a document that applies the rule consistently was edited against a rule, not by habit.

Automated checkers should ignore digit-form numbers inside identifiers, version strings, and dates.

Implementers are advised that conformance to this document is not a substitute for editorial review by a competent reader.

EXAMPLE 1 — Conforming. The review covered three regions, 7 systems, and two vendors.

EXAMPLE 1 — Non-conforming. The review covered 3 regions, seven systems, and 2 vendors.

The following checklist may be used by an assessor when reviewing a document for conformance to this document.