Skip to content

stable-release

New issue
Open
No due date
Last updated Jun 8, 2025
81% complete

Anything which should be done for a stable release

List view

0 issues of 69 selected

  • Proposal: Remove initial resolution step for dynamic references

    Status: Closed (completed).
    #1140 In json-schema-org/json-schema-spec;
    · by jdesrosiers was closed on Mar 11, 2025

  • Section "Keyword independence" is written twice

    Status: Closed (completed).
    #1218 In json-schema-org/json-schema-spec;
    · by awwright was closed on Nov 8, 2024

  • Avoid language that seems to attempt to modify JSON parsing behavior

    clarificationItems that need to be clarified in the specification
    core
    Priority: Medium
    Status: Closed (completed).
    #1284 In json-schema-org/json-schema-spec;
    · by handrews was closed on Nov 12, 2024

  • Consider whether "$schema" should allow fragments

    core
    Type: Enhancement
    Status: Closed (completed).
    #1292 In json-schema-org/json-schema-spec;
    · by handrews was closed on Oct 20, 2024

  • contentSchema has implementation-defined referencing behavior when contentMediaType is not present

    Status: Closed (completed).
    #1381 In json-schema-org/json-schema-spec;
    · by Julian was closed on Feb 14, 2025

  • Schema Update: Require dialect to be declared and understood

    Status: Closed (completed).
    #1420 In json-schema-org/json-schema-spec;
    · by jdesrosiers was closed on Sep 20, 2023

  • Reconsider allowing "contains" to apply to objects

    validation
    Status: Closed (completed).
    #1358 In json-schema-org/json-schema-spec;
    · by handrews was closed on Nov 13, 2023

  • URI/IRI "Normalization" and Compatibility

    Status: Closed (completed).
    #1349 In json-schema-org/json-schema-spec;
    · by watuwo was closed on Nov 2, 2024

  • Convert the spec to Markdown

    Status: Closed (completed).
    #1335 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Aug 25, 2023

  • Write blog post introducing and describing the new process

    Status: Closed (completed).
    #1338 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Jan 14, 2025

  • description of readOnly is ambiguous and refers to property when it should be instance

    Status: Closed (completed).
    #1402 In json-schema-org/json-schema-spec;
    · by DavidBiesack was closed on Jul 10, 2024

  • Update guidance on use with non-JSON formats

    Status: Closed (completed).
    #1390 In json-schema-org/json-schema-spec;
    · by awwright was closed on Nov 28, 2024

  • Spec and meta-schema seem inconsistent w.r.t empty "type" array

    Status: Closed (completed).
    #1404 In json-schema-org/json-schema-spec;
    · by aha79 was closed on Nov 28, 2024

  • Pattern: clarification on whether leading and trailing delimiters are allowed or required

    Status: Closed (completed).
    #1478 In json-schema-org/json-schema-spec;
    · by spacether was closed on Feb 13, 2025

  • Encountering <code>$schema</code> during meta-schema validation

    Status: Closed (completed).
    #1442 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Nov 28, 2024

  • Statement on annotation values is unclear

    Status: Closed (completed).
    #1493 In json-schema-org/json-schema-spec;
    · by hudlow was closed on Feb 14, 2025

  • Proposal: Make <code>format</code> validate by default

    Status: Closed (completed).
    #1520 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Nov 21, 2024

  • 🧹 Clarification: Scopes section could be improved

    core
    Status: Closed (completed).
    #1566 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Apr 26, 2025

  • 🧹 Clarification: MAYs in several sections are linquistic, not requirements

    validation
    Status: Closed (completed).
    #1573 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Feb 22, 2025

  • Link directly to targets

    core
    proposalInitial discussion of a new idea. A project will be created once a proposal document is created.
    validation
    Status: Closed (completed).
    #1536 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Feb 2, 2025

  • 🧹 Clarification: Behavior for duplicate <code>$id</code>s or <code>$anchor</code>s

    Status: Closed (completed).
    #1533 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Nov 12, 2024

  • Clean-up of stable features and removal of unstable features

    Status: Closed (completed).
    #1444 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Jan 19, 2025

  • Should we have a supplementary spec template for proposals?

    Status: Closed (completed).
    #1443 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on May 15, 2024

  • Fixing <code>contains</code> and <code>minContains</code>

    Status: Not planned (skipped).
    #1446 In json-schema-org/json-schema-spec;
    · by gregsdennis was closed on Sep 20, 2023

  • We should all agree what constitutes an "implementation"

    Status: Closed (completed).
    #1440 In json-schema-org/json-schema-spec;
    · by Relequestual was closed on Feb 8, 2024
    •