Re: [community-group] Conflicting language in "References and JSON Pointer Integration" (#383)

> > Does the spec allow using {path} syntax for color components? It's not quite clear since there is a number token which can fit.
> 
> It currently does not, because color is a basic token (it used to be a hex string). A component must be a **composite type** (gradient, typography, etc.) in order to allow aliases within. We also get the same question about `cubicBezier` which also does not allow aliases to numbers within its array either (though some tools may choose to support this, it’s _technically_ invalid).

@drwpow I didnt realize that. I think that the JSON schema currently allows for it. Should I update it?

-- 
GitHub Notification of comment by dgtlntv
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/383#issuecomment-3765431662 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 18 January 2026 15:53:11 UTC