Open Design Tokens
Reference

Spec coverage table

Fixture counts per specification section, and the known spec issues.

Fixtures: 191 (57 basic, 39 advanced, 95 invalid). Verbatim spec examples: 64; cleaned (comments or trailing commas removed): 15.

Sections

SpecSectionBasicAdvancedInvalid
color4.1 Format100
color4.1.1.1 Using the none keyword200
color4.2.1.1 Components100
color4.2.2.1 Components100
color4.2.3.1 Components100
color4.2.4.1 Components100
color4.2.5.1 Components100
color4.2.6.1 Components100
color4.2.7.1 Components100
color4.2.8.1 Components100
color4.2.9.1 Components100
color4.2.10.1 Components100
color4.2.11.1 Components100
color4.2.12.1 Components100
color4.2.13.1 Components100
color4.2.14.1 Components100
color7.1.1 Base100
color7.1.2 Alias100
color7.1.3 Component001
color7.2.1.1 Descriptive100
color7.2.1.2.1 Ordered scales200
color7.2.1.2.2 Bounded scales100
color7.2.1.2.3 Computer generated scales100
color7.2.2 Alias Tokens002
color7.2.3 Component Tokens001
format4. File format013
format5.1 Name and value122
format5.1.1 Character restrictions012
format5.2 Additional properties016
format5.2.1 Description100
format5.2.2 Type101
format5.2.3 Extensions100
format5.2.4 Deprecated100
format6.1 Group Structure003
format6.2 Root Tokens in Groups111
format6.3 Group Properties113
format6.3.2 $extensions001
format6.4 Extending Groups111
format6.4.1 Equivalence to JSON Schema $ref010
format6.4.3 Inheritance Semantics021
format6.4.4 Circular Reference Prevention004
format6.5 Empty Groups110
format6.6 References and JSON Pointer Integration010
format6.6.1 Current Reference Syntax (Recommended)001
format6.6.2 JSON Pointer Support001
format6.7.3 Type Inheritance022
format6.7.4 Circular Reference Detection001
format6.9.1 Basic Group with Root Token100
format6.9.2 Group Extension with Override Example001
format6.9.3 Complex Hierarchical Structure100
format6.10.1 File authoring & organization200
format6.10.3 Translation tools100
format7.1.1 Curly Brace Syntax (Token References)111
format7.1.2 JSON Pointer Syntax (Required Support)112
format7.2 Reference Resolution013
format7.2.2 Chained References100
format7.2.3 Circular References001
format7.3 Property-Level References011
format7.3.1 Color Component References100
format7.3.2 Dimension Component References100
format7.3.3 Typography Component References001
format7.4.5 Error Conditions004
format8.1 Color / Color Module 40613
format8.2 Dimension115
format8.3 Font family112
format8.4 Font weight123
format8.5 Duration114
format8.6 Cubic Bézier114
format8.7 Number111
format9.1 Array aliasing in composite types221
format9.3 Stroke style012
format9.3.1 String value100
format9.3.2 Object value200
format9.4 Border012
format9.5 Transition101
format9.6 Shadow012
format9.7 Gradient212
format9.8 Typography012

Known spec issues

These examples appear in the 2025.10 specifications but contradict the specifications' own normative rules, or are incomplete snippets. They are kept as expected-failure fixtures rather than as valid examples.

SpecExampleSectionCodes emittedWhy
color207.1.3 Componentalias.target.missingAliases {color.brand.primary}, {color.palette.black} have no target inside this snippet. As a standalone document those aliases are unresolvable.
color267.2.2 Alias Tokensalias.target.missingAliases {color.red.600}, {color.green.400}, {color.palette.black}, {color.red.700} have no target inside this snippet. As a standalone document those aliases are unresolvable.
color277.2.2 Alias Tokensalias.target.missingAliases {color.red.600}, {color.green.400} have no target inside this snippet. As a standalone document those aliases are unresolvable.
color287.2.3 Component Tokensalias.target.missingAliases {color.background.error}, {color.background.success}, {color.text.error}, {color.text.success} have no target inside this snippet. As a standalone document those aliases are unresolvable.
format126.3 Group Propertiestoken.type.invalidUses $type "string", which this spec version does not define (§8 lists no string type).
format146.4.3 Inheritance Semanticstoken.type.missinginput.field.background has no determinable $type (§5.2.2). The override input-amount.field.width ("100px") sits under $extends and is judged once group extension is resolved (Milestone 4).
format166.4.4 Circular Reference Preventionextends.cycleDeliberately invalid in the spec: a group extends its own ancestor.
format176.4.4 Circular Reference Preventionextends.cycleDeliberately invalid in the spec: two groups extend each other. The placeholder "token" members are empty groups.
format186.4.4 Circular Reference Preventiontoken.type.missingbutton-large.padding has no determinable $type: neither the token, its group, the extended group, nor any ancestor declares one (§5.2.2, §6.7.3).
format206.6.1 Current Reference Syntax (Recommended)token.type.missingbase has no $type and no typed ancestor, so it is invalid per §5.2.2. The alias inherits that problem once alias resolution lands (Milestone 4).
format216.6.2 JSON Pointer Supporttoken.type.missingSame missing $type on base as Example 20. "alias" is a group carrying $ref (JSON Schema spelling of $extends); its target is resolved in Milestone 4.
format226.7.3 Type Inheritanceextends.inherited-token.invalidextended declares $type dimension and inherits a color-valued token with no own $type; the spec says both constraints must hold, so the inherited token is invalid in the extending group.
format236.7.4 Circular Reference Detectionextends.cycleDeliberately invalid in the spec: a → b → c → a. The spec requires an error on all three groups.
format256.9.2 Group Extension with Override Exampledimension.unit.invalidinput.field.width uses unit "%", which §8.2 does not allow.
format347.2.3 Circular Referencesalias.cycleDeliberately invalid in the spec: a → b → c → a. The spec requires an error on all tokens in the chain.
format377.3.3 Typography Component Referencescomposite.property.missingThe typography values omit letterSpacing, which §9.8 requires. The $ref fragments themselves resolve correctly.
format529.4 Borderalias.target.missing{color.focusring} is not defined in the snippet, so the alias is unresolvable.
format549.6 Shadowalias.target.missingThe spec text is missing a comma between members (cleaned); {base.shadow}, {brand.accent}, and {highlight.shadow} are not defined in the snippet.
format579.7 Gradientalias.target.missing{brand.secondary} is not defined in the snippet.
format589.8 Typographyalias.target.missing{font.serif}, {font.size.smallest}, and {font.weight.normal} are not defined in the snippet.

On this page