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.

Sign up for GitHub

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

Jump to bottom

Delete non-actionable statement about authentication #61

Closed
selfissued opened this issue Aug 25, 2024 · 6 comments
Closed

Delete non-actionable statement about authentication #61

selfissued opened this issue Aug 25, 2024 · 6 comments
Assignees
@msporny
Labels
editorial This item is editorial in nature. pr exists A Pull Request exists to address this issue.

Comments

@selfissued
Copy link
Collaborator

https://www.w3.org/TR/2024/WD-controller-document-20240817/#authentication
This sentence doesn't provide actionable information: "If authentication is established, it is up to the application to decide what to do with that information." It should either be deleted or updated to do so.
@msporny
Copy link
Member

msporny commented Aug 26, 2024

That sentence was added because a previous reviewer wanted to know what happens when authentication is established.

@msporny msporny added the pending close This item will be closed in 7 days unless there are objections. label Aug 26, 2024
@selfissued
Copy link
Collaborator Author

And this sentence doesn't answer the question of what happens when authentication is established, nor should it. The spec will be better off without this.

@selfissued selfissued removed the pending close This item will be closed in 7 days unless there are objections. label Aug 26, 2024
@dlongley dlongley mentioned this issue Aug 26, 2024
Closed
@selfissued
Copy link
Collaborator Author

How about replacing the whole sentence with "The processing performed following authentication is application-specific."?

This was referenced Aug 29, 2024
Closed
Closed
@msporny
Copy link
Member

msporny commented Sep 22, 2024

In order to make progress at W3C TPAC, I am suggesting that this issue is "editorial" and can be resolved during the Candidate Recommendation phase. The VCWG will discuss this issue at W3C TPAC to see if the "during CR" determination is correct.

@msporny msporny added editorial This item is editorial in nature. during CR This issue will be addressed during Candidate Recommendation labels Sep 22, 2024
@msporny msporny self-assigned this Nov 16, 2024
@msporny msporny mentioned this issue Nov 16, 2024
Merged
@msporny
Copy link
Member

msporny commented Nov 16, 2024

PR #122 has been raised to address this issue. This issue will be closed once PR #122 has been merged.

@msporny msporny added pr exists A Pull Request exists to address this issue. and removed discuss during CR This issue will be addressed during Candidate Recommendation labels Nov 16, 2024
@msporny
Copy link
Member

msporny commented Nov 23, 2024

PR #122 has been merged, closing.

@msporny msporny closed this as completed Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msporny msporny

Labels
editorial This item is editorial in nature. pr exists A Pull Request exists to address this issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@msporny @selfissued