- From: Donnie D'Amato via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 May 2024 14:37:50 +0000
- To: public-design-tokens-log@w3.org
> I’d say as a general rule, anything more than a single pass/step is probably non-static (and maybe by that definition, some simpler operations are “static” and that’d be OK! But layers upon layers would not be). I think it's a tough sell for me personally. But I'm also known to be more polarizing in my decisions. 😈 > So by that logic, if JSON’s strengths are in describing static data, and we want something more programmatic, I’d probably advocate for outlining a [DSL](https://en.wikipedia.org/wiki/Domain-specific_language) that can describe operations more fluidly, with less indirection. Probably more appropriate for the [Token Operations discussions](https://github.com/ddamato/token-operations/issues) specifically but yes, I'm not trying to tout myself as knowing the first thing about language authoring. But I do want to raise that if we do compute tokens that we shouldn't try to define specific computations like what `alpha` is but instead have a method to describe how to `alpha` so we aren't waiting for tools to implement `alpha`. The community is already waiting for the simplest parts of the spec to be finalized and I can only imagine how long it would take to agree on what `alpha` is meant to do. -- GitHub Notification of comment by ddamato Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/238#issuecomment-2088560988 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 May 2024 14:37:51 UTC