Major The current metadataurl pattern for specifying a subset of properties is broken for selects on expanded navigation props.
We need to know the projected properties in order to know, for example, whether missing navigation properties are omitted because they matched a convention (in which case they can be constructed on the client) or because they weren't selected (in which case they should not be constructed on the client because they may not match convention)..
Also, we don't want to have to have the client parse select (and nested expands, etc.)
