Merge pull request #177 from farshidtz/event-data-filtering-note

Remove payload-based event filtering. Note this only comments out the section, we can revert this easily if desired. Related issue (#176) is to figure out how to do this properly so will remain open.
w3c · May 17, 2021 · a431190 · a431190
2 parents 3db135e + 4ff78a6
commit a431190
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/index.html b/index.html
@@ -1503,7 +1503,8 @@ <h4>Notification</h4>
                                     At the absence of any `type` query parameter, the server will deliver all
                                     types of events.
                                 </li>
-                                <li>
+                                <!-- Commented for now. See the issue details below. -->
+                                <!-- <li>
                                     <span class="rfc2119-assertion" id="tdd-notification-filter-search">
                                         The server MAY support event filtering based on the 
                                         search expressions passed as one of `jsonpath`, `xpath`, 
@@ -1523,8 +1524,11 @@ <h4>Notification</h4>
                                     </span>
                                     This is to inform the clients about the missing feature at the connection
                                     time and prevent unexpected network traffic and events.
-                                </li>
+                                </li> -->
                             </ul>
+                            <div class="issue" data-number="176">
+                                Event filtering based on the payload is work in progress. 
+                            </div>
                         </dd>
                         <dt>Event Data</dt>
                         <dd>