However, in 8-1, the MinTime and MaxTime is an Unsigned32 / INT32U
MinTime Unsigned32 r o INT32U – As specified in the SCD
file for the GoCB, See 1
MaxTime Unsigned32 r o INT32U – As specified in the SCD
file for the GoCB. See 1
What shall the ICT process the values as? Input as Decimal and then pass it as Integer to the application?
Or does it makes sense to change the -6 to have these values as Integer?
If you look at Table 45 in -6, it does point to that way.
To change MinTime and MaxTime base to Integer from Decimal in -6.
Discussion
Created
Status
Approved Future
12 Dec 23
Future Improvement
change to future improvement
22 Jun 23
Approval (Future Improvement)
proposal joint to the tissue
22 Jun 23
Approval (Editoral)
proposal to write
22 Jun 23
Discussion (red)
Accepted to modify both types (tDurationInMilliSec and tBitRateInMbPerSec
22 Jun 23
Accepted
Agree that tDurationInMilliSec should be extended from xs:nonNegativeInteger (arbitrary precision) or xs:unsignedInt (32 bit) and NOT from xs:decimal (which has whole and fractional components).
However, look also at tBitRateInMbPerSec which similarly is extended from xs:decimal but should be extended from xs:nonNegativeInteger (or maybe extend tBitRateInMbPerSec from xs:unsignedLong (64-bit) or xs:positiveInteger (arbitrary precision). Note that xs:unsignedInt is not appropriate here because someone could try to enter 10 GB without using the multiplier which overflows 32-bits.