-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_CS01
-
Fix Version/s: V4.0_CSD03
-
Component/s: Vocabularies
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
-
Resolution:
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.