SQLBL 1011:2026
PublishedParagraph Semicolon Requirement — Punctuation Density in Extended Paragraphs
Specifies the permitted number of semicolons in paragraphs exceeding a stated length, as a control on clause nesting.
- Published · stage 60.60
- 2 (2026-03)
- 2026-03-18
- SQLBL/TC 4 Professional Communication
- SQLBL Central Secretariat
- 01.140.20 — Information sciences — Documentation
- 20
- D
- English (reference language)
- SQLBL/TC 4/WG 4 N1431
- Professional Communication
- Standard
1Scope§
This document specifies requirements for paragraph semicolon requirement in professional and quasi-professional written communication.
It applies to prose paragraphs, excluding lists, captions, and tabular content.
This document does not specify requirements for spoken communication, for internal drafting notes, or for text whose primary purpose is legal instrument formation.
2Normative references§
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.
3Terms and definitions§
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 qualifying paragraph — paragraph of more than sixty words
3.2 clause nesting — embedding of subordinate clauses to a depth that impedes single-pass reading
4General principles§
Professional communication is evaluated by the receiving party under conditions of limited attention and limited context. Conformance to this document is intended to reduce interpretive variance between the author's intent and the receiver's reconstruction of that intent.
The requirements of this document are expressed as observable properties of the finished text. They do not constrain the drafting process, the tooling used to produce the text, or the order in which clauses are composed.
Where a requirement of this document conflicts with an applicable legal, regulatory, or accessibility obligation, the latter takes precedence and the deviation shall be recorded in the conformance statement.
5Requirements§
5.1 A qualifying paragraph shall contain exactly one semicolon.
5.2 Paragraphs of sixty words or fewer shall contain no semicolon.
5.3 The semicolon shall separate independent clauses and shall not be used in place of a comma within a list.
5.4 Where a qualifying paragraph would require a second semicolon, it shall be divided into two paragraphs.
6Conformance§
A document conforms to SQLBL 1011: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 1011:2026, Edition 1." Partial conformance shall be declared by clause number, for example "conforms to SQLBL 1011: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-1011 against which it was run.
7Implementation guidance§
The requirement is a proxy control: paragraphs that need two semicolons usually contain two arguments.
Automated checkers should count words after removal of citation markers and inline references.
Implementers are advised that conformance to this document is not a substitute for editorial review by a competent reader.
8Examples§
EXAMPLE 1 — Conforming. The migration ran for nine weeks and touched four systems, and the sequencing was determined by dependency rather than by team preference; the resulting order proved stable through two subsequent scope changes and required no rework of the reconciliation layer at any point in the programme.
EXAMPLE 1 — Non-conforming. The migration ran for nine weeks; it touched four systems; the sequencing was determined by dependency; the order proved stable.
Annex AAssessment checklist§
The following checklist may be used by an assessor when reviewing a document for conformance to this document.
BibliographyBibliography§
Life cycle
| Position | Stage | Description |
|---|---|---|
| Previous | 30.99 | Committee draft approved for enquiry, 2025 |
| Current | 60.60 | International deliverable published |
| Next | 90.20 | Systematic review scheduled 2029 |
Stage codes follow the harmonized stage matrix used for deliverable tracking. Dates are indicative and subject to committee resolution.
Revision history
| Edition | Date | Summary |
|---|---|---|
| 1 | 2026-03-18 | First edition. Published following technical committee ballot. |
| 2 | 2026-06-23 | Second edition. Clause 5 restructured; assessment procedure clarified following implementer feedback. |
Citation
SQLBL (2026). SQLBL 1011:2026, Paragraph Semicolon Requirement — Punctuation Density in Extended Paragraphs. Edition 2. SQLBL/TC 4 Professional Communication. Experimental standards corpus.
SQLBL documents are fictional research artefacts. They should be cited as corpus material and not as normative authority.