Create dataclass to represent DecisionTable selection #800

Activity

1. ahouseholder

   added

   enhancementNew feature or requestNew feature or request

   on Jun 23, 2025
2. ahouseholder

   added a parent issue on Jun 23, 2025

   • DecisionTable object extensions #796
3. ahouseholder

   added

   tech/backendBack-end tools, code, infrastructureBack-end tools, code, infrastructure

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

   on Jul 1, 2025
4. ahouseholder commented on Jul 29, 2025

   

   ahouseholder

   on Jul 29, 2025

   ContributorAuthor

   More actions

   The decision point selection object was significantly updated in #821

   That object is specifically geared toward representing a set of selections drawn from a set of decision points.

   However, the DecisionTable object is more about selecting rows from the mapping value. That's a bit different from what's in ssvc.selection. So I think this is going to wind up being something different from ssvc.selection
5. ahouseholder commented on Aug 13, 2025

   

   ahouseholder

   on Aug 13, 2025

   ContributorAuthor

   More actions

   While creating the CVSS v4 MacroVector → QSR DecisionTable, we ran across a conflict between two requirements:

   • As of Fix a few bugs around Human Impact decision point and decision table #870, we enforce that DecisionTable objects must fully map all input DecisionPointValue combinations
   • In Add CVSS v4 MacroVector to Quality Severity Rating DecisionTable #871, we had to work around this requirement because CVSSv4 has some "invalid" macrovectors that are logical impossibilities.

   This leads us to a few side effect notes on any implementation of the current issue:

   1. A DecisionTable downselect object must not require full input coverage, because that defeats the purpose of being a downselect.
   2. Every item in a downselect object mapping must be present in the parent DecisionTable object from which it is derived.
   3. We'd probably want some sort of converter method to go from a DecisionTable to the downselect object.
   4. That converter might handle CVSS v4 QSR specially, by explicitly removing the "invalid" rows from the mapping (i.e., the rows where EQ3=L and EQ6=H). These would be unreachable by any rational input for the EQ sets anyway.