- From: Nico André via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2022 10:52:33 +0000
- To: public-design-tokens-log@w3.org
> The spec only mentions that using JSON has the side effect of being somewhat human-readable. But it doesn't even state that this is a goal or a requirement. You're right @romainmenke - I did a shortcut here. I do share your claims around making the format future proof being careful on architectural choices. Yet, I do see the `$type` resolution as a quite simple macro that could not drive regressions moving forward, at least not with its [current definition](https://design-tokens.github.io/community-group/format/#type-0). IMO, what is actually at stake here is performance. Any loose schema with implicit resolutions like `$type` will cost a couple of extra spins to make sure of its integrity / validity. But in the case of DTCG, aliasing is already way more greedy compared to `$type` resolution and seems to be a valuable feature for the format. These are definitely design decisions that will impact any future tools, UX and performance. -- GitHub Notification of comment by nclsndr Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/139#issuecomment-1296915048 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 10:52:35 UTC