[OASIS Issue Tracker] (ODATA-884) Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62257#comment-62257 ] 

Ralf Handl commented on ODATA-884:
----------------------------------

This term could also be leveraged by the transformation to OpenAPI: Path Objects could then explicitly list these error codes

> Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
> -----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-884
>                 URL: https://issues.oasis-open.org/browse/ODATA-884
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.01_WD01, V4.0_ERRATA02
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> Jeff Wight proposes to add a term that allows describing possible code values in OData error responses, see https://lists.oasis-open.org/archives/odata-comment/201510/msg00019.html,
> <Annotation Term=”Core.ErrorCodes”>
>   <Record>
>     <PropertyValue Property=”ErrorCode” String=”QueryFilterFunctionNotSupported”/>
>     <PropertyValue Property=”Description” String=”This error indicates that a request was made with a filter function that isn’t supported on this entity set.  Please refer to the Capabilities.FilterFunctions annotation on this entity set for a list of supported functions, and the exact error message for which function usage triggered this error.”/>
>   </Record>
> </Annotation>



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)