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

@drwpow I hear everything you said. I still have reservations about JSON pointers coupling you to the exact syntax used to declare a color, which seems a bit accidental, but... I suppose, with great power... 😌

> > [@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? 😏)

-- 
GitHub Notification of comment by mindplay-dk
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/383#issuecomment-3767081038 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:31:43 UTC