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] (ODATA-995) Resolve inconsistencies in JSON streaming property ordering


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

Michael Pizzo updated ODATA-995:
--------------------------------

    Proposal: 
Update 18.2 to state that annotations must come before the property
Update 4.4 to say that 4.0 services MUST return nav annotations after structural properties, 4.01 clients MUST NOT assume this ordering. 


  was:
Update 18.2 to state that annotations must come before the property
After making sure existing streaming clients don't rely on this ordering, update 4.4 to remove constraint that navigation annotations must come after structural properties.



> Resolve inconsistencies in JSON streaming property ordering
> -----------------------------------------------------------
>
>                 Key: ODATA-995
>                 URL: https://issues.oasis-open.org/browse/ODATA-995
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> Section 18.2 states that annotations must be "adjacent to" the properties they annotate.
> Section 4.4 states that annotations must come before the property they annotate.
> Section 4.4 also states that navigation annotations must come after structural properties, which seemed unnecessary



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


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