- From: John Foliot <john@foliot.ca>
- Date: Tue, 12 Oct 2021 18:21:01 -0400
- To: Matthew Atkinson <matkinson@tpgi.com>
- Cc: "public-personalization-tf@w3.org" <public-personalization-tf@w3.org>
- Message-ID: <CAFmg2sV-9itBKTo-Yzs5g8Gw7sbm96==H7u3LyT+D3whjKiwkg@mail.gmail.com>
Hi Matthew and Lisa, I just finished reviewing the slides, and overall very well done! I have one minor bit of feedback, and it's that I think you've sorta hidden the actual "Thing" we are doing until slide 15, and specifically: - *We're aiming for the sweet spot, where a small addition of machine-readable semantics supports a wide range of helpful adaptations.* Might I suggest that we move that critical bit of info closer to the start? Perhaps slide 2 with, or part of, the bullet: "We've developed a specification that will help content authors do this." Revision: "We've developed a specification that will help content authors do this, *where a small addition of machine-readable semantic metadata supports a wide range of helpful adaptations.*" (yes, leave it bolded, and note the addition of the term metadata - a key concept I don't see anywhere else in the slide deck...) ...taking a cue from the 90's pop band Roxette, who famously released a greatest hits record titled "*Don't Bore Us, Get to the Chorus!*" - in other words, let's tell attendees right up front what we're doing. My $0.02 Canadian (which is kind of difficult, as Canada no longer has 1-cent coins...) JF On Tue, Oct 12, 2021 at 5:08 PM Matthew Atkinson <matkinson@tpgi.com> wrote: > Hello TF, > > Lisa and I took a couple of hours this morning to really improve the > slides, and think they're in much better shape now. I also have extensive > notes (currently in some of the slides as HTML comments) about emphasis I > need to put on what COGA will need to know, and what we'll need to know > from them, so I will be sure to address that as we go through. I still may > cut out some slides—at the very least some will be moved to "appendix" > sort-of material—but I don't think any more need to be added. (There are > some placeholders for code samples I just couldn't get to this evening; > will add those very soon.) > > PR URL: https://github.com/w3c/personalization-semantics/pull/199 > Preview URL: > https://raw.githack.com/w3c/personalization-semantics/tpac-2021-talk/talks/2021/tpac/index.html > > We've made general changes to keep the focus on our core use-cases, > pre-empt questions about i18n issues, clarify how we're aiming to solve > problems and generally ensure that proper terminology is being used. > > Feedback welcome though hopefully we're pretty close now. > > 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. > > -- *John Foliot* | Senior Industry Specialist, Digital Accessibility | W3C Accessibility Standards Contributor | "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"
Received on Tuesday, 12 October 2021 22:21:32 UTC