Page History
Per RDS PDP WG Call 24 May, 2016, Action item #3: Staff to create a , below please find the latest sign-up list to facilitate volunteers coming forward allowing WG members to volunteer to review documents and identify possible requirements. WG members to sign up to review documents for possible requirements within 48 hours of circulation of sign-up sheet (below).
Instructions: This wiki sign-up sheet is to be used by RDS PDP WG members to volunteer to extract possible requirements for gTLD registration data or directory services (see https://community.icann.org/x/8waOAw). To volunteer, sign up for a key input document that is familiar to you by picking an unassigned document from the sign-up sheet (below). You may volunteer to review multiple documents, but please sign up for only one document at a time to give all a chance to contribute in parallel.
...
- 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 30 May.docx
Due date: WG members are encouraged to make progress on this task before the next WG call (7 June 2016), at which time the WG will assess progress and confirm that the initial possible requirements page is sufficiently complete to proceed to Task 9. Staff will integrate all submissions into the next draft of the RDS PDP List of Possible Requirements.
Currently, the latest version of the RDS PDP List of Possible Requirements is Draft #2, 30 May. Draft #3 will be produced on 7 June. All WG member submissions to date can also be found by clicking on "Y" in the "Done" column below.
- for gTLD registration data and directory services (28 October 2016) [PDF] and [DOC]
- An Excel workbook version is also available for filtering: PRSpreadsheets-D5Triage-28October.xlsx
- (Hint: Set all column filters to "All" to view all rows)
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 4: RDS PDP Initial List of Possible Requirements for gTLD registration data and directory services (11 September 2016)
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 codings.
The WG will now begin deliberation using subsets drawn from Draft 5, considering the possible requirements themselves.
All WG member submissions to date can be found by clicking on "Y" in the "Done" column below.
Note:
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 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).