[ALAC] Fwd: Re: CALL FOR COMMENTS: ALAC Statement on the Translation and Transliteration of Contact Information Working Group SO-AC Input Request

Rinalia Abdul Rahim rinalia.abdulrahim at gmail.com
Mon Feb 17 01:05:37 UTC 2014


Thanks for the information, Carlton.
Olivier, the ALAC needs to decide if it wishes to submit a view to the WG
at this stage or wait to see the EWG view on the matter.

An option to consider:
For now, send a simple, but clear message to the WG that says the ALAC
firmly believes that Registrants should not have to bear any of the cost
burden for translation and / or transliteration of registration contact
data.

The rest of the issues may benefit from waiting and hearing the EWG view,
the At-Large Registration WG view + the At-Large IDN WG view, which will
take time.

There will be calls for comments on the EWG work as well as the Translation
Transliteration WG work in the future, so there will be future
opportunities for providing input on the more complex aspects of the
issue.

Best regards,

Rinalia
On Feb 17, 2014 8:36 AM, "Carlton Samuels" <carlton.samuels at gmail.com>
wrote:

> FWIW, the specific issue of whether translations should be provided for
> registration data for directory services is under active discussion in the
> EWG.
>
> -Carlton
>
>
> ==============================
> Carlton A Samuels
> Mobile: 876-818-1799
> *Strategy, Planning, Governance, Assessment & Turnaround*
> =============================
>
>
> On Sun, Feb 16, 2014 at 1:20 AM, Rinalia Abdul Rahim <
> rinalia.abdulrahim at gmail.com> wrote:
>
>> Dear Olivier,
>>
>> I believe the questions posed to SO/AC  from the Translation
>> Transliteration of Contact Information WG requires At-Large scrutiny
>> beyond
>> the IDN Working Group.  The Registration Issues WG, among others, may have
>> a view on some of the key issues.
>>
>> The question of who should pay for translation and / or transliteration,
>> for example, may implicate registrants.  This question is linked to the
>> purpose and benefit of contact data transformation, which is a higher
>> level
>> issue.
>>
>> Best regards,
>>
>> Rinalia
>>  Dear Staff,
>>
>> I note the request for feedback.  I think the format in which the request
>> is made will deter responses.  Specifically, the questions posed are
>> buried
>> in a PDF document and not highlighted for appropriate attention.
>>
>> Action Needed:
>> 1. Please lift the questions out of the mail from Glen and highlight
>> prominently on the wiki page.
>> 2.  Please number the questions so that people can identify the ones that
>> they are responding to and so that it would be easier to aggregate and
>> analyze the response.
>>
>> Thanks.
>>
>> Rinalia
>>
>>
>> On Thu, Feb 13, 2014 at 9:35 AM, ICANN At-Large Staff <
>> staff at atlarge.icann.org> wrote:
>>
>> > Dear Edmon and Rinalia,
>> >
>> > Please note that the At-Large Translation and Transliteration of Contact
>> > Information Working Group SO-AC Input Request Workspace<
>> https://community.icann.org/x/bgDRAg>
>> >  has been created. Please note that this workspace will be used to
>> gather
>> > the At-Large's comments on this Input Request
>> >
>> > Please submit any comments on the workspace using the comments function
>> by *28
>> > Feb 2014 23:59 UTC*.
>> >
>> > Regards,
>> >
>> >
>> > Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie
>> > Peregrine and Julia Charvolen
>> >
>> > ICANN Policy Staff in support of ALAC
>> >
>> > E-mail: staff at atlarge.icann.org
>> >
>> >
>> >
>> _______________________________________________
>> ALAC mailing list
>> ALAC at atlarge-lists.icann.org
>> https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>> At-Large Online: http://www.atlarge.icann.org
>> ALAC Working Wiki:
>> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>>
>
>



More information about the ALAC mailing list