Select restrictions

[JefWight]

Similar to how the Capabilities vocabulary allows annotating entity sets with information about when an entity set supports $filter, $orderby, and $expand, it should be possible to express the ability to use $select, and which properties may be explicitly not selectable.

An example of why this is needed:
Some services may have the same entity exposed in different entity sets, with different sets of properties available from the different entity sets. This may happen more often with non-contained entities. For example, a service with both Products and Orders entity sets, where Product can have a collection of Orders it is part of, and Order can have a collection of Products it includes, it may be possible to select all Product properties from /Products, but a limited selection of propertiess from /Orders(id)/Products.

[msftclas]

Hi @JefWight, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Jeff Wight). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

[JefWight]

Fixes #16

[ralfhandl]

Hi Jeff,

This is an interesting proposal. Please note that the Core and Capabilities vocabularies are part of the OData 4.0 specification, so please propose this change via the odata-comment mailing list: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata.

Thanks in advance!
--Ralf