Update RWS-Submission_Guidelines.md #528
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed first section, which is now out of date. Minor formatting updates.
cfredric
approved these changes
Sep 10, 2024
| A <b>subset</b> 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 <a href="#set-formation-requirements">formation requirements</a>, has passed the <a href="#set-validation-requirements">validation requirements</a>, and has been successfully submitted to the canonical RWS list. |
There was a problem hiding this comment.
If you feel like making more formatting updates, I think we can use Markdown syntax instead of HTML syntax for the links (here and elsewhere):
Suggested change
| A **Related Website Set**, or **set**, is a collection of domains that is subject to the <a href="#set-formation-requirements">formation requirements</a>, has passed the <a href="#set-validation-requirements">validation requirements</a>, and has been successfully submitted to the canonical RWS list. | |
| A **Related Website Set**, or **set**, is a collection of domains that is subject to the [formation requirements](#set-formation-requirements), has passed the [validation requirements](#set-validation-requirements), and has been successfully submitted to the canonical RWS list. |
There was a problem hiding this comment.
:) I'm on leave, back 19 September, but I'll have a go then (since I've started, I might as well finish!)
| @@ -220,7 +226,8 @@ The /.well-known/related-website-set.json file for set members must follow the s | |||
| "required": ["primary"] | |||
| } | |||
| ``` | |||
| ## Subset-level technical validation ## | |||
|
|
|||
| ### Subset-level technical validation | |||
|
|
|||
| Additionally, more granular technical checks will also run on GitHub for service domains and ccTLD variants in the submissions. | |||
|
|
|||
There was a problem hiding this comment.
If you feel like doing more formatting cleanup, we could convert the <ul> below to use markdown syntax (*).
|
Looks like you've passed all of the checks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed first section, which is now out of date.
Minor formatting updates.