Hi Mark
I don't think it's practical to legislate the bounds of this type of attribute in the Open API standard, since the boundaries will depend on implementation. Unless we can get the entire industry to agree an a percentage scale for risk, say 0-100, in which case it would be feasible, using the "maximum" and "minimum" keywords for a "number" property.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 28, 2024 22:50
From: Mark Ussher
Subject: Bounding of Integer data types in specifications
This is a very specific question on the datatype for the creditRiskRating attribute of the CreditProfile in the TMF 629 version 5.0.0 specification.
The specification defines it as an integer but the integer values are not bounded by upper and lower values. Should the TMF specification be improved to include the bounded values, and a definition for each of the integer values that can be assigned, or perhaps define a "Risk" enumeration with values "High", "Medium" and "Low".
A more general question is whether the TMF API specifications should be regarded as baselines, and service providers feel free to extend them to suit their specific requirements.
------------------------------
Mark Ussher
Telstra Corporation
------------------------------