Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust notes with normative content #101

Closed
tidoust opened this issue Aug 25, 2017 · 1 comment
Closed

Adjust notes with normative content #101

tidoust opened this issue Aug 25, 2017 · 1 comment

Comments

@tidoust
Copy link
Member

tidoust commented 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:

  • 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".
tidoust added a commit to tidoust/remote-playback that referenced this issue Aug 25, 2017
This update updates the notes that contained normative statements as suggested
in w3c#101.
@anssiko
Copy link
Member

anssiko commented Aug 28, 2017

Fixed with #102

@anssiko anssiko closed this as completed Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants