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

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

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

Michael Pizzo updated ODATA-537:
--------------------------------

    Environment: [Proposed]  (was: [Discussion needed])
       Proposal: 
Option 1: Get rid of the Association Link altogether.
Option 2: Retain association link, but state that the only case that the service must return it is if it differs from the convention of appending /$ref to the navigation link.

  was:Get rid of the Association Link altogether.


Our discussion over the past few days on how clients might represent non-canonical navigation links leads me to believe that there are valid cases where the association link is not just the nav link plus /$ref. However, I do agree that this will be rare, and I would hate to include association links (even in full metadata) for the common case where they follow convention.

So I would propose (which I think Hubert was alluding to in our 10/1 TC call) that the association link be retained but it only MUST be written if it differs from the nav link (plus /$ref), even in the full metadata case.

> 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
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: V4.0_CSD03
>
>
> 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