Re: Personalization brand discussion - Friday 18 February 8:30amET

Very excited to have so many knowledgeable and committed people lending
their a hand on this important naming task.

I am available most days at +7 from EDT, looking forward to a meeting time
proposal.

- Lionel


Lionel Wolberger
COO, UserWay Inc.
lionel@userway.org
UserWay.org <http://userway.org/>
<https://userway.org>[image: text]


On Fri, Feb 18, 2022 at 6:30 PM Matthew Atkinson <matkinson@tpgi.com> wrote:

> Hello again all,
>
> Fortunately I was able to make some of the meeting, along with Janina, and
> it was great; your thoughtful feedback is much appreciated. This is
> intended to bring the Personalization TF up-to-date with what's been
> discussed so far, and how we can coordinate and discuss this further.
>
> There is a GitHub thread that everyone is encouraged to join and
> contribute to:
> https://github.com/w3c/wai-personalization-standards/issues/7
>
> Some background for EO from Personalization:
> * GitHub wiki page collating suggestions:
> https://github.com/w3c/personalization-semantics/wiki/Personalization-module-renaming-discussion
> * Minutes from the 31st of January:
> https://www.w3.org/2022/01/31-personalization-minutes.html#t02
>
> From EO, here are two sections in minutes for EO's recent calls that cover
> this discussion:
> * Last week's: https://www.w3.org/2022/02/11-eo-minutes#t03
> * Today's: https://www.w3.org/2022/02/18-eo-minutes#item01
>
> We'll put Lionel and Sharon (Personalization's chairs) in touch with EO's,
> so that another joint meeting can be organised. We need as many people from
> Personalization to attend as possible, very preferably everyone!
>
> Some highlights from today's EO call (for me—I'm trying to be
> representative, but this will almost certainly fail to be so, and all of
> the input was helpful!)...
>
> * Most of what we're doing affects content, and that's really
> important—though as it's such a broad area, we may want to qualify exactly
> what we're doing with the content.
> * Bringing it back to the user and their needs is paramount.
> * An acknowledgement that ARIA is a great acronym because everyone knows
> about it, but perhaps not many people understand the implications of its
> expansion (hence it's over-used sometimes).
> * A concise "phrase" (though just two words would be fine, if they fit) is
> possibly better than an acronym, though if that phrase happened to collapse
> to a convenient acronym, that could only help.
> * ...but we may not even want to ACK that implied acronym in the name of
> the spec (i.e we'd just use the full, albeit concise, name). Our intent
> would be just to allow people to start naturally referring to the spec in
> the logical shorter way, which will happen naturally if it collapses well,
> and it avoids too many acronyms on our part.
>
> It seems that something around "adaptation" was a strong focus, like
> content, and something to indicate that the adaptation would be for a
> particular user, such as "Personalizable" or similar would be required.
>
> Best regards,
>
>
> Matthew
> --
> Matthew Tylee Atkinson
> --
> 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 18/02/2022, 13:20, "Matthew Atkinson" <matkinson@tpgi.com> wrote:
>
>     CAUTION: This email originated outside Vispero. Do not click links,
> open attachments or forward unless you recognize the sender.
>
>
>     Hello Shawn, EO, all,
>
>     This is really exciting stuff, and I hope to be able to attend future
> similar meetings (and will check out the GitHub thread). However regrets
> for likely most, if not all, of this call due to some plumbing work that is
> going on (nothing bad, but somewhat disruptive). I'll try to listen in to
> some if I can, and hopefully we may have others in future too. Meanwhile,
> enjoy today's!
>
>     best regards,
>
>
>     Matthew
>     --
>     Matthew Tylee Atkinson
>     --
>     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 17/02/2022, 20:17, "Shawn Henry" <shawn@w3.org> wrote:
>
>         CAUTION: This email originated outside Vispero. Do not click
> links, open attachments or forward unless you recognize the sender.
>
>
>         Hi all,
>
>         It's great to see ideas already brewing for branding
> formerly-known-as Personalization. Here's a GitHub issue so ideas are in
> one place and we can all add ideas asynchronously:
>
> https://github.com/w3c/wai-personalization-standards/issues/7
>
>         You are invited to the next discussion with EOWG and some
> Personalization folks:
>                 Friday 18 February at 8:30 am Eastern
>         Call-in info is at this page, with W3C login:
>                 https://www.w3.org/2017/08/01-eowg-info.html
>         IRC is #eo
>
>         Let the creative juices flow. :-)
>
>         Best,
>         ~Shawn
>         --
>         <http://www.w3.org/People/Shawn/>
>
>
>
>