Re: [community-group] Conflicting language in "References and JSON Pointer Integration" (#383) from Drew Powers via GitHub on 2026-01-16 (public-design-tokens-log@w3.org from January 2026)

From: Drew Powers via GitHub <noreply@w3.org>
Date: Fri, 16 Jan 2026 20:21:47 +0000
To: public-design-tokens-log@w3.org
Message-ID: <issue_comment.created-3761669012-1768594904-noreply@w3.org>

> 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).

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


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

Received on Friday, 16 January 2026 20:21:47 UTC