| Workaround | Pros | Cons | Notes |
|---|
| Limiting the delta between Anchor and JSON payload to only one DataNode | The DeltaReport will be consistent with the existing API i.e., Delta between 2 anchors | - Limited to only 1 data node at a time
|
|
| Using alternative paths, like JSON path | The delta report will have xpaths replaced by JSON path | - CPS is dependent and built around xpath, hence this will be a major inconsistency
- If implemented, we will need to generate JSON paths for both, the data from anchor and the JSON payload,
- making the operation more expensive
|
|
| Not reporting the xpaths in the delta report between anchor and JSON payload | Can be implemented for multiple data nodes | - Delta report will be inconsistent and not as per the RFC standard
- It is inconsistent with respect to the existing API of delta report.
|
|