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

Check the use of SHOULD vs. MUST in Protocol spec

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      Protocol spec (2013-03-12) states:

      10.4.2.2 Create Related Entities When Creating an Entity
      A service that supports creating entities SHOULD support creating related entities as part of the same request.

      We might wonder here (and in other sections in the spec, since I just gave this as one example) if instead of "SHOULD", we should see "MUST", in accordance with RFC 2119.

      Use of "SHOULD" implies that there are certain scenarios where the server does not need to support creating related entities when creating an entity. If that is the case, then the spec ought to define a way for the server to advertise whether or not it provides this service, so that the client can formulate valid requests that are possible for the server to execute.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              evan.ireland.2 Evan Ireland
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: