ISO/IEC 9075-10:2023/Cor 1:2026

• Status: Published
• Publication Date: 02-Aug-2026
• ICS: 35.060 - Languages used in information technology
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 3 - Database language
• Current Stage: 6060 - International Standard published
• Start Date: 03-Aug-2026
• Completion Date: 03-Aug-2026

• Corrects: ISO/IEC 9075-10:2023 - Information technology — Database languages SQL — Part 10: Object language bindings (SQL/OLB)
• Effective Date: 07-Jan-2026

ISO/IEC 9075-10:2023/Cor 1:2026 is an ISO/IEC technical corrigendum for the SQL database language series, focused on Part 10, Object language bindings (SQL/OLB). It corrects conformance wording in the object language bindings part of SQL, so implementers and conformance checkers can apply the amended rules consistently. This document is for people maintaining, testing, or claiming support for SQL/OLB.

What does ISO/IEC 9075-10:2023/Cor 1:2026 specify?

ISO/IEC 9075-10:2023/Cor 1:2026 specifies corrections to ISO/IEC 9075-10:2023, not a new standalone feature set. The corrigendum is organized around two targeted changes in Clause 9 and Clause 14, both dealing with conformance rules around compound statements.

Clause	What it covers
9.2 <compoundstatement>	Deletes Conformance Rule 1 after a stated rationale.
14.11 <statementclause>	Replaces an over-restrictive conformance rule and inserts a new Conformance Rule 2.

In practice, the document is a small amendment package. Readers use it together with ISO/IEC 9075-10:2023 when checking whether an SQL/OLB implementation is conforming.

What are the key requirements of ISO/IEC 9075-10:2023/Cor 1:2026?

The corrigendum changes conformance language in two places, and those changes affect what a conforming SQL language may contain.

• Clause 9.2 <compoundstatement> deletes Conformance Rule 1. In practice, this removes a rule that had been too restrictive in that part of the standard.
• Clause 14.11 <statementclause> inserts a new Conformance Rule 2. In practice, this gives a new condition that implementers must check when they support statement clauses.
• The new rule applies when Feature J007, “Compoundstatement”, is not present. In practice, a product that does not claim Feature J007 must not allow a <statementspecclause> that contains a <compoundstatement>.
• The change is written as a conformance restriction, not as a syntax definition. In practice, this matters for declarations of support, validation, and test coverage rather than for adding a new SQL construct.
• The corrected wording is placed under <SQLJspecificclause> and contents. In practice, the affected area is the SQL/J-specific part of the language binding, so vendors should review their binders and documentation there.
• The rationale in both places says the previous wording was over-restrictive. In practice, this signals a narrowing or correction of the rule set rather than a broader expansion of SQL/OLB behavior.

What terms does ISO/IEC 9075-10:2023/Cor 1:2026 define?

The corrigendum uses several key terms and identifiers that matter when reading the corrected rules.

• Technical Corrigendum 1 - A correction document that amends ISO/IEC 9075-10:2023.
• Conformance Rule - A rule that defines what a conforming SQL language may or may not contain.
• Feature J007, “Compoundstatement” - The named feature used as a switch in the conformance rule.
• <compoundstatement> - The SQL grammar element named in Clause 9.2 and Clause 14.11.
• <statementspecclause> - The statement specification clause that is restricted by the new conformance rule.
• <SQLJspecificclause> - The SQL/J-specific clause area where the corrected wording appears.

Who uses ISO/IEC 9075-10:2023/Cor 1:2026?

ISO/IEC 9075-10:2023/Cor 1:2026 is used by SQL database engine vendors, language binding implementers, conformance test teams, and standards-aware buyers or auditors. It matters when a product claims support for SQL/OLB and needs to show exactly which compound-statement forms are allowed. Quality managers and technical reviewers use it to confirm that product claims match the corrected conformance rules.

What changed in ISO/IEC 9075-10:2023/Cor 1:2026 from the previous edition?

ISO/IEC 9075-10:2023/Cor 1:2026 is Technical Corrigendum 1 to ISO/IEC 9075-10:2023. It changes Clause 9.2 and Clause 14.11 by deleting one conformance rule and inserting a new one tied to Feature J007, “Compoundstatement”.

Which standards are used with ISO/IEC 9075-10:2023/Cor 1:2026?

• ISO/IEC 9075-10:2023 - The base standard corrected by this technical corrigendum.

What does the ISO/IEC 9075-10:2023/Cor 1:2026 document contain?

The document contains front matter identifying it as Technical Corrigendum 1 to ISO/IEC 9075-10:2023, prepared by ISO/IEC JTC 1/SC 32. The substantive content is limited to two correction items, one in Clause 9.2 and one in Clause 14.11. Each item gives a rationale and a precise change instruction, either deleting or inserting conformance-rule text. For readers, this means the document is mainly a maintenance text for updating conformance language in SQL/OLB implementations and related test material.

International
Standard
ISO/IEC 9075-10
Fifth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 10:
CORRIGENDUM 1
Object language bindings (SQL/
2026-08
OLB)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données
SQL —
Partie 10: Liaisons de langage objet (SQL/OLB)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-10:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-10:2023/Cor. 1:2026(en)
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: copyr
...