[ODATA-1132] Propagation of NavigationRestrictions - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Proposal:

Hide

As per 2018-2-8 discussion: State that clients can assume that restrictions specified on an entity set are valid whether the request is to the entity set or through a navigation property bound to that entity set. Service could specify a different set of restrictions specific to a path, in which case any specified restrictions take precedence.

Show
As per 2018-2-8 discussion: State that clients can assume that restrictions specified on an entity set are valid whether the request is to the entity set or through a navigation property bound to that entity set. Service could specify a different set of restrictions specific to a path, in which case any specified restrictions take precedence.
Resolution:

Hide

https://github.com/oasis-tcs/odata-vocabularies/pull/11

Show
https://github.com/oasis-tcs/odata-vocabularies/pull/11

Clarify whether/how navigation restrictions "propagate".

Assume we have

Order entity related to single Customer entity
Customer entity related to multiple Address entities
a navigation restriction on Customers entity set which lists Addresses as filterable:false.

Now a client knows that it cannot filter Customers by Addresses.

Should a client assume that it also cannot filter Orders by Customer/Addresses?

Or would the service have to explicitly declare navigation restrictions for all entity sets with navigation paths ending in Customer/Addresses?