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
While there may be good reasons for specs to export informative terms (e.g. the Internationalization glossary), there should be limited reasons for a spec to export an informative term that is not a dfn type of definition.
Looking at data in Webref yields the following list of informative, non-dfn, and exported terms across specs. Many of them seem to be due to sections being incorrectly flagged as informative. For instance:
Web Bluetooth defines IDL names in "Notes" sections, which seems wrong.
Event Timing ends up defining IDL attribute in an informative section mostly by accident
WebRTC specs define event names in informative sections and it's not clear why.
In other cases, the informative nature of the definition is warranted, e.g. obsolete dictionaries members in WebRTC stats, but probably these terms should not be exported. These may disappear if ReSpec stops auto-exporting informative terms by default (see https://github.com/w3c/respec/issues/4349)
That could be something that Strudy ends up analyzing and reporting on.
While there may be good reasons for specs to export informative terms (e.g. the Internationalization glossary), there should be limited reasons for a spec to export an informative term that is not a
dfn
type of definition.Looking at data in Webref yields the following list of informative, non-dfn, and exported terms across specs. Many of them seem to be due to sections being incorrectly flagged as informative. For instance:
In other cases, the informative nature of the definition is warranted, e.g. obsolete dictionaries members in WebRTC stats, but probably these terms should not be exported. These may disappear if ReSpec stops auto-exporting informative terms by default (see https://github.com/w3c/respec/issues/4349)
That could be something that Strudy ends up analyzing and reporting on.
css-gcpm-3
css-nav-1
css-overflow-4
event-timing
geolocation
html
mediacapture-streams
miniapp-lifecycle
overscroll-scrollend-events
tracking-dnt
web-bluetooth
webrtc-ice
webrtc-identity
webrtc-stats
webrtc
The text was updated successfully, but these errors were encountered: