[community-group] Merged Pull Request: clarify that token names must be valid json strings

ilikescience has just merged ilikescience's pull request 327 for https://github.com/design-tokens/community-group:

== clarify that token names must be valid json strings ==
## Changes

Specifically requires token names to be a valid JSON string. Currently, keeps the restrictions on using `{`, `}`, and `.` inside token names, though it might be worth revisiting that to make it easier to maintain parity with established standards.

Closes https://github.com/design-tokens/community-group/issues/194, but needs clarification on aliasing/referencing tokens with whitespace. I'll be updating #298 to include this guidance.

Also, we might want to provide non-normative guidance to vendors on how to manage tokens with whitespace in their names.

## How to Review

`pnpm run dev`, check for errors :)


See https://github.com/design-tokens/community-group/pull/327


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

Received on Wednesday, 22 October 2025 14:46:15 UTC