[community-group] Remove JSON derived types from the specification (#120)

romainmenke has just created a new issue for https://github.com/design-tokens/community-group:

== Remove JSON derived types from the specification ==
https://design-tokens.github.io/community-group/format/#types

This part of the specification assumes that implementers will have an inherent understanding of certain types and how to handle them.

This implicit typing will lead to interop issues.
It's better to have exact definitions for each type supported in the schema.

An obvious example is `String`.
When converting a value to CSS it is non-obvious if should become an ident token or a string token.

```json
{
  "$value": "center"
}
```

```css
.foo {
  content: "center";
}
```

or

```css
.foo {
  text-align: center;
}
```

You also can't do this in the tokens file :

```json
{
  "$value": "\"center\""
}
```

Because that dictates how strings work in any consuming context.

Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/120 using your GitHub account


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

Received on Friday, 25 March 2022 18:38:44 UTC