[OASIS Issue Tracker] (ODATA-771) Exponential notation for Edm.Decimal values in JSON payloads

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58550#comment-58550 ] 

Evan Ireland commented on ODATA-771:
------------------------------------

Also consider that Term Org.OData.Measures.V1.Scale has a maximum value of 255 (and cannot be nagative). So its applicability to a DECFLOAT stored in a Property of type Edm.Decimal would be in doubt.

It seems clear that Edm.Decimal is, by design, fundamentally different from decimal floating point.


> Exponential notation for Edm.Decimal values in JSON payloads
> ------------------------------------------------------------
>
>                 Key: ODATA-771
>                 URL: https://issues.oasis-open.org/browse/ODATA-771
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA03
>
>
> IEEE754 defines the DECFLOAT data type for high-precision decimal arithmetic. They have 16 or 34 decimal digit mantissas and exponents between -383 and +384 or -6143 and +6144.
> The correct, lossless representation of DECFLOAT values is an Edm.Decimal with unspecified precision and variable scale.
> The OData JSON Format represents Edm.Decimal values as JSON numbers, and JSON numbers allow exponential notation, so 
> "VeryLittle":1.4e-6143
> should be valid in JSON payloads.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)