Statement of Use for OData 4.0, OData JSON Format 4.0, and OData ATOM Format 4.0 by Microsoft

["Ram Jeyaraman (MS OPEN TECH)" <Ram.Jeyaraman@microsoft.com>]

Microsoft has successfully implemented the Committee Specification 02 (dated November 17, 2013) version of the OASIS OData Protocol Version 4.0 specification in a pre-release of our core OData libraries for the .NET framework, and has demonstrated use of those libraries through an experimental service.

 

The libraries enable developers to write OData Read-only or Updatable Data Services in accordance with the required clauses for Intermediate Conformance as specified in Section 13.1 of Part 1: Protocol and Section 6 of Part 2: URL Conventions, and in accordance with the conformance clauses for services specified in Section 18 of Part 3: CSDL, with the following exceptions:

-Some unsupported requests may return 400 Bad Request instead of 501 Not Supported as required by Section 13.1.2, Clause 2, of Part1:Protocol

-The libraries do not currently support the use of a variable alias in the $filter clause as required in Section 13.1.2, Clause 7.2 of Part 1: Protocol

 

These libraries support the Committee Specification 02 (dated November 17, 2013) version of both the OData JSON Format version 4.0 specification and the OData Atom Format version 4.0 specification in accordance with the conformance clauses for services specified in Section 22 of each of those specifications.

 

In addition, these libraries support writing .NET clients for consuming such services. Over the coming months Microsoft will complete the remaining work to make these client libraries compliant with the Interoperable Client Conformance Level defined in Section 13.2 of Part 1: Protocol, supporting both the OData JSON and OData Atom specifications, and including interoperability testing with other independent implementations at that time.

 

I, Ram Jeyaraman, OASIS Primary Representative for Microsoft, endorse the above Statement of Use.