W3C home > Mailing lists > Public > public-personalization-tf@w3.org > August 2020

Re: Personalization for ML Workshop on RQTF Wednesday

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Wed, 12 Aug 2020 10:36:36 +0300
To: "Janina Sajka" <janina@rednote.net>
Cc: "public-rqtf" <public-rqtf@w3.org>, "Personalization tf" <public-personalization-tf@w3.org>
Message-Id: <173e1979991.1079b90111023779.1143333658240489738@zoho.com>
i do not have access to the call information page

can someone send me the zoom link?

All the best

Lisa Seeman

http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa

---- On Tue, 04 Aug 2020 01:46:15 +0300 Janina Sajka <janina@rednote.net> wrote ----

Dear RQTF and Personalization Task Forces: 
The possibility that the Personalization TF specification about to enter 
CR could actually help machine learning deliver smarter results--whether 
or not the task is accessibility related--came up during our 
Personalization call Monday. 
I've invited Lisa Seeman to join RQTF Wednesday to discuss this briefly 
and I've cleared this with Jason. We will take up this topic at the 
beginning of our RQTF call Wednesday. Instructions for joining the RQTF 
call are in the forwarded agenda below. Other Personalization 
participants are also welcome. 
Lisa, can you please reply to All with a brief paragraph explaining the way 
this would work so RQTF folks can have a bit of a headstart ahead of our 
The relevant technology is described in the Explainer and Module 1 
specification documents linked on the Personalization Task Force Home 
Page here: 
Meanwhile, here's a somewhat helpful extract from the Personalization 
minutes at: 
JF: believe the other attributes in module 1 that are not symbols will 
be most used 
JS: but symbols have higher PR value - we need to take advantage of that 
JF: action, destination, purpose are beneficial in early days of AI 
JS: we have a slot in the W3C AI workshop - perhaps we should present 
LS: COGA has examples 
JS: Jutta will cover built in biases of AI/ML at the workshop 
... we also have issues with tools - making sure they are accessible 
... example: google earth to define the most accessible path from point 
a to b 
LS: John's point is that the attributes can be used for training 
... that is important 
JS: can contribute to RQTF proposal - suggests Lisa attend the meeting 
on Wednesday 
White, Jason J writes: 
> Meeting logistics: 
>   *   Wednesday 5 August 2020, 9:00am US eastern time (1300 UTC) 
>   *   Teleconference details: https://www.w3.org/2017/08/telecon-info_rqtf<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F08%2Ftelecon-info_rqtf&data=02%7C01%7Cjjwhite%40ets.org%7C96e1d912b97b43ebedfd08d8016f1173%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637260923837587515&sdata=mzjAkcI0zQvbTZS4PhnE%2FYeFZc%2FRqrEo%2BCQgnPqic18%3D&reserved=0>. 
> This meeting continues the conversations and associated work undertaken last week. The agenda are as follows. 
> 1.      Miscellaneous updates: TPAC 2020 arrangements, Accessibility of Remote Meetings, Web of Things consensus statement, or any other matters that have changed appreciably since last week’s teleconference. 
> 2.      Real-Time Communication Accessibility User Requirements (RAUR), open issues, as identified below. 
> The RAUR issues identified by Josh are as follows. We plan to resume at issue #43. 
> Capture of on record/off record captions in RTC 
> #102 opened on May 25 by RealJoshue108 
> https://github.com/w3c/apa/issues/102 
> In a video conference session in which sign language interpretation is 
> provided, both the signer and the speaker should be visible 
> #97 opened on Apr 8 by jasonjgw 
> https://github.com/w3c/apa/issues/97 
> Audio and Video Quality RAUR 
> #46 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/46 
> Clarification needed on Req 13a, 13b, 14a 
> #45 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/45 
> Section 2.8: REQ 10a and 15a: Seem UI-related, and not WebRTC-related. 
> #44 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/44 
> REQ 9a: Security Issues and Bias 
> #43 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/43 
> Section 2.6: REQ 8a only refers to real-time text, but User Need 8 seems 
> to be calling for something more 
> #42 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/42 
> REQ 2b: doesn’t make sense in view of the role of screen readers in 
> controlling the attached braille device. 
> #41 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/41 
> Section 2.2: User need 2 – It isn’t clear what the need is here. 
> #40 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/40 
> Section 2.1: Req 1a – consider dividing this into different cases and 
> elaborating each of them. 
> #39 opened on Jan 29 by RealJoshue108 
> https://github.com/w3c/apa/issues/39 
> References: 
> Minutes of the previous RQTF meeting are available at 
> https://www.w3.org/2020/07/29-rqtf-minutes.html 
> ________________________________ 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 
> Thank you for your compliance. 
> ________________________________ 
Janina Sajka 
Linux Foundation Fellow 
Executive Chair, Accessibility Workgroup:    http://a11y.org 
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) 
Co-Chair, Accessible Platform Architectures    http://www.w3.org/wai/apa
Received on Wednesday, 12 August 2020 07:37:26 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 12 August 2020 07:37:28 UTC