[OASIS Issue Tracker] (ODATA-557) Allow exponential notation for Edm.Decimal

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

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

Ralf Handl commented on ODATA-557:
----------------------------------

Worst case: respond with 400 Bad Request and an error message explaining that this service contains data that cannot be represented with plain V4.0.

Best case: morph the response down to V4.0, use Scale="variable" in $metadata and use 500 Bad Request for data requests that encounter decimal values that the service is unwilling to represent with kilobytes of zeroes.

If a service uses Scale="floating" it also has to indicate version 4.01 in the $metadata document.

> Allow exponential notation for Edm.Decimal
> ------------------------------------------
>
>                 Key: ODATA-557
>                 URL: https://issues.oasis-open.org/browse/ODATA-557
>             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: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> IEEE754 also 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.
> Representing them exactly in current Edm.Decimal would result in at most 34 non-zero digits and several thousand zeroes. This waste can easily be avoided by allowing exponential notation also for Edm.Decimal.



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