What is the relationship between OData, Atom, Json, and WCF Data Services

I recently studied the WCF Data service. I know that the Data Service exposes a Data As Rest Resource that can be manipulated by URL. But there are a lot of technologies in this area. Hope someone can help me understand them. thanks

+8
wcf-data-services
source share
2 answers

OData is a protocol for exposing (as you said) data as a REST resource. Page to learn more, http://www.odata.org .

WCF Data Services is an implementation of Microsoft's OData protocol (both client and server) on the .NET platform. Therefore, the service created by the WCF data services uses the OData protocol.

ATOM is a standard format and is one of the possible wiring formats for data transfer in the OData protocol. The OData protocol defines extensions for it. For a better picture, ATOM is an XML-based format that defines XML elements and their meaning (channels, records, links), and OData uses this along with several of its own XML elements to serialize data.

JSON is a standard format (for serializing JavaScript objects) and is one of the possible wiring formats for transferring data in the OData protocol. Thus, the OData protocol uses JSON to serialize data.

+10
source share

WCF Data Services (formerly known as "ADO.NET Data Services") is a component of the .NET Framework that allows you to create services that use the open data protocol (OData) to expose and consume data over the Internet or intranet using the semantics of representing a representative state ( REST).

The open data protocol ( OData strong>) is an open protocol that allows you to create and use requested and compatible RESTful APIs in a simple and standard way.

more details http://en.wikipedia.org/wiki/Open_Data_Protocol

Atom is a way to submit messages just like RSS does.

JSON (JavaScript object designation) is a lightweight data exchange format. It’s easy for a person to read and write. Cars are easily disassembled and generated. It is based on a subset of the JavaScript programming language, ECMA-262 3rd Edition - December 1999.

0
source share

All Articles