Skip to content

Commit

Permalink
Remove commented event filtering section, related to w3c#176
Browse files Browse the repository at this point in the history
  • Loading branch information
farshidtz committed Jun 7, 2021
1 parent 8ccc0ff commit deb23da
Showing 1 changed file with 0 additions and 22 deletions.
22 changes: 0 additions & 22 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1533,28 +1533,6 @@ <h4>Notification</h4>
At the absence of any `type` query parameter, the server will deliver all
types of events.
</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`,
or `sparql` query parameters.
</span>
This is to detect changes on particular TDs or attributes and does not affect
the event's data object.
<p>
For example, the JSONPath expression `$.properties`
will reduce the number of events to TDs that change their `properties` attributes.
The resulting events may be for created or deleted TDs with the `properties` attribute
or updates to `properties` attribute of existing TDs.
</p>
<span class="rfc2119-assertion" id="tdd-notification-filter-search-unsupported">
If the server does not support a given search query parameter, it
MUST reject the request with 501 (Not Implemented) status.
</span>
This is to inform the clients about the missing feature at the connection
time and prevent unexpected network traffic and events.
</li> -->
</ul>
<div class="issue" data-number="176">
Event filtering based on the payload is work in progress.
Expand Down

0 comments on commit deb23da

Please sign in to comment.