- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Apr 2022 08:42:45 +0000
- To: public-design-tokens-log@w3.org
`$include` is definitely interesting as it allows the creation of a single tokens collection that is composed of multiple sources that can originate from multiple tools. I would however not include a network protocol as a way to include design token files. This has obvious security concerns and doesn't solve anything that can not be worked around :) -------------- `$include` as a feature does not eliminate the need to define the parsing and resolving steps in this specification. My example above was also just to illustrate the need for a full definition of parsing and resolving. This is something that other specifications also define for their syntaxes and helps to eliminate subtle interop issues. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/123#issuecomment-1091333799 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 April 2022 08:42:46 UTC