[ https://issues.oasis-open.org/browse/ODATA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Pizzo updated ODATA-747:
--------------------------------
Proposal:
Modify the related ABNF construction rules to allow nanInfinity also for decimalValue:
decimalValue = [SIGN] 1*DIGIT ["." 1*DIGIT] / nanInfinity
doubleValue = decimalValue [ "e" [SIGN] 1*DIGIT ] ; IEEE 754 binary64 floating-point number (15-17 decimal digits)
singleValue = doubleValue ; IEEE 754 binary32 floating-point number (6-9 decimal digits)
nanInfinity = 'NaN' / '-INF' / 'INF'
was:
Modify the related ABNF construction rules to allow nanInfinity also for decimalValue:
decimalValue = [SIGN] 1*DIGIT ["." 1*DIGIT] / nanInfinity
doubleValue = decimalValue [ "e" [SIGN] 1*DIGIT ] ; IEEE 754 binary64 floating-point number (15-17 decimal digits)
singleValue = doubleValue ; IEEE 754 binary32 floating-point number (6-9 decimal digits)
nanInfinity = 'NaN' / '-INF' / 'INF'
> Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal
> ------------------------------------------------------------
>
> Key: ODATA-747
> URL: https://issues.oasis-open.org/browse/ODATA-747
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ABNF Construction Rules, OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol, OData URL Conventions
> Affects Versions: V4.0_CSD03
> Environment: Decimal
> Reporter: Gerald Krause
> Labels: AdoptionBlocker
> Fix For: V4.01_WD01
>
>
> Just as for IEEE 754 floating-point numbers, calculations of Edm.Decimal values also can lead to results that can only be represented by constants for "Not a Number" or "(negative) Infinity".
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
