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

Convert rationaleBySite free text fields to structured enumerations? #531

Open
krgovind opened this issue Sep 6, 2024 · 1 comment
Open

Comments

@krgovind
Copy link
Collaborator

krgovind commented Sep 6, 2024

Currently the submission process requires submitters to provide a free text field for associated and service sites. The field is expected to capture:

  • For associated sites - "An explanation of how you clearly present the affiliation across domains to users and why users would expect your domains to be affiliated”
  • For service sites - "An explanation of how each domain in this subset supports functionality or security needs."

Based on a quick skim of the existing entries, it appears that not all submitters are completing this field as recommended; so it might make sense to convert these to structured enumerations. This will enable at least a couple of things:

  • Ensures consistent application of the guidelines
  • Allows browsers to present the rationales on UI

The list of available enumerations should ideally be comprehensive to allow submitters to make the choice that is most appropriate to their set. An initial set of enumerations could be as follows:

Associated site rationale options - submitter could choose one of these options:

  • Common branding
  • Shared naming
  • Single sign-on
  • Shared privacy policy
  • Other/unlisted

Service site rationale options - submitter could choose multiple of the following:

  • Content delivery
  • API Service
  • Data Management
  • Performance metric collection
  • Sandbox domain
  • Other/unlisted

The Chrome team would be interested in ecosystem feedback on this potential direction.

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