| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:r:rest [2026/07/18 12:33] – external edit 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:r:rest [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| A REST interface typically uses resource-oriented interaction, request and response messages, representations of resource state, stateless interaction, and standard protocol mechanisms. In common web implementations, REST interfaces often use HTTP methods, URIs, headers, status codes, and payload representations such as JSON or XML. | A REST interface typically uses resource-oriented interaction, request and response messages, representations of resource state, stateless interaction, and standard protocol mechanisms. In common web implementations, REST interfaces often use HTTP methods, URIs, headers, status codes, and payload representations such as JSON or XML. |
| |
| In the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], REST references identify possible implementation mechanisms. REST does not define the logical meaning of a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], data structure, policy decision, release package, or runtime plane. | In the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], REST references identify possible implementation mechanisms. REST does not define the logical meaning of a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], data structure, policy decision, release package, or runtime plane. |
| |
| A REST interface can realize, expose, or support a logical communication pattern selected by an implementation profile. The logical architecture remains independent of REST resource design, URI design, HTTP method selection, payload format, authentication mechanism, deployment boundary, and service implementation. | A REST interface can realize, expose, or support a logical communication pattern selected by an implementation profile. The logical architecture remains independent of REST resource design, URI design, HTTP method selection, payload format, authentication mechanism, deployment boundary, and service implementation. |