-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_ERRATA03
-
Fix Version/s: V4.01_CSD02
-
Component/s: Protocol
-
Labels:None
-
Environment:
Applied
-
Proposal:
-
Resolution:
Today we say that expanded properties in the defining query define the scope of the graph for which the client is interested in receiving changes.
It could be that the client is interested in knowing about added/deleted links, but doesn't care about the contents of the entities related through those links.
This could easily by supported by saying that navigation properties in the select list define the links that the client is interested in knowing about changes for. If the service represents deltas to related entities through an inline collection, that inline collection would contain (minimally) the entity references (or key properties of entities) representing the current membership.
I'm getting the impression this issue is related to deltas and that its scope is as such but, to me at least, that is not clear from the description/proposal.
If it is not, just in case, doesn't putting a navigation property in the $select list currently return the navigationLink? And what are we proposing we'd change that too exactly?