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] Updated: (ODATA-223) Specify Service behavior for not implemented functionality


     [ http://tools.oasis-open.org/issues/browse/ODATA-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-223:
-----------------------------

          Component/s: OData ATOM Format v1.0
                       OData Batch Processing Format v1.0
                       OData CSDL v1.0
                       OData Extension for Data Aggregation v1.0
                       OData Extension for JSON Data v1.0
                       OData Extension for Temporal Data v1.0
                       OData Extension for XML Data v1.0
                       OData JSON Format v1.0
                       OData Protocol v1.0
                       OData URL Conventions v1.0
        Fix Version/s: WD01
    Affects Version/s: WD01

> Specify Service behavior for not implemented functionality
> ----------------------------------------------------------
>
>                 Key: ODATA-223
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-223
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Task
>          Components: OData ATOM Format v1.0, OData Batch Processing Format v1.0, OData CSDL v1.0, OData Extension for Data Aggregation v1.0, OData Extension for JSON Data v1.0, OData Extension for Temporal Data v1.0, OData Extension for XML Data v1.0, OData JSON Format v1.0, OData Protocol v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: WD01
>
>
> 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?)).

-- 
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]