LUW

Author: HeikoTheissen

vocabularies/Common.json

@@ -1401,7 +1401,7 @@
       "$AppliesTo": ["EntityType"],
       "@Common.Experimental": true,
       "@Core.Description": "An operation that updates properties one of which is a stream property",
-      "@Core.LongDescription": "To invoke the operation the client makes two requests that change the same entity in one LUW:\n- a POST, PUT or PATCH request that updates the non-stream properties followed by\n- a PUT or DELETE request on the stream property (not in a $batch).\n\nBoth requests become effective only if the second request succeeds."
+      "@Core.LongDescription": "To invoke the operation the client makes two requests that change the same entity in one LUW:\n- a POST, PUT or PATCH request that updates the non-stream properties\n- a PUT or DELETE request on the stream property (not in a $batch).\n\nIf one of these request fails, any effect of the other MUST be rolled back as well."
     }
   }
 }

vocabularies/Common.md

@@ -115,7 +115,7 @@ Term|Type|Description
 [WebSocketBaseURL](Common.xml#L1610) *([Experimental](Common.md#Experimental))*|URL|<a name="WebSocketBaseURL"></a>Base URL for WebSocket connections<br>This annotation MUST be unqualified.
 [WebSocketChannel](Common.xml#L1618) *([Experimental](Common.md#Experimental))*|String?|<a name="WebSocketChannel"></a>Channel for WebSocket connections<br><p>Messages sent over the channel follow the <a href="https://community.sap.com/t5/application-development-blog-posts/specification-of-the-push-channel-protocol-pcp/ba-p/13137541">ABAP Push Channel Protocol</a>. To consume a channel, the client opens a web socket connection at the <a href="#WebSocketBaseURL"><code>WebSocketBaseURL</code></a> followed by URL parameters</p> <ul> <li>parameter name = annotation qualifier, parameter value = channel ID (see below)</li> <li>parameter name = <code>relatedService</code>, parameter value = base URL (relative to server root) of the OData service of the app</li> </ul> <p>Supported qualifiers and channel IDs:</p> <dl> <dt>`sideEffects` <dd>Notifications about side effects to be triggered by the client (channel ID = non-null annotation value) </dl> 
 [AddressViaNavigationPath](Common.xml#L1635)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|<a name="AddressViaNavigationPath"></a>Service prefers requests to use a resource path with navigation properties<br>Use this tag on services that do not restrict requests to certain resource paths via [`Capabilities`](https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Capabilities.V1.html) or [`Core.RequiresExplicitBinding`](https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Core.V1.html#RequiresExplicitBinding) annotations, but that prefer requests with a resource path that contains the navigation properties reflecting the UI structure.<br>For example, entering a cancellation fee into an order item field bound to `CancellationItem/Fee` leads to a `PATCH Orders(23)/Items(5)/CancellationItem` request with `{"Fee": ...}` payload.
-[StreamOperation](Common.xml#L1650) *([Experimental](Common.md#Experimental))*|\[PropertyPath\]|<a name="StreamOperation"></a>An operation that updates properties one of which is a stream property<br><p>To invoke the operation the client makes two requests that change the same entity in one LUW:</p> <ul> <li>a POST, PUT or PATCH request that updates the non-stream properties followed by</li> <li>a PUT or DELETE request on the stream property (not in a $batch).</li> </ul> <p>Both requests become effective only if the second request succeeds.</p> 
+[StreamOperation](Common.xml#L1650) *([Experimental](Common.md#Experimental))*|\[PropertyPath\]|<a name="StreamOperation"></a>An operation that updates properties one of which is a stream property<br><p>To invoke the operation the client makes two requests that change the same entity in one LUW:</p> <ul> <li>a POST, PUT or PATCH request that updates the non-stream properties</li> <li>a PUT or DELETE request on the stream property (not in a $batch).</li> </ul> <p>If one of these request fails, any effect of the other MUST be rolled back as well.</p> 
 
 <a name="TextFormatType"></a>
 ## [TextFormatType](Common.xml#L134)

vocabularies/Common.xml

@@ -1652,10 +1652,10 @@ leads to a
         <Annotation Term="Core.Description" String="An operation that updates properties one of which is a stream property" />
         <Annotation Term="Core.LongDescription">
           <String>To invoke the operation the client makes two requests that change the same entity in one LUW:
-- a POST, PUT or PATCH request that updates the non-stream properties followed by
+- a POST, PUT or PATCH request that updates the non-stream properties
 - a PUT or DELETE request on the stream property (not in a $batch).
 
-Both requests become effective only if the second request succeeds.</String>
+If one of these request fails, any effect of the other MUST be rolled back as well.</String>
         </Annotation>
       </Term>