Clarification of the numerical range

As common set of formula might be used, ensuring a bounded range
could help for future features.
pull/8/head
Alexandre Dulaunoy 2017-11-30 15:37:20 +01:00
parent a92b7eb648
commit 8299677163
No known key found for this signature in database
GPG Key ID: 09E2CD4944E6CBCD
1 changed files with 3 additions and 0 deletions

View File

@ -133,6 +133,9 @@ description fields **MAY** be used at predicates or values level to add a descri
numerical_value fields **MAY** be used at a predicate or value level to add a machine-readable numeric value to a specific predicate or value. numerical_value fields **MAY** be used at a predicate or value level to add a machine-readable numeric value to a specific predicate or value.
The field is represented as a JSON number. Implementations **SHOULD** use the decimal value provided to support scoring or filtering. The field is represented as a JSON number. Implementations **SHOULD** use the decimal value provided to support scoring or filtering.
The decimal range for numerical_value **SHOULD** use a range from 0 up to 100. The range is recommended to support common mathematical properties
among taxonomies.
Example use of the numerical_value in the MISP confidence level: Example use of the numerical_value in the MISP confidence level:
~~~~ ~~~~