I suggest the following structure for the schema:

Document name	Purpose	Hosted on
devContainer.schema.json	master schema consisting only of references to the schemas below (base schema as well as all schemas containing vendor specific properties)	github.com/devcontainers/spec
devContainer.base.schema.json	schema describing all base properties as documented here	github.com/devcontainers/spec
devContainer.vscode.schema.json	schema describing vscode specific properties	github.com/Microsoft/vscode
devContainer.codespaces.schema.json	schema describing codespaces specific properties	github.com/github/codespaces or similar
devContainer.vendorFoo.schema.json	schema describing 'vendor foo' specific properties	location provided by 'vendor foo'

The catalog file at schemastore.org will get an entry to the master schema:

    {
      "name": "Dev Container configuration file",
      "description": "The devcontainer.json file contains any needed metadata and settings required to configurate a development container for a given well-defined tool and runtime stack",
      "fileMatch": ["devcontainer.json", ".devcontainer.json"],
      "url": "https://raw.githubusercontent.com/devcontainers/spec/main/schemas/devContainer.schema.json"
    }

Vendors such as VS Code, Codespace, GitPod, Foo.. are free to choose any hosting location (can also be on schemastore.org)
The master schema is just a collection of $refs that are and'ed: allOf: [ { $ref: devContainer.base.json, $ref: ..., $ref .... } ].
For a new vendor to add a new $ref to the master schema, a PR against devcontainers/spec/ needs to be made. We will need to come up with a policy that decides which contributions can be accepted.

I imagine the policy to accept a new $ref would be:

the newly added properties need to follow certain naming guidelines (camelCase, dot separated, ect...)
all properties need to be documented
a global link to documentation/spec needs to be provided so it can be added to the devcontainers/spec documentation as well

Publish devcontainer.json schema #14

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions