Currently, SSVC's DecisionTable objects lack versioning rules. This is a significant omission — without versioning conventions, it is unclear how to track changes to decision tables, how to communicate compatibility, or how to deprecate old versions. We should define versioning semantics (e.g., semantic versioning), rules for when a version bump is required, and how versions should be represented in the Python model and JSON/CSV data files.
Currently, SSVC's
DecisionTableobjects lack versioning rules. This is a significant omission — without versioning conventions, it is unclear how to track changes to decision tables, how to communicate compatibility, or how to deprecate old versions. We should define versioning semantics (e.g., semantic versioning), rules for when a version bump is required, and how versions should be represented in the Python model and JSON/CSV data files.