[OASIS Issue Tracker] Updated: (ODATA-450) ordering of association link , navigation link, expanded nav prop

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

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

Michael Pizzo updated ODATA-450:
--------------------------------

    Proposal: 
Association link, if written, should immediately precede navigation link,if written, should immediately precede expanded nav prop. 
The navigation link is present whenever the nav prop is expanded.
The association link does not need to be written in atom or json if it follows convention (associationlink/$ref)

  was:Association link, if written, should immediately precede navigation link,if written, should immediately precede expanded nav prop. 


> ordering of association link , navigation link, expanded nav prop
> -----------------------------------------------------------------
>
>                 Key: ODATA-450
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-450
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData JSON Format
>    Affects Versions: V4.0_CSD01
>         Environment: [proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> atom and json each have slightly different constraints about ordering of association link, navigation link, and expanded navigation. we should define consistent rules for ordering of association link, navigation link, and expanded navigation between atom and json.

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