Candidate Recommendation Draft (CRD)

IndustryCRD

Description

A daily-build draft of a Candidate Recommendation. CRDs are published frequently to track ongoing editorial changes between formal CR snapshots.

Syntax

W3C identifiers are slug-based with an optional type prefix indicating the document's maturity stage: WD (Working Draft), CR (Candidate Recommendation), CRD (Candidate Recommendation Draft), NOTE (Working Group Note), PR (Proposed Recommendation), PER (Proposed Edited Recommendation), REC (Recommendation), OBSL (Obsolete Recommendation), SPR (Superseded Recommendation). The slug carries the spec shortname and optional date suffix (YYYYMMDD).

Examples 1

W3C CRD-css-color-5-20240101

Components Used

W3C Candidate Recommendation Draft (CRD) identifiers are composed of these elements:

Publisher

W3C — omitted when with_publisher=false

e.g.W3C

Type Prefix

Maturity stage abbreviation: WD, CRD, CR, PR, PER, REC, NOTE, OBSL, SPR (or empty for unprefixed forms)

e.g.REC

:type_prefix

Code

Spec shortname + optional date suffix (YYYYMMDD)

e.g.html52-20171214

:code

Algebraic Relations

Relations that can involve Candidate Recommendation Draft (CRD) identifiers:

Relation	Description	Syntax	Example
Maturity Lifecycle	Standard progression: WD → CRD → CR → PR → REC	`<type_prefix>-<code>`	`W3C REC-html52-20171214`
Note	Informative Working Group Note	`NOTE-<code>`	`W3C NOTE-xml-names`
Status Change	Obsoleted (OBSL) or superseded (SPR) former Recommendations	`<OBSL\|SPR>-<code>`	`W3C OBSL-xhtml1-20180327`
Without Publisher	Bare slug form (no 'W3C ' prefix)	`[<type_prefix>-]<code>`	`REC-html52-20171214`

URN Mapping

Patternurn:w3c:[type]:[code]