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] Commented: (ODATA-537) Ordering of navigationLink and associationLink annotations in JSON


    [ http://tools.oasis-open.org/issues/browse/ODATA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34844#action_34844 ] 

Hubert Heijkers commented on ODATA-537:
---------------------------------------

Ok, my gut feel tells me to propose to get rid of associationLink altogether in that case. Can you think of any reason where nowadays with v4 we'd need that extra annotation? To me its like one of the remains of what we used to have but I might be missing a case where one might not be following convention that I've never ran into myself yet.

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

        


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