Skip to content

Identify a list of critical interfaces that implementations should have and empower implementers with better resources #408

Closed
@Relequestual

Description

@Relequestual

The ecosystem has many implementations across many languages, but it's often a real challenge to advise people how to do some things the core team would consider fairly basic, for all implemenations.

The specification tells you what must be true about the JSON Schema, and it lays out requirements for what implementations must support, but it doesn't tell implementers how to support specific elements.

One basic example, being able to reference other schemas is something that's required. Some implementations provide an interface to add schemas ahead of time, while others provide a hook function to allow for resolving references at run time.

One way we can help fix this problem is to identify a list of critical interfaces that implementations should have, and empower implementers with better resources.

Assessed as high impact/low effort during our collaborators summit 2023.

Metadata

Metadata

Labels

summit-resultsIssues created as the result of or related to the 2023 JSON Schema in person summit

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions