[OASIS Issue Tracker] Created: (ODATA-537) Ordering of navigationLink and associationLink annotations in JSON

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

Ordering of navigationLink and associationLink annotations in JSON
------------------------------------------------------------------

                 Key: ODATA-537
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-537
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData JSON Format
    Affects Versions: V4.0_CS01
            Reporter: Hubert Heijkers
            Priority: Minor
             Fix For: V4.0_CSD03


8.2 - Association Link specifies that if both navigationLink and associationLink are represented, for example in the odata.metadata=full case, that the associationLink MUST immediately precede the navigationLink.

Example 10 however shows two cases were both links are represented however they are in the opposite order of what is specified in 8.2.

Unless there is a specific reason why associationLink MUST precede the navigationLink, presuming an order needs to be enforced in the first place, I'd propose to have navigationLink precede the associationLink, as associationLink builds on, if following convention, the navigationLink.

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