- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2022 17:09:35 +0000
- To: public-design-tokens-log@w3.org
@ChucKN0risK This is really unexpected. I truly can not understand the reasoning here combined with the core concept of this specification. This specification exists to remove interop issues between tools. If anyone needs a type that doesn't exist in the specification they should open an issue here so that it can be specified and a new version can be published. This is in direct conflict with : > It makes the spec flexible enough to support a whole variety of use cases we can't guess. > JSON derived types enable teams and tools to create proprietary types, which can help inform future spec iterations and we do expect more types to be needed in the future. If teams or tools need to store and communicate bits of information that are not part of this specification they can use `$extensions` or use a separate file. ------ > It removes the burden of thinking about all types possible and thus it helps us maintain and release the spec as easily as possible. I can be as simple as reference to the JSON specification and `"$type": "string"` This extra effort does not way up against the ambiguity in the current specification. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/120#issuecomment-1297403020 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 October 2022 17:09:37 UTC