You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current state, aas-core-codegen supports integer primitives although they are not part of the official meta-model yet. If the integers become part of the meta-model, we have to make sure that they are all constrained to the range [-2^53 + 1, 2^53 - 1], i.e.[-9007199254740991, 9007199254740991], (both inclusive) so that the JSON format is interoperable with XML and other formats.
JSON intrinsically represents numbers as 64-bit floats, so there might be silent precision loss.
Such a constraint can be implemented by a unit test in aas-core-meta which checks that all integers are constrained, similar to how we check that all strings are serializable to XML.
The text was updated successfully, but these errors were encountered:
In the current state, aas-core-codegen supports integer primitives although they are not part of the official meta-model yet. If the integers become part of the meta-model, we have to make sure that they are all constrained to the range
[-2^53 + 1, 2^53 - 1]
, i.e.[-9007199254740991, 9007199254740991]
, (both inclusive) so that the JSON format is interoperable with XML and other formats.JSON intrinsically represents numbers as 64-bit floats, so there might be silent precision loss.
Such a constraint can be implemented by a unit test in aas-core-meta which checks that all integers are constrained, similar to how we check that all strings are serializable to XML.
The text was updated successfully, but these errors were encountered: