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

Clearly mark the "Implementation Suggestions" section as normative or not #390

Closed
jyasskin opened this issue Sep 6, 2016 · 5 comments · Fixed by #395
Closed

Clearly mark the "Implementation Suggestions" section as normative or not #390

jyasskin opened this issue Sep 6, 2016 · 5 comments · Fixed by #395
Assignees

Comments

@jyasskin
Copy link
Member

jyasskin commented Sep 6, 2016

https://w3c.github.io/mediacapture-main/getusermedia.html#implementation-suggestions does not have a clear "This section is non-normative." indication, and the Conformance section says

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

which says the Suggestions section is normative. However, the change log for its addition says it's non-normative, and it'd be very strange for a section titled "suggestions" to actually hold requirements.

@jan-ivar's citing the section as normative in #387 (comment), so I think the decision either way will be controversial.

@jan-ivar
Copy link
Member

jan-ivar commented Sep 7, 2016

@jyasskin I didn't mean to suggest it was normative, only that it sheds light on the thinking behind related normative language (specifically a concern about privacy around device accessibility, that non-stored permission ends when all tracks stop).

@alvestrand
Copy link
Contributor

@jyasskin the authors thought it was non-normative when written. I think adding "implementation suggestions" to the list in the "Conformance" section should the right thing to do. But this text is generated from ReSpec boilerplate - it's not actually present in the source. Calling out to @dontcallmedom for advice here.

@dontcallmedom
Copy link
Member

There is <section id='conformance'> where we can add anything we want to add to the conformance section.

In this specific case, I think we probably need to distinguish more clearly what's purely suggestions from what is normative, and put what is clearly normative in a section with a less confusing name.

@alvestrand
Copy link
Contributor

Before marking it as non-normative (by merging PR #395), we need to review the section to make sure all normative-sounding statements are indeed stated normatively elsewhere - this section should either point to those statements or delete the text.

@burnburn
Copy link
Contributor

FYI, review will start after we conclude on PR #411 sometime next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants