Will be very useful. But will certainly need more time to sort that out that just in AOB ;) Tall to you soon. All the best SeB

Le 22 févr. 2017 à 09:04, Thomas Rickert <rickert@anwaelte.de> a écrit :

Hi Avri, that is a great idea. We should use consistent terminology in all our efforts. Putting it in AOB for the call is a good idea.

BTW - I will only be able to attend part of the call in several hours due to travel.

Best Thomas

...

Am 22.02.2017 um 07:24 schrieb avri doria <avri@acm.org>:

But which I have seen elsewhere.

Does/should WS2 have a consistent terminology for deal with the dichotomy between a single ICANN multistakeholder organization and the Trinity of Board, Staff & the community.

Each person writing a doc finds another clever way to try and express this, but they all differ a bit.

It struck us that it might be useful for there to be one set of language for expressing this across the work we are doing. Is there such a set of terminology that I have missed?

perhaps this can be added to AOB in the plenary meeting?

thanks

avri

--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

Thanks a million to Avri for raising this issue! I believe that HR pen-holders and the whole HR subgroup already faced the ambiguity re term ICANN and the lack of agreed terminology while drafting the Human Rights FoI. Or better to say, while drafting the second part of it, which is still work in progress. Would be great to have at least some agreement on consistent terminology before we finalise it. Then the subgroup can edit the document accordingly. AOB slot on the agenda of course wouldn't be enough to agree on this, but at least we can discuss the way forward. Warm regards, Tanya On 22/02/17 18:18, Greg Shatan wrote:

Good point.

ICANN the corporation now seems to prefer "ICANN Org" or "ICANN Organization." I have tended to call it "ICANN Inc." or sometimes "ICANN Corp."

I'm not sure if this means that the unholy trinity is merely "ICANN", or is it the "ICANN Ecosystem" or the "ICANN System" or the "ICANN Environment" or something else.... Personally, I suggest that it NOT be merely "ICANN," since that is ambiguous.

Whatever we decide, it should be clearly noted and defined at the beginning of the document.

It would be good to decide this soon so that all documents can be edited accordingly while they are still in subgroup drafting.

Greg

*Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc@gmail.com <mailto:gregshatanipc@gmail.com>

On Wed, Feb 22, 2017 at 8:49 AM, Sebastien Bachollet <sebicann@bachollet.fr <mailto:sebicann@bachollet.fr>> wrote:

Will be very useful. But will certainly need more time to sort that out that just in AOB ;) Tall to you soon. All the best SeB

> Le 22 févr. 2017 à 09:04, Thomas Rickert <rickert@anwaelte.de <mailto:rickert@anwaelte.de>> a écrit : > > Hi Avri, > that is a great idea. We should use consistent terminology in all our efforts. Putting it in AOB for the call is a good idea. > > BTW - I will only be able to attend part of the call in several hours due to travel. > > Best > Thomas > >> Am 22.02.2017 um 07:24 schrieb avri doria <avri@acm.org <mailto:avri@acm.org>>: >> >> >> But which I have seen elsewhere. >> >> Does/should WS2 have a consistent terminology for deal with the >> dichotomy between a single ICANN multistakeholder organization and the >> Trinity of Board, Staff & the community. >> >> Each person writing a doc finds another clever way to try and express >> this, but they all differ a bit. >> >> It struck us that it might be useful for there to be one set of language >> for expressing this across the work we are doing. Is there such a set of >> terminology that I have missed? >> >> perhaps this can be added to AOB in the plenary meeting? >> >> thanks >> >> avri >> >> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus <https://www.avast.com/antivirus> >> >> _______________________________________________ >> Accountability-Cross-Community mailing list >> Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> >> https://mm.icann.org/mailman/listinfo/accountability-cross-community <https://mm.icann.org/mailman/listinfo/accountability-cross-community> > > > _______________________________________________ > Accountability-Cross-Community mailing list > Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> > https://mm.icann.org/mailman/listinfo/accountability-cross-community <https://mm.icann.org/mailman/listinfo/accountability-cross-community>

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> https://mm.icann.org/mailman/listinfo/accountability-cross-community <https://mm.icann.org/mailman/listinfo/accountability-cross-community>

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

Hi all, I agree with Seuns proposal, it is simpler. Best Regards On 2/23/17, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:

Hello,

I also had issues around this but I soon got used to it within the CCWG.

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):

- ICANN Community - ICANN Staff - ICANN Board

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)

I think ICANN organisation should be the single word phrase that covers the entire 3 categories.

Regards 1. https://www.icann.org/community/explore 2. https://www.icann.org/community

Sent from my LG G4 Kindly excuse brevity and typos

On Feb 22, 2017 07:25, "avri doria" <avri@acm.org> wrote:

...

But which I have seen elsewhere.

Does/should WS2 have a consistent terminology for deal with the dichotomy between a single ICANN multistakeholder organization and the Trinity of Board, Staff & the community.

Each person writing a doc finds another clever way to try and express this, but they all differ a bit.

It struck us that it might be useful for there to be one set of language for expressing this across the work we are doing. Is there such a set of terminology that I have missed?

perhaps this can be added to AOB in the plenary meeting?

thanks

avri

--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

-- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A