[OASIS Issue Tracker] Created: (ODATA-549) Clarify use of IEEE754Compatible format parameter

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

Clarify use of IEEE754Compatible format parameter
-------------------------------------------------

                 Key: ODATA-549
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-549
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData JSON Format
    Affects Versions: V4.0_CSD03
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_CS02


In ODATA-342 we introduced the IEEE754Compatible for formatting Int64 and Decimal values as string. However, we didn't clarify or show examples of how this is used.

According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7:

"Parameters MAY follow the type/subtype in the form of attribute/value pairs (as defined in section 3.6)."

Which seems to imply that Parameters MAY (or MAY NOT) follow the type/subtype, and if they do follow they would be in the form of attribute/value pairs.

We should therefore clarify that the IEEE754Compatible format parameter with a value of TRUE means Int64 and Decimal values are serialized as string, and a value of FALSE (or omitting the parameter) means that Int64 and Decimal are serialized as numbers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira