The W3C has a working group producing the Design Tokens Format Module. It's not stable yet and has a lot of open questions so we shouldn't shift our tooling over to that format anytime soon, BUT it should be trivial to add "W3C" as another export from the pipeline. Then someday in the future we could rip out things that aren't supported by the W3C system into a preprocessing step (hopefully by using the extensions node in their format), the same way that this codebase heavily preprocesses tokens before sending them through Style Dictionary, and then we could use the standard W3C form as our format.
The W3C has a working group producing the Design Tokens Format Module. It's not stable yet and has a lot of open questions so we shouldn't shift our tooling over to that format anytime soon, BUT it should be trivial to add "W3C" as another export from the pipeline. Then someday in the future we could rip out things that aren't supported by the W3C system into a preprocessing step (hopefully by using the
extensions
node in their format), the same way that this codebase heavily preprocesses tokens before sending them through Style Dictionary, and then we could use the standard W3C form as our format.