I apologise for coming in somewhat late on this thread... I strongly suggest that before this group develops yet another vocabulary, that it carefully study the new Bylaws, and in particular, Annex D, and adopt the vocabulary which has been developed in both the Bylaws and Annex D as its basis going forward, augmenting it as necessary, but not re-inventing what's already in place, which is considerable. Best Regards, Stephen Deerhake AS Domain Registry GDNS, LLC sdeerhake@nic.as sdeerhake@gdns.net -----Original Message----- From: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] On Behalf Of avri doria Sent: Thursday, March 02, 2017 1:52 PM To: CCWG Accountability <accountability-cross-community@icann.org> Subject: [CCWG-ACCT] Terminology for the ICANN trinity hi, Sébastien and I [were] volunteered for the task of trying to clarify the words to be used in WS2 of documents when referring to ICANN, its workers, its board, and its community. While there were a few terms we could not come to agreement on, we have produced the enclosed draft terminology. It includes alternatives in the places where we disagreed. The doc can be found at: <https://docs.google.com/document/d/1JadPh5TJQ_-_LNfVu3EicZct1JMKk__b03W43IsF...> As always the document is open for suggestions and comments We are sending this for discussion by the full group and, if it is acceptable in general, for help in deciding between the alternatives numbered A1/A2 & B1/B2. thanks Avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus