ISO IEC 20802-2-2016 PDF

Full title and description

Information technology — Open data protocol (OData) v4.0 — Part 2: OData JSON Format. This International Standard specifies the JSON representations used for OData v4.0 requests and responses, extending the core OData protocol to define how entities, collections, primitive values, errors and service documents are encoded in JSON for interoperable REST-based data services.

Abstract

ISO/IEC 20802-2:2016 defines the OData JSON Format as an extension to ISO/IEC 20802-1 (the OData core). It specifies the allowable JSON payload structures for OData operations (single values, complex types, entities, collections, changes/deltas, service documents and errors), the expected media types and conventions for mapping the Entity Data Model (EDM) to JSON.

General information

• Status: Published (International Standard; confirmed after periodic review).
• Publication date: 15 December 2016 (published December 2016).
• Publisher: ISO/IEC (developed under ISO/IEC JTC 1 — Information technology).
• ICS / categories: 35.100.70 (Application layer / information technology).
• Edition / version: Edition 1 (2016).
• Number of pages: 43 pages.

Scope

This standard extends the OData core specification (Part 1) by prescribing a JSON encoding for OData v4.0 messages. It covers the JSON structures for representing single primitive/complex values, single entities and entity collections, reference and delta payloads, service documents and error responses, and defines the media type usage and HTTP header expectations necessary for interoperable client-server exchanges. The specification is intended to ensure consistent serialization and parsing of OData payloads across implementations.

Key topics and requirements

• JSON payload structures for OData v4.0: single primitives, complex types, entities, collections and deltas.
• Service document and metadata-related JSON representations and error payload format.
• Conventions for mapping the Entity Data Model (EDM) to JSON (naming, type information, nulls and arrays).
• Media type and HTTP header guidance for requests and responses (Content-Type, Accept, use of JSON light conventions where applicable).
• Conformance requirements for servers and clients to ensure interoperable parsing, serialization and error handling.

Typical use and users

API designers, web service implementers, middleware developers, open-data providers and government/enterprise IT teams use this standard when implementing or consuming OData v4.0 services to ensure consistent JSON serialization and interoperability across platforms and vendors. It is also used by tool and library authors that provide OData client/server stacks.

Related standards

ISO/IEC 20802-1:2016 — Information technology — Open data protocol (OData) v4.0 — Part 1: Core (defines core semantics and the EDM). The OData family is derived from the OASIS OData v4.0 specifications; implementers should consider both the ISO/IEC parts and the originating OASIS documents for full context. Also related: relevant JSON RFCs referenced by the standard for JSON syntax and media-type handling.

Keywords

OData, Open Data Protocol, JSON, OData JSON Format, OData v4.0, Entity Data Model, EDM, REST API, serialization, interoperability.

FAQ

Q: What is this standard?

A: ISO/IEC 20802-2:2016 is the International Standard that specifies the JSON format for the Open Data Protocol (OData) v4.0, providing rules for serializing requests and responses in JSON.

Q: What does it cover?

A: It covers JSON representations for single primitive and complex values, entities and collections, changes/deltas, service documents and errors, plus conventions for mapping the Entity Data Model (EDM) to JSON and the related HTTP/media-type usage.

Q: Who typically uses it?

A: Developers and architects building or consuming OData v4.0 APIs (clients, servers, middleware), library/tool vendors, and organizations publishing open data or interoperable REST-based data services.

Q: Is it current or superseded?

A: It is published and remains current; the ISO entry shows the standard as published in December 2016 and confirmed during the periodic review cycle (status: International Standard — confirmed). Implementers should check for any later amendments or revisions from ISO/IEC or OASIS if they require the very latest updates.

Q: Is it part of a series?

A: Yes — it is Part 2 of ISO/IEC 20802. Part 1 (ISO/IEC 20802-1:2016) defines the core OData semantics and EDM; Part 2 defines the JSON format extension for those semantics.

Q: What are the key keywords?

A: OData, JSON, serialization, EDM, REST, Open Data Protocol, v4.0, service document, delta, error response.