Clarify IEEE754Compatible applies to request payloads as well

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.01_OS
    • Affects Version/s: None
    • Component/s: JSON Format
    • None
    • Environment:

      Proposed

    • Hide

      Change:
      "OData JSON payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify this format parameter in the media type returned in the Content-Type header."
      to:
      "OData JSON request and response payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify this format parameter in the media type returned in the Content-Type header."

      (or other clarifications as editor deems appropriate)

      Show
      Change: "OData JSON payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify this format parameter in the media type returned in the Content-Type header." to: "OData JSON request and response payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify this format parameter in the media type returned in the Content-Type header." (or other clarifications as editor deems appropriate)
    • Hide

      https://www.oasis-open.org/committees/download.php/66488/odata-json-format-v4.01-wd09-2020-01-15.docx

       

      Show
      https://www.oasis-open.org/committees/download.php/66488/odata-json-format-v4.01-wd09-2020-01-15.docx  

      Section 3.2 in the JSON format does not make it clear that IEEE 754 Compatibility applies to both response and requests.  Reword the section to make it more clear by stating explicitly which component (client and/or service) can add the IEEE754Compatible format parameter to the Accept and Content-Type headers.

            Assignee:
            Unassigned
            Reporter:
            matt.borges
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: