Re: [community-group] Split units and values in type definitions (#121)

> > this specification is precise and exact and doesn't leave room for implementors to make the wrong assumptions

> And that's exactly the mindset/philosophy that imo leads to over-engineering the spec. You can't realistically do this - pragmatism is just as important as correctness, if not more important.

I am not sure how to respond to that.

A specification, by its very nature, is a document that helps and guides multiple implementors realize different implementations that still behave in the same way. A primary purpose of specifications is to have interop between various tools.

This is not a mindset or philosophy... 😕 



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


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

Received on Thursday, 12 September 2024 11:23:44 UTC