[OASIS Issue Tracker] (ODATA-916) Define what services (and clients?) do with unknown format parameters

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

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

Michael Pizzo updated ODATA-916:
--------------------------------

    Description: 
if accept header contains an unknown (as opposed to not supported) type parameter, the service should not choose that option.

Services should not add format parameters not specified in request header.

For each format parameter, we can specify whether it is allowable for the service to return something according to the format parameter without the format parameter being specified.

Clients/services should not expect that they can ignore unknown format parameters when matching types in content-type.

> Define what services (and clients?) do with unknown format parameters
> ---------------------------------------------------------------------
>
>                 Key: ODATA-916
>                 URL: https://issues.oasis-open.org/browse/ODATA-916
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Task
>          Components: OData JSON CSDL, OData JSON Format, OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Michael Pizzo
>             Fix For: V4.0_ERRATA03
>
>
> if accept header contains an unknown (as opposed to not supported) type parameter, the service should not choose that option.
> Services should not add format parameters not specified in request header.
> For each format parameter, we can specify whether it is allowable for the service to return something according to the format parameter without the format parameter being specified.
> Clients/services should not expect that they can ignore unknown format parameters when matching types in content-type.



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