[OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=35044#action_35044 ] 

Michael Pizzo commented on ODATA-537:
-------------------------------------

I think we should retain association links.

One scenario where these would be useful would be where I have a navigation (I.e., from customers to orders in an external system that knows nothing about my customers). I can create non-conventional navigation links that directly access the related resource by filtering the related resource based on my primary key value, but appending /$ref to that URL would be meaningless to the external resource.

Supporting appending /$ref to the navigation link as the association link would require me to construct a URL to my own service for the navigation link that encoded the information I needed to redirect to the query on the external service. Simply using the conventional navigation link may require me to do additional lookups (for example, to determine what server this particular client's orders are on in a distributed system) which could be bypassed if I encoded the information into the navigation link in the first place.

I *may* have to do a redirect for the query case if I also support POSTing a new entity to the collection, but requiring this in the general case seems unfortunate.

> 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: [Applied]
>            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