Logged as a placeholder, pending agreement on difference between select & properties (and related).
In summary, as of now, for entities and collections of entities (at least):
- "properties" provides structural filtering of the response to reduce the amount of data returned over the wire (if desired by clients, eg. mobile).
- "select" provides the ability to add ('expand') more information beyond the basic response. This information usually requires additional lookup.
It has been noted, that rather than having to repeat everything in the "select" in the "properties", it should be included automatically. In other words, "select" takes precedence over "properties.
Here's a contrived example. Instead of specifying:
It should be possible to improve the REST fwk such that we can simply specify:
Caveat: The "properties" clause currently only applies to the top-level members. Hence, if "select"ing a single property and using "properties, it is necessary to fully qualify the "select". This should be logged as a separate/related enhancement request.
In other words. This will not return the property (unless "properties" clause is omitted):
This will work as expected: