Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Latest commit

 

History

History
64 lines (36 loc) · 1.43 KB

OData JSON Format.markdown

File metadata and controls

64 lines (36 loc) · 1.43 KB
Raw

OData JSON With Meatadata Format

Overview

  • Description of document; refer to core doc.
  • Design goals
  • Efficient format vs historical (needs better name) format

2. Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2.1 ???

  • Normative reference to the OData core document
  • Any other notational conventions?

Common Payload Format

  • This section includes all the stuff that is common between request and response payloads. Mostly, this means the representations of EDM values.

Entities

Properties

Navigation Properties

Metadata

Primitive Values

  • All of the types, by category (numeric, string, spatial, temporal, special)
  • Specific statement of representation in payload.

Complex Types

Properties

Metadata

Request Specifics

  • All the stuff that only applies to request payloads.

HTTP Headers

  • proper accept header to request this format.
  • other stuff?

Response Specifics

  • All the stuff that only applies to response payloads.

HTTP Headers

  • proper content type for this format.
  • other stuff?

Next Links

Response-Level Properties

  • Inline count
  • Others?