[OASIS Issue Tracker] (ODATA-846) Add version 4.01

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

     [ https://issues.oasis-open.org/browse/ODATA-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-846:
--------------------------------

    Proposal: 
Part 1: Protocol
- Section 5.1 Protocol Versioning
- Chapter 12 Security Considerations

Part 3: CSDL
- Section 3.1.1 Attribute Version

JSON Format
- Chapter 21 Security Considerations

Negotiation:
-A client that specifies odata.maxversion=4.0 must receive 4.0 compliant responses.
-A client that specifies odata.maxversion=4.01, or no odata.maxversion, may get back 4.01-specific responses
-A client must only send payloads containing 4.01 structure to a service that advertises support for 4.01 or greater
-A client should use capabilities to determine if a 4.01 feature is supported but may attempt syntax (and receive either 501 not implemented or 400 bad request)

For new 4.01 features, we should define vocabularies to test the presence and expected behavior for 4.0 clients.


  was:
Part 1: Protocol
- Section 5.1 Protocol Versioning
- Chapter 12 Security Considerations

Part 3: CSDL
- Section 3.1.1 Attribute Version

JSON Format
- Chapter 21 Security Considerations



> Add version 4.01
> ----------------
>
>                 Key: ODATA-846
>                 URL: https://issues.oasis-open.org/browse/ODATA-846
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> This issue tracks all places that need to reflect the new version number in the  prose text.
> We will also use this issue to track how we do version negotiation between a 4.0 and a 4.01 client and service.



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