Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-920

Specify overflow for int data types (-INF, INF, NaN)

    Details

    • Proposal:
      Hide

      New Proposal:

      1) Because annotating numeric values of arrays is problematic, and we are no longer trying to use JSON Schema as our schema language, revert application of the numericValueException annotation and continue the 4.0 literal "INF", "-INF", and "NaN" values.
      2) Support these values all numeric types. --> reduced to Decimal with floating scale by ODATA-1091
      3) Support -INF and INF for Edm.Date and Edm.DateTimeOffset --> OData Temporal Extension

      Previously applied proposal from 2016-5-12:

      1) Add a new annotation, "odata.numericValueException", with valid values "INF", "-INF" and "NaN".
      2) Services don't return the property, just the property annotation specifying the value exception:
      "NumberOfODataUsers@odata.numericValueException":"INF"
      3) Could be applied to any numeric type.
      4) For 4.01 clients, always return this for all numeric types, including single/double, instead of as property values.

      Show
      New Proposal: 1) Because annotating numeric values of arrays is problematic, and we are no longer trying to use JSON Schema as our schema language, revert application of the numericValueException annotation and continue the 4.0 literal "INF", "-INF", and "NaN" values. 2) Support these values all numeric types. --> reduced to Decimal with floating scale by ODATA-1091 3) Support -INF and INF for Edm.Date and Edm.DateTimeOffset --> OData Temporal Extension Previously applied proposal from 2016-5-12: 1) Add a new annotation, "odata.numericValueException", with valid values "INF", "-INF" and "NaN". 2) Services don't return the property, just the property annotation specifying the value exception: "NumberOfODataUsers@odata.numericValueException":"INF" 3) Could be applied to any numeric type. 4) For 4.01 clients, always return this for all numeric types, including single/double, instead of as property values.
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/60255/odata-v4.01-wd02-part2-url-conventions-2017-03-10.docx https://www.oasis-open.org/committees/download.php/60257/odata-json-format-v4.01-wd02-2017-03-13.docx

      Description

      See ODATA-785 for a description of the issue --> Comments Section.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo
              Reporter:
              martinzurmuehl Martin Zurmuehl
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: