From nathalie.peregrine at icann.org  Mon Aug  4 19:57:20 2014
From: nathalie.peregrine at icann.org (Nathalie Peregrine)
Date: Mon, 4 Aug 2014 19:57:20 +0000
Subject: [gnso-contactinfo-pdp-wg] REMINDER: PLEASE RSVP  Monthly GNSO WG Newcomer Open House Session
Message-ID: <e994ba95180e4f41aff072ad84fe98dd@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>


Reminder: Monthly GNSO WG Newcomer Open House Session


These ongoing monthly sessions are for new GNSO WG participants to come
together and discuss any questions they may have about GNSO Working Groups,
procedures and/or processes. We know there is a lot of information to digest
when you join a GNSO Working Group and these monthly meetings are an
opportunity for newcomers and more experienced participants to meet in an
informal setting without the pressure of "real work" that needs be done.

The agenda is flexible.  The presenters will be ready with a standard set of
materials if people would like to discuss them.  Feel free to submit
questions, either in advance or at the beginning of the meeting, if there is
a topic that you would like to explore in more depth .  Providing useful
answers to a wide range of questions is part of the reason why these
meetings are 


Thursday 7 August at 12.00 UTC
Thursday 4 September at 20.00 UTC
Thursday 2 October at 12.00 UTC
Thursday 6 November at 20.00 UTC
Thursday 4 December at 12.00 UTC

To convert to your local time zone, please see
http://www.timeanddate.com/worldclock/converter.html

If you are interested to join the next meeting on 7 August or any of the
future meetings, please let the GNSO Secretariat know (
<mailto:gnso-secs at icann.org> gnso-secs at icann.org) and we will send you the
call details. If there are any specific questions you already have, or any
overviews or introductions you think would be helpful (e.g. GNSO Policy
Development Process or GNSO Working Group guidelines), please let us know in
advance and we will prepare materials accordingly. Feel free to share this
invitation with others that you think may be interested.

We look forward to welcoming you at the next meeting!

Nathalie Peregrine 

GNSO Secretariat

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140804/8507d5a0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5457 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140804/8507d5a0/smime.p7s>

From c.dillon at ucl.ac.uk  Mon Aug 11 17:48:52 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Mon, 11 Aug 2014 17:48:52 +0000
Subject: [gnso-contactinfo-pdp-wg] Themes for discussion
Message-ID: <D00EBF3C.1FA8A%ccaacdi@live.ucl.ac.uk>

Dear colleagues,

As promised during our last call, I am recirculating the latest version of the recommendations and the points identified so far for discussion, in preparation for Thursday's meeting. Please feel free to circulate any other themes you spot as you read the recommendations to this mailing list.

Regards,

Chris.

From: <Dillon>, Chris Dillon <c.dillon at ucl.ac.uk<mailto:c.dillon at ucl.ac.uk>>
Date: Wednesday, 30 July 2014 10:31
To: "gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>" <gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>>
Subject: [gnso-contactinfo-pdp-wg] Themes for discussion

Dear colleagues,

I would like to assemble here some themes for discussion during tomorrow's call, apart from the purposes/accuracy one that has already come up (see my earlier email below).

Here are some other themes I am aware of:

?         Should we recommend that there should be an option for registrants voluntarily to input transformed contact information?

?         Should we recommend that something be done with legacy transformed contact information (i.e. contact information input using a different policy from what we are recommending)?

?         It seems likely that our recommendations for those cases when transformation occurs will not be binding. That would mean, for example, that C5 on when the policy comes into effect would need to be redrafted.

?         What should happen to transformed contact information created by other stakeholders? O2 may need redrafting.

Please send any additional themes for discussion to this mailing list. I've attached the recommendations for your convenience.

Regards,

Chris.

From: owner-gnso-contactinfo-pdp-wg at icann.org<mailto:owner-gnso-contactinfo-pdp-wg at icann.org> [mailto:owner-gnso-contactinfo-pdp-wg at icann.org] On Behalf Of Dillon, Chris
Sent: 25 July 2014 11:00
To: gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>
Subject: [gnso-contactinfo-pdp-wg] Purpose and accuracy

Dear colleagues,

Ideally we need to add something about the purposes of contact information that require accuracy and those that don't.

The Final report from the EWG on gTLD Directory Services has a good list of purposes from p.19-34.

The Study to evaluate solutions for the submission and display of internationalized contact data has a useful section on Information accuracy for effective use on p.9 with three levels of accuracy suggested:
1. Requiring accurate transformation (e.g. valid in a court of law, matching information in a passport, matching information in legal incorporation etc.)
2. Requiring consistent transformation (allowing use of such information to match other information provided in another context, e.g. to match address information to a registrant on a Google map, etc.)
3. Requiring ad hoc transformation (allowing informal or casual version of the information in another language to provide more general accessibility)

The last sentence of the study is of particular interest to us from the accuracy point of view and also from its summary of the state of the transformation tools etc.:
"The study has found that provisioning and querying protocols are lacking either support or deployment for internationalized registration data, and that the tools tested are not providing a high level of transformation accuracy and consistency of internationalized registration data."

Do we need a better analysis of purposes and accuracy? Does one exist?

Incidentally, see https://community.icann.org/display/tatcipdp/7+Studies+and+Background+Documents
for links to the reports mentioned above.

Regards,

Chris.
--
Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140811/1f10cfd5/attachment.html>

From c.dillon at ucl.ac.uk  Mon Aug 11 20:15:00 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Mon, 11 Aug 2014 20:15:00 +0000
Subject: FW: [gnso-contactinfo-pdp-wg] Themes for discussion
Message-ID: <D00EE2A6.1FA9F%ccaacdi@live.ucl.ac.uk>

Sorry! This time with attachment.]

Dear colleagues,

As promised during our last call, I am recirculating the latest version of the recommendations and the points identified so far for discussion, in preparation for Thursday's meeting. Please feel free to circulate any other themes you spot as you read the recommendations to this mailing list.

Regards,

Chris.

From: <Dillon>, Chris Dillon <c.dillon at ucl.ac.uk<mailto:c.dillon at ucl.ac.uk>>
Date: Wednesday, 30 July 2014 10:31
To: "gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>" <gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>>
Subject: [gnso-contactinfo-pdp-wg] Themes for discussion

Dear colleagues,

I would like to assemble here some themes for discussion during tomorrow's call, apart from the purposes/accuracy one that has already come up (see my earlier email below).

Here are some other themes I am aware of:

?         Should we recommend that there should be an option for registrants voluntarily to input transformed contact information?

?         Should we recommend that something be done with legacy transformed contact information (i.e. contact information input using a different policy from what we are recommending)?

?         It seems likely that our recommendations for those cases when transformation occurs will not be binding. That would mean, for example, that C5 on when the policy comes into effect would need to be redrafted.

?         What should happen to transformed contact information created by other stakeholders? O2 may need redrafting.

Please send any additional themes for discussion to this mailing list. I've attached the recommendations for your convenience.

Regards,

Chris.

From: owner-gnso-contactinfo-pdp-wg at icann.org<mailto:owner-gnso-contactinfo-pdp-wg at icann.org> [mailto:owner-gnso-contactinfo-pdp-wg at icann.org] On Behalf Of Dillon, Chris
Sent: 25 July 2014 11:00
To: gnso-contactinfo-pdp-wg at icann.org<mailto:gnso-contactinfo-pdp-wg at icann.org>
Subject: [gnso-contactinfo-pdp-wg] Purpose and accuracy

Dear colleagues,

Ideally we need to add something about the purposes of contact information that require accuracy and those that don't.

The Final report from the EWG on gTLD Directory Services has a good list of purposes from p.19-34.

The Study to evaluate solutions for the submission and display of internationalized contact data has a useful section on Information accuracy for effective use on p.9 with three levels of accuracy suggested:
1. Requiring accurate transformation (e.g. valid in a court of law, matching information in a passport, matching information in legal incorporation etc.)
2. Requiring consistent transformation (allowing use of such information to match other information provided in another context, e.g. to match address information to a registrant on a Google map, etc.)
3. Requiring ad hoc transformation (allowing informal or casual version of the information in another language to provide more general accessibility)

The last sentence of the study is of particular interest to us from the accuracy point of view and also from its summary of the state of the transformation tools etc.:
"The study has found that provisioning and querying protocols are lacking either support or deployment for internationalized registration data, and that the tools tested are not providing a high level of transformation accuracy and consistency of internationalized registration data."

Do we need a better analysis of purposes and accuracy? Does one exist?

Incidentally, see https://community.icann.org/display/tatcipdp/7+Studies+and+Background+Documents
for links to the reports mentioned above.

Regards,

Chris.
--
Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140811/e8cf2bb7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Straw man v6.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 33940 bytes
Desc: Straw man v6.docx
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140811/e8cf2bb7/Strawmanv6.docx>

From nathalie.peregrine at icann.org  Thu Aug 14 15:13:13 2014
From: nathalie.peregrine at icann.org (Nathalie Peregrine)
Date: Thu, 14 Aug 2014 15:13:13 +0000
Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG
  meeting - 14 August 2014
Message-ID: <541a1cc8e8f74deb90ab742408a1c978@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>

Dear All,


Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 14 August at 1300 UTC at:
http://audio.icann.org/gnso/gnso-transliteration-contact-20140814-en.mp3

 

On page: 

http://gnso.icann.org/en/group-activities/calendar#aug

The recordings and transcriptions of the calls are posted on the GNSO

Master Calendar page:

 <http://gnso.icann.org/calendar/> http://gnso.icann.org/calendar/

 

Attendees:

Emily Taylor - RrSG

Chris Dillon ? NCSG

Amr Elsadr ? NCUC

Rudi Vansnick ? NPOC

Jennifer Chung - RySG

Jim Galvin ? SSAC

Ubolthip Sethakaset ? Individual

Wolf-Ulrich Knoben ? ISPCP

Wanawit Ahkuputra ? GAC

Mae Suchayapim Siriwat ? GAC

Patrick Lenihan - NCUC

 

Apologies: 
Petter Rindforth ? IPC

Iliya Bazlyankov ? RrSG

 

ICANN staff:

Julie Hedlund 

Mary Wong

Amy Bivins

Nathalie Peregrine

 

** Please let me know if your name has been left off the list **

 

 Wiki page:  <http://tinyurl.com/mpwxstx> http://tinyurl.com/mpwxstx 

 

Thank you.

Kind regards,

 

Nathalie 

GNSO Secretariat 

 

Adobe Chat Transcript for Thursday 14 August 2014:

   Nathalie  Peregrine:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 14th August 2014

  Rudi Vansnick:hi everyone

  Emily Taylor:Hi everyone

  Chris Dillon:Hello all!

  Rudi Vansnick:just back from holidays 

  Rudi Vansnick:very limited internet access during 2 weeks is painful ... 

  Amr Elsadr:Hi all. Apologies about the prolonged absence. Hope you're all well.

  Nathalie  Peregrine:Welcome back Rudi and Amr!

  Jennifer Chung:Hello everyone!

 Emily Taylor:This is my first call participating in the working group.  I come from Registrar SG

  Chris Dillon:Welcome!

  Rudi Vansnick:welcome Emily 

  Emily Taylor:Thank you.  And thanks for the draft papers, Chris

  Julie Hedlund:I am in the process of getting on the call.  Called in but got dropped.

  Julie Hedlund:Back on

  Jennifer Chung:I have updated my SOI - to include my wgs and picture

  Jennifer Chung:sorry couldn't connect audio just now

  Rudi Vansnick:thanks Jennifer

  Julie Hedlund:The document is unsynced.

  Nathalie  Peregrine:Patrick Lenihan has joined the AC room

  Amr Elsadr:Can the document be shared in the AC Room?

  Emily Taylor:Sorry - acronym check - what's IRD?

  Amr Elsadr:Internationalized Registration Data.

  Emily Taylor::)  Thanks

  Amr Elsadr:;-)

  Julie Hedlund:Pardon me -- which document is being referenced?  I did not catch it.

  Amr Elsadr:@Jim: Is your concern about this WG recommending that IRD be provided as an option for registrants?

  Emily Taylor:I can hear you! but I'm not able to be heard.  Sorry

  Emily Taylor:Agree with Jim Galvin

  Nathalie  Peregrine:Emily, we can dial out to you if you provide me with a contact number

  Emily Taylor:on the costs and unintended consequences of two tracks of data, not knowing which is authoritative, and the legacy issue.

  Emily Taylor:I see Amr's question - I don't see IRD as being the optional bit, but a translation/transliteration as being optional

  Emily Taylor:Thanks for clarification Chris.  

  Emily Taylor:I also got some feedback from our technical people, who were also questioning the value of having transliteration, and the difficulties/costs for registrars to have to validate such data

  Amr Elsadr:@Emily: I believe those concerns are reflected in the proposed recommendations.

  Emily Taylor:I think they are too :)

  Emily Taylor:Thanks for that, Chris. Very useful.  One other thing (that may already be incorporated in your thinking), is that even to have an option to transliterate/translate will mean creation of new database fields, and potentially lengthening and complicating the process of registration

  Amr Elsadr:Ah. Thanks Chris.

  Emily Taylor:Thanks Chris

  Emily Taylor:LOL

  Amr Elsadr:Isn't legacy transformed contact information presumably already validated?

  Amr Elsadr::)

  Emily Taylor:Ok back to typing

  Emily Taylor:Everything you say is very sensible, Chris.  My concern is that even setting flags to indicate that data is legacy or not will introduce costs for registrars potentially

  Emily Taylor:Is this something that has already been discussed?

  Emily Taylor:Thanks.  LIke others, I just got back from holiday, and would like to share with other members of the RrSG who manage large databases

  Emily Taylor:to get their views

  Amr Elsadr:I (with my limited knowledge) agree with Emily. I'm also not exactly sure what purpose it would serve.

  Emily Taylor:Thanks Jim.  Appreciate the clarification

  Rudi Vansnick:it looks like it is important to have clear view on the data model requests and the need for futher investigation on this topic

  Emily Taylor:Agree 

  Amr Elsadr:OK. Thanks. :)

  Amr Elsadr:I'm wondering if there is a sense about the level of consensus amongst the WG on the proposed recommendations?

  Rudi Vansnick:very good question Jim ... 

  Julie Hedlund:Apologies, but I have to leave to join another call.

  Rudi Vansnick:requires a lot of thinking ... 

  Julie Hedlund:Thanks everyone!

  Rudi Vansnick:thanks Julie 

  Emily Taylor:To borrow from the Dispute Resolution world, it could also be language of the Registrar agreement :)

  Jim Galvin:I have to leave for another call.  See you next week.

  Rudi Vansnick:thanks to you Chris for the great work 

  Emily Taylor:Thank you for your comments and chairing, Chris.  Very useful call

  Amr Elsadr:Thanks Chris and all. Bye.

  Jennifer Chung:Thank you Chris and everyone.

  Mary Wong:Thanks for attending and participating, everyone.

  Chris Dillon:Thank you very much indeed!

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140814/595c4191/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5457 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140814/595c4191/smime.p7s>

From c.dillon at ucl.ac.uk  Fri Aug 15 08:37:17 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Fri, 15 Aug 2014 08:37:17 +0000
Subject: [gnso-contactinfo-pdp-wg] RE: MP3 Translation and Transliteration of Contact Information PDP WG
  meeting - 14 August 2014
In-Reply-To: <541a1cc8e8f74deb90ab742408a1c978@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
References: <541a1cc8e8f74deb90ab742408a1c978@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
Message-ID: <c94fc81f62f14d65a03663a28deb0d41@DB4PR01MB0461.eurprd01.prod.exchangelabs.com>

Dear colleagues,

Thank you for yesterday?s discussion.

Some of the themes still requiring attention are:

1.    Is it within the remit of this group to consider the purpose of data? Purpose is certainly covered in detail in the ?Final report from the EWG on gTLD Directory Services?. I fear we cannot ignore purpose, as there is a close link to need for accuracy (which again is linked to how any transformation is done). As I mentioned during the call, asking the question ?Which purposes may be adequately fulfilled with inaccurate data?? may be a useful approach.

2.    During the call I wasn?t sure what to do with registrants applying for domain names in languages not typically supported in a country ? for example, a Russian applying to a Chinese registrar for a Russian Cyrillic domain name. Presumably registrars would do a business analysis; in this case Chinese registrars would decide whether to sell Russian Cyrillic domain names. If the guidelines in the straw man are followed, the Russian would be inputting data in Russian Cyrillic.

3.    For those stakeholders who do decide to transform, how binding are our recommendations?

4.    The draft was written, presuming that allowing registrants optionally to transform data could be an easy way of building up transformed data in the database. However, such optional transformation raises data quality, matching and versioning problems. Do we actually want actively to discourage transformation and have a simpler database with data only in original language and script?

This is certainly not an exhaustive list. Please feel free to suggest other issues (and also ones we didn?t touch at all yesterday). Text addressing these and other issues is very welcome.

Please note that there have been problems with email forwarding at UCL since yesterday, so I have put my underlying email address (ccaacdi at live.ucl.ac.uk) in the Cc field of this email to avoid delays.

Regards,

Chris.
--
Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

From: owner-gnso-contactinfo-pdp-wg at icann.org [mailto:owner-gnso-contactinfo-pdp-wg at icann.org] On Behalf Of Nathalie Peregrine
Sent: 14 August 2014 16:13
To: gnso-contactinfo-pdp-wg at icann.org
Cc: gnso-secs at icann.org
Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG meeting - 14 August 2014

Dear All,

Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 14 August at 1300 UTC at:
http://audio.icann.org/gnso/gnso-transliteration-contact-20140814-en.mp3


On page:
http://gnso.icann.org/en/group-activities/calendar#aug
The recordings and transcriptions of the calls are posted on the GNSO
Master Calendar page:
http://gnso.icann.org/calendar/

Attendees:
Emily Taylor - RrSG
Chris Dillon ? NCSG
Amr Elsadr ? NCUC
Rudi Vansnick ? NPOC
Jennifer Chung - RySG
Jim Galvin ? SSAC
Ubolthip Sethakaset ? Individual
Wolf-Ulrich Knoben ? ISPCP
Wanawit Ahkuputra ? GAC
Mae Suchayapim Siriwat ? GAC
Patrick Lenihan - NCUC

Apologies:
Petter Rindforth ? IPC
Iliya Bazlyankov ? RrSG

ICANN staff:
Julie Hedlund
Mary Wong
Amy Bivins
Nathalie Peregrine

** Please let me know if your name has been left off the list **

 Wiki page: http://tinyurl.com/mpwxstx

Thank you.
Kind regards,

Nathalie
GNSO Secretariat

Adobe Chat Transcript for Thursday 14 August 2014:

   Nathalie  Peregrine:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 14th August 2014

  Rudi Vansnick:hi everyone

  Emily Taylor:Hi everyone

  Chris Dillon:Hello all!

  Rudi Vansnick:just back from holidays

  Rudi Vansnick:very limited internet access during 2 weeks is painful ...

  Amr Elsadr:Hi all. Apologies about the prolonged absence. Hope you're all well.

  Nathalie  Peregrine:Welcome back Rudi and Amr!

  Jennifer Chung:Hello everyone!

 Emily Taylor:This is my first call participating in the working group.  I come from Registrar SG

  Chris Dillon:Welcome!

  Rudi Vansnick:welcome Emily

  Emily Taylor:Thank you.  And thanks for the draft papers, Chris

  Julie Hedlund:I am in the process of getting on the call.  Called in but got dropped.

  Julie Hedlund:Back on

  Jennifer Chung:I have updated my SOI - to include my wgs and picture

  Jennifer Chung:sorry couldn't connect audio just now

  Rudi Vansnick:thanks Jennifer

  Julie Hedlund:The document is unsynced.

  Nathalie  Peregrine:Patrick Lenihan has joined the AC room

  Amr Elsadr:Can the document be shared in the AC Room?

  Emily Taylor:Sorry - acronym check - what's IRD?

  Amr Elsadr:Internationalized Registration Data.

  Emily Taylor::)  Thanks

  Amr Elsadr:;-)

  Julie Hedlund:Pardon me -- which document is being referenced?  I did not catch it.

  Amr Elsadr:@Jim: Is your concern about this WG recommending that IRD be provided as an option for registrants?

  Emily Taylor:I can hear you! but I'm not able to be heard.  Sorry

  Emily Taylor:Agree with Jim Galvin

  Nathalie  Peregrine:Emily, we can dial out to you if you provide me with a contact number

  Emily Taylor:on the costs and unintended consequences of two tracks of data, not knowing which is authoritative, and the legacy issue.

  Emily Taylor:I see Amr's question - I don't see IRD as being the optional bit, but a translation/transliteration as being optional

  Emily Taylor:Thanks for clarification Chris.

  Emily Taylor:I also got some feedback from our technical people, who were also questioning the value of having transliteration, and the difficulties/costs for registrars to have to validate such data

  Amr Elsadr:@Emily: I believe those concerns are reflected in the proposed recommendations.

  Emily Taylor:I think they are too :)

  Emily Taylor:Thanks for that, Chris. Very useful.  One other thing (that may already be incorporated in your thinking), is that even to have an option to transliterate/translate will mean creation of new database fields, and potentially lengthening and complicating the process of registration

  Amr Elsadr:Ah. Thanks Chris.

  Emily Taylor:Thanks Chris

  Emily Taylor:LOL

  Amr Elsadr:Isn't legacy transformed contact information presumably already validated?

  Amr Elsadr::)

  Emily Taylor:Ok back to typing

  Emily Taylor:Everything you say is very sensible, Chris.  My concern is that even setting flags to indicate that data is legacy or not will introduce costs for registrars potentially

  Emily Taylor:Is this something that has already been discussed?

  Emily Taylor:Thanks.  LIke others, I just got back from holiday, and would like to share with other members of the RrSG who manage large databases

  Emily Taylor:to get their views

  Amr Elsadr:I (with my limited knowledge) agree with Emily. I'm also not exactly sure what purpose it would serve.

  Emily Taylor:Thanks Jim.  Appreciate the clarification

  Rudi Vansnick:it looks like it is important to have clear view on the data model requests and the need for futher investigation on this topic

  Emily Taylor:Agree

  Amr Elsadr:OK. Thanks. :)

  Amr Elsadr:I'm wondering if there is a sense about the level of consensus amongst the WG on the proposed recommendations?

  Rudi Vansnick:very good question Jim ...

  Julie Hedlund:Apologies, but I have to leave to join another call.

  Rudi Vansnick:requires a lot of thinking ...

  Julie Hedlund:Thanks everyone!

  Rudi Vansnick:thanks Julie

  Emily Taylor:To borrow from the Dispute Resolution world, it could also be language of the Registrar agreement :)

  Jim Galvin:I have to leave for another call.  See you next week.

  Rudi Vansnick:thanks to you Chris for the great work

  Emily Taylor:Thank you for your comments and chairing, Chris.  Very useful call

  Amr Elsadr:Thanks Chris and all. Bye.

  Jennifer Chung:Thank you Chris and everyone.

  Mary Wong:Thanks for attending and participating, everyone.

  Chris Dillon:Thank you very much indeed!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140815/ccad3b66/attachment.html>

From c.dillon at ucl.ac.uk  Thu Aug 21 08:22:11 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Thu, 21 Aug 2014 08:22:11 +0000
Subject: [gnso-contactinfo-pdp-wg] Preparation for today's call
Message-ID: <6bc2fbcf2f6841c2a61cf0630e6758a7@DB4PR01MB0461.eurprd01.prod.exchangelabs.com>

Dear colleagues,

I'd like herewith to circulate ver.6 of the straw man and a list of the remaining major themes of which I'm aware, so that it is handy for today's call.

Going through the document, the only other major theme I spotted was legacy data (which we did discuss last week). This certainly doesn't mean that there are no more major themes, just that I have looked at this document so many times I am no longer seeing them. You are more than welcome to bring them up before or during the call.

Incidentally, UCL's email system has now recovered from last week's forwarding problems.

Regards,

Chris.

==

...
Some of the themes still requiring attention are:

1.    Is it within the remit of this group to consider the purpose of data? Purpose is certainly covered in detail in the 'Final report from the EWG on gTLD Directory Services'. I fear we cannot ignore purpose, as there is a close link to need for accuracy (which again is linked to how any transformation is done). As I mentioned during the call, asking the question "Which purposes may be adequately fulfilled with inaccurate data?" may be a useful approach.

2.    During the call I wasn't sure what to do with registrants applying for domain names in languages not typically supported in a country - for example, a Russian applying to a Chinese registrar for a Russian Cyrillic domain name. Presumably registrars would do a business analysis; in this case Chinese registrars would decide whether to sell Russian Cyrillic domain names. If the guidelines in the straw man are followed, the Russian would be inputting data in Russian Cyrillic.

3.    For those stakeholders who do decide to transform, how binding are our recommendations?

4.    The draft was written, presuming that allowing registrants optionally to transform data could be an easy way of building up transformed data in the database. However, such optional transformation raises data quality, matching and versioning problems. Do we actually want actively to discourage transformation and have a simpler database with data only in original language and script?
...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140821/e8e24e25/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Straw man v6.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 33940 bytes
Desc: Straw man v6.docx
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140821/e8e24e25/Strawmanv6.docx>

From terri.agnew at icann.org  Thu Aug 21 21:05:32 2014
From: terri.agnew at icann.org (Terri Agnew)
Date: Thu, 21 Aug 2014 21:05:32 +0000
Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG
  meeting - 21 August 2014
Message-ID: <0b9fe6ac40f44df282daa3fc59369127@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>

Dear All,


Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 21 August at 1300 UTC at:
 <http://audio.icann.org/gnso/gnso-transliteration-contact-20140821-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140821-en.mp3

 

On page: 

 <http://gnso.icann.org/en/group-activities/calendar#aug> http://gnso.icann.org/en/group-activities/calendar#aug

The recordings and transcriptions of the calls are posted on the GNSO

Master Calendar page:

 <http://gnso.icann.org/calendar/> http://gnso.icann.org/calendar/

 

Attendees:

Chris Dillon ? NCSG

Amr Elsadr ? NCUC

Rudi Vansnick ? NPOC

Jennifer Chung - RySG

Jim Galvin ? SSAC

Ubolthip Sethakaset ? Individual

Wolf-Ulrich Knoben ? ISPCP

Wanawit Ahkuputra ? GAC

Mae Suchayapim Siriwat ? GAC

Iliya Bazlyankov ? RrSG

Peter Dernbach- IPC

Wen Zhai- NTAG

Pitinan Kooarmornpatana-GAC

Howard Li- SOI

 

Apologies: 
Petter Rindforth ? IPC

Emily Taylor - RrSG

 

 

ICANN staff:

Julie Hedlund 

Mary Wong

Amy Bivins

Terri Agnew

 

** Please let me know if your name has been left off the list **

 

 Wiki page:  <http://tinyurl.com/mpwxstx> http://tinyurl.com/mpwxstx 

 

Thank you.

Kind regards,

 

Terri Agnew

GNSO Secretariat 

 

Adobe Chat Transcript for Thursday 21 August 2014:

    Terri Agnew:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 21 August 2014

  Rudi Vansnick:sorry being late ... 

  Rudi Vansnick:just got back from hospital visit, mother had cerebral infarction more than a week ago 

  Chris Dillon:Sorry to hear that.

  Pitinan Kooarmornpatana:sorry to hear that rudi

  Terri Agnew:Welcome Iliya Bazlyankov

  Iliya Bazlyankov:Hello, sorry for delay.

  Terri Agnew:Welcome Ubolthip Sethakaset

  ubolthip sethakaset:Hello all sorry for delay

  Julie Hedlund:@Chris: I have unsynced the document.  I'll switch the documents as noted.

  Amr Elsadr:Hi all. Dialling in now.

  Terri Agnew:Rudi, I hope she is on the road to recovery

  Terri Agnew:Welcome Amr Elsadr

  Rudi Vansnick:actually she is stable but seen her age (82) it will be a difficult process

  Amr Elsadr:Rudi..., sorry to hear about your Mom.

  Wanawit Ahkuputra:Rudi, hope your mom will be okay and recovery soon

  Amr Elsadr:Thnx Terri.

  Jim Galvin:When it says "languages not typically supported in a country" don't we mean "languages not typically support by the country of the registrar"?

  Jim Galvin:it's really about the registrar not the country, right?

  Amr Elsadr:I agree on allowing flexibility for the business models of registrars to decide what languages they would like to support.

  Amr Elsadr:@Jim: +1. I believe it is about the registrar, not the country.

  Amr Elsadr:I am guessing that registrars are well equipped to understand how to operate and maintain ability to serve their desired consumers while maintaining contractual compliance. If they fail to meet market requirements, then that gap may be filled by other or new registrars that pop up.

  Rudi Vansnick:is helpful anyway

  Amr Elsadr:What would stop a Russian registrar from hiring (or outsourcing tasks to) Chinese speakers or contractors? It's a matter of demand and supply between registrars and registrants, isn't it?

  Rudi Vansnick:to make it a bit more complex ... same case except the registrant does not live in china but in russia !

  Rudi Vansnick:address = russian address 

  Jim Galvin:@rudi - that's a business choice for the registrar.

  Jim Galvin:@ rudi - the registrar either supports cyrillic or not, as a choice.

  Amr Elsadr:I'm not sure this puzzle is really within the scope of this PDP. Do we need to tackle it?

  Rudi Vansnick:as we consider the basics being the ability to deliver a physical letter to the address of the registrant, we need to have the address in the native language of the country ?

  Mary Wong:Good point about scope, @Amr; but as a general high-level issue, this WG's recs should not (ideally) make it more difficult for Registrars to validate or verify (as required by the RAA).

  Amr Elsadr:@Mary: Of course, which is one of the reasons why I think it might be best for registrars to manage these sort of registrations (in the absence of a policy).

  Peter Dernbach:@Amr: I didn't read the Charter's reference to "a single common language" to necessarily mean English

  Peter Dernbach:or a "single common script" to necessarily mean ASCII, though that has been the standard to date.

  Amr Elsadr:@Peter: Not English, but a Latin-based script, yes?

  Amr Elsadr:Wasn't ASCII specified in the charter?

  Peter Dernbach:I don't think it was specified as the single common script, but there was a reference here:

  Peter Dernbach:With  respect  to  the  first  issue  above,  it  should  be  noted  that  text  requests  and  content  returned  by  Domain  Name  Registration  Data  Services  (such  as  WHOIS)  are  historically  encoded  using  US-??American  Standard  Code  for  Information  Interchange  (ASCII).  This  is  a  character-??encoding  scheme  originally  based  on  the  English  alphabet.    While  the  WHOIS  protocol  does  not  specify  US-??ASCII  as  the  exclusive  character  set  for  text  requests  and  textcontent  encoding,  thecurrent  situation  is  that  no  standards  or  conventions  exist  for  all  WHOIS  protocol  implementations  to  signal  support  of  characters other than US-ASCII

  Amr Elsadr:@Peter: Looking at the charter again, I think you are right, and I am mistaken. It was cited as the example for common practice but not as a required output of this PDP.

  Mary Wong:@Peter, @Amr - the WG Charter doesn't limit the "single common" language or script.

  Mary Wong:@Amr, yes, that's right.

  Peter Dernbach:I agree with your point about scope Amr.

  Peter Dernbach:I think that the registrars are able to choose what languages they support.

  Peter Dernbach:that is separate from the issue we are to address, regarding whether it is desirable that the contact information is translated or transliterated into a single common language or single common script. 

  Jennifer Chung:@ Peter +1

  Amr Elsadr:@Peter: Agree on seperation of issues.

  Jim Galvin:@peter +1

  Mary Wong:@Chris, by "binding" do you mean on Registrars? If so, that means Consensus Policy, right?

  Iliya Bazlyankov:@Peter +1

  Amr Elsadr:Not mandatory doesn't mean that it isn't optional.

  Jim Galvin:@chris - are you suggesting that "if you transform do it this way" scenario?

  Mary Wong:@Jim, by "you" does that refer to Registrars who decide for biz reasons they will offer the service/option?

  Jim Galvin:@amr +1 to your comment

  Jim Galvin:@mary "you" means whoever choose to do the transformation

  Mary Wong:OK thx - I keep coming back to Registrars b/c it won't be possible to "bind" a registrant legally unless it's specified that all registration agreements MUST have such and such a provision.

  Mary Wong:Whereas for Registrars there is the RAA.

  Amr Elsadr:@Chris: Again..., I don't see it as being of too much consequence as long as there is an authoritative and validated set of contact data meeting RAA requirements.

  Amr Elsadr:@Jim: +1 on your bias. :)

  Jennifer Chung:@Jim and Amr, that logic makes sense to me as well 

  Amr Elsadr:I've been having trouble having my bank in Egypt (which uses English) to send me mail to my Norwegian address, because of some characters in my mailing address. I would be grateful to be spared that difficulty when registering domain names.

  Amr Elsadr::)

  Mary Wong:@Amr, would that be a "validation" rather than "verification" problem? :)

  Amr Elsadr::)

  Peter Dernbach:Thanks all.

  Julie Hedlund:Thank you everyone -- great call!

  Jennifer Chung:Thank you Chris, thanks everyone.

  Jim Galvin:thanks bye

  Amr Elsadr:Thanks. Bye.

  Wanawit Ahkuputra:THank you, bye

  Rudi Vansnick:thanks and till next week

  Pitinan Kooarmornpatana:thanks

  Wen:Thanks to all. Bye.

  Howard Li:thank

  Chris Dillon:Thank you all!

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140821/f55119a1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5417 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140821/f55119a1/smime.p7s>

From c.dillon at ucl.ac.uk  Tue Aug 26 10:14:07 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Tue, 26 Aug 2014 10:14:07 +0000
Subject: [gnso-contactinfo-pdp-wg] Preparations for Thursday's meeting
Message-ID: <45aab5c730684cd2accef0a54a8a8513@DB4PR01MB0461.eurprd01.prod.exchangelabs.com>

Dear colleagues,

Some things to think about before Thursday's meeting:

*         Should we recommend registrants voluntarily to transform contact information? Version 7 of the straw man will probably make no recommendation on this, so speak now if you disagree. There will almost certainly be no recommendations on transformation to languages other than English (which in fact means "Roman script with the exceptions of 1. cases where is an English translated form of the organization and 2. of the country which is always English").

*         Are there any purposes for which inaccurate contact information is sufficient? There don't seem to be. Again, speak now if you disagree.


As I mentioned last week, I believe the remaining alterations to version 6 are small, but they may reveal larger issues, and that's fine. Sometime before the meeting I will circulate a version ("6a") with the small changes highlighted and this email (and any substantial additions) at the end for convenience.

As usual, please feel free to send text to the list on any issue.

Regards,

Chris.
--
Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140826/73185a54/attachment.html>

From c.dillon at ucl.ac.uk  Wed Aug 27 17:11:53 2014
From: c.dillon at ucl.ac.uk (Dillon, Chris)
Date: Wed, 27 Aug 2014 17:11:53 +0000
Subject: [gnso-contactinfo-pdp-wg] Version 7
Message-ID: <D023CFE7.21E7B%ccaacdi@live.ucl.ac.uk>

Dear colleagues,

When I came this morning to add the minor updates to version 6 I discovered there weren't enough to justify a meeting, as our work during the last two meetings had cleared up over half of them.

I shall get version 7 to you as early next week as possible. You are most welcome at this stage to send aides memoires to the list, for example, if you had the impression during a call that I wasn't completely understanding a point.

Regards,

Chris.
--
Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140827/102d418e/attachment.html>

From nathalie.peregrine at icann.org  Thu Aug 28 22:49:24 2014
From: nathalie.peregrine at icann.org (Nathalie Peregrine)
Date: Thu, 28 Aug 2014 22:49:24 +0000
Subject: [gnso-contactinfo-pdp-wg] PLEASE RSVP  Monthly GNSO WG Newcomer Open House Session
In-Reply-To: <5832a2df9ae24d7289db5eb7facb472e@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
References: <BDBCC21442A22640A4ECE2C75A8E215AC5EA2FF74B@EXVPMBX100-1.exc.icann.org>
 <5832a2df9ae24d7289db5eb7facb472e@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
Message-ID: <501d57d9cb96490793416b30667ffe79@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>


Reminder: Monthly GNSO WG Newcomer Open House Session


These ongoing monthly sessions are for new GNSO WG participants to come
together and discuss any questions they may have about GNSO Working Groups,
procedures and/or processes. We know there is a lot of information to digest
when you join a GNSO Working Group and these monthly meetings are an
opportunity for newcomers and more experienced participants to meet in an
informal setting without the pressure of "real work" that needs be done.

The agenda is flexible.  The presenters will be ready with a standard set of
materials if people would like to discuss them.  Feel free to submit
questions, either in advance or at the beginning of the meeting, if there is
a topic that you would like to explore in more depth .  Providing useful
answers to a wide range of questions is part of the reason why these
meetings are 


Thursday 4 September at 20.00 UTC
Thursday 2 October at 12.00 UTC
Thursday 6 November at 20.00 UTC
Thursday 4 December at 12.00 UTC

To convert to your local time zone, please see
http://www.timeanddate.com/worldclock/converter.html

If you are interested to join the next meeting on 4 September or any of the
future meetings, please let the GNSO Secretariat know (
<mailto:gnso-secs at icann.org> gnso-secs at icann.org) and we will send you the
call details. If there are any specific questions you already have, or any
overviews or introductions you think would be helpful (e.g. GNSO Policy
Development Process or GNSO Working Group guidelines), please let us know in
advance and we will prepare materials accordingly. Feel free to share this
invitation with others that you think may be interested.

We look forward to welcoming you at the next meeting!

Nathalie Peregrine 

GNSO Secretariat

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140828/57325690/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5457 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140828/57325690/smime.p7s>