Meeting minutes
Naming progress, status of EO effort - 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) https://
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 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.