[OASIS Issue Tracker] (ODATA-754) Clarify that numeric enum values are serialized as strings

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

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

Michael Pizzo commented on ODATA-754:
-------------------------------------

Minor grammatical error introduced in applying this issue to section 7.1 of [JSON]:
The new text reads:
"Enumeration values are represented as JSON strings whose content satisfies the enumValue in [OData-ABNF]"

should read:
"Enumeration values are represented as JSON strings whose content satisfies the rule enumValue in [OData-ABNF]"

(the word "rule" is missing)



> Clarify that numeric enum values are serialized as strings
> ----------------------------------------------------------
>
>                 Key: ODATA-754
>                 URL: https://issues.oasis-open.org/browse/ODATA-754
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Applied]
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA03
>
>
> Section 7.1 states that
>     Values of type enumValue are represented as JSON strings using the
>     enumerationMember, defined in [OData-ABNF], where available.
> Unfortunately it does not state explicitly how the numeric alternative values for enumeration members are to be serialized.
> The original intent stated in https://issues.oasis-open.org/browse/ODATA-96 and the referenced revised proposal https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47997/Supporting%20Enumeration%20Types%20in%20OData.docx was to 
>     support the alternate representation of an enumeration value as the
>     underlying integer value as a string.
> with an explicit example for JSON
>     "color":"32"



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