OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Michael Pizzo updated ODATA-270:

are there other restrictions we can introduce for V4 (with the knowledge that it's easier to relax restrictions than add them later?)

do we need (have use cases for):
    <Property Name="..." Type="Edm.PrimitiveType"/>?
    <Property Name="..." Type="Edm.ComplexType"/>?
    <Property Name="..." Type="Collection(Edm.ComplexType)"/>?

if not, we can simply limit the use of those types. 

We could still have:

<NavigationProperty Name="..." Type="Edm.EntityType"/>
<NavigationProperty Name="..." Type="Collection(Edm.EntityType)"/>

For the cases we wanted to support where a service was pointing to an entity type (or collection of entity types) but didn't know their types, and 

<Function Name="..." ReturnType="Edm.EntityType"/>
<Function Name="..." ReturnType="Collection(Edm.EntityType)"/>

allow functions to return entities or collections of entity(es) of any type (i.e., a search function).

> 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, OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]