Re: [community-group] Reserve top-level `$schema` property? (#107)

I agree this could be useful and could double as a versioning field (something we've been meaning to add anyway). We could have the spec version that the file conforms to as part of the URL to the corresponding schema. E.g.:

```jsonc
{
  "$schema": "https://designtokens.org/spec/v1.2.3/schema.json",
  // ^ This file follows version 1.2.3 of the DTCG spec

  // tokens and groups go here as per usual
}
```

I also agree that having a JSON schema for our spec could be useful. It would allow some basic validation of files and can enable some auto-completion features in some IDEs. It's something that's been suggested before and has been discussed at previous editors meetings too. We've just not gotten around to properly exploring the topic yet. When we do, I'm sure @natemoo-re's schema will be a valuable input, so thanks for sharing that!

Also, since we've now [decided to use `$` as our prefix for all format-specific properties](https://github.com/design-tokens/community-group/issues/61#issuecomment-1021459887), this would fit in nicely with that :-)

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


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

Received on Tuesday, 25 January 2022 23:30:40 UTC