[OASIS Issue Tracker] (ODATA-747) Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal

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

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

Michael Pizzo commented on ODATA-747:
-------------------------------------

Question is: what should server do for 4.0 clients?  

Some Optioins:
1) return null
    a) perhaps with an annotation to specify that it's +/- INF or NaN? (require that properties that could contain +/-INF or NaN be nullable)
2) use a different type
3) server error 500
4) return the string +/- INF or NaN and give the client the chance figure it out
5) Return some other value, along with the annotation to specify that it's +/- INF or NaN

It would be helpful to understand what common client programming languages do in their decimal equivalents; if they have representations of these special values then it probably makes sense just to serialize the +/-INF or NaN as the property value, otherwise it might make sense to serialize as null and add an annotation since that's probably what the client representation would need to do anyway (and, in this case, it would be useful to annotate the property as to whether or not it may return these special values as it may affect the generated code).
.

> 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)