Re: [community-group] [RFC] Format specification (#1)

From the principles:

> The format is simple, extensible, and as unopinionated as possible

Language agnostic data formats like JSON and YAML are very unopinionated, but don't support things like functions. Should the spec take a stance on how users combine tokens? This would necessitate running all token files through some tool before use.

Is `tokenC = multiply(tokenA, tokenB)` "human readable"? To use `tokenC` in a design, I would need to look up both tokens, convert them to RGB if not stored in that format, and trust that my napkin math is correct.

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

Received on Friday, 24 January 2020 14:45:53 UTC