-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_OS
-
Fix Version/s: V4.01_WD01, V4.01_CSD02
-
Component/s: Protocol, URL Conventions
-
Labels:
-
Environment:
Applied
-
Proposal:
-
Resolution:
Another natural extension
Previous proposal:
(was 11.4.3) 11.4.3.1 Update a Single Entity
(add this first sentence to explain the expected request URL) To update a single entity in a collection, the client sends a PATCH or POST request to an entity's edit URL.
11.4.3.2 Updating Multiple Entities
To update multiple entities in a collection, the client sends a PATCH request to that collection's URL.
The URL may include a $filter query option restricting the entities to be updated. For the entities matching the filter expression or all entities in the collection if no $filter query option was given, the service handles the request as a request to update a single entity (link to 11.4.3.1).
On success, the response MUST be a valid success response (link to 9.1).
On failure, the service MUST NOT update any of the qualifying entities.
11.4.5 Deleting Entities from a Collection
(was 11.4.5) 11.4.5.1 Delete a Single Entity
11.4.5.2 Deleting Multiple Entities
To delete multiple entities in a collection, the client sends a DELETE request to that collection's URL.
The URL may include a $filter query option restricting the entities to be deleted. For the entities matching the filter expression or all entities in the collection if no $filter query option was given, the service handles the request as a request to delete a single entity (link to 11.4.5.1).
On success, the response MUST be 204 No Content (link to 9.1.4) and contain an empty body. .
On failure, the service MUST NOT delete any of the qualifying entities.
part2-url-conventions
In section "5.1 System Query Options", change the sentence "POST requests to entity sets as well as all PUT and DELETE requests do not allow system query options." to "POST and PUT requests to entity sets do not allow system query options."