Skip to content

Create ADR for SSVC JSON schema versioning #601

Description

@ahouseholder

Yeh - I think we can move that way later without a problem. The idea would be to provide "breaking" vs "non-breaking" Schema changes to be version controlled. Mostly from Snowplow's musings .

The challenge with some of these issues seems to show that much of the schema versioning itself is so experimental and we are trying to imagine an operational viability which is sort of impossible to know till we have enough usage.

Originally posted by @sei-vsarvepalli in #599 (comment)

This issue can be resolved by a PR that includes a new ADR addressing JSON schema versioning and pointing to the snowplow.io link in the above comment.

Activity

  1. sei-vsarvepalli commented on Jul 15, 2024

    @sei-vsarvepalli
    Contributor

    Also related #596

  2. added
    tech/dataData implementation (content of /data, data object instances, etc.)
    on Jul 1, 2025
  3. sei-renae commented on Apr 6, 2026

    @sei-renae
    Contributor
  4. Copilot commented on Apr 6, 2026

    Copilot
    Contributor

    The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 12BF:42323:1063CB7:1647E91:69D3EB15)

  5. added a commit that references this issue on May 5, 2026
    d91d032
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    tech/dataData implementation (content of /data, data object instances, etc.)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions