"Long" numbers in response payloads without IEEE754Compatible=true

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CS02
    • Affects Version/s: V4.01_CS01
    • Component/s: JSON Format
    • None
    • Environment:

      Applied

    • Hide

      Keep the rules for requesting and sending representations of numbers.

      Allow services to represent "overly long" numbers in responses without format parameter IEEE754Compatible=true as an instance annotation on the numeric property with term Core.ValueException containing the exact value as a string. The service MAY also include the numeric property with a rounded/inexact value as a JSON number.

      This is not supported in request payloads, clients can use format parameter IEEE754Compatible=true and pass all Int64 and Decimal values as strings.

      Show
      Keep the rules for requesting and sending representations of numbers. Allow services to represent "overly long" numbers in responses without format parameter IEEE754Compatible=true as an instance annotation on the numeric property with term Core.ValueException  containing the exact value as a string. The service MAY also include the numeric property with a rounded/inexact value as a JSON number. This is not supported in request payloads, clients can use format parameter IEEE754Compatible=true and pass all Int64 and Decimal values as strings.
    • Show
      https://www.oasis-open.org/committees/download.php/65505/odata-json-format-v4.01-wd06-2019-06-20.docx  

      Section 3.2 Controlling the Representation of Numbers currently states:


      If not specified, or specified as IEEE754Compatible=false, all numbers MUST be serialized as JSON numbers.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: