You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Currently the submission process requires submitters to provide a free text field for associated and service sites. The field is expected to capture:
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:
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:
Service site rationale options - submitter could choose multiple of the following:
The Chrome team would be interested in ecosystem feedback on this potential direction.
The text was updated successfully, but these errors were encountered: