---
schema-version: v1.2.8
id: OASISOData-JSON-Format-v4.0-plus-Errata01
title:
- content: OData JSON Format Version 4.0 Plus Errata 01
  language:
  - en
  script:
  - Latn
  format: text/plain
  type: main
link:
- content: http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata01/os/odata-json-format-v4.0-errata01-os-complete.html
  type: src
type: standard
docid:
- id: OASIS OData-JSON-Format-v4.0-plus-Errata01
  type: OASIS
  primary: true
docnumber: OData-JSON-Format-v4.0-plus-Errata01
date:
- type: issued
  value: '2014-09-04'
contributor:
- organization:
    name:
    - content: OASIS
    contact:
    - uri: https://www.oasis-open.org/
  role:
  - description:
    - content: Standards Development Organization
    type: authorizer
  - type: publisher
- organization:
    name:
    - content: OASIS Open Data Protocol (OData) TC
    contact:
    - uri: https://www.oasis-open.org/committees/odata/
  role:
  - description:
    - content: Committee
    type: authorizer
- person:
    name:
      given:
        forename:
        - content: Ralf
          language:
          - en
          script:
          - Latn
      surname:
        content: Handl
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: SAP AG
        contact:
        - uri: http://www.sap.com/
    contact:
    - email: ralf.handl@sap.com
  role:
  - description:
    - content: Chair
    type: editor
- person:
    name:
      given:
        forename:
        - content: Ram
          language:
          - en
          script:
          - Latn
      surname:
        content: Jeyaraman
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Microsoft
        contact:
        - uri: http://www.microsoft.com/
    contact:
    - email: Ram.Jeyaraman@microsoft.com
  role:
  - description:
    - content: Chair
    type: editor
- person:
    name:
      given:
        forename:
        - content: Ralf
          language:
          - en
          script:
          - Latn
      surname:
        content: Handl
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: SAP AG
        contact:
        - uri: http://www.sap.com/
    contact:
    - email: ralf.handl@sap.com
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Michael
          language:
          - en
          script:
          - Latn
      surname:
        content: Pizzo
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Microsoft
        contact:
        - uri: http://www.microsoft.com/
    contact:
    - email: mikep@microsoft.com
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Martin
          language:
          - en
          script:
          - Latn
      surname:
        content: Zurmuehl
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: SAP AG
        contact:
        - uri: http://www.sap.com/
    contact:
    - email: martin.zurmuehl@sap.com
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Mark
          language:
          - en
          script:
          - Latn
      surname:
        content: Biamonte
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Progress Software
        contact:
        - uri: http://www.progress.com/
    contact:
    - email: mark.biamonte@progress.com
  role:
  - type: editor
language:
- en
script:
- Latn
abstract:
- content: 'The Open Data Protocol (OData) for representing and interacting with structured
    content is comprised of a set of specifications. The core specification for the
    protocol is in OData Version 4.0 Part 1: Protocol; this document extends the former
    by defining representations for OData requests and responses using a JSON format.'
  language:
  - en
  script:
  - Latn
  format: text/plain
relation:
- type: partOf
  bibitem:
    formattedref:
      content: OASIS OData-JSON-Format-v4.0
      format: text/plain
doctype:
  type: standard
editorialgroup:
- name: "OASIS Open Data Protocol\r\n(OData) TC"
ext:
  schema-version: v1.0.1
technology_area:
- Messaging