[OASIS Issue Tracker] (ODATA-1624) Make conformance clauses more future-proof

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

Ralf Handl created ODATA-1624:
---------------------------------

             Summary: Make conformance clauses more future-proof
                 Key: ODATA-1624
                 URL: https://issues.oasis-open.org/browse/ODATA-1624
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Protocol
    Affects Versions: V4.01_OS
            Reporter: Ralf Handl
             Fix For: V4.02


The current [Conformance clauses|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Conformance]Ârequire services to fail with {{501 Not Implemented}} for unsupported functionality.

This is problematic when adding new functionality in later specification versions that is unknown to services conforming with earlier specification versions: do they become non-conforming by responding with {{400 Bad Request}} to the new functionality?



--
This message was sent by Atlassian Jira
(v8.3.3#803004)