Minutes: APA Personalization Task Force Teleconference - Monday August 12, 2019

Minutes from the Personalization Task Force teleconference of 12 August are
provided below as text. They're also available as hypertext at:

https://www.w3.org/2019/08/12-personalization-minutes.html

   W3C

                                                                                                            - DRAFT -

                                                                                            Personalization Task Force Teleconference

12 Aug 2019

Attendees

   Present
          JF, Becky, Roy, sharon, janina, CharlesL, stevelee, LisaSeemanKest, MichaelC, Becka11y, Ori

   Regrets
          JohnF

   Chair
          CharlesL

   Scribe
          janina

Contents

     * Topics
         1. Close on the research project (Peter and Ori joining) User Testing after AAAT (last week in Aug) want them to discuss what the plan is.
     * Summary of Action Items
     * Summary of Resolutions
     ___________________________________________________________________________________________________________________________________________________________________________________________________________________

   <scribe> scribe: janina

   <LisaSeemanKest> We seem to agree on using bic number as the standard reference mechanism for each concept common in symbols .

   <LisaSeemanKest> for example

   <LisaSeemanKest> data-symbol ="10230"

   cl: Summarizing the proposal along the lines Lisa just pasted in

   <LisaSeemanKest> :)

   cl: We're still open to using word names in some cases

   <LisaSeemanKest> terms (or more terms) that replace very common concepts

   <LisaSeemanKest> a way to associate new symbol(s) with the reference mechanism in a mapping file (phase 2 for scalability for authors if the content provider is using their own symbols?)

   <LisaSeemanKest> a way to reference a mapping file to use in the content (phase 2 for scalability for authors if the content provider is using their own symbols?)

   ls: terms for common concepts still an open possibility
   ... By separating the two we are able to move forward with testing and other development activity
   ... Notes that we would still need the ID, because we can't have terms for everything
   ... Notes JF's support for this approach

   <LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2019Aug/0011.html

   Becky, try your audio again ...

   [discussion of when and how to engage I18N WG]

   ls: Mentioning her upcoming conference participation where there will be lots of I18N symbol discussion

   <LisaSeemanKest> http://aaate2019.eu/

   <CharlesL> Janina: is there an ISO designation for these symbols as well?

   <CharlesL> 
 is this also true for IEC?

   ls: Don't know, what will ask

   <LisaSeemanKest> data-symbol="10294 68321"

   Lisa: : Suggesting symbol=X Y Z -- should be allowable

   js: How does the UA choose?

   ls: Puts in all of them

   <LisaSeemanKest> more then one value is allowed

   [discussion on how this might work]

   <LisaSeemanKest> so that a picture of a woman running can be replaced by two symbols - woman and running

   <LisaSeemanKest> or a symbol to be specfic for both

   js: Still worried on who combines?

   bg: Our plugin

   ls: Notes this can be culturally defined

   cl: Notes this is from our standardized Bliss to a different symbol set, so it's in our tables

   <LisaSeemanKest> allows mappin a few symbols to a single one

   ori: Asks about many to one

   cl: Allows other symbol lang to define them

   <CharlesL> "55 22" this maps to "88234" for a new combined symbol

   bg: Are we space delimited, something else?
   ... Notes a concern mapping these to common names

   cl: Yes, also an i18n concern with that reason

   bg: wanted to note this now

   DRAFT RESOLUTION: Personalization will move forward with Bliss ID

   <LisaSeemanKest> resultion - to go with data- and bci number - such as data-symbol ="10230 "

   <LisaSeemanKest> allow space sperated more then one value

   <LisaSeemanKest> and move off use of commone terms , and mapping files and linking in page headers to extra module to be discussed

   <LisaSeemanKest> silace seen as concent

   <LisaSeemanKest> silence seen as concent

   <LisaSeemanKest> +1

   <CharlesL> +1

Close on the research project (Peter and Ori joining) User Testing after AAAT (last week in Aug) want them to discuss what the plan is.

   [discussion on rescheduling until Peter might be available]

   ls: Hope was to cover user testing
   ... Next week?

   <LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2019Jul/0016.html

   <LisaSeemanKest> https://docs.google.com/document/d/1GW5joienKWD6rsQstZSAsJpcBE0jj3p4Gl8o7hhoOA4/edit#

   ls: Please do not edit the above, post on list instead
   ... Proposes to request a methodology doc we can review

   <CharlesL> -The page without symbols.

   <CharlesL> -The page with automatically inserted symbols such as by machine learning.

   <CharlesL> -The page with bliss symbols based on the codes inserted manually.

   <CharlesL> -The page with symbols that the use prefers based on the codes inserted manually and a mapping file

   ls: Asks whether handbook is on line?
   ... Is it confidential?

   <CharlesL> https://drive.google.com/file/d/1TWVAISi3v1tG19gpiQJISb5uXDFpYVoC/view?ts=5d384721

   cl: Not world readable

   ls: Will ask whether our group can review

   <CharlesL> data-symbol

   ls: We'll now be rid of AUI-
   ... Will be good to have this working by AAATT meeting

   Yes,

   Believe so, anyway!

   cl: Testing methodology deferred to the 19th

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     ___________________________________________________________________________________________________________________________________________________________________________________________________________________

Present: JF Becky Roy sharon janina CharlesL stevelee LisaSeemanKest MichaelC Becka11y Ori
Regrets: JohnF
Found Scribe: janina
Found Date: 12 Aug 2019

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Received on Monday, 12 August 2019 16:24:09 UTC