Issue #475 - update of CORE:Error Message chapter.Merge conflict fix.

w3c · Mar 8, 2023 · bce9169 · bce9169
2 parents 850359e + 5b7630e
commit bce9169
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/spec/VISSv2_Core.html b/spec/VISSv2_Core.html
@@ -440,8 +440,10 @@ <h2>Subscription</h2>
       <section id="error-message">
         <h2>Error Message</h2>
         <p>The server MUST inform a client about errors ocurring in interactions between the two, whether it is in a synchronous 
-        error response, or an asynchronous error event message as a result of a previous subscribe. The error message has three arguments, 
-        of which subscriptionId is mandatory only for error event messages.
+        error response, or an asynchronous error notification as a result of a previous subscribe. 
+        For transport protocols which do not control the logical linking between request and response messages it may not be possible to link an error message to the correct client request. 
+        In cases like this the server may omit sending an error message. 
+        The error message has three arguments, of which subscriptionId is mandatory only for error notifications.
         </p>
           <p>Arguments: 
             <ul>