-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_WD01
-
Fix Version/s: V4.0_WD01
-
Component/s: ATOM Format, JSON Format, Protocol
-
Labels:None
-
Environment:
[Proposed]
-
Proposal:
-
Resolution:
The ATOM format already says, in section 15, that additional payload may be returned anywhere supported by Section 6 of [RFC4287], but that extensions must not be in the OData namespaces and should not be required to be understood by the client in order for the payload to be correctly interpreted.
In ATOM we should be clear that this means that the service may return additional children of the <feed> or <entry> elements, and that it is safe for the client to ignore anything (in any namespace, including the odata namespace) not defined in the version of the payload being returned. This allows for forward compatibility of incremental information without rev'ing the payload version.
In JSON we should be clear that clients should ignore annotations (in any namespace, including the odata namespace), as well as objects with an odata.kind, that are not defined in the version of the payload being returned.