[Note: This issue captures an open question related to the changes proposed in PR #91 and summarized on issue #92]

Chrome hopes to mitigate abuse of set formation through a transparent assertion process, which will increase accountability by facilitating awareness for users, developers, and interested parties.

We are also proposing some technical measures to prevent the scope of abuse (e.g., limit on associated domains). We may consider expanding the technical checks, where possible, involved in mitigating abuse (e.g., to validate the ccTLD and common eTLD subset categories). What are possible technical checks we should consider?