An Elegy for Immersive

There is an old Sanskrit word, Lila (Leela), which means play. Richer than our word, it means divine play, the play of creation and destruction and re-creation, the folding and unfolding of the…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Formats Supported By the API Platform

The API system has built-in content negotiation capabilities. By default, only the JSON-LD format is enabled. However, API Platform Core supports many more formats and can be extended.

Available formats are: JSON-LD, GraphQL, JSON, JSON:API, HAL, XML, YAML, CSV, HTML (API docs).

Data is messy and disconnected. JSON-LD organizes and connects it, creating a better Web.

JSON-LD is a lightweight Linked Data format. It is easy for humans to read and write. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. JSON-LD is an ideal data format for programming environments, REST Web services, and unstructured databases such as Apache CouchDB and MongoDB.

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.

JSON is built on two structures:

These are universal data structures. Virtually all modern programming languages support them in one form or another. It makes sense that a data format that is interchangeable with programming languages also be based on these structures.

JSON API is a format that works with HTTP. It delineates how clients should request or edit data from a server, and how the server should respond to said requests. A main goal of the specification is to optimize HTTP requests; both in terms of the number of requests and the size of data packages exchanged between clients and servers. JSON API module exposes an implementation for data stores and data structures, such as entity types, bundles, and fields.

HAL is a simple format that gives a consistent and easy way to hyperlink between resources in your API.

Adopting HAL will make your API explorable, and its documentation easily discoverable from within the API itself. In short, it will make your API easier to work with and therefore more attractive to client developers.

APIs that adopt HAL can be easily served and consumed using open source libraries available for most major programming languages. It’s also simple enough that you can just deal with it as you would any other JSON.

HAL provides a set of conventions for expressing hyperlinks in either JSON or XML.

Instead of using ad-hoc structures, or spending valuable time designing your own format; you can adopt HAL’s conventions and focus on building and documenting the data and transitions that make up your API.

HAL is a little bit like HTML for machines, in that it is generic and designed to drive many different types of application via hyperlinks. The difference is that HTML has features for helping ‘human actors’ move through a web application to achieve their goals, whereas HAL is intended for helping ‘automated actors’ move through a web API to achieve their goals.

Having said that, HAL is actually very human-friendly too. Its conventions make the documentation for an API discoverable from the API messages themselves. This makes it possible for developers to jump straight into a HAL-based API and explore its capabilities, without the cognitive overhead of having to map some out-of-band documentation onto their journey.

Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879). Originally designed to meet the challenges of large-scale electronic publishing, XML is also playing an increasingly important role in the exchange of a wide variety of data on the Web and elsewhere.

YAML is a human friendly data serialization standard for all programming languages. It is commonly used for configuration files and in applications where data is being stored or transmitted.

The comma separated values format (CSV) has been used for exchanging
and converting data between various spreadsheet programs for quite
some time. Surprisingly, while this format is very common, it has
never been formally documented. Additionally, while the IANA MIME
registration tree includes a registration for "text/tab-separated-values" type, no MIME types have ever been registered with IANA for CSV. At the same time, various programs and operating systems have begun to use different MIME types for this format.

HTML stands for Hyper Text Markup Language

My YouTube Channel;

Learn How Computer Works and What is Binary in 2 minutes

JWT Authentication and Refresh Token to API Platform

Symfony Search Engine with Elasticsearch

Testing Benford’s Law in Symfony 5, Php Framework

Add a comment

Related posts:

Press Photos as a store of value

The market for memorabilia is valued to be around $5.4 Billion, then I am talking about sports memorabilia only in America. We then have stamps,arts , and other memorabilia. In this Forbes article…

What if Things Turn Out Great?

As a Certified Life & Relationship Coach, I’m in the Positive Psychology business. However, that doesn’t mean I’m always positive. To the contrary, I’m wired for anxiety, hypervigilance, and negative…

ica10 companies revolutionising blockchain technology in Africa

Accenture estimates that the banking sector could make an estimated USD 12 BILLION yearly by utilising blockchain technology. As keen interest emerges in the potential for blockchain, major vendors…