-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.01_WD01
-
Fix Version/s: V4.01_WD01
-
Component/s: Protocol
-
Labels:None
-
Environment:
[Proposed]
-
Proposal:
-
Resolution:
In ODATA-928 we added the ability for a service to make breaking changes to metadata, and for a client to request a specific version of the metadata using the new SchemaVersion header.
Do we need a way to encode the schemaversion as part of the contextUrl, or must the client processing the response know the schemaversion to use when requesting the metadata (including for nested contextUrls)?
Perhaps using the SchemaVersion annotation as an instance annotation on the result payload?