You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on a discussion in the context of MDN, I think it would be useful to look into reffy (or maybe more likely, a tool built on top of reffy) providing some kind of monitoring infrastructure for changes in specifications.
The rough idea would be to allow people to subscribe to a notification mechanism that alerts you when a given condition in a given spec changes; for instance, detect if the number of items in <ul> in a given section has changed, or if the .textContent of a given node has changed, etc.
One thing I'm not clear on yet is whether we can find the right level of expressiveness for defining meaningful conditions that would trigger these notifications; there is a high risk of creating too much noise.
cc @wbamberg since I think we would want a committed customer before we investigate this.
The text was updated successfully, but these errors were encountered:
Based on a discussion in the context of MDN, I think it would be useful to look into reffy (or maybe more likely, a tool built on top of reffy) providing some kind of monitoring infrastructure for changes in specifications.
The rough idea would be to allow people to subscribe to a notification mechanism that alerts you when a given condition in a given spec changes; for instance, detect if the number of items in
<ul>
in a given section has changed, or if the.textContent
of a given node has changed, etc.I imagine subscription could be managed with a github managed configuration file (à la https://github.com/w3c/github-notify-ml-config/), with notifications themselves probably provided via github issues?
One thing I'm not clear on yet is whether we can find the right level of expressiveness for defining meaningful conditions that would trigger these notifications; there is a high risk of creating too much noise.
cc @wbamberg since I think we would want a committed customer before we investigate this.
The text was updated successfully, but these errors were encountered: