Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update proposal support approach #1617

Open
Assignees
Labels
clarificationItems that need to be clarified in the specification
Milestone
@gregsdennis

Description

In PROPOSALS.md, we have a section on how proposals will be supported through the meta-schema by adding the keywords to the meta-schema with a true subschema so that the keyword's value can continue to evolve. Then implementations would bear the responsibility of validating a keyword's subschema based on the proposal version that they support.

I wonder if we can instead take advantage of the new meta-schema extension model to include proposals. We would build the extension schemas ourselves, but we wouldn't necessarily be able to create all permutations of combinations of those proposals. Maybe we just create one extension that includes all open proposals?

It would produce new $ids for proposals, and people who want to use extensions would have their schemas use a different $schema value. Maybe that's a good thing...

Metadata

Metadata

Labels

clarificationItems that need to be clarified in the specification

Type

No type

Projects

Status

In Discussion

Relationships

None yet

Development

No branches or pull requests

Issue actions

    AltStyle によって変換されたページ (->オリジナル) /