[ODATA-223] Specify Service behavior for not implemented functionality - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Details

Type: Sub-task
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: V4.0_WD01
Fix Version/s: V4.0_WD01
Component/s: ATOM Format, CSDL XML, Data Aggregation, Extension for JSON Data, JSON Format, Protocol, Temporal, URL Conventions
Labels:
None
Environment:

[Applied]

Proposal:

Hide

Services MUST return 501 not implemented and SHOULD include a description of the error in an OData error object.

Show
Services MUST return 501 not implemented and SHOULD include a description of the error in an OData error object.
Resolution:

Hide

https://www.oasis-open.org/committees/download.php/48963/odata-core-v4.0-wd01-part1-protocol-2013-4-26PR1.docx

Accepted: https://www.oasis-open.org/committees/download.php/49055/odata-meeting-35_on-20130502-minutes.html#odata-223

Show
https://www.oasis-open.org/committees/download.php/48963/odata-core-v4.0-wd01-part1-protocol-2013-4-26PR1.docx Accepted: https://www.oasis-open.org/committees/download.php/49055/odata-meeting-35_on-20130502-minutes.html#odata-223

Description

We need to specify, in each spec, the minimal conformance.
For functionality beyond minimal conformance, we need to specify how the service responds when certain support (i.e., certain query options) are not implemented (for example, return Not Implemented status code, with a well defined header or response body describing what is not implemented (perhaps referencing "codes" in the capabilities vocabulary, as appropriate?)).

Attachments

Activity

People

Assignee:

Michael Pizzo (Inactive)

Reporter:

Michael Pizzo (Inactive)

Watchers:

0 Start watching this issue

Dates

Created:

30/Jan/13 5:47 AM

Updated:

02/Feb/24 12:17 PM

Resolved:

02/May/13 1:15 PM