- From: Dan Donald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Aug 2022 16:12:13 +0000
- To: public-design-tokens-log@w3.org
@lauthieb I think part of the structure here is not just about deprecation but the full history that could be written across products/touch-points that interact with the tokens. Knowing when it was added, why and by who becomes more valuable over time when tokens truly become the core of an organisation's site/app/design strategy. I agree that it certainly could get bulky! Perhaps a `token.history.json` file might work? The issue there becomes the fragility of maintaining relationships between nomenclature than might change over time. Use IDs as reference? The argument against might be that Git does this well already, but as we know tokens might never reach Git - it depends entirely on a given set-up...so some kind of changelog/history sounds like the kind of maturity we may need in an interoperable space Really curious what others think too! -- GitHub Notification of comment by hereinthehive Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/161#issuecomment-1233142509 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 August 2022 16:12:15 UTC