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

Delete misleading text about possible purposes for authentication #60

Open
selfissued opened this issue Aug 25, 2024 · 5 comments
Open
Labels
discuss during CR This issue will be addressed during Candidate Recommendation editorial This item is editorial in nature.

Comments

@selfissued
Copy link
Collaborator

https://www.w3.org/TR/2024/WD-controller-document-20240817/#authentication
Delete everything starting with the comma in this sentence: "The authentication verification relationship is used to specify how the controller is expected to be authenticated, for purposes such as logging into a website or engaging in any sort of challenge-response protocol." Defining a login protocol is way out of scope here. And the second clause is also about protocols. The first part of the sentence will work fine on its own.

@msporny
Copy link
Member

msporny commented Aug 26, 2024

The text was put in there initially because readers wanted us to provide examples of authentication. Removing it would re-raise those concerns.

@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

It remains that the suggested uses are out of scope - especially login.

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

My proposed wording for #61 "The processing performed following authentication is application-specific." also covers the ground that "for purposes such as logging into a website or engaging in any sort of challenge-response protocol" is trying to, but in a more general way. I suggest deleting the latter phrase and adding the former.

@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
@iherman
Copy link
Member

iherman commented Oct 15, 2024

If the choice is between, on the one hand, a spec that is succinct and with every sentence being actionable, or, on the other hand, a spec that is more readable and understandable for specification readers by way of examples, my choice goes clearly for the second. Therefore, my vote is to keep things as they are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss during CR This issue will be addressed during Candidate Recommendation editorial This item is editorial in nature.
Projects
None yet
Development

No branches or pull requests

3 participants