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

Hey @kaelig I just thought about another topic: relationships.

##There are two types:
### 1) Values from a visual group (what DSP of combines as collections)
- Font properties e.g. font-size, font-weight, font-family
- Shadow properties e.g. shadow color, shadow blur, shadow offset

While one could argue that the font example would be a text-style group, and the tokens make sense on and individual base, this is not true for the shadow example. An `x-offset` of a shadow has no other use. 

### 2) Logical pairs (e.g. a background & text font)
In css this is apparent by having an element and checking the background color and the text color. For tokens you can not know this at the moment.

I personally use the google material approach, where you have a color e.g. `surface` and a text/icon color to use on top `on surface`. I find this very helpful. However you need to logically understand this to make the connection, which is hard for tools.

Therefore it could be helpful to allow for some kind of pairing.

This could be solved via the data properties, but if this use case is bigger, it may make sense to consider it.

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


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

Received on Tuesday, 16 March 2021 19:57:02 UTC