Re: [community-group] Shadow type feedback (#100)

Another thought: Should the standardization of design tokens empower (to build custom design systems) or limit down (to follow a given approach)?
Just using primitive tokens leaves a lot of space for interpretation and thus causes a lot of work and vagueness for translation tools.
Narrowing it down to composite tokens helps avoiding disambiguation, but on the other hand assumes how tokens should be used. And we can’t for see future frameworks, design systems, whatever (maybe we don’t have to, because this will be the standard ?!).

Is there something in between? Like a name-spaced type set?
like 

```json
{
  "dropShadow": {
    "$type": "@web/shadow",
    "$value": {
      "offsetX": "0px",
      "offsetY": "0px",
      "blur": "2px",
      "spread": "4px",
      "color": "#cccccc"
    }
  }
}
```

or even an offer of multiple types?
(thinking of multiple color spaces or ways of defining `line-height` (like in px, w/o unit or em....))

```json
{
  "dropShadow1": [
    {
      "$type": "@web/shadow",
      "$value": {
        "offsetX": "0px",
        "offsetY": "0px",
        "blur": "2px",
        "spread": "4px",
        "color": "#cccccc"
      }
    },
    {
      "$type": "@flutter/shadow",
      "$value": {
        "blurRadius": 2,
        "spreadRadius": 4,
        "color": "#cccccc",
        "offset": [0, 0],
        "blurStyle": "normal"
      }
    }
  ]
}
```

Downside: this does not look like a standard, but like a collection of different platform definitions.

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


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

Received on Sunday, 12 June 2022 17:29:36 UTC