- From: Drew Powers via GitHub <noreply@w3.org>
- Date: Fri, 30 Jan 2026 16:00:28 +0000
- To: public-design-tokens-log@w3.org
I hadn’t heard of `application/schema+json`. It seems to be used by some JSON schemas, but not all. According to the README [in the library](https://github.com/hyperjump-io/json-schema?tab=readme-ov-file#usage): > You can add/modify/remove support for any media-type using the [plugin system](https://github.com/hyperjump-io/browser/#media-types) provided by @hyperjump/browser. The schemas work in VS Code just fine with `application/json`, and it looks like [schemastore.org](https://schemastore.org), a popular JSON Schema library, serves all its schemas with simple `application/json`. Given this is a nonstandard MIME type, and this change is only in service of a single library, I’m inclined to not accept this PR and keep it as `application/json` unless you can you provide more evidence about the tradeoffs of `application/schema+json`? Such as: - IDE support (VS Code, Cursor, others?) - Prior art—which services/JSON Schema utilities use `application/schema+json`? - Which server libraries serve JSON Schema using `application/schema+json`? (i.e. how do others implement this—is it manual? are there libraries that automatically detect it?) -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/388#issuecomment-3824453220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 January 2026 16:00:29 UTC