Is your feature request related to a problem? Please describe.
Yes. SSVC requires decision-point values and outcomes to be ordered sets so that relationships between decisions can be reasoned about and validated. SEE ADR's https://certcc.github.io/SSVC/adr/0009-outcomes-are-ordered-sets/ and https://certcc.github.io/SSVC/adr/0008-decision-points-are-ordered-sets/
However, it is not clear from the documentation what happens when a proposed decision point has values that cannot be meaningfully ordered—for example, an attribute such as color: red, blue, green. Without a meaningful ordering, the assumptions used to construct and validate an SSVC decision model may not hold.
Describe the solution you'd like
Add documentation and examples showing how to identify decision points and outcomes that cannot be meaningfully ordered, how this affects SSVC decision-table construction and validation, and when SSVC may therefore not be an appropriate modeling approach for such decision-making.
Is your feature request related to a problem? Please describe.
Yes. SSVC requires decision-point values and outcomes to be ordered sets so that relationships between decisions can be reasoned about and validated. SEE ADR's https://certcc.github.io/SSVC/adr/0009-outcomes-are-ordered-sets/ and https://certcc.github.io/SSVC/adr/0008-decision-points-are-ordered-sets/
However, it is not clear from the documentation what happens when a proposed decision point has values that cannot be meaningfully ordered—for example, an attribute such as color: red, blue, green. Without a meaningful ordering, the assumptions used to construct and validate an SSVC decision model may not hold.
Describe the solution you'd like
Add documentation and examples showing how to identify decision points and outcomes that cannot be meaningfully ordered, how this affects SSVC decision-table construction and validation, and when SSVC may therefore not be an appropriate modeling approach for such decision-making.