Overview
ISO/IEC 20802-1:2016 - Information technology - Open Data Protocol (OData) v4.0 - Part 1: Core defines the core semantics and facilities of OData v4.0, the Open Data Protocol for creating REST-based data services. The standard specifies how resources (identified by URLs and defined in an Entity Data Model, EDM) are published and edited by web clients using simple HTTP messages. This ISO adoption is based on the OASIS OData v4.0 Part 1 (Protocol) specification, including errata and related artifacts.
Key Topics and Technical Requirements
- Core semantics and data model
- Entity Data Model (EDM) constructs and annotations that describe entities, types and relationships.
- Service model
- Identification and addressing of resources: Entity-Ids, entity references, read URLs and edit URLs, and handling of transient entities.
- Versioning
- Rules for protocol versioning and model versioning to ensure interoperability across client and server implementations.
- Extensibility
- Mechanisms for extending query options, payloads, actions/functions, vocabularies, header fields, and formats to support custom scenarios without breaking core behavior.
- Formats and payloads
- Normative support and pointers to OData JSON and Atom formats, ABNF grammar components, XML schemas for EDMX/EDM, and metadata artifacts.
- Header fields and HTTP semantics
- Defined common and request/response headers such as Content-Type, Accept, Content-Encoding, Content-Language, Content-Length, OData-Version, If-Match, and If-None-Match among others.
- Related artifacts
- Associated resources: Part 2 (URL Conventions), Part 3 (CSDL), vocabularies, schemas, and ABNF test cases.
Practical Applications - Who Uses This Standard
- API architects and backend developers building RESTful data services that must expose structured data consistently.
- Integration engineers and system integrators creating interoperable connectors between enterprise systems, analytics platforms, and cloud services.
- Tool vendors and middleware providers implementing OData servers/clients, metadata tooling, and SDKs.
- Data platform teams publishing cataloged resources and metadata for consumption by web clients, BI tools, and low-code platforms.
Practical benefits include standardized resource addressing, consistent metadata descriptions via EDM/CSDL, reliable versioning strategies, and extensibility paths for custom requirements - all improving compatibility and reducing integration costs.
Related Standards and Resources
- OData v4.0 Part 2: URL Conventions (ISO/IEC 20802-2)
- OData v4.0 Part 3: Common Schema Definition Language (CSDL)
- OData JSON and Atom format specifications, ABNF components, and EDMX/EDM XML schemas
Keywords: ISO/IEC 20802-1, OData v4.0, Open Data Protocol, REST-based data services, Entity Data Model, EDM, OData Core, OData headers, API versioning, extensibility.