- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 01 Apr 2023 19:15:20 +0000
- To: public-design-tokens-log@w3.org
> It seems prudent to me, that the DTCG spec should aim to provide the means for a designer/team to model the relationship of the tokens to modes, but leave the business of how tokens are translated to generator tools. Leveraging the $extensions field to provide instructions for generator tools accomplishes that very well. As a translation tool implementer I can safely and surely say that we will never go beyond the specification. If there is an expectation of some behavior in translation tools, it needs to be specified. We don't see the point of building tools for a specification and then having to invent critical implementation details. I think it is dangerous to consider `$extensions` as an escape hatch that can be used to fill in holes in this specification. We zero interest in keeping track of what other tools are dumping in `$extensions` and building logic around that. I am still hoping that this format looks at the whole picture, design tools and translation tools. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/210#issuecomment-1493080347 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 1 April 2023 19:15:22 UTC