[OASIS Issue Tracker] Updated: (ODATA-270) Collections of Edm.PrimitiveType are problematic in JSON

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Drees updated ODATA-270:
-------------------------------

    Resolution: 
https://www.oasis-open.org/committees/download.php/48587/odata-core-v4.0-wd01-part3-csdl-2013-03-19.doc

Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-270

  was:https://www.oasis-open.org/committees/download.php/48587/odata-core-v4.0-wd01-part3-csdl-2013-03-19.doc


> Collections of Edm.PrimitiveType are problematic in JSON
> --------------------------------------------------------
>
>                 Key: ODATA-270
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-270
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
>
>
> In adding Edm.Primitive as a type specifying "any primitive type" we introduced a problem for JSON. We have no way to annotate individual elements of a JSON array, so we have no way of specifying the types of a heterogeneous collection of primitive types. In some cases these might be heuristically determined, but not all. We might consider disallowing collections of Edm.Primitive as being underspecified. In the future it would be non-breaking to add these as long as we solved the primitive types in a json array problem.

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