<div dir="auto">Hello,<div dir="auto"><br></div><div dir="auto">I also had issues around this but I soon got used to it within the CCWG. </div><div dir="auto"><br></div><div dir="auto">That said and while I understand we've made a call for a small group to figure this out. I will suggest that this doesn't result to yet another multiple pages document with new titles that requires getting used to. I think we can rely on the existing profile categorisation on the site which indicates the following 3 categories (as Tijani also hinted during the call):</div><div dir="auto"><br></div><div dir="auto">- ICANN Community</div><div dir="auto">- ICANN Staff</div><div dir="auto">- ICANN Board</div><div dir="auto"><br></div><div dir="auto">There is something about the MS community[2] as well and that includes the ICANN Board (which I think is appropriate because the community put the Board)</div><div dir="auto"><br></div><div dir="auto">I think ICANN organisation should be the single word phrase that covers the entire 3 categories.</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto">1. <a href="https://www.icann.org/community/explore">https://www.icann.org/community/explore</a></div><div dir="auto"> 2. <a href="https://www.icann.org/community">https://www.icann.org/community</a><br><br><div data-smartmail="gmail_signature" dir="auto">Sent from my LG G4<br>Kindly excuse brevity and typos</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Feb 22, 2017 07:25, "avri doria" <<a href="mailto:avri@acm.org">avri@acm.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
But which I have seen elsewhere.<br>
<br>
Does/should WS2 have a consistent terminology for deal with the<br>
dichotomy between a single ICANN multistakeholder organization and the<br>
Trinity of Board, Staff & the community.<br>
<br>
Each person writing a doc finds another clever way to try and express<br>
this, but they all differ a bit.<br>
<br>
It struck us that it might be useful for there to be one set of language<br>
for expressing this across the work we are doing. Is there such a set of<br>
terminology that I have missed?<br>
<br>
perhaps this can be added to AOB in the plenary meeting?<br>
<br>
thanks<br>
<br>
avri<br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/<wbr>antivirus</a><br>
<br>
______________________________<wbr>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-<wbr>Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/accountability-cross-<wbr>community</a><br>
</blockquote></div></div>