[OASIS Issue Tracker] Updated: (ODATA-530) Navigable capability term should apply to entityset, not navigationproperty directly

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

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

Ralf Handl updated ODATA-530:
-----------------------------

    Environment: [Applied]  (was: [Proposed])

> Navigable capability term should apply to entityset, not navigationproperty directly
> ------------------------------------------------------------------------------------
>
>                 Key: ODATA-530
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-530
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.0_CS01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> We decided to define all capabilities on either the entity set or the entity container, rather than type, so that we could share a type definitions across sets, and even services, and define the relative restrictions based on the actual exposed set.
> Somehow we missed the navigable term in doing this, the current definition of which is:
>       <Term Name="Navigable" Type="Core.Tag" DefaultValue="true" AppliesTo="NavigationProperty">
>         <Annotation Term="Core.Description" String="Supports navigation paths according to OData URL conventions" />
>       </Term>
> Also, note that many service support one level of navigation but not recursive navigation. We should capture that as well.

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