Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1624

Make conformance clauses more future-proof

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.02
    • Component/s: Protocol
    • Labels:
      None

      Description

      The current Conformance clauses 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?

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: