!!! Overview
[{$pagename}] is the specific Action that may be performed on a [Target Resource].

[{$pagename}]s might be used as [Contextual Attributes] within an [Attribute Based Access Control]

An [Example] [{$pagename}] might be the [CRUD] [Access] Actions: 
* [Create]
* [Read] 
* [Update]
* [Delete]

Or [Example] we could have [{$pagename}]s:
* [Operating System] [Privilege] to "[Read]" a File.
* [Physical Access Control] [Privilege] to "Open" a Door.!! [{$pagename}] for [SQL] and [HTTP] / [REST] and [LDAP][1]
%%zebra-table
%%sortable
%%table-filter
||Operation||[SQL]||[HTTP]/[REST]|[LDAP]
|[Create]|INSERT|[PUT|HTTP PUT] / [POST|HTTP POST]|[Add Request]
|[Read]|SELECT|[GET|HTTP GET]|[Search Request]/[SearchResultEntry]
|[Update]|UPDATE|[PUT|HTTP PUT] / [POST|HTTP POST] / [PATCH|HTTP PATCH]|[Modify Request]
|[Delete]|DELETE|[DELETE|HTTP DELETE]|[Delete Request]
/%
/%
/%

Though [HTTP GET] and [HTTP DELETE] coordinate well, [HTTP POST], [HTTP PUT], and [HTTP PATCH] aren’t directly synonymous with a single [CRUD] operation.
For [example], [HTTP POST] doesn’t necessarily only mean “Create”. It’s actually a very versatile method — so versatile that the entire [SOAP] [protocol] is tunneled through the [HTTP POST] method when used with [HTTP].

Since [HTTP Methods] don’t map cleanly to [CRUD], Ulsberg argues that [API] providers should consider how they might describe their [APIs] in a different way:
''"Don’t limit yourself to [CRUD] when you design a [REST] [API]. You should read the specification and understand the semantics of each method, and use it properly."''
What it comes down to is that [REST] is an [Architecture] [Model], not a [protocol].

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Designing a True REST State Machine|http://nordicapis.com/designing-a-true-rest-state-machine/|target='_blank'] - based on information obtained 2017-02-02-