diff --git a/RWS-Submission_Guidelines.md b/RWS-Submission_Guidelines.md index 66225f94..78a46ff0 100644 --- a/RWS-Submission_Guidelines.md +++ b/RWS-Submission_Guidelines.md @@ -1,53 +1,51 @@ # Related Website Sets Submission Guidelines -# Important Notice regarding Set Submissions -As Chrome prepares to [ship Related Website Sets](https://groups.google.com/a/chromium.org/g/blink-dev/c/7_6JDIfE1as) to General Availability (targeting a phased roll-out beginning Chrome 113), we will shift from “testing” to “live” for Related Website Sets submissions. Please note key dates below as they relate to when your submissions will be applied to Stable behavior in Chrome: - -# Overview Related Website Sets ("RWS") provides a framework for developers to declare relationships among sites, to enable limited cross-site cookie access for specific, user-facing purposes. This framework may help user agents, such as the Chrome browser ("Chrome"), to decide when to allow or deny a site access to their cookies when in a third-party context. RWS is a [Privacy Sandbox](https://privacysandbox.com/) proposal being incubated in the W3C's [WICG](https://www.w3.org/community/wicg/). For a full overview, consult the [explainer](https://github.com/privacycg/first-party-sets). The Related Website Sets Submission Guidelines ("Guidelines") are put forth by Chrome to define requirements and expectations for sets submitted by developers. Chrome remains committed to pursuing [standardization](https://www.w3.org/standards/) of RWS through engaging with developers, other browser vendors, and other interested parties. - # Definitions -A Related Website Set, or set, is a collection of domains that is subject to the formation requirements, has passed the validation requirements, and has been successfully submitted to the canonical RWS list. -A subset is a defined use case within a set. Set members, or domains, will always be part of a subset. +## Definitions + +A **Related Website Set**, or **set**, is a collection of domains that is subject to the formation requirements, has passed the validation requirements, and has been successfully submitted to the canonical RWS list. + +A **subset** is a defined use case within a set. Set members, or domains, will always be part of a subset. + +A **set primary** is the domain a set submitter has identified as the representative of its set. Other domains within the set have a defined relationship with the primary. -A set primary is the domain a set submitter has identified as the representative of its set. Other domains within the set have a defined relationship with the primary. +A **set member** is a domain that is part of a set that is not the primary. A set member will always be part of a subset within the set. -A set member is a domain that is part of a set that is not the primary. A set member will always be part of a subset within the set. +The **canonical RWS list** is a publicly viewable list in a JSON file format housed in the RWS GitHub repository that is the source-of-truth for all sets that are subject to the formation requirements and have passed the validation requirements. Browsers, such as Chrome, can consume this file to apply to their behavior. -The canonical RWS list is a publicly viewable list in a JSON file format housed in the RWS GitHub repository that is the source-of-truth for all sets that are subject to the formation requirements and have passed the validation requirements. Browsers, such as Chrome, can consume this file to apply to their behavior. +A **pull request (PR)**, is the method of requesting a change on GitHub (like adding or modifying a set to the canonical RWS list). -A pull request (PR), is the method of requesting a change on GitHub (like adding or modifying a set to the canonical RWS list). +A **submission** is an addition or modification to the canonical RWS list submitted by the submitter that is subject to the formation and the validation requirements. -A submission is an addition or modification to the canonical RWS list submitted by the submitter that is subject to the formation and the validation requirements. +A **submitter** is the individual or, if an individual is acting on behalf of their organization, the organization that has submitted a pull request against the canonical RWS list to create or modify a set for validation. -A submitter is the individual or, if an individual is acting on behalf of their organization, the organization that has submitted a pull request against the canonical RWS list to create or modify a set for validation. +An **equivalent domain** is the primary, service, or associated domain in a set for which there is a ccTLD variant in the same set. The equivalent domain has the same effective second-level domain (eSLD, or eTLD+1 minus eTLD) as a ccTLD variant in the same set. -An equivalent domain is the primary, service, or associated domain in a set for which there is a ccTLD variant in the same set. The equivalent domain has the same effective second-level domain (eSLD, or eTLD+1 minus eTLD) as a ccTLD variant in the same set. -# Set Formation Requirements -The table below describes the types of subsets that RWS currently supports, including requirements to help prevent misuse of the subset. +## Set Formation Requirements -All submissions are subject to the formation requirements detailed in this section as well as the technical validation requirements in the next section. +The table below describes the types of subsets that RWS currently supports, including requirements to help prevent misuse of the subset. + +All submissions are subject to the formation requirements detailed in this section as well as the technical validation requirements in the next section. | Subset Type | Subset Definition | | ----------- | ----------------- | | Service |