UA Issue Logging Report
The latest version of this report has been published https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... <https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat...> (and attached) Background: Since just after the ICANN meeting in India last year, we have operated, through ICANN’s Global Support team, a facility where people can log a non-UA compliant experience and we then record it and reach out to the relevant website to raise awareness. There has been some progress, including a significant regional airline in the United States that has worked to make their systems more UA Ready. Thanks again to the ICANN teams- the Global Support Centre for recording the issues and pursuing resolution and the GDD Comms group for preparing the report presentation. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander
404 On 10/11/2017 12:57 AM, Don Hollander wrote:
The latest version of this report has been published https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... (and attached)
Background: Since just after the ICANN meeting in India last year, we have operated, through ICANN’s Global Support team, a facility where people can log a non-UA compliant experience and we then record it and reach out to the relevant website to raise awareness.
There has been some progress, including a significant regional airline in the United States that has worked to make their systems more UA Ready.
Thanks again to the ICANN teams- the Global Support Centre for recording the issues and pursuing resolution and the GDD Comms group for preparing the report presentation.
Don
Don Hollander Universal Acceptance Steering Group Skype: don_hollander
I am having trouble understanding the graphic, sorry. * Inbound Cases are complaints, received by UASG people or UASG.tech logging service. * Outbound Cases are escalations, from UASG to the organization called out in an inbound case. * There were 96 escalations, distributed over 46 organizations. * Since 9+17+20 = 46, I assume that an org falls totally into one bucket or another (i.e. doesn’t fix one bug yet ignore another). Did I get that correct? In the case of Return & Forwarded, does that indicate that the site acknowledged our escalation, but actually didn’t fix anything yet? What are “radar”, “radarview” and “radar-admin”? Sorry if these were explained before or elsewhere. PS: Typo on Website #6 “cosed” From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, October 11, 2017 12:57 AM To: Universal Acceptance <ua-discuss@icann.org> Subject: [UA-discuss] UA Issue Logging Report The latest version of this report has been published https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... (and attached) Background: Since just after the ICANN meeting in India last year, we have operated, through ICANN’s Global Support team, a facility where people can log a non-UA compliant experience and we then record it and reach out to the relevant website to raise awareness. There has been some progress, including a significant regional airline in the United States that has worked to make their systems more UA Ready. Thanks again to the ICANN teams- the Global Support Centre for recording the issues and pursuing resolution and the GDD Comms group for preparing the report presentation. Don
On 10/12/2017 5:13 PM, Mark Svancarek via UA-discuss wrote:
I am having trouble understanding the graphic, sorry.
I continue to get a 404 on this link: https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat...
* Inbound Cases are complaints, received by UASG people or UASG.tech logging service. * Outbound Cases are escalations, from UASG to the organization called out in an inbound case. * There were 96 escalations, distributed over 46 organizations. * Since 9+17+20 = 46, I assume that an org falls totally into one bucket or another (i.e. doesn’t fix one bug yet ignore another).
Did I get that correct?
In the case of Return & Forwarded, does that indicate that the site acknowledged our escalation, but actually didn’t fix anything yet?
What are “radar”, “radarview” and “radar-admin”? Sorry if these were explained before or elsewhere.
PS:
Typo on Website #6 “cosed”
*From:* ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] *On Behalf Of *Don Hollander *Sent:* Wednesday, October 11, 2017 12:57 AM *To:* Universal Acceptance <ua-discuss@icann.org> *Subject:* [UA-discuss] UA Issue Logging Report
The latest version of this report has been published https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... (and attached)
Background: Since just after the ICANN meeting in India last year, we have operated, through ICANN’s Global Support team, a facility where people can log a non-UA compliant experience and we then record it and reach out to the relevant website to raise awareness.
There has been some progress, including a significant regional airline in the United States that has worked to make their systems more UA Ready.
Thanks again to the ICANN teams- the Global Support Centre for recording the issues and pursuing resolution and the GDD Comms group for preparing the report presentation.
Don
Fwiw, the link gives me a 404 as well. Using the hard to find search on the site (only comes up with the 404 apparently) doesn’t return the doc either. tex From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Asmus Freytag Sent: Thursday, October 12, 2017 7:37 PM To: ua-discuss@icann.org Subject: Re: [UA-discuss] UA Issue Logging Report On 10/12/2017 5:13 PM, Mark Svancarek via UA-discuss wrote: I am having trouble understanding the graphic, sorry. I continue to get a 404 on this link: https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... * Inbound Cases are complaints, received by UASG people or UASG.tech logging service. * Outbound Cases are escalations, from UASG to the organization called out in an inbound case. * There were 96 escalations, distributed over 46 organizations. * Since 9+17+20 = 46, I assume that an org falls totally into one bucket or another (i.e. doesn’t fix one bug yet ignore another). Did I get that correct? In the case of Return & Forwarded, does that indicate that the site acknowledged our escalation, but actually didn’t fix anything yet? What are “radar”, “radarview” and “radar-admin”? Sorry if these were explained before or elsewhere. PS: Typo on Website #6 “cosed” From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, October 11, 2017 12:57 AM To: Universal Acceptance <mailto:ua-discuss@icann.org> <ua-discuss@icann.org> Subject: [UA-discuss] UA Issue Logging Report The latest version of this report has been published https://uasg.tech/wp-content/uploads/2017/06/UASG_Issue-logging_report_Updat... (and attached) Background: Since just after the ICANN meeting in India last year, we have operated, through ICANN’s Global Support team, a facility where people can log a non-UA compliant experience and we then record it and reach out to the relevant website to raise awareness. There has been some progress, including a significant regional airline in the United States that has worked to make their systems more UA Ready. Thanks again to the ICANN teams- the Global Support Centre for recording the issues and pursuing resolution and the GDD Comms group for preparing the report presentation. Don
participants (4)
-
Asmus Freytag -
Don Hollander -
Mark Svancarek -
Tex Texin