I filed Issue #292 , “Specify a default value for result.rank”. Please contribute your thoughts to the issue’s discussion thread. Thanks, Larry From: Larry Golding (Myriad Consulting Inc) <
v-lgold@microsoft.com> Sent: Wednesday, November 28, 2018 3:40 PM To: Larry Golding (Myriad Consulting Inc) <
v-lgold@microsoft.com>; OASIS SARIF TC Discussion List <
sarif@lists.oasis-open.org> Subject: RE: Default value for rank Sorry, it’s not quite as bad as I thought. We can either specify a numeric default (0? 50? 100?) or not. If we don’t, then at the format level, the absence of the property signifies “unknown”. The SDK can translate “absent” to “-1.0”. We’ve played this trick many times; I don’t know why I keep forgetting it. From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org > On Behalf Of Larry Golding (Myriad Consulting Inc) Sent: Wednesday, November 28, 2018 3:30 PM To: OASIS SARIF TC Discussion List <
sarif@lists.oasis-open.org > Subject: [sarif] Default value for rank What’s the default for result.rank? 0? 50? 100? “-1”, meaning unassigned? (but then we have to set minValue: -1.0, maxValue: 100, and now -0.5 is valid). Null? Is this what breaks us down and forces us to support nullable properties in the code generator? Thanks, Larry