clarify support for navigation properties on deleted entries

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CS01
    • Affects Version/s: V4.01_CSD03
    • Component/s: JSON Format, Protocol
    • None
    • Environment:

      Applied/Approved/Closed

    • Hide

      Clarify that navigation properties, as well as structural properties, are supported within a deleted entry, to show changes to entities related to the deleted entry.

      Just as for a regular entity in a delta response, a single-valued navigation property may reference a tombstone, in which case that related entity is also deleted, and the deleted entry may include a nested delta (represented using @delta annotation in JSON) that includes both changed and deleted related entities.

      Show
      Clarify that navigation properties, as well as structural properties, are supported within a deleted entry, to show changes to entities related to the deleted entry. Just as for a regular entity in a delta response, a single-valued navigation property may reference a tombstone, in which case that related entity is also deleted, and the deleted entry may include a nested delta (represented using @delta annotation in JSON) that includes both changed and deleted related entities.
    • Show
      https://www.oasis-open.org/committees/download.php/62018/odata-v4.01-wd04-part1-protocol-2017-11-13-redlined.docx https://www.oasis-open.org/committees/download.php/62016/odata-json-format-v4.01-wd04-2017-11-10-redlined.docx

      In 4.01 we added support for properties within a deleted entry. This allows us to omit the @odata.id, if key fields are included, and may provide other information about the deleted entry.

      We are not clear, however, whether "properties" includes navigation properties and what the semantics of navigation properties on a deleted entry should be.

      If you think of a delta payload as a graph of changes, the fact that a node within that graph has been deleted doesn't mean that you aren't interested in changes to other nodes within the graph; it's still interesting to report changes to nodes that may no longer be accessible (at least from the root) after applying changes.

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: