- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jan 2022 22:37:22 +0000
- To: public-design-tokens-log@w3.org
Does anyone have _objections_ to going down the prefix route? If not, I think we should press ahead and update the spec draft accordingly. All that remains is to choose a prefix. I don't have a strong preference myself. As @TravisSpomer noted, `$` is similar to what [JSON Schema](https://json-schema.org/learn/getting-started-step-by-step) uses for some of its keywords. That may or may not be a reason for our format to use the same character. [JSON-LD](https://json-ld.org/) on the other hand uses `@` as a prefix for "special" things, so that might be another alternative to consider. And then there's the `_` as @ilikescience has proposed. How about we do a vote? React with the emoji that corresponds to your preferred prefix: | **Prefix** | **Emoji** | |-----------|-----------| | `$` (dollar sign) | 😄 | | `@` (at sign) | ❤️ | | `_` (underscore) | 🚀 | | Other - suggest in a comment | 👎 | -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/61#issuecomment-1014930778 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 January 2022 22:37:23 UTC