# Transport layer HTTP has become the unquestioned standard to exchange data unidirectionally. FTP is still relevant to exchange files containing data like ods or xlsx values but is not adapted to our needs. HTTP can be improved with the REST logic. This good practice makes the best use of the HTTP standard to harmonize APIs. In the semantic world, another standard complements the HTTP: Linked Data Platform. This standardizes the structure of the requested semantic content. It is based on 2 concepts: containers and resources. Containers contain resources. A resource can reference containers that contain data linked to it. A resource can itself be a container. Some contradictions exist between REST and LDP. The header link for example is used to indicate the links that a resource has with another resource in REST while it is used to indicate what is the nature of the resource (Resource, BasicContainer, DirectContainer ...) in LDP. JSON-LD is compatible with LDP provided that it complies with the Resource / Container logic. LDP does not impose a form of url and OpenApi remains relevant to describe the API. **Conclusion: use HTTP and LDP while following a REST logic as much as possible** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.dfc-standard.org/dfc-standard-documentation/appendixes/technical-decisions/transport-layer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.