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

Allow for language negotiation or localization of privacy policy and TOS? #681

Open
aphillips opened this issue Nov 7, 2024 · 1 comment
Open

Allow for language negotiation or localization of privacy policy and TOS? #681

aphillips opened this issue Nov 7, 2024 · 1 comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link

3.4 Client Metadata
https://w3c-fedid.github.io/FedCM/#idp-api-client-id-metadata-endpoint

privacy_policy_url, of type USVString
A link to the RP's Privacy Policy.
terms_of_service_url, of type USVString
A link to the RP's Terms of Service.

The client metadata structure allows for URLs to documents related to privacy policy and TOS. There is no affordance for performing language negotiation. These static links might be to documents for which it is important to have a translation available.

In addition, there doesn't appear to be a mechanism for negotiating language (locale) between the RP and IDP.
@aphillips aphillips added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Nov 7, 2024
@aphillips aphillips mentioned this issue Nov 7, 2024
Open
@cbiesinger
Copy link
Collaborator

Might be a duplicate of bug #592

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aphillips @cbiesinger