- From: Maximilian Blazek via GitHub <noreply@w3.org>
- Date: Mon, 19 Jan 2026 08:37:57 +0000
- To: public-design-tokens-log@w3.org
> > > [@drwpow](https://github.com/drwpow) I didnt realize that. I think that the JSON schema currently allows for it. Should I update it?
> >
> >
> > Ah yes we should fix that! I didn’t catch that, apologies.
>
> wait, so you're saying you'll update the schema to _disallow_ references in component definitions?
>
> this wouldn't work like Drew said?
>
> ```
> "primary": {
> "$type": "color",
> "$value": { "colorSpace": "oklch", "components": [0.65, 0.18, { "$ref": "#/brand/hue/$value" }] }
> },
> "hue": {
> "$type": "number",
> "$value": 264,
> "$description": "Shared hue for brand color family"
> },
> ```
>
> I think `{ "$ref" }` should work anywhere in the object graph, should it not?
>
> Isn't that what makes JSON pointers useful/powerful? (dangeous? 😏)
What I meant and what was updated in #387 was to disallow curly brace references in non-composite tokens. So the updated JSON schema still allows for JSON pointers in sub-values of non-composite tokens, just not curly brace references. :)
--
GitHub Notification of comment by dgtlntv
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/383#issuecomment-3767103823 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 January 2026 08:37:58 UTC