Re: [community-group] $type should be a required property (#139)
Re: [community-group] Adds new token property (`$private`) (#172)
[community-group] Merged Pull Request: Fix the color alpha syntax to be 50%
[community-group] Define error handling (#200)
[community-group] Implicit vs. explicit typing in composite tokens (#199)
[community-group] Pull Request: feat: add Kaspersky to DTCG members
- Re: [community-group] feat: add Kaspersky to DTCG members (#198)
- Re: [community-group] feat: add Kaspersky to DTCG members (#198)
- [community-group] Merged Pull Request: feat: add Kaspersky to DTCG members
- Re: [community-group] feat: add Kaspersky to DTCG members (#198)
Re: [community-group] Clarify if manually typing and reading token files is a primary concern (#149)
- Re: [community-group] Clarify if manually typing and reading token files is a primary concern (#149)
- Re: [community-group] Clarify if manually typing and reading token files is a primary concern (#149)
- Re: [community-group] Clarify if manually typing and reading token files is a primary concern (#149)
- Re: [community-group] Clarify if manually typing and reading token files is a primary concern (#149)
[community-group] Pull Request: Bump decode-uri-component from 0.2.0 to 0.2.2
- Re: [community-group] Bump decode-uri-component from 0.2.0 to 0.2.2 (#197)
- Re: [community-group] Bump decode-uri-component from 0.2.0 to 0.2.2 (#197)
- [community-group] Merged Pull Request: Bump decode-uri-component from 0.2.0 to 0.2.2
[community-group] Token aliases with invalid or unsuited intermediate value (#196)
- Re: [community-group] Token aliases with invalid or unsuited intermediate value (#196)
- Re: [community-group] Token aliases with invalid or unsuited intermediate value (#196)
- Re: [community-group] Token aliases with invalid or unsuited intermediate value (#196)
- Re: [community-group] Token aliases with invalid or unsuited intermediate value (#196)
- Re: [community-group] Token aliases with invalid or unsuited intermediate value (#196)
[community-group] Token name can be an empty string (#195)
- Re: [community-group] Token name can be an empty string (#195)
- Re: [community-group] Token name can be an empty string (#195)
[community-group] Leading/trailing white space in token names. (#194)
[community-group] `none` values (#193)
[community-group] A token value with multiple aliases (#192)
Re: [community-group] How do you refer to files in the DTCG format? (#164)
- Re: [community-group] How do you refer to files in the DTCG format? (#164)
- Re: [community-group] How do you refer to files in the DTCG format? (#164)
Closed: [community-group] Support json5 in format (#175)
Re: [community-group] Support json5 in format (#175)
Re: [community-group] Remove JSON derived types from the specification (#120)
Closed: [community-group] Use CSS as a transfer format instead of JSON. (#185)
Re: [community-group] Use CSS as a transfer format instead of JSON. (#185)
Closed: [community-group] How to define negative zero in a design tokens file (#184)
Re: [community-group] How to define negative zero in a design tokens file (#184)
Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
- Re: [community-group] Split units and values in type definitions (#121)
Re: [community-group] Status object: simplified audit/decision history (#161)
Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
- Re: [community-group] Types for CSS Keywords (#177)
Re: [community-group] Escape sequences are not defined (#167)
Re: [community-group] Conditional token values (#169)
Re: [community-group] High contrast colors (#91)
[community-group] Possible Color Subtypes/Metadata (#191)
- Re: [community-group] Possible Color Subtypes/Metadata (#191)
- Re: [community-group] Possible Color Subtypes/Metadata (#191)
- Closed: [community-group] Possible Color Subtypes/Metadata (#191)
- Re: [community-group] Possible Color Subtypes/Metadata (#191)
[community-group] Using target platforms to guide the specification (#190)
- Re: [community-group] Using target platforms to guide the specification (#190)
- Re: [community-group] Using target platforms to guide the specification (#190)
Re: [community-group] Shadow type feedback (#100)
Re: [community-group] Themes/Schemes vs. Design Tokens (#187)
- Re: [community-group] Themes/Schemes vs. Design Tokens (#187)
- Re: [community-group] Themes/Schemes vs. Design Tokens (#187)
Re: [community-group] How to deal with "fluid" dimensions (#188)
- Re: [community-group] How to deal with "fluid" dimensions (#188)
- Re: [community-group] How to deal with "fluid" dimensions (#188)
- Re: [community-group] How to deal with "fluid" dimensions (#188)