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
Notes in specs are by nature informative and as such should not contain normative statements. Notes in the current draft of the Remote Playback API that contain normative statements should either be adjusted to remain informative, or the content should be turned into real normative statements, to remove all ambiguity on the informative/normative nature of the text.
Notes that need some update:
At the end of §6.2.1.3. Suggestion would be to simply make the "should not" an informative one.
Note in §6.2.2 that states "for example it MAY show the user a dialog". Suggestion would be to make that "may" an informative one.
Notes at the end of §6.2.4. Here I would rather drop the "note" tag to make the text normative. Both normative statements sound good and are (manually) testable.
Note at the end of §6.2.7 about abrupt disconnection. I guess I would make the "should" an informative one as it's not going to be easy to test the notion of "abrupt disconnection".
The text was updated successfully, but these errors were encountered:
tidoust
added a commit
to tidoust/remote-playback
that referenced
this issue
Aug 25, 2017
Notes in specs are by nature informative and as such should not contain normative statements. Notes in the current draft of the Remote Playback API that contain normative statements should either be adjusted to remain informative, or the content should be turned into real normative statements, to remove all ambiguity on the informative/normative nature of the text.
Notes that need some update:
The text was updated successfully, but these errors were encountered: