|
|
Posted on 2/26/2023 9:20:03 PM
|
|
|
|
Welcome to OData
OData (Open Data Protocol) is an ISO/IEC-approved OASIS standard that defines a set of best practices for building and using REST APIs. It enables the creation of REST-based services that allow resources identified and defined in the data model using Uniform Resource Locators (URLs), published and edited by web clients using simple HTTP messages.
OData helps applications focus on business logic without worrying about various API methods that define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, and more. It is a great way to track changes, define functions/actions for reusable processes, and send asynchronous/batch requests.
Development history
Who - Who Released OData?
The standard was initiated by Microsoft,The first three versions 1.0, 2.0, and 3.0 are all Microsoft open standards。
When - When did it become an industry standard?
The fourth version, 4.0, was voted on as an open industry standard at OASIS on March 17, 2014
agreement
The OData protocol is an application-level protocol used to interact with data through a RESTful interface. It supports the description of data models and edits and queries the data based on those models. OData-based REST APIs are easy to discover and use thanks to OData metadata, a machine-readable description of data models that are presented in a human-readable format and enable the creation of powerful general-purpose client agents and tools.
OData improves semantic interoperability between systems and follows the following design principles:
- Follow REST principles.
- Keep things simple. Handle common situations and provide scalability when necessary.
- Build step by step. A very basic, compliant service should be easy to build and require only extra work to support additional functionality.
- Scalability is important. The service should be able to support extended functionality without leaving the customer unaware of the extensions.
- Prefer mechanisms that work with various data sources. In particular, don't assume a relational data model.
The OData protocol differs from other REST-based web service approaches because it provides a unified way to describe data and data models. This improves semantic interoperability between systems and allows for an ecosystem to emerge. It follows the following design principles:
The following diagram shows how different libraries can be used for both server-side and client-side implementations.
OData documentation:The hyperlink login is visible.
ASP.NET Core and OData documentation:The hyperlink login is visible.
|
Previous:cloc counts blank, comment, and physical lines of source code in programming languagesNext:IIS 500 error failed request trace
|
Landlord|
Posted on 5/28/2023 7:50:55 PM
|
