[OASIS Issue Tracker] (ODATA-838) Allow inclusion of "untyped JSON" into JSON requests and responses

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

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

Michael Pizzo commented on ODATA-838:
-------------------------------------

ODATA-881 addressed the requirement of having untyped structure.

The remaining issue is the ability for properties to contain names that are valid in (i.e.,) JSON, but not valid OData identifiers.

We could address that remaining requirement by allowing tagging of properties with an alias.

> Allow inclusion of "untyped JSON" into JSON requests and responses
> ------------------------------------------------------------------
>
>                 Key: ODATA-838
>                 URL: https://issues.oasis-open.org/browse/ODATA-838
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, Vocabularies
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Ralf Handl
>              Labels: Extension
>             Fix For: V4.01_WD01
>
>
> JSON allows more flexibility than OData, e.g. arrays that mix primitive values, objects, and other arrays, or property names that aren't SimpleIdentiifers.
> Some extension scenarios for OData services require adding JSON data to requests and responses that cannot be modeled with OData means.



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