Re: APA Personalization Task Force Teleconference - Monday 28 Mar 2022 Agenda

Hi all,

Minutes can be found at https://www.w3.org/2022/03/28-personalization-minutes.html and are repeated below in plain text for convenience.

Best regards,


Matthew

                             – DRAFT –
               Personalization Task Force Teleconference

28 March 2022

   [2]IRC log.

      [2] https://www.w3.org/2022/03/28-personalization-irc


Attendees

   Present
          CharlesL, janina, Lionel_Wolberger, Matthew_Atkinson,
          mike_beganyi, Roy, sharon

   Regrets
          -

   Chair
          sharon

   Scribe
          Matthew_Atkinson

Contents

    1. [3] Naming progress, status of EO effort - https://
       github.com/w3c/wai-personalization-standards/issues/9
    2. [4]Follow-up on i18n issue #144 https://github.com/w3c/

       personalization-semantics/issues/144
    3. [5]TPAC
    4. [6]Implementations

Meeting minutes

   Naming progress, status of EO effort - [7]https://github.com/w3c/

  wai-personalization-standards/issues/9

      [7] https://github.com/w3c/wai-personalization-standards/issues/9


   sharon: Any further comments? Becky added hers.

   janina: Propose that we have an official name including the
   'WAI-' prefix.

   janina: I like Becky's suggestion.

   sharon: +1

   janina: It's a little smaller in scope than 'adapt' which is
   very general. We are one way to adapt, but not the only way.
   Plus in the US there is a well-known group working on
   transportation barriers called 'Adapt'.

   sharon: Adaptable Personalization Techniques

   janina: What else would fit as a T?

   Lionel_Wolberger: Could also be 'Technology'

   janina: +1

   janina: It wouldn't restrict us; has a meaning in WCAG space.

   Matthew_Atkinson: I think we should solicit Lisa's opinion.

   Matthew_Atkinson: Also +1 to something other than 'Techiques'
   for the T (thinking, in addition to the above, it would get
   confused with things like authoring practices).

   <Lionel_Wolberger> Adaptive Personalizeable Technologies

   janina: Propose 'Personalizable' as this, as EO pointed out, is
   the correct, adjective, form.

   Matthew_Atkinson: It seems rather generic. Thinking on
   'adaptable' vs 'adaptive'—is it a tautology?

   Matthew_Atkinson: Need to check discussion again for reasoning
   behind both.

   Lionel_Wolberger: I love 'adapt' becuase it says what it is.

   Lionel_Wolberger: Agree it says it's very broad and ACK the
   concern.
   … ACK is a known public advocacy group.
   … This standard is called ADAPT because it's powerful and we
   want to get it out there. The association with the other
   organization would likely only be made by insiders.

   CharlesL: +1 to Lionel_Wolberger

   CharlesL: Nobody will remember what APT stands for, but people
   will remember what ADAPT stands for. It means something and is
   easily recognizable. Not perfect but so much better than trying
   to come up with an acronym as Matthew_Atkinson mentioned.

   sharon: I understand both viewpoints; shall we consult on list?

   janina: I propose we should include 'WAI-' regardless. [ sharon
   and Lionel_Wolberger agree ]

   <Lionel_Wolberger> +1 to WAI-ADAPT

   +1

   CharlesL: +1

   janina: We should canvas for WAI-ADAPT and WAI-APT. We should
   run this up to management. Not ready for CfC until we have a
   decision from our TF. We should consult staff contacts, EO and
   WAI.

   janina: Meanwhile, yes please canvas the group.

   Lionel_Wolberger: This is a call for consensus (CfC)?

   janina: Yes, within the TF.

   Lionel_Wolberger: Is the question about prefering one or both.

   janina: The question, per W3C process, is can you live with the
   alternative?

   janina: (I can)

   <Lionel_Wolberger> DRAFTING Dear Personalization Task Force
   Member,

   janina: We want people to weigh in between the two, but say if
   you can live with the alternative—and if not, why not?

   <Lionel_Wolberger> This is a Call for consensus regarding our
   Task Force stand regarding the name for our standard.

   sharon: We want to make sure we hear from Lisa. [ scribe note:
   ensuring John is included was already discussed; I didn't catch
   up ]

   CharlesL: Should we also get COGA's approval? This started with
   them.

   <Lionel_Wolberger> Please reply with you position: (A)
   WAI-ADAPT, (B) WAI-APT, (C) I can live with either one

   janina: We'll consider this. Some COGA members are active APA
   members too, and can weigh in.

   <Lionel_Wolberger> Note that this name will be the prefix for
   the modules.

   <Lionel_Wolberger> WAI-ADAPT: Content Module, WAI-ADAPT: Help
   Module, WAI-ADAPT Tools Module

   <Lionel_Wolberger> WAI-APT: Content Module, WAI-APT: Help
   Module, WAI-APT Tools Module

   janina: We need to make sure this is all clear, and tested
   (with the group).

   <Lionel_Wolberger> And the name of the task force will also
   follow on this decision: Either W3C WAI-ADAPT Task Force or W3C
   WAI-APT Task Force

   <Lionel_Wolberger> Please reply with you position: (A)
   WAI-ADAPT, (B) WAI-APT and also reply with your position
   regarding this decision (X) I only consent to my choice or (Y)
   I can live with either one

   Matthew_Atkinson: The question needs to be one or the other,
   plus whether you can live with the other if it's chosen, and
   why.

   Matthew_Atkinson: Think we should spell them out (might need
   regexes...)

   <Lionel_Wolberger> Please reply with your choice of A or B, (A)
   WAI-ADAPT, (B) WAI-APT and also reply with your position
   regarding this decision X or Y (X) I only consent to my choice
   or (Y) I can live with either one

   janina: We can say "such as" re the expansions.

   CharlesL: Wording needs to ask for reasons.

   <Lionel_Wolberger> Please reply with your choice of A or B, (A)
   WAI-ADAPT, (B) WAI-APT. If your preference is not the majority
   decision, can you live with the other option? Yes/No

   janina: As CharlesL says, there should be a 'because' in there.

   <Lionel_Wolberger> Please reply with your choice of A or B, (A)
   WAI-ADAPT, (B) WAI-APT. If your preference is not the majority
   decision, can you live with the other option? Yes/No. If you
   answer "No" please explain.

   janina: +1

   CharlesL: We need to give possible expansion(s).

   janina: +1 but for ADAPT there doesn't need to be one.

   CharlesL: I thought the T stood for 'transformable'

   janina: We need a noun.

   CharlesL: When we send this out, should it go to the public or
   private list? [scribe note: 'private' probably refers to admin;
   public but members only can post]

   janina: Lists are always world-readable. Some are only
   writeable by members.

   <Lionel_Wolberger> ================================

   <Lionel_Wolberger> This is a Call for consensus regarding our
   Task Force stand regarding the name for our standard.

   <Lionel_Wolberger> This is a Call for consensus regarding our
   Task Force stand regarding the name for our standard.

   <Lionel_Wolberger> Two names have made it to this final
   decision. Below please find each name, and how it will read as
   a prefix:module.

   <Lionel_Wolberger> WAI-ADAPT. WAI-ADAPT: Content Module,
   WAI-ADAPT: Help Module, WAI-ADAPT Tools Module

   <Lionel_Wolberger> WAI-APT. WAI-APT: Content Module, WAI-APT:
   Help Module, WAI-APT Tools Module APT possible expansion,
   "Adaptable Personalizeable Technologies"

   <Lionel_Wolberger> Please reply with your choice of A or B, (A)
   WAI-ADAPT, (B) WAI-APT. If your preference is not the majority
   decision, can you live with the other option? Yes/No. If you
   answer "No" please explain.

   <Lionel_Wolberger> ================

   Lionel_Wolberger: any objections to this?

   janina: We should say that we're not expanding ADAPT.

   <Lionel_Wolberger> (No expansion necessary for ADAPT -- it is
   just "ADAPT")

   <Lionel_Wolberger> Still digressing, look at this book cover
   (saw it today on a shelf) [8]https://www.amazon.com/

   Hummus-Route-Journey-Between-Cities-ebook/dp/B08GV45HV6/
   ref=sr_1_1_sspa?crid=124OW3D21FCO3&keywords=hummus+book&qid=164
   8478539&sprefix=hummus+book%2Caps%2C190&sr=8-1-spons&psc=1&spLa
   =ZW5jcnlwdGVkUXVhbGlmaWVyPUEySjlCNFdUOEhXWVlVJmVuY3J5cHRlZElkPU
   EwODg3OTE2Mlg5SlNTUDNNWkE5MCZlbmNyeXB0ZWRBZElkPUEwOTI2MDI3Mk03M
   0tSTVlWQTNIMyZ3aWRnZXR[CUT]

      [8] https://www.amazon.com/Hummus-Route-Journey-Between-Cities-ebook/dp/B08GV45HV6/ref=sr_1_1_sspa?crid=124OW3D21FCO3&keywords=hummus+book&qid=1648478539&sprefix=hummus+book,aps,190&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEySjlCNFdUOEhXWVlVJmVuY3J5cHRlZElkPUEwODg3OTE2Mlg5SlNTUDNNWkE5MCZlbmNyeXB0ZWRBZElkPUEwOTI2MDI3Mk03M0tSTVlWQTNIMyZ3aWRnZXR[CUT]

   Matthew_Atkinson: Something to think about: how would we intro
   this at conferences, and maintain the Personalization
   connection? Is ADAPT 'ADAptive Personalization Technologies'
   when expanded?

   janina: We should point this out in the CfC.

   Matthew_Atkinson: Not suggesting we use the mixed case when
   writing; just thinking about how to introduce the
   Personalization connection.

   janina: This is for the first slide in conference talks. We can
   say the expansion works for either one.

   <Lionel_Wolberger> ===============================

   <Lionel_Wolberger> Please note that these are not both
   abbreviations that need to be expanded. No expansion necessary
   for ADAPT -- it is just "ADAPT".

   <Lionel_Wolberger> We propose this candidate possible expansion
   of APT: "Adaptable Personalizeable Technologies". Note that
   this expansion can also be used with "ADAPT": 'ADAptable
   Personalizeable Technologies.'

   <Lionel_Wolberger> ==============================

   Matthew_Atkinson: Have we decided what will be in the <h1> in
   the spec?

   janina: We haven't, and we aren't now. We can do another CfC
   later, and run by EO.

   <Lionel_Wolberger> ===========================

   <Lionel_Wolberger> We propose this potential possible expansion
   for either of the above: "Adaptable Personalizeable
   Technologies". This expansion can be applied to "APT" or
   "ADAPT": 'ADAptable Personalizeable Technologies.'

   <Lionel_Wolberger> ===================

   <Lionel_Wolberger> We propose this potential possible expansion
   for either of the above: "Adaptable Personalizeable
   Technologies".

   <Lionel_Wolberger> =======================

  Follow-up on i18n issue #144 [9]https://github.com/w3c/

  personalization-semantics/issues/144

      [9] https://github.com/w3c/personalization-semantics/issues/144


   sharon: Any updates?

   janina: Roy any updates?

   Roy: None yet.

   Roy: Heard from i18n's team contact that this issue is atop
   their queue.

   Roy: Suggest we wait one more week.

   janina: When do they meet?

   Roy: Will confirm.

   janina: The group is really good when they get together; we
   (APA) have a good relationship with them.

   janina: OK to wait a week? Need to finalize name (and
   expansion) before CR (this is something Shawn finds important
   and I agree).

  TPAC

   CharlesL: I am planning to attend, barring further outbreaks
   etc.

  Implementations

   sharon: Work ongoing to discuss with potential implementors.


    Minutes manually created (not a transcript), formatted by
    [10]scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

     [10] https://w3c.github.io/scribe2/scribedoc.html


-- 
Matthew Tylee Atkinson (he/him)
--
Senior Accessibility Engineer
TPG Interactive
https://www.tpgi.com

A Vispero Company
https://www.vispero.com

--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

On 25/03/2022, 19:54, "Sharon D Snider" <snidersd@us.ibm.com> wrote:

    CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.

    Hi all,

    Please review the agenda for Monday's Personalization TF call and let us know if there are any other topics that need to be added:

    Chair: Sharon

    agenda+  Naming progress, status of EO effort - https://github.com/w3c/wai-personalization-standards/issues/9

    agenda+ Follow-up on i18n issue #144 https://github.com/w3c/personalization-semantics/issues/144

    agenda+ Follow-up with potential implementers 
    agenda+ Issue 202 regarding Visible Indicators on 2.2 - https://github.com/w3c/personalization-semantics/issues/202

    agenda+ Planning future COGA meetings on Our Other Two Modules

    The  teleconference information is at: call info - personalization <https://www.w3.org/2017/08/telecon-info_personalization>

    Time:
    · 10 am Eastern time
    ·  5 pm IS
    ·  3 pm UK time

    IRC access

    An IRC (Internet Relay Chat) channel will be available during the call at: https://irc.w3.org/?channels=personalization <http://irc.w3.org/?channels=personalization>

    The server is  irc.w3.org <https://irc.w3.org/> 
    The port number is 6665
    The channel is #personalization 

    You can write any name as a nickname

    Resources and useful links
    ·  Wiki <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>; - this page has links to all our work
    ·  mailing list archives <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj26QkH8W3T3qGX1JHM74W43Wg2w2p76z4W3T4FNJ1Lm8YzW3ZWTXk45W2z0W3SYFSb3K8R4LW41PFYp4ttcHyw43Tw4j48K2&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>
    ·  Personalization Semantics 1.0 <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrl308ysDW49RkMP3zd6m0W3zhs7S41p0TNW3_R5CW3SYMZQf1Q1_Lt04&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce> (Personalization Semantics 1.0 Editors' Draft <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mbpRl3P28X2W4hCPvp43np2_W49RkMP3zd6m0W3zhs7S41p0TNW3_R5CW3SYMZS0&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>). See also the Personalization Semantics Task Force GitHub repository <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RHW3K8R4L41PFYpW4ttcHy43Tw4hW3K6K7d4fJd-31V3&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>.
    ·  our home page
    ·  Web-Based Surveys (WBS) <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49LdqK1N4hm1W1N81nQ3Cfv3hw1N4K5047V2&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>;
    ·  personalization-semantics source repository issue tracker <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RHW3K8R4L41PFYpW4ttcHy43Tw4hW3K6K7d4fJd-3F1LyzF7W1vp1&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>. 
    ·  Scribing and Participation Tips: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet 
    ·  Demo: https://github.com/ayelet-seeman/coga.personalisation and  https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.htm <https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html>

    Regards, 
    Sharon Snider 
    IBM Design ► IBM Accessibility Team
    (512)965-3957
    www.ibm.com/able <https://www.ibm.com/able> and w3.ibm.com/able <https://w3.ibm.com/able>

Received on Monday, 28 March 2022 15:03:13 UTC