Re: [community-group] Make whitespace invalid in token names (#216)

• From: Matt Ström-Awn via GitHub <noreply@w3.org>
• Date: Tue, 17 Jun 2025 18:38:20 +0000
• To: public-design-tokens-log@w3.org
• Message-ID: <issue_comment.created-2981445335-1750185498-noreply@w3.org>

I'm still a fan of the JSON definition of a string, as it is:
1. very precise, and
2. well-supported from a tooling perspective

Here's the definition:
![Screen-Capture-2025-06-17-14-31-36](https://github.com/user-attachments/assets/e1a677dc-72ab-4e75-a849-cac658e9ac0d)

The upside is that we can say a DTS file _must_ be valid JSON. On the downside, it does mean that whitespace is valid in token names. We can follow up on what is syntactically valid vs. recommended/not recommended as a non-normative thing.


-- 
GitHub Notification of comment by ilikescience
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/216#issuecomment-2981445335 using your GitHub account


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

Received on Tuesday, 17 June 2025 18:38:21 UTC