ICEQC-GOV-002 — Standard Numbering and Identification Rules

This document defines the public identifiers used for ICEQC controlled documents, editions, amendments, corrections, language versions, clauses and publication records.

Its purpose is to make every cited requirement unambiguous, durable and independently retrievable across human-readable documents, structured data and the Standards Register.

Every controlled document, edition, language version, clause, scheme, module and publication event shall receive a unique stable identifier.

An identifier shall refer to one defined object and shall never be reassigned to different content, even after withdrawal.

Capitalization, spacing or presentation may vary for accessibility, but the underlying identifier and its meaning shall remain unchanged.

A public controlled document shall use the base designation ICEQC-[FAMILY]-[NUMBER].

ICEQC identifies the issuer; FAMILY identifies the document family; and NUMBER is the stable serial number within that family.

A published text shall additionally identify its edition in the form 'Edition [YEAR]' and shall show its publication and effective dates in the document record.

The base designation identifies the continuing document series; the base designation together with the edition identifies a particular controlled text.

The controlled family codes are GOV for governance and document control, CER for common certification rules and procedures, QF for cross-scheme education-quality requirements, ORG for education-organization schemes and modules, EDT for education-technology service schemes and modules, and PRD for educational-product schemes and modules.

A new family code shall be defined publicly before first use and shall not duplicate, imitate or create ambiguity with an existing ICEQC family.

ICEQC uses the publication year as the public edition identifier unless the Standards Register expressly assigns a more specific controlled edition label.

For example, 'ICEQC-GOV-002, Edition 2026' identifies the controlled 2026 text while ICEQC-GOV-002 alone identifies the document series.

A revised edition published in a later year receives the later year as its edition and retains the same base document number.

More than one full edition of the same document shall not be assigned an indistinguishable edition label.

A controlled amendment shall be identified by the base document number, affected edition, the word 'Amendment', a sequential number and the amendment publication year.

A correction shall use the word 'Correction' in the equivalent position.

Amendment and correction numbers begin at 1 for each affected edition and are never reused.

The consolidated reading view shall identify every amendment or correction incorporated into it and shall preserve access to the originally published edition.

Every normative clause shall have a visible clause number and a stable machine-readable key.

Clause numbering shall express hierarchy by decimal notation, such as 7, 7.2 and 7.2.1.

Renumbering in a new edition shall not change the historical identifiers of the superseded edition.

Where traceability across editions is claimed, the relationship between old and new clause identifiers shall be published in a change or correspondence table.

Each language version shall carry the designation and edition of its source together with a language tag conforming to a recognized Internet language-tag convention.

Examples include en, fr, es, zh-Hans and ar.

A language tag identifies language and, where necessary, script or regional variation; it does not by itself indicate whether the text is authoritative, controlled or informative.

That status shall be stated separately under ICEQC-GOV-007.

A document record shall distinguish at least proposal, working draft, consultation draft, approved for publication, published, superseded and withdrawn status.

Draft identifiers shall not be presented in a manner likely to be confused with a published edition.

A document may change status without changing its base number, but every status change shall be dated and the public record shall identify whether the text has normative effect.

A formal citation shall include the base document number and edition and, where relevant, the clause number and language.

The Standards Register shall provide a permanent edition-specific link for each published edition.

A link containing /latest is a convenience link that resolves to the current edition at the time of access and shall not be used where legal, certification or historical certainty requires an edition-specific citation.

Supersedes, superseded by, amends, corrects, translates, adopts, depends on and is used with are distinct document relationships.

A public record shall identify the relationship, the exact related edition and the date on which the relationship took effect.

A document title, family resemblance or shared subject shall not be treated as evidence that one document replaces or modifies another.

'ICEQC-GOV-002, Edition 2026' denotes the controlled 2026 text; 'ICEQC-GOV-002, Edition 2026, Clause 7' denotes a clause in that text; 'ICEQC-GOV-002, Edition 2026 (fr)' denotes its French-language version; and 'ICEQC-GOV-002, Edition 2026, Amendment 1 (2027)' denotes the first amendment to that edition published in 2027.

An identifier remains reserved after cancellation, supersession or withdrawal.

Erroneously assigned public identifiers shall be marked void with an explanatory record rather than silently deleted or reassigned.

An ICEQC public identifier shall be assigned only under the authority of the Standards Council or another body expressly authorized for the relevant document, scheme, module, certificate or register class.

Assignment confirms identity and reservation within the ICEQC namespace; it does not approve content, confer publication status or authorize certification.

A person preparing a draft may use a clearly marked provisional working reference, but that reference shall not be represented as a reserved public number until assignment is recorded.

The assignment record shall identify the object class, responsible body, date, lifecycle status and any predecessor or parent relationship necessary to prevent ambiguity.

A software-generated value does not acquire authority merely because it is unique.

Where an external service supplies technical identifiers, ICEQC shall retain control of their public meaning, persistence and relationship to the human-readable ICEQC designation.

Each base document number, edition identity, amendment, correction, clause key, scheme code, module code, certificate number and public-register identifier shall resolve to one controlled object of its stated class.

Uniqueness shall be evaluated across active, superseded, withdrawn, void and archived records, not only among current publications.

Identical character strings may exist in different explicitly separated technical classes only where their context can never create reasonable public confusion; public-facing identifiers shall avoid such reliance on hidden context.

Case, punctuation, spacing, Unicode normalization or display styling shall not be used to create identifiers that appear identical to ordinary readers.

A collision shall be treated as an integrity issue, and the later or erroneous assignment shall be voided or corrected without changing the historical meaning of the identifier that was validly assigned first.

The ICEQC identifier namespace shall distinguish institutional documents, certification schemes, applicability modules, clauses and provisions, certification cases and certificates, public-register entries, consultations, amendments, corrections, interpretations and translations.

The visible identifier shall carry enough structure for a reader to recognize its class where confusion could affect reliance, while additional database or storage keys may remain non-public.

A technical identifier shall not replace the controlled public designation in a certificate, citation or reader record.

Namespace rules shall remain stable across changes of platform, domain, supplier or data model, and shall not depend on a directory location that may change.

Creation of a new namespace class shall be documented before public use and shall define its owner, syntax, uniqueness boundary, lifecycle and relationship to existing classes.

A new ICEQC document family code shall consist of a concise uppercase alphabetic designation that is distinct from existing codes and reasonably connected to the public subject or function of the family.

Allocation shall consider possible confusion across languages, similarity to scheme or status abbreviations, accessibility in speech and text, and long-term suitability if the family expands.

A family code shall not be chosen to imply government, accreditation, licensing, endorsement or association with another organization.

Once used in a public identifier, the code shall remain reserved even if the family is discontinued.

A change of family name shall ordinarily preserve the code where continued use does not mislead; if a new code is necessary, the relationship between old and new document series shall be established through explicit successor records rather than renaming historical identifiers.

The numeric component of a document identifier shall be allocated within its family from a controlled range and shall remain stable for the life of the document series.

A serial number identifies the series and shall not be treated as a score, priority, maturity level, ranking or statement that a higher number is more authoritative.

Gaps may be retained for planned architecture, cancelled projects or historical reservations and do not create missing obligations.

Leading zeros used in a controlled designation shall be preserved, because ICEQC-GOV-001 and ICEQC-GOV-1 are not interchangeable public forms.

A number shall not be recycled after a proposal, publication, cancellation or voiding has become part of a controlled record.

Where ranges indicate related schemes or modules, the relationship shall also be stated in metadata rather than inferred solely from numerical proximity.

ICEQC may reserve number ranges for governance, common certification, core quality, organization, technology, product or other document architectures in order to preserve coherent future allocation.

Reservation shall be recorded and shall not be presented as evidence that every number in the range corresponds to an approved or planned document.

A blocked number shall not be assigned where prior public use, external similarity, security risk, offensive meaning or likely transcription error could undermine reliable identification.

Reserved ranges may be amended prospectively, but existing identifiers shall not be renumbered merely to remove a gap or create visual order.

Public architecture information may describe major ranges where useful, while unpublished reservations remain administrative and shall not create normative expectations or a right to a future document.

An ICEQC number is an identifier and shall not by itself communicate quality, sequence of certification achievement, level of recognition, risk class or relative status unless a controlled document expressly defines that separate meaning.

Marketing shall not describe a certificate with a visually larger or lower number as superior, earlier, more official or more comprehensive.

A module number located near a scheme number does not establish applicability without the published scheme and scope record.

Readers shall rely on the title, family, edition, status and documented relationships rather than infer meaning from numerical pattern.

Where a number has a defined architectural function, that function shall be stated consistently in the Standards Register and shall remain distinct from any conformity conclusion.

Each controlled document record shall identify a document type consistent with ICEQC-GOV-003, such as Charter, Rule, Standard, Certification Scheme, Applicability Module, Procedure, Policy, Guidance, Form, Register, Notice or Research Publication.

The type shall describe normative function and shall not be inferred solely from the family code, title or file extension.

A change of type that alters authority or normative effect is a substantive controlled change and shall not be made only by editing metadata.

Where one publication contains normative and informative parts, the record shall state the overall type and the text shall distinguish the status of its components.

Public interfaces, downloads and structured data shall use equivalent type information so that a draft guidance document cannot appear as a published certification standard in one representation.

Every public document shall have one controlled English title approved with the text and associated permanently with the base document number and edition.

The title shall describe the subject accurately, avoid promotional claims and distinguish the document from related standards, schemes and guidance.

Minor typographical correction of a title shall be controlled because citations and permanent links may depend on it; a material change of subject or function normally requires a new edition and may require a new base number.

Translated titles shall identify their language status and shall not replace the English controlled title in language-neutral metadata.

A cover, reader heading, download, register entry, citation record and structured response shall not display materially different controlled titles for the same edition.

A short title or display label may be provided for navigation where it remains a faithful, unambiguous abbreviation of the controlled title.

It shall not omit a limitation in a way that enlarges scope, convert a procedure into a standard, or imply approval, accreditation or recognition absent from the full title.

The document number and full title shall remain available in the same reader context or through an immediate accessible record.

A change to a short title that does not affect identity may be treated as metadata correction, but the earlier form shall remain traceable where it appeared in public citations.

Search and interface constraints shall not justify truncation that makes two different ICEQC documents appear to have the same name.

A public web path may use a lowercase slug derived from the base document number or title, but the path is a retrieval mechanism and not the authoritative identifier.

The canonical slug shall be unique, stable and independent of a temporary campaign, status or language presentation.

If a slug changes, a permanent redirect or equivalent relationship shall preserve existing citations and shall not silently resolve an old edition-specific path to different content.

A path containing a language segment, latest alias or reader tab shall retain connection to the same controlled document record.

The visible page shall display the document number, edition and status so that a user who arrives through a search result can verify identity without relying on the address alone.

The edition field shall identify a complete approved state of a controlled document and shall remain distinct from version label, publication date, effective date and lifecycle status.

ICEQC ordinarily uses the publication year as the edition identifier, consistent with current public records, but may add a controlled distinguishing element where more than one full edition in a year cannot otherwise be identified.

A draft shall not be assigned the same version identifier as the published edition it proposes to replace.

Edition identity shall be repeated consistently in the document, reader data, download name, register record, citation and transition notice.

A corrected representation that does not change normative effect retains the edition, while an amendment or revision shall be identified in accordance with ICEQC-GOV-006.

Where exceptional circumstances require more than one full edition of the same document in a calendar year, each shall have a distinct, human-readable edition label approved before publication.

The label may combine the year with a sequential edition indicator, but shall not resemble an amendment or correction identifier or imply a ranking.

Publication and effective dates shall remain separately recorded and shall not be used as the only distinction in ordinary citations.

The successor relationship, transition and reason for the additional edition shall be public.

ICEQC shall avoid same-year full editions where a controlled amendment can provide clearer traceability, but shall not misuse an amendment where the extent or structure of change makes a new complete edition necessary.

A version label describes the development or publication state in language useful to readers, such as Working Draft, Consultation Draft, Approved for Publication or Edition 2026.

It shall correspond to the lifecycle status and shall not create a second conflicting edition identity.

Terms including final, official, approved, current and authoritative shall be used only where the controlled record supports their ordinary meaning.

A development iteration may include a sequential internal label, but public consultation materials shall carry a stable version identity sufficient to distinguish the exact text commented upon.

Changing a label shall not overwrite the underlying version record or content hash.

Public interfaces shall not suppress a non-published status merely because a shorter title or cleaner display is desired.

Lifecycle status shall be represented by a controlled value whose public meaning is defined under ICEQC-GOV-003 and ICEQC-GOV-006.

A status change is an authorized event associated with a date, responsible authority and content identity; it is not merely a visual badge.

Development, consultation, approved, published, superseded and withdrawn states shall remain distinguishable in structured data and human-readable text.

A draft may share a base document number with the series it may later replace, but shall not share the immutable published version identifier.

A status shall not be inferred from whether a link is publicly accessible, because consultation and archived texts may be public without being current normative requirements.

Each language version shall use a valid recognized language tag and shall associate that tag with the exact edition and version record.

A base language tag may be used where script and regional variation do not affect identification; a script or region subtag shall be added where necessary to prevent ambiguity or support correct presentation.

Tags shall use standardized syntax rather than translated language names, flags or proprietary platform codes.

The language tag does not determine authoritative status, which shall be recorded separately under ICEQC-GOV-007.

A change correcting an invalid tag shall preserve the relationship to earlier links and shall not be represented as a new translation unless the text itself changed.

A script or regional subtag shall be used only where it identifies a materially distinct written representation, terminology set or localization relevant to retrieval and interpretation.

It shall not be used to imply that the standard has been legally adapted to every jurisdiction associated with the tag.

Chinese simplified and traditional scripts, for example, shall be distinguishable where both are published, while an English text need not carry a regional tag merely because it is accessed from a particular country.

A localized informative translation and a controlled translation shall remain separately identified even if their language tags are similar.

The public record shall explain any non-obvious relationship among variants and shall identify the authoritative source edition from which each was prepared.

Language status shall identify whether a text is authoritative, co-authoritative, a controlled translation or an informative translation.

The field shall be visible with the language tag and source-edition relationship and shall not be replaced by an ambiguous label such as official language version.

Only the approval required by ICEQC-GOV-007 may change language status.

A translation may be complete and professionally reviewed while remaining non-authoritative, and metadata shall preserve that distinction.

Search results, downloads and structured responses shall not give a non-authoritative text greater visual precedence without displaying the authoritative source and conflict rule.

Where translation status changes, the earlier status and effective date of the change shall remain historically identifiable.

Top-level substantive clauses shall be numbered consecutively with Arabic numerals beginning at 1 unless a document-specific controlled structure requires another unambiguous form.

Clause numbers shall reflect reading structure and shall not be assigned according to importance, conformity severity or organizational ownership.

A heading shall accompany each top-level clause, and the number-heading combination shall remain consistent across the reader, download and structured record.

Introductory material before clause 1 may use a separate unnumbered or roman-numeral convention only where it cannot be mistaken for normative requirements.

Gaps, duplicate numbers and hidden clauses are not permitted in a published edition.

A new edition may renumber clauses, but the prior edition's numbers shall remain immutable and a correspondence record shall support material cross-edition references.

A subclause shall extend its parent number by decimal notation and shall have a stable position and meaning within the edition.

Each independently citable normative proposition should receive a subclause number so that comments, findings, interpretations, corrections and appeals can identify it without quoting uncertain text.

Decimal levels shall not be used beyond what readers can navigate reliably; excessive nesting shall be resolved by restructuring the document.

A subclause number shall not end with an unnecessary zero and shall not be confused with a quantitative value.

When several sentences form one indivisible rule, they may share a subclause, but a sentence creating a separate obligation or exception shall be separately identifiable where this is necessary for conformity or due process.

Paragraphs within a subclause may be divided into lower-case lettered items where each item is grammatically and logically governed by the introductory text.

The introduction shall state whether all items, one or more items, or a defined alternative combination is required.

Lettered items shall not mix requirements, recommendations and examples without clear status.

Nested lists may use roman numerals or another controlled style, but each level shall remain unique within its parent and capable of accurate citation.

A list shall not continue across an unrelated heading or depend on visual indentation alone for meaning.

Addition or deletion of an item through amendment shall identify the exact parent and item and shall preserve historical citations to the earlier list.

Every table shall have a unique number within the edition, a concise title and an explicit relationship to the clause that gives it normative or informative effect.

Column and row headings, units, footnotes, symbols and empty cells shall be defined sufficiently to prevent inconsistent reading.

A normative table shall be cited by the controlling provision and shall not contain a hidden exception or obligation unrelated to that citation.

Continued tables across pages or reader views shall preserve headings and identity.

A replacement table issued by amendment shall identify the affected edition and table number and shall not silently reuse the number for a different subject.

Structured and visual representations shall carry equivalent data, including footnotes and merged-cell meaning.

A figure or diagram shall have a unique number, title and stated normative or informative status.

Essential normative meaning shall be available in text or another accessible structured form and shall not depend solely on colour, scale, spatial position or an inaccessible image.

Symbols, arrows, boundaries and sequence conventions shall be explained where a reasonable reader could interpret them differently.

A diagram illustrating one permitted architecture shall not be read as prohibiting an equivalent architecture unless the normative text states that result.

Updates shall preserve the figure's identity or issue a new controlled figure and shall identify any changed normative effect.

Alternative text shall describe the information necessary for understanding rather than merely repeat the figure title.

Each equation used normatively shall have a stable identifier, define every variable, unit, source value, period, rounding rule, boundary condition and treatment of missing or invalid data.

The surrounding clause shall state the outcome governed by the equation and whether the result establishes a threshold, input to judgment or informative indicator.

Equivalent digital and rendered forms shall produce the same result and shall not lose superscripts, symbols or operator precedence.

A corrected typographical symbol that could change a result shall be treated as normative change unless it is demonstrably impossible for a reasonable implementation to have relied on the error.

An example calculation shall carry its own label and shall not redefine the general formula.

An annex or schedule shall be identified by a unique letter or number, title and normative status, and shall state the document and edition to which it belongs.

A normative annex forms part of the requirements only within the scope stated by the referring clause; an informative annex provides explanation or examples and shall not create conformity conditions.

A separately controlled schedule shall have its own version relationship and shall not change automatically because the parent document changes unless that relationship is expressly defined.

Citation shall include the parent document, edition and annex or schedule identifier.

Removal or replacement shall preserve historical access and shall identify the effect on certification and transition.

Each assessable ICEQC requirement shall have a stable machine-readable key associated with the visible clause or subclause citation for its edition.

The key shall support data exchange, evidence mapping, findings, decision records and change correspondence without replacing the reader-facing number.

A key shall not be reassigned to a materially different requirement in a later edition; continuity may be expressed through an explicit successor or equivalent relationship.

Splitting or merging requirements shall create new keys and map the predecessors rather than conceal the structural change.

Keys used for governance obligations shall remain distinguishable from certification assessment-unit identifiers, because a rule binding ICEQC is not automatically a requirement assessed against an applicant.

A certification scheme and each applicability module shall have a controlled public code distinct from the document version identifier and from internal workflow or product codes.

The scheme code shall identify the continuing certification architecture, while the controlling documents and editions determine the requirements applied at a stated time.

A module code shall identify one defined applicability subject and shall not imply that the module is optional where its published trigger is present.

Codes shall remain stable across ordinary revisions and shall not be used for a different scope after withdrawal.

A certificate and public-register entry shall use the same scheme and module codes as the applicable controlled records, accompanied by titles or scope information sufficient for a reasonable reader to understand their meaning.

A certification application or case may receive a controlled identifier for communication and traceability, but that identifier shall not be presented as a certificate number or evidence of status.

It shall remain associated with one applicant, certification object and procedural record, subject to lawful rules for a materially changed application or successor entity.

Public disclosure is not required unless the identifier appears in a public decision or verification service, and personal or confidential information shall not be encoded visibly in the identifier.

Cancellation, refusal, withdrawal or closure shall not release the identifier for reuse.

A new application after final closure shall receive a new case identity while preserving an authorized relationship to the earlier record where continuity is relevant.

Each ICEQC certificate shall have a unique identifier generated only after or in direct association with an authorized certification decision and shall resolve to the controlled public-register record.

The number shall not disclose sensitive personal information, encode a quality level, or imply that sequence establishes seniority or superior status.

A corrected or reissued representation of the same decision may retain the certificate identifier with a controlled version or issue date, while a new certification cycle or materially different certification object shall be treated according to the applicable scheme and decision rules.

A withdrawn, expired or void certificate identifier remains permanently reserved.

A QR code or verification token may supplement but shall not replace the visible certificate number.

A public-register entry shall have a stable record identifier that permits the current status and historical status changes to be distinguished from copied certificate representations.

The record may cover one certificate and its lifecycle or another defined public decision object, but the relationship shall be explicit.

A change of certified-client name, scope, status or certificate representation shall update or version the record without causing the identifier to resolve to an unrelated entity.

Search-friendly aliases may be provided, but the stable record identifier shall remain available for verification.

Where a record is corrected after identity error, both the correction and the prevention of misleading access through the prior form shall be addressed without unnecessary publication of protected data.

An amendment identifier shall combine the affected base document, affected edition, amendment sequence and amendment publication year in a form readable without proprietary software.

The sequence begins at 1 for each edition and follows publication order; withdrawal of an amendment shall not cause later amendments to be renumbered.

The amendment record shall identify its status, effective date, affected clauses, relation to any consolidated view and whether a later edition incorporates it.

A reference to an edition subject to an effective amendment shall include the amendment where omission could change the applicable text.

An amendment shall not be given a new base document number merely to avoid showing that it changes an existing edition.

A correction identifier shall combine the affected base document and edition with a sequential correction number and correction publication year.

The record shall distinguish correction of normative text, translation, metadata, link, rendering and another representation, and shall state whether normative effect is unchanged.

Several minor errors may be grouped in one correction where every affected location is identified.

A corrected download may include the correction while retaining the immutable identity of the original publication, provided the incorporated correction and its date are visible.

If analysis shows that meaning could change, the action shall be reclassified as amendment and given the corresponding identifier rather than preserving the less demanding correction label.

A published interpretation shall have a unique identifier linked to the exact document, edition and provisions interpreted.

The record shall show the question, authority, approval date, status, any period of effect and whether the issue was later incorporated into an amendment or edition.

Interpretation numbers shall be sequential within a defined document or system register and shall not be reused after withdrawal.

A training answer, help-page response or individual case explanation shall not use an identifier likely to be mistaken for a formal interpretation.

Citations shall identify both the controlling provision and interpretation, because an interpretation does not become a freestanding standard.

Each transition notice shall have a controlled identifier and shall identify the old and new document editions, affected schemes or certification scopes, issue date, transition beginning and end, status and approving authority.

Where one notice governs several documents, each relationship shall be explicit and searchable; similarity of dates shall not be treated as sufficient linkage.

A revised notice shall receive a version or replacement relationship and shall not overwrite deadlines on which affected persons may have relied.

Citations to a certificate or decision made during transition shall identify the governing edition and, where material, the transition notice.

Expired transition notices shall remain available as historical evidence but shall not be displayed as current action.

A public consultation shall have a unique identifier linked to the exact draft, project, opening and closing dates and responsible body.

Reopening or materially extending a consultation shall update the controlled record without concealing the original period; a new consultation on materially changed text shall receive a distinct round or identifier.

Submission receipts may use related private identifiers, but shall not reveal other contributors or imply acceptance of the comment.

A consultation identifier shall not be cited as an approved standard.

The final disposition and resulting edition shall reference the consultation so that readers can reconstruct which draft and comment opportunity supported publication.

Every controlled relationship shall identify the source object, target object, relationship type, editions where relevant, effective date and authority.

Relationship types including supersedes, is superseded by, amends, corrects, interprets, translates, depends on, incorporates, is used with and is annex to shall not be treated as interchangeable.

Reciprocal relationships shall be consistent in structured records and public reader views.

A relationship shall not be inferred from shared title words, adjacent numbering, common owner or simultaneous publication.

Where a relationship changes applicability or normative effect, the controlling clause and transition shall be identified rather than relying on metadata alone.

Each published edition shall have a canonical permanent URI or equivalent durable locator that resolves to its controlled record and does not later display a different edition as if it were the cited text.

The locator shall remain stable through site redesign, hosting change and reader evolution, using redirection where necessary without erasing edition identity.

It shall identify language or permit selection without confusing the authoritative source.

A canonical link may lead to a reader containing multiple representations, provided the cited edition, status and content are immediately unambiguous.

Link persistence shall be treated as a document-control obligation because broken or repurposed citations can change public understanding even when the underlying text remains archived.

ICEQC may provide a latest or current alias that resolves dynamically to the edition currently designated for general use.

The alias shall state the edition reached and shall not be used in a formal certification basis, contract, decision or historical citation where future resolution to another text would create uncertainty.

During transition, the alias shall not conceal that more than one edition may lawfully apply and shall provide access to the transition notice and edition-specific records.

Search engines and external links may use the alias for discovery, but downloadable citations generated by the reader shall default to the exact edition.

Withdrawal without successor shall cause the alias to display that status rather than silently redirect to an unrelated document.

A controlled download name shall include the base document number, edition and language and, where applicable, amendment, correction or draft status.

The extension identifies format and shall not be used as a version indicator.

Spaces, punctuation and capitalization may be normalized for technical compatibility, but the document itself and metadata shall display the exact controlled identity.

A replaced file shall not be stored under the same public name without an integrity-preserving version relationship or correction record.

Convenience bundles may contain several documents, but each file shall retain its own identity and the bundle name shall not imply a new consolidated standard unless one was formally approved.

Structured reader data shall expose stable identifiers for the document, version and clauses that correspond to the visible human-readable record.

Internal database keys may be included where useful but shall not be represented as document numbers or require a user to understand implementation details.

The same public identifier shall have the same meaning across interfaces, exports and verification responses.

An interface version is distinct from a standard edition and shall not change normative content.

Where a structured schema evolves, mappings or compatibility arrangements shall preserve document identity, content hashes and clause relationships so that a technical migration cannot create a new authoritative text silently.

A published digital representation shall carry a cryptographic content hash or equivalent integrity identifier derived from the controlled content and metadata defined for that representation.

The method and value shall permit ICEQC or another competent user to detect whether the representation differs from the approved record; it does not by itself prove legal authority, approval or current status.

A different representation, such as HTML and PDF, may have different file hashes while sharing a controlled normative-content relationship.

Recalculation after a correction shall produce a new integrity value and preserve the earlier value in the historical record.

A hash shall not be truncated in a way that makes collision reasonably material to the intended verification use.

Publication, approval, effective, transition, correction and status dates shall use an unambiguous calendar form in structured records and shall be rendered to readers without reversing day and month.

Where time is material, the timestamp shall include a time zone or universal offset and shall distinguish creation, decision and system-recording time.

A date alone shall not be inferred to begin or end at the reader's local time if a deadline or status change depends on another controlling zone.

Estimated and planned dates shall be labelled and shall not be stored as completed publication events.

Correction of a date that could affect validity, transition or rights shall receive controlled review and public notice proportionate to the reliance risk.

An identifier assigned in error or to a project that is cancelled shall remain reserved and shall be marked void or cancelled with a reason and date appropriate to its public exposure.

If the identifier was never public and no external reliance is reasonably possible, the reservation may remain in the controlled register without a public page.

Once an identifier appears in a consultation, citation, certificate, register or other public record, its status shall remain publicly discoverable.

A void record shall not display unrelated content, and a later project shall receive a new identifier.

Cancellation of a project does not withdraw another published document with a similar title or planned relationship unless that separate action is expressly authorized.

A legacy identifier from an earlier ICEQC architecture may remain usable for historical retrieval where its original meaning, period and relationship to the current system are documented.

It shall not be reformatted to appear as a current identifier if that would imply approval or continuity that did not exist.

Where a current document succeeds a legacy text, the relationship shall state whether content was revised, adopted, replaced or merely covers a similar subject.

Legacy certificate and document references shall not be reassigned or normalized in a way that causes them to resolve to new objects.

Public search may recognize common former forms while displaying the controlled historical status and current successor, if any.

When two public objects are found to share or appear to share an identifier, ICEQC shall promptly determine which assignment had authority, the records and claims affected, and the risk of mistaken reliance.

The valid historical identifier shall be preserved unless a broader corrective action is necessary to protect the public; the erroneous object shall receive a new or void status with cross-links that prevent silent substitution.

Certificates, downloads, citations, metadata and cached representations shall be corrected consistently.

A public notice shall explain the affected forms and verification route where confusion could alter certification or legal understanding.

The correction shall not retroactively attribute a decision or status to the object that did not receive it.

The preferred formal citation shall state the document number, edition and clause or annex where relevant, followed by language and amendment or correction information needed to identify the applicable text.

Titles may be added for readability but shall not substitute for the number and edition.

Punctuation may follow an accepted bibliographic style if the components remain unambiguous.

A citation to several clauses shall identify ranges and separate non-contiguous provisions without implying that omitted material is inapplicable.

ICEQC-generated citations shall use a consistent order and shall include an edition-specific link in digital contexts.

A citation error does not amend the referenced text and shall be resolved by the surrounding controlled context only where one meaning is objectively clear.

A short citation using only the document number or clause may be used within a document where the complete reference is established and no other edition or document could reasonably be intended.

In a certificate, decision, agreement, public register or cross-document normative reference, shorthand shall not omit the edition where omission could change applicable requirements.

The expression 'current edition' shall be avoided in historical or long-lived records unless the record fixes the relevant date and transition rule.

Defined abbreviations may be used after first identification but shall not be confused with family or scheme codes.

A reader shall not be required to infer a certification basis from navigation context or a filename alone.

A citation to a non-English text shall include the language tag and, where relevant, its controlled or informative status.

If the cited proposition depends on a translation while English is authoritative, the citation shall permit access to both and shall not imply equal authority.

Co-authoritative language citations may identify either text, but a discrepancy record shall reference all affected versions.

A translated title may accompany the controlled English title without altering the base identifier.

Where a third party cites an unofficial translation, it shall identify that status and shall not use an ICEQC language-version identifier reserved for controlled publications.

A consolidated view incorporating amendments or corrections shall identify the base edition, every incorporated action and the consolidation date.

It is a reading aid or controlled representation of the combined text and shall not conceal the originally published edition or create a new edition unless separately approved as one.

A formal citation shall identify the amendment where its provisions are material, even if the reader used the consolidated view.

Consolidation shall preserve clause history, effective dates and content integrity and shall not resolve conflicts by editorial choice.

Where an amendment has not yet taken effect, the consolidated view shall not present its text as current without clear temporal distinction.

A machine-actionable citation shall contain the public document and edition identifiers, clause or requirement key, language and integrity or version information necessary for deterministic resolution.

It may include a URI, compact identifier or structured object, but shall remain connected to a human-readable citation.

Resolution shall return status and relationship information so that a superseded clause is not mistaken for current normative text.

A machine key shall not be used to hide a change from readers by retaining the same value for materially different content.

Interface errors or unavailable services shall not change the legal or normative meaning of the underlying approved text, and offline records shall remain capable of later reconciliation.

A third party may cite an ICEQC document accurately using its controlled number, edition, title and clause without implying sponsorship or authorization.

Reproduction shall preserve document identity, copyright and status and shall not alter, excerpt or combine text in a way that misrepresents normative meaning.

A third-party index, mirror or knowledge base shall not use an ICEQC identifier for modified content or present itself as the authoritative Standards Register.

Where reasonable, the citation should link to the canonical ICEQC record so current status can be verified.

ICEQC may correct misuse of an identifier or mark, but shall not restrict truthful critical or scholarly reference merely because the conclusion is unfavorable.

ICEQC shall maintain a controlled identifier register covering public document series, editions, language versions, amendments, corrections and other classes whose reuse could affect public trust.

The register shall show current status and enough historical reservation to prevent reassignment, and shall be capable of reconciling human-readable and machine identifiers.

Public access may be limited for private case or security identifiers, but the corresponding certificate or public-record verification shall expose the information necessary for lawful reliance.

Register changes shall be attributable and shall not erase prior assignments.

Periodic integrity review shall address duplicates, orphan relationships, invalid syntax, broken canonical links and inconsistent titles or statuses across representations.

Search metadata may include titles, short titles, subjects, keywords, aliases and former identifiers to help readers locate controlled content.

It shall not change classification, scope, status or normative effect and shall not use promotional phrases likely to imply government recognition, ranking or broader certification.

Results shall display the document number, edition and status sufficiently early to distinguish current, draft, superseded and withdrawn texts.

Synonyms and translated keywords may improve discovery but shall resolve to the controlled title and language record.

Search ranking shall not be represented as standards precedence, and paid or popular content shall not displace the authoritative record for an exact identifier query.

Identifiers shall be designed and presented for accurate reading, copying, speech and assistive-technology use.

Fonts and styling shall distinguish letters and digits where confusion is possible, and identifiers shall not rely solely on colour, superscript or punctuation omitted by screen readers.

Human-readable forms should avoid excessive length and ambiguous characters while preserving established ICEQC syntax.

A spoken or plain-text alternative may be provided for QR codes and long hashes.

Line wrapping shall not insert or remove characters from the identifier, and copied metadata shall preserve hyphens and leading zeros.

Accessibility presentation may add separators or labels but shall not create a different controlled identifier.

Access to assign, activate, void or alter identifier relationships shall be restricted to authorized functions and protected against impersonation, accidental duplication and unauthorized bulk creation.

Technical controls shall support, but not replace, institutional authorization and review.

Public identifiers shall not contain secrets, authentication credentials or predictable personal data whose exposure creates security risk.

Discovery of fraudulent issuance or manipulation shall trigger preservation of evidence, status protection, public clarification where reliance is possible and correction by the competent authority.

A security response shall not silently change an authentic historical identifier or redirect it to a replacement without a visible relationship.

Identifier assignments and relationships shall be retained for as long as public or certification reliance may exist and, for published documents and certificates, as part of the permanent institutional record.

Migration to a new registry, domain, schema or provider shall verify counts, uniqueness, relationships, content hashes and resolution before the prior service is retired.

An archival copy without functioning relationships is not sufficient where a reader must distinguish current from historical status.

Technical deprecation may remove an interface method but shall preserve the public identifier and an accessible resolution route.

If complete migration is impossible, ICEQC shall publish the limitation and prioritize records whose loss could misstate certification or normative authority.

These identification rules shall be reviewed when document architecture expands, repeated citation errors occur, language or accessibility needs reveal ambiguity, security or platform changes affect persistence, or external users cannot reliably distinguish editions and statuses.

Review shall include samples across human-readable documents, structured data, certificates, register entries, translations and archives.

A revised syntax shall preserve existing assignments or provide explicit permanent mappings and shall not require historical documents to be relabelled as if issued under the new rule.

Public consultation shall address any change capable of breaking citations or affecting verification.

Confirmation shall record that the current system remains unique, stable, intelligible and fit for long-term international use.

A normative reference shall identify the external or ICEQC source at the level necessary to determine exactly what text is indispensable, including issuer, number or title, edition or date and relevant part where applicable.

An acronym, hyperlink or organization name alone is not sufficient where several texts could be intended.

Dated and undated references shall be visibly distinguishable and their transition effect shall be governed by the referring provision.

If an external identifier changes, ICEQC shall preserve the originally cited identity and may add the successor relationship without rewriting historical meaning.

A referenced source shall not be assigned an ICEQC number unless it has become a separately approved ICEQC document.

An informative source shall be cited using a sufficiently complete bibliographic identity to permit retrieval and distinguish editions, versions, authorship and publication date.

A DOI, repository identifier or permanent link may supplement the citation but shall not substitute for the descriptive information needed when the service is unavailable.

A cited dataset shall identify the relevant release or access date and any material population or license limitation.

Bibliographic numbering is local to the bibliography and shall not be confused with normative clause identifiers.

Correction or withdrawal of a source shall not silently change the ICEQC requirement, but may trigger a documented review where the source was material to the rationale.

A digital reader should provide stable fragment identifiers for clauses, annexes, tables and other citable units.

The anchor shall remain associated with the same unit within the edition and shall not be regenerated from a heading alone if an editorial title change would break links.

A human-readable clause number shall remain visible when a fragment link is opened, and the reader shall identify the edition and status without requiring navigation to another page.

Where an old anchor changes for accessibility or technology reasons, redirection shall preserve resolution.

A fragment identifier is subordinate to the edition-specific canonical URI and shall not resolve the same string to a clause in a different edition without making that change unmistakable.

Page numbers may be shown in a fixed-layout representation but shall not be the sole identifier of a normative provision, because pagination can change by format, language, accessibility settings and device.

Citations shall use clause, annex, table or figure identifiers that remain stable across equivalent representations.

A page-specific reference may supplement the controlled citation for convenience or evidentiary quotation, provided the document edition and representation are identified.

Running headers, footers and page breaks shall not create or remove normative meaning.

When a printed edition and digital reader differ in pagination, neither is incorrect if content identity and stable provision references remain equivalent.

ICEQC shall avoid assigning titles or short titles so similar that a reasonable reader could confuse document series, certification objects or normative effects.

Where similar wording is necessary across related schemes or modules, the document number, object and distinguishing subject shall be prominent in lists, search results and certificates.

A translated title that coincides with another controlled title shall retain the source number and language marker.

Discovery of material title confusion shall be addressed by metadata clarification or controlled title change without reassigning either base identifier.

Historic citations shall remain resolvable through alias and former-title records.

A correspondence record between editions shall identify each predecessor clause or requirement key and its successor relationship as unchanged, modified, divided, merged, relocated, deleted or newly introduced.

It shall not claim equivalence where scope, obligation, exception, evidence or conformity effect materially changed.

Many-to-one and one-to-many mappings shall be explicit and shall preserve the ability to cite the earlier requirement independently.

The mapping is informative unless a transition rule assigns it a specific effect and shall not replace assessment against the controlling edition.

Corrections to a mapping shall not change either normative text and shall be recorded so prior reliance can be understood.

Where a defined part, language version, annex, module or application of a document is withdrawn without withdrawal of the entire document, the status record shall identify the exact affected component and effective date.

The base document shall not be labelled wholly withdrawn if other parts remain current, and the retained text shall not be displayed in a way that conceals the limitation.

Certificates and citations affected by the partial withdrawal shall identify the governing transition.

A withdrawn component identifier remains reserved and shall not be reused for replacement content; the successor, if any, receives a controlled relationship.

Partial withdrawal shall not be used to edit an immutable edition silently.

ICEQC may publish a correction sheet or errata collection containing several controlled corrections to one edition.

Each entry shall retain its own location, error, corrected form, classification and date, and the collection shall have a stable identity and revision history.

Inclusion in a collection does not permit a normative change to be labelled editorial.

A reader shall be able to determine which corrections are incorporated in a consolidated representation and whether any earlier correction was superseded.

The collection shall not become an alternative edition or require readers to infer the current text from undated annotations.

A visual status badge shall use the same controlled status as the underlying record and shall be accompanied by accessible text.

Colour, icon or placement alone shall not distinguish development, published, superseded, suspended or withdrawn status.

The badge shall not use terms such as verified, official or active where the document status has a different defined meaning.

A cached badge embedded by a third party shall link to current verification and shall not be treated as authoritative independently of the register.

Where status changes, public reader and download views shall be updated consistently while preserving the historical effective date.

A certificate may have an issue, reissue or representation version that is separate from the edition of the standards and schemes applied to the certification decision.

These values shall not be combined or displayed in a way that suggests reprinting a certificate changed the certification basis.

The certificate shall identify controlling document editions, while its own issue date and identifier support authentication and correction history.

A change to scope or status requires the applicable certification decision and shall not be implemented merely by incrementing a document version.

Public-register data shall keep these relationships explicit so that a user can distinguish the age of the certificate representation from the edition under which conformity was determined.

Where an ICEQC document cites legislation, regulation or an official decision, the citation shall identify the jurisdiction, issuing authority, instrument, date or version and relevant provision sufficiently to avoid implying universal application.

A convenient unofficial link may accompany but shall not replace the authoritative source identity.

Amendments, repeal and territorial variation shall be considered where the legal reference affects the rule, and an informative legal note shall not be represented as legal advice or ICEQC recognition of compliance.

The ICEQC document number shall remain distinct from any government instrument number.

A later legal change shall trigger review rather than silently changing the edition cited.

ICEQC may associate a DOI, archival identifier, library identifier or another external persistent identifier with a publication where this improves discovery and preservation.

The external identifier shall resolve to or accurately describe the same controlled publication and shall not be treated as the source of ICEQC approval or status.

If external metadata is incorrect, ICEQC shall seek correction and shall keep its Standards Register authoritative.

An identifier issued by another system shall not be reused as an ICEQC clause, certificate or scheme identifier.

Withdrawal or transfer of the external service shall not impair the ICEQC canonical link or historical record.

Before an identifier is relied upon in a published standard, certificate or register, its syntax, uniqueness, title, edition, language, status, relationships and canonical resolution shall be mutually consistent.

Public assurance concerns the integrity of the complete identity, not only whether a number exists.

A detected inconsistency shall be classified according to its possible effect on retrieval, citation, conformity or certification claims and corrected under the appropriate governance rule.

ICEQC shall monitor exact-identifier searches and verification routes sufficiently to detect broken or misleading resolution.

Confirmation of identity does not approve technical content, but publication authorization shall not proceed while a material identity conflict remains unresolved.

An abbreviation or acronym used as a recurring identifier shall be defined at first material use and shall not conflict with a controlled family, scheme, status or authority code in the same context.

It shall remain typographically consistent and shall not acquire a different meaning within the document family without explicit qualification.

A translated text may use a language-appropriate abbreviation while preserving the controlled English form where it appears in certificates, citations or metadata.

An acronym shall not be created to suggest government, accreditation or external recognition.

The full controlled term shall remain available to readers and assistive technologies and shall prevail if a non-controlled abbreviation is ambiguous.

A symbol, unit abbreviation or coded value shall be defined before normative use and shall follow an internationally intelligible convention where one exists.

Visually similar symbols shall be avoided or disambiguated, and case sensitivity shall be stated where it changes meaning.

A code set used in structured data shall have a public label and definition and shall not expose implementation-only values as if they were normative status.

Changes to a code set shall preserve earlier meanings and provide mappings rather than reinterpret stored historical records.

A rendered symbol and its machine-readable form shall remain equivalent across languages and accessible representations.

Material changes to title, short title, owner, approval authority, status, dates, language status, canonical link or document relationships shall be attributable and historically recoverable.

A change history shall identify the field, prior and new values, date, authority and whether the action is correction, status event or consequence of a new edition.

Routine technical replication and harmless display formatting need not create public events, but shall not alter controlled values.

Metadata history shall not be used to rewrite the normative text outside amendment or revision.

Where a public reader displayed wrong metadata, the correction record shall consider reliance as well as internal data accuracy.

The identifier, title, edition, language, status, responsible body, approval authority and integrity relationship shall agree across the Standards Register, reader, downloadable text, certificate references and structured interfaces.

A representation may omit nonessential metadata for space only where immediate verification remains available and omission cannot enlarge or confuse meaning.

Discovery of divergence shall trigger comparison with the approved record and coordinated correction; the most convenient or most recently edited copy shall not automatically prevail.

Public notices shall identify any period during which conflicting representations could have affected reliance.

Equivalent representations may differ in layout and file hash but shall not differ in controlled identity or normative content.