SData on GitHub

Welcome to SData!

This site provides technical information on the version 2.0, 1.1 and synchronization of the standard.

SData is a web toolkit, promoting the development of REST-orientated services and their consumption. It consists of a small, standards-based core (HTTP, ATOM, JSON) and a set of optional mechanisms solving common implementation challenges in a consistent manner.

Version 2.0 of the standard is current. It expands upon the 1.1 version providing additions aimed towards the needs of web product- and interface definitions. The focal points of the new release are:

  • Specification of the JSON format for SData information exchanges
  • Relaxation of several SData restrictions, resulting in a smaller, better-defined specification core
  • Compatibility with the SData 1.1 version, ensuring that SData 1.1 implementations are automatically version 2.0 compliant
  • Clarification of the role and form of contracts
  • Reorganization of the standard, stressing the freedom of choice for development teams and architects

Included in the site are older but still valid specifications:

  • Vesion 1.1 of the standard is the basis on which the current version (2.0) is built. The focus is on ATOM+xml and REST as applicable primarily for integrating applications. The specification contained herein maintains its validity in the context of the 2.0 release.
  • SData Sync describes the synchronization protocol underlying compliant applications.

Conventions used on the site

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 RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels” [5].

  • Compliance aspects are displayed in a black box as shown below
Compliance requirements
  • Aspects of particular importance are highlighted in an orange box
Important text
  • Notes to the reader are displayed as shown below
note contents


1SData Welcome to SData1.12011Sage Group plc
2RFC 4627 The application/json Media Type for JavaScript Object Notation (JSON)InformationalJuly 2006Internet Engineering Task Force
3RFC 6749 The OAuth 2.0 Authorization FrameworkProposed StandardOctober 2012Internet Engineering Task Force
4RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token UsageProposed StandardOctober 2012Internet Engineering Task Force
5RFC 2119 Key words for use in RFCs to Indicate Requirement LevelsBest Current PracticeInternet Engineering Task Force
6RFC 5322 Internet Message FormatDraft StandardOctober 2008Internet Engineering Task Force
7ISO 4217 Codes for the representation of currencies and funds-2008International Organization for Standardization
8RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1StandardJune 1999Internet Engineering Task Force
9ISO 3166-1 Codes for the representation of names of countries and their subdivisions - Part 1: Country codes-2006International Organization for Standardization
10ISO 8601 Data elements and interchange formats - Information interchange - Representation of dates and timesThird Edition03-Dec-2004International Organization for Standardization

Related work

You may also find these SData-related GitHub repositories of interest: