Page History
...
- Identify the associated charter question(s);
- Succinctly quote or paraphrase a possible requirement, focusing on phase 1 policy requirements;
- Cite the source document by title and hyperlink. Possible requirements may also be submitted from new sources not already listed below.
- Many examples can be found in the latest draft of the WG list of possible requirements:
- Draft 35: RDS PDP Initial List of Possible Requirements for gTLD registration data and directory services (10 June 28 October 2016) [PDF] and [DOC]This has been partially triaged for WG review: RDS PDP List of Possible Requirements D3 - TriageInProgress - 13 July.docx
- An Excel workbook version is also available for filtering on phase and group: PRSpreadsheets-D3TriageD5Triage-13July-withInstructions28October.xlsx
- (Hint: Set all column filters to "All" to view all rows)
- Work is also underway to refine additional columns for sorting and filtering triaged possible requirements: see draft Keyword Definitions and Coding Definitions submitted to the WG mailing list for review.
Next Steps:
History:
Draft 3 of this document was originally attached to Outreach Message #2 and provided to SO/AC/SG/Cs so that those groups could suggest any needed additions. WG members then extracted further possible requirements from additional documents (as recorded below) and from other sources for inclusion in Draft 4.
Draft 3 was also organized into grid format for triage into phases and groups - see RDS PDP List of Possible Requirements D3 - TriageInProgress - 13 July.docx.
Draft 4 included all possible requirements submitted since the original publication of Draft 3, in triaged grid format, along with keyword and coding definitions - see Draft 4All WG member submissions of possible requirements for registration data and directory services through 10 June 2016 were incorporated into Draft 3: RDS PDP Initial List of Possible Requirements for gTLD registration data and directory services (10 June 11 September 2016).
Draft 3 was attached to Outreach Message #2 and provided to SO/AC/SG/Cs so that those groups may suggest any needed additions. WG members are asked to complete pending assignments (recorded below) as soon as possible for inclusion in Draft 4. WG members may also continue to volunteer to extract possible requirements from other sources.
Note that Draft 3 has been organized into grid format for triage into phases and groups - see RDS PDP List of Possible Requirements D3 - TriageInProgress - 13 July.docx.
...
Next Steps:
All WG member submissions of possible requirements for registration data and directory services through 28 October 2016 have now been incorporated into:
This new draft:
- includes all possible requirements submitted since the original publication of Draft
...
- 4,
- deletes or moves possible requirements identified by the WG as having questionable relevance to the RDS,
- refines the code values initially mapped from keywords, and
- orders code and keyword values alphabetically for easier filtering.
Triage will continue as the WG incorporates additional possible requirements (see pending assignments below) and reviews and refines phases and groups and codings.
The WG will now begin deliberation using subsets drawn from Draft 5, considering the possible requirements themselves during deliberation.
All WG member submissions to date can be found by clicking on "Y" or "d4" in the "Done" column below.
...
...
Additional possible requirements have been submitted to the WG list from unpublished sources. Although these do not correspond to input documents and so are not listed above, those additional possible requirements can be found in the WG email archive and either have or will be incorporated into the draft initial possible requirements list. These addtions additions include possible requirements gathered during the Cross-Community Session on RDS in Helskinki (see http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2016-June/000933.html) and provided by SO/AC/SG/Cs in response to Outreach Message #2 (see SG/C/SO/AC Input).