Re: [community-group] Should composites be part of the MVP specification? (#54)

I know I'm a bit out of the loop on the conversation, but I'd love to keep digging on why composite types need to be further defined at all, whether by a user (in user-defined composite types) or by the spec (in predefined composite types).

To take a common use case, for example, say I define a composite token for a type style:

```json
{ "display-large" : {
    "type": "composite",
    "description": "The largest heading",
    "value": {
        "font":  {
            "type": "string",
            "value": "Roboto Regular"
        }, {
        "size": {
            "type": "number",
            "value": "57"
        }
    }
}
```
Is there a benefit to having some further definition? My first thought is that it might give a parser some hints as to what the end user will do with those tokens, but I imagine that the same could be accomplished by inferring the use case from the contents.


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


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

Received on Tuesday, 11 January 2022 22:58:14 UTC