- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Feb 2025 21:49:54 +0000
- To: public-design-tokens-log@w3.org
Thanks for the original question; we’ve gotten this question [in other issues that have been addressed](https://github.com/design-tokens/community-group/issues/240#issuecomment-2294986119), and at this time we’re not open to revisiting the `$` prefix. TL;DR: this comes from [JSON Schema’s concept of lexical scoping](https://json-schema.org/draft/2020-12/json-schema-core#name-lexical-scope-and-dynamic-s) which uses the `$` keyword to mark reserved words in a dynamic, arbitrarily-nested structure. Another way of looking at it is this specification requires _some_ words to be reserved no matter what; the `$` prefix just gives you more flexibility in naming tokens (including using `value`, `description`, etc.). -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/225#issuecomment-2644193004 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 February 2025 21:49:55 UTC