[OASIS Issue Tracker] Updated: (ODATA-376) Navigation link representation for navigation properties of complex type instances

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

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

Ralf Handl updated ODATA-376:
-----------------------------

    Environment: [Applied]  (was: [Proposed])
       Assignee: Ralf Handl

> Navigation link representation for navigation properties of complex type instances
> ----------------------------------------------------------------------------------
>
>                 Key: ODATA-376
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-376
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> Currently the JSON spec requires that the navigation link for a navigation property is only represented if the client requests odata.metadata=full or if the client explicitly selects the navigation property in $select.
> It would be more accurate to state that it also gets represented if it cannot be "computed"
> While "computing" works for navigation properties of an entity type (http://host/service/Set(key)/NavProp), and even for navigation properties of single-valued complex properties ((http://host/service/Set(key)/ComplexProp/NavProp), it breaks down for navigation properties of complex-valued properties.

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