[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1132) Propagation of NavigationRestrictions
[ https://issues.oasis-open.org/browse/ODATA-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-1132: --------------------------------- Environment: Proposed Proposal: 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. > Propagation of NavigationRestrictions > ------------------------------------- > > Key: ODATA-1132 > URL: https://issues.oasis-open.org/browse/ODATA-1132 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: Vocabularies > Affects Versions: V4.0_CSD01 > Environment: Proposed > Reporter: Ralf Handl > Fix For: V4.01_CS02, V4.0_ERRATA04 > > > 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? -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]