Many geoname TLDs delegated in the last round were in fact community applications (although I don't know if any went through the CPE since that only happens if they are contested.

The question here is that IF you are applying for a geoname, and IF you are applying as a community TLD, then should you get extra points under the CPE because it is a geoname (that is, it improves your chances of satisfying the CPE and thus winning over some other applicant.

I am not sure we have a strong case for getting this approved, nor am I sure it is even worth the effort to try, but I see it as a good thing if we could.

Alan

At 2020-07-08 11:50 AM, Tijani BEN JEMAA wrote:

Dear Jonathan and all,

Following up on our discussion today during the CPWG call about the geo-names, I would like to explain why I donâ€™t think that geo-names should be incorporated into the CPWG evaluation.
In fact, the CPE role is to evaluate whether the application is a community application or not (this is what Alan explained and what I agreed on). So how it might be incorporated? as a criterion to decide if the application is a community application? Shall we request that if the application is for a geo-name string, the CPE should consider it as a community application?
The CPE evaluates if the applicant represents a community and if the application serves that community whatever the string applied for is (geo-name, language name, culture name, etc.).

Tijani

Le 8 juil. 2020 Ã 07:34, ICANN At-Large Staff <staff@atlarge.icann.org > a Ã©crit :

***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org with your preferred number***

Dear All,

The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 08 July 2020 at 13:00 UTC for 90 mins.

For other times: https://tinyurl.com/y9ghlcz3

The agenda and call details can be found at: https://community.icann.org/x/XYRIC

Zoom Room: https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 / Passcode: 2345cpwg**

Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net]

ADIGO Conference Bridge:
EN: 1638
ES: 1738
FR: 1838

Toll-free access number (US and Canada): 800 550 6865

Other toll-free numbers: https://www.adigo.com/icann [adigo.com]

At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB

If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org

Thank you.
Kind regards,

At-Large Staff

ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org [atlarge.icann.org]
Facebook: facebook.com/icann [facebook.com] atlarge [facebook.com]
Twitter: @ [twitter.com] ICANNAtLarge [twitter.com]

<At-Large Consolidated Policy Working Group (CPWG) Call[28].ics>_______________________________________________
CPWG mailing list
CPWG@icann.org
https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy) and the website Terms of Service ( https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

Tijani BEN JEMAA

_______________________________________________
CPWG mailing list
CPWG@icann.org
https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy) and the website Terms of Service ( https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.