- From: John Foliot <john.foliot@deque.com>
- Date: Fri, 9 Aug 2019 11:00:19 -0500
- To: Charles LaPierre <charlesl@benetech.org>
- Cc: public-personalization-tf <public-personalization-tf@w3.org>
- Message-ID: <CAKdCpxx+eqHXGEnSoobJ=HS6eeHWMtzBbyAOsyeC2T_JuT5+Vg@mail.gmail.com>
Hi Charles, Lisa, colleagues, Sadly, I will be unable to join you on Monday, as I am training (again). Regarding Lisa's July 29 email: *If we are agreeing on the basic concept of using the bic numbers* FWIW, *I* think that is a good path forward, and support that approach. *1. Items that speed up the authoring process and make it more scalable can be moved to a separate module. This could included:* - *terms (or more terms) that replace very common concepts* - *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?)* - *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?)* I think a two-step approach like this makes more sense. While I agree and would like to see a more "common list of usable terms", any internationalization concern there needs to be explored in more detail. I'd suggest this be a topic for discussion at TPAC if you can find Richard Ishida. A formal or informal (hallway chat) discussion should be pursued. *2. Are we happy with the term data-symbol (I get the impression that we are) Could data-symbol merge this with data-action ?* I am happy with "data-symbol" going forward. Lisa, I am not sure what you mean by "merge". If the question is, could we merge action symbols in such a way that we wouldn't need to use 2 attributes, then maybe... I think that would also be a phase 2 discussion, because programatically identifying actions is a different "ask" than substituting symbols for text, although I do see an overlap there. Were you suggesting that the taxonomy terms for action also be mapped to Bliss BIC numbers? *3. we also have to check any patent issues involved with bliss.* Indeed, and while I think we all believe we're in the clear here, a more formal verification as part of our emergent Recommendation would add value and weight. JF On Fri, Aug 9, 2019 at 10:13 AM Charles LaPierre <charlesl@benetech.org> wrote: > Hello all, > Below is the agenda for Mondays meeting. > We would like to have a final decision on what will go into the > specification for Symbols initially and what will be put off until a future > revision . Lisa wrote an email on July 29th discussing this > <https://lists.w3.org/Archives/Public/public-personalization-tf/2019Jul/0021.html>. > If you all can review this email prior to our meeting Monday. For those > unable to attend Mondays meeting if you can email us your comments, > concerns or support that will be very helpful. > > We will also have two guests Peter and Ori to discuss Symbol testing. > > agenda+ Finalize Symbol for module 1 and what goes into an advance module > (for optimization/speedup etc.) review email from Lisa on July 29th > https://lists.w3.org/Archives/Public/public-personalization-tf/2019Jul/0021.html > agenda+ 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. > > Research Project Summary > > 3 options: > 1. No enhancements just text > 2. Machine generated (text to pictures) (IBM tool possibly others) > 3. Manually added symbols (Bliss / user chosen > > 2 groups of testers > Symbol users / non symbol users but have a cognitive disability > > > > ***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 > 4 pm CET > > IRC access > An IRC (Internet Relay Chat) channel will be available during the call. > (The server is irc.w3.org ,The port number is 6665 ) > > IRC made simple: > IRC is like our chat room. You can join us on IRC simply by clicking on > http://irc.w3.org/?channels=personalization > > The channel is #personalization > You can write any name as a nickname > > Now you can chat while we talk. > > *Resources and useful links* > > > - our home page > - Teleconferences of the Working Group and its task forces (also see meeting > minutes > <https://www.w3.org/WAI/ARIA/task-forces/personalization/minutes>); Face > to face meetings (also see face to face meeting pages > <https://www.w3.org/WAI/ARIA/task-forces/personalization/wiki/Meetings> > ); > > > > - mailing list archives > <http://lists.w3.org/Archives/Public/public-personalization-tf/> > - IRCC discussion on the #personalization IRC channel, used largely > for minute-taking; > - Personalization Semantics 1.0 > <https://www.w3.org/TR/personalization-semantics-1.0/> (Personalization > Semantics 1.0 Editors' Draft > <https://w3c.github.io/personalization-semantics/>). See also the Personalization > Semantics Task Force GitHub repository > <https://github.com/w3c/personalization-semantics/>. > - Wiki <https://www.w3.org/WAI/ARIA/task-forces/personalization/wiki/>; > - Web-Based Surveys (WBS) <https://www.w3.org/2002/09/wbs/101569/>; > - personalization-semantics source repository issue tracker > <https://github.com/w3c/personalization-semantics/issues>. > - http://diagramcenter.org/personalizedlearning.html > > > > WCAG SC > https://github.com/w3c/wcag21/issues/6 > > > https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/sc/21/purpose-of-controls.html > > > https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/sc/21/contextual-information.html > > > Demo > https://github.com/ayelet-seeman/coga.personalisation > https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html > > > * Some helpful Scribing and Participation Tips > http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet > > > - For more on W3C use of IRC see: > http://www.w3.org/Project/IRC/ > > > -- *John Foliot* | Principal Accessibility Strategist | W3C AC Representative Deque Systems - Accessibility for Good deque.com
Received on Friday, 9 August 2019 16:01:25 UTC