OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (ODATA-290) Check the use of SHOULD vs. MUST in Protocol spec

Check the use of SHOULD vs. MUST in Protocol spec

                 Key: ODATA-290
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-290
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData Protocol 
    Affects Versions: V4.0_WD01
            Reporter: Evan Ireland

Protocol spec (2013-03-12) states: 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]