Re: [community-group] Status object: simplified audit/decision history (#161)

Fair comment!

I guess I see that for an individual token, you have many use cases. If it's an alias, it effectively defers to the originating token for the history but may have a status attached to it. Moving a token is interesting - perhaps that's actually a remapping? One deprecating and assigned to the new one so the audit trail is still there?

On the whole, I don't see many changes needed. If the core values, however they're expressed haven't changed, the audit log would be in the change of relationship in the component-level token or something. The chain is circumstantial with transitory relationships

-- 
GitHub Notification of comment by hereinthehive
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/161#issuecomment-1196942115 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 27 July 2022 15:54:08 UTC