[OASIS Issue Tracker] (ODATA-928) Allow client to use OData-SchemaVersion header to indicate the metadata version it is using

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62852#comment-62852 ] 

Michael Pizzo commented on ODATA-928:
-------------------------------------

Do we need a way to specify the metadata version in the context url, or must the client know the schema version when processing the payload?

> Allow client to use OData-SchemaVersion header to indicate the metadata version it is using
> -------------------------------------------------------------------------------------------
>
>                 Key: ODATA-928
>                 URL: https://issues.oasis-open.org/browse/ODATA-928
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData Protocol
>    Affects Versions: V4.01_WD01
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.01_WD01
>
>
> Once we define a standard annotation term to allow the metadata author to define a schema version, it would be extremely useful for clients to be able to indicate to the server which version of the metadata document the client is working with (since no matter when the client received the metadata, it may since have changed at the server).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)