Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto
In general agreement. And even if we agree to forget about the problem, the communities in need are unlikely to allow it to be forgotten for long. Ram On Tue, May 14, 2019, 1:44 PM Roberto Gaetano <roberto_gaetano@hotmail.com> wrote:
Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto
… and if the community won’t let us forget it, they may possibly push the issue in ways that I find strange, complicated and foreign. I’ll try to be more open to that. From: UA-discuss <ua-discuss-bounces@icann.org> On Behalf Of Ram Mohan Sent: Tuesday, May 14, 2019 1:47 PM To: Roberto Gaetano <roberto_gaetano@hotmail.com> Cc: Universal Acceptance <UA-discuss@icann.org> Subject: Re: [UA-discuss] Cultural Acceptance In general agreement. And even if we agree to forget about the problem, the communities in need are unlikely to allow it to be forgotten for long. Ram On Tue, May 14, 2019, 1:44 PM Roberto Gaetano <roberto_gaetano@hotmail.com<mailto:roberto_gaetano@hotmail.com>> wrote: Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto
In general agreement with Roberto and Ram. If we work towards making the tools and software as per the requirements of the community taking their literacy and cultural aspects , the adoption rate of UA will be accordingly faster. Further ,often we try to fix one solution for all ignoring the community's behaviour in adoption of technology. Best Govind On Wed, May 15, 2019 at 10:57 PM Mark Svancarek (CELA) via UA-discuss < ua-discuss@icann.org> wrote:
… and if the community won’t let us forget it, they may possibly push the issue in ways that I find strange, complicated and foreign. I’ll try to be more open to that.
*From:* UA-discuss <ua-discuss-bounces@icann.org> *On Behalf Of *Ram Mohan *Sent:* Tuesday, May 14, 2019 1:47 PM *To:* Roberto Gaetano <roberto_gaetano@hotmail.com> *Cc:* Universal Acceptance <UA-discuss@icann.org> *Subject:* Re: [UA-discuss] Cultural Acceptance
In general agreement.
And even if we agree to forget about the problem, the communities in need are unlikely to allow it to be forgotten for long.
Ram
On Tue, May 14, 2019, 1:44 PM Roberto Gaetano <roberto_gaetano@hotmail.com> wrote:
Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto
On Tue, 14 May 2019 22:47:12 +0200, Ram Mohan <rmohan@afilias.info> wrote:
In general agreement.
Likewise.
And even if we agree to forget about the problem, the communities in need are unlikely to allow it to be forgotten for long.
Unfortunately, they might just decide to give up on us. If we lose the people we are supposed to serve, and the people we need to help serve them, then we might as well be doing something else... So I believe it is partially up to us to make sure we are visibly concerned about issues that we may not have a quick solution for, and about working out what those are... cheers Chaals
Ram
On Tue, May 14, 2019, 1:44 PM Roberto Gaetano <roberto_gaetano@hotmail.com> wrote:
Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what >>seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” >>vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more >>complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto
-- Using Opera's mail client: http://www.opera.com/mail/
Dear all, Even if it’s not explicitly covered in written documents or it’s partially covered, Multicultural Acceptance is something which was practiced by previous and will be practiced by new leadership. Cultural diversity is well covered by new leadership, and especially in UA Ambassadorship program. There is no doubt that we always pay attention to that. And even for existence of UASG we need to thank to cultural acceptance. My personal opinion is that whole IDN TLD and the whole New gTLD program was done as a result of entrepreneurship culture, practiced mostly in US. This culture is in essence – put idea on the market asap, and solve the problems along the way. By nature, very much like updates for your apps, or Windows, or Mac OS… Europeans, at least Eastern European style (and the style seen in ME area and other areas in the woirld), would be differently – first complete planning, strategy, and solving problems (variants, emoji, emails and all other possible problems), then – IDNs and New Gs can go on the market. I don’t have any wish for accusations, or claims what is better approach. But, in essence, most of the discussions here on the list are about what I just said. Take for example IDN Guidelines 4.0 discussion – those guidelines are similar like “upgrade for an app”, by nature, but on the other hand, causing some other problems – changing the value of some existing IDN domain names, which can be the problem for the end user. J So without any doubts, we are always dealing with cultural differences in UASG – it’s not just obvious at first glance. Cheers, Dusan From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Charles 'chaals' (McCathie) Nevile Sent: 16. мај 2019. 1:28 To: ua-discuss@icann.org Subject: Re: [UA-discuss] Cultural Acceptance On Tue, 14 May 2019 22:47:12 +0200, Ram Mohan <rmohan@afilias.info <mailto:rmohan@afilias.info> > wrote: In general agreement. Likewise. And even if we agree to forget about the problem, the communities in need are unlikely to allow it to be forgotten for long. Unfortunately, they might just decide to give up on us. If we lose the people we are supposed to serve, and the people we need to help serve them, then we might as well be doing something else... So I believe it is partially up to us to make sure we are visibly concerned about issues that we may not have a quick solution for, and about working out what those are... cheers Chaals Ram On Tue, May 14, 2019, 1:44 PM Roberto Gaetano <roberto_gaetano@hotmail.com <mailto:roberto_gaetano@hotmail.com> > wrote: Hi all. I am under the impression that we need to address one issue that is a subset of the overarching Universal Acceptance, and that is related to cultural differences. In simple words, we need to accept the fact that in different parts of the world people have different way of thinking and different priorities, and sometimes what seems logical, easy and familiar to some is strange, complicated and foreign to others. I have spent decades in software development and have often witnessed discussions on the lines of “Why can’t you use the tool in the way it has been designed?” vs “Why can’t you design the tool in the way we want to use it?”. The question I have is whether we accept the fact that some languages and scripts have features that require a different approach - and probably a more complicated solution to provide users that belong to that particular culture with a fully satisfactory user experience - and include these related issues in our to-do list. There is then a completely separate question that is “Do we have the resources to do it?”. And the follow-up question “Who does it?”. While I can understand that we might not implement solutions in the near future, I have difficulties in accepting to forget about the problem altogether. Cheers, Roberto -- Using Opera's mail client: http://www.opera.com/mail/ --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
participants (6)
-
Charles 'chaals' (McCathie) Nevile -
Dr. Govind -
Dušan Stojičević -
Mark Svancarek (CELA) -
Ram Mohan -
Roberto Gaetano