Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-916

Define what services (and clients?) do with unknown format parameters

    XMLWordPrintable

    Details

    • Proposal:
      Hide

      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.

      Show
      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.
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/57689/odata-v4.0-wd08-part1-protocol-2016-03-03.docx https://www.oasis-open.org/committees/download.php/57684/odata-json-format-v4.0-wd08-2016-03-03.docx

      Description

      Need to define how clients/services deal with unknown (as opposed to not supported) type parameters in Accept and Content-Type headers.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo (Inactive)
              Reporter:
              mikep Michael Pizzo (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: