[ioepanel] suggestions

Tue Jan 14 10:01:36 UTC 2014

It's a long way to go but in the end we will have 99% correct automatic translation for both alphabetic and verbal text. I assume the Chief Internet Evangelist of Google is encouraging relevant innovation initiatives within his company and beyond, including Adobe. It may evolve into one of the strategic issues of the Internet Community, maybe even of ICANN.
....Hagen
_____________________________________________________________________________________________________
Dr. Hagen Hultzsch | Löwenburgweg 2 | D-53229 Bonn | Germany
desk: +49-228-976-5000 | cell: +49-171-228-8200 | fax: +49-228-976-5001 | e-fax +49 391 580115000 | hultzsch at telekom.de

________________________________
Von: ioepanel-bounces at icann.org [mailto:ioepanel-bounces at icann.org] Im Auftrag von Vint Cerf
Gesendet: Dienstag, 14. Januar 2014 03:47
An: InterNetX - Daniel Oppermann
Cc: ioepanel at icann.org
Betreff: Re: [ioepanel] suggestions

Daniel these are very good points. We probably won't be able to follow your recipe for the webinar on the 15th but the point about multi-lingual accommodation is very well taken and ought to be a point we tackle in the ecosystem document. I will ask the drafting team to find a place for that.

I think there is a speculative chance that some automatic translations could help but as you know the quality is still probably too low to be useful in a substantive conversation - taking us back to multi-lingual translations by humans. ICANN also makes use of transcription (real-time captions) although at this point only in English. I think Beth Noveck's panel on participation has an opportunity to engage on this point as well.

v

On Mon, Jan 13, 2014 at 4:53 PM, InterNetX - Daniel Oppermann <daniel.oppermann at internetx.com<mailto:daniel.oppermann at internetx.com>> wrote:
Hi all,

First I want to thank you guys for making todays webinar possible. It is certainly a good place to exchange ideas on the future of Internet governance. And I would like to make two suggestions:

1) Although it is important to get a free-flow input from participants and stakeholders I would suggest a little more structure during the webinars. Maybe by defining certain topics a week before the webinar so that people are aware what the discussion is going to focus on. Today we had 80 people in the webinar, 2-3 using the microphone option and 5-10 using the chat although a lot of stuff on the chat was not content-related. If we try to focus on topics we can get a better output I think.

2) Concerning globalization of ICANN: language is an important issue. There are many people out there that want to participate but do not speak English sufficiently or at all. When we look at several ICANN webinars we figure out that they are mostly dominated by English-speaking people, a lot of them (maybe the majority?) native-speakers. Others maybe understand English but are not able to express themselves in the same way they could in their own language. ICANN is on a good way to reach out to other regions of the world and now we need to include not only the names of countries and cities where ICANN has new offices but also the languages people speak on the Internet. We need webinars not only in English but also in Spanish, Chinese, Arab, French, Portuguese, Indonesian, Russian, Korean etc.

Best regards,
Daniel

------
Dr. Daniel Oppermann
CEO Domain Robot Ltda.
São Paulo, Brasil

InterNetX GmbH
Maximilianstr. 6
93047 Regensburg
Germany

Cel (BR) +55 11 98575 9090<tel:%2B55%2011%2098575%209090>
Tel. +49 941 59559-0/483<tel:%2B49%20941%2059559-0%2F483>
Fax  +49 941 59579-052<tel:%2B49%20941%2059579-052>

www.internetx.com<http://www.internetx.com/>
www.facebook.com/InterNetX<http://www.facebook.com/InterNetX>
www.twitter.com/InterNetX<http://www.twitter.com/InterNetX>

Geschäftsführer/CEO: Thomas Mörz
Amtsgericht Regensburg, HRB 7142

_______________________________________________
ioepanel mailing list
ioepanel at icann.org<mailto:ioepanel at icann.org>
https://mm.icann.org/mailman/listinfo/ioepanel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ioepanel/attachments/20140114/cd7a980f/attachment.html>