Make conformance clauses more future-proof

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

      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?

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: