[OASIS Issue Tracker] (ODATA-1639) Distinguish expandability for a collection vs expandability for an item within a collection

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

Ralf Handl created ODATA-1639:
---------------------------------

             Summary: Distinguish expandability for a collection vs expandability for an item within a collection
                 Key: ODATA-1639
                 URL: https://issues.oasis-open.org/browse/ODATA-1639
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Vocabularies
            Reporter: Ralf Handl


Gareth Jones opened [https://github.com/oasis-tcs/odata/issues/12:]

It's very useful to be able to distinguish capabilities of a single entity in a collection vs the capabilities of a collection.

This is embodied in ReadRestrictions vs ReadByKeyRestrictions for support for GET foos vs GET foos/\{fooId}

In practice we've found that implementing $expand on a single entity is frequently cost-effective, whereas implementing it across a whole collection is not. Consequently we'd like to be able to qualify ExpandRestrictions with something akin to an ExpandByKeyRestrictions.

A cheap and cheerful variant of this would be a boolean control flag in ExpandRestrictions, but it misses the possibility that the expandable set of nav properties varies between single/collection.

For clarity, we need a vocabulary annotation that allows us to express
 # NOT Supported: {{GET /foos?$expand=bars}}
 # Supported: {{GET /foos/\{fooId}?$expand=bars}}



--
This message was sent by Atlassian Jira
(v8.3.3#803004)