OGC Document

Industry

Description

All OGC specification documents — standards, discussion papers, engineering reports, and best practice documents — share the same identifier shape. The two-digit year, three-digit zero-padded sequence number, and optional revision suffix uniquely identify any OGC document. Examples: 24-032r1 (a 2024 standard revision 1), 01-009a (a 2001 document revision 'a').

Syntax

OGC identifiers are digit-leading: '<yy>-<nnn>[<revision>]'. The year is 2 digits, the number is 3 digits (zero-padded), and the optional revision suffix is the lowercased token including its separator letter: 'r1', 'c1', 'a', 'r3a', 'r12a'. The leading 'OGC ' publisher token is added only when with_publisher=true (default is bare).

Examples 5

24-032r1

01-009a

OGC 24-032r1

06-042r3

17-016r2

Components Used

OGC OGC Document identifiers are composed of these elements:

Publisher

OGC — omitted by default, added when with_publisher=true

e.g.OGC

Year

Two-digit year (the 'yy' field)

e.g.24

:year

Number

Three-digit zero-padded sequence number (preserves leading zeros)

e.g.032

:number

Revision

Optional lowercased revision token including separator: 'r1', 'c1', 'a', 'r3a', 'r12a'. nil when absent.

e.g.r1

:revision

Algebraic Relations

Relations that can involve OGC Document identifiers:

Relation	Description	Syntax	Example
Bare Document	Default form without publisher prefix	`<yy>-<nnn>[<revision>]`	`24-032r1`
With Publisher	Publisher prefix added when with_publisher=true	`OGC <yy>-<nnn>[<revision>]`	`OGC 24-032r1`
Revision	Revision suffix variants: r (revision), c (corrigendum), a (amendment)	`<yy>-<nnn>[r<c><n>\|<a>]`	`01-009a`

URN Mapping

Patternurn:ogc:[year]:[number]:[revision]